Atomic Systems

I am getting these on a variety of routes in activities where no-one else is getting them. They normally cause the activity not to start and I have ruled our the usual problems of badly located loose consists or conflicting AI traffic. The reference number given is always in the form 2000xx (eg 200013) which in nowhere in the activity details.

I have come to the conclusion that it is something general with my setup which is causing this. Can anyone assist with the following:

1. Details of any unusual causes for RigidBody errors you have found.

2. Has anyone found any temporary files that MSTS generates which may include more details and possibly the 2000xx number?

Thanks,
David

Hi David

I have only recently got this problem as detailed in the Link below :-

http://forums.uktrainsim.com/viewtopic. ... 8&t=104923

Up till this I never had the problem and I never did get to the bottom of it and/or the Solution.

Both the Activity Author and Bob (latimer) did not have the problem with the Activity which checked out OK in AE/RR & AA

As a matter of interest I got the problem in my main MSTS set up using Trainstore (easy mode) and my Mini Route Set up using the Mini Loader and not using the Mini Loader.

I also checked in AE with this particular Activity for the "usual" cause of a loose Consist too close to the end of a siding but all were well clear.

Regards

Mike

Mike, you do seem to be having the same problem as me. It must be something different from the normal. Something about our configuration of MSTS, but what?

David

I am getting the same problem at the start-up of the "Milky Bath" activity. The number given is "200233" which is not a Service or Loose Consist.

The interesting thing is that the activity starts OK under OpenRails.

David

Are you guys using Tsection 41 by any chance?

jimmyladd wrote:Are you guys using Tsection 41 by any chance?

I was, but have just changed to 38 and the problem is the same.

David

Bang goes that theory then!

Rigidbody error can also be caused by uncompressed shape files but these are usually followed by a Failed to Load error and a tell Bill.

ianmacmillan wrote:Rigidbody error can also be caused by uncompressed shape files but these are usually followed by a Failed to Load error and a tell Bill.

Ian, no failed load error etc. I am sure it is something other than a stock positioning conflict but what?

David

Open the activity in the Activity Editor.
View button on the menu bar.
Deselect everything apart from Service info.
Tools button on the menu bar, select Verify starting state.
The player, AI and loose consists will be displayed and any error messages pertaining to the same.
The most common cause of `Failed to initialise car <number> ridgidbody in the game is a loose consist in collision. Another reason is the service is too long for the path it is on, ie. in collision, impinging on points or other paths.
The former requires the consist to be dragged or repositioned until all the consist is fully displayed. The later will need the start part of the path extending to include the desired (consist) service.
Search the activity map for the offending UD number, player and AI are displayed in green, loose consists in purple.

Kindest regards
Ray

rlmathers wrote:Open the activity in the Activity Editor.
View button on the menu bar.
Deselect everything apart from Service info.
Tools button on the menu bar, select Verify starting state.
The player, AI and loose consists will be displayed and any error messages pertaining to the same.
The most common cause of `Failed to initialise car <number> ridgidbody in the game is a loose consist in collision. Another reason is the service is too long for the path it is on, ie. in collision, impinging on points or other paths.
The former requires the consist to be dragged or repositioned until all the consist is fully displayed. The later will need the start part of the path extending to include the desired (consist) service.
Search the activity map for the offending UD number, player and AI are displayed in green, loose consists in purple.

Kindest regards
Ray

Ray, thanks but you did mot read the earlier part of this discussion in full.

I am talking about RigidBody errors where the "offending UD number" is not a Service or Loose Consist ID number.

David

Now I am far from knowledgable on this subject, but I recall posts on this subject before in particular responses by Laurie (LAD491) in which he echoed Ray's comments.

I believe this can also be caused by problems with AI locos - possibly related to start position or time? It can also be caused when the orginal stock is substituted by alternatives that are typically longer, and hence don't fit the siding or similar.

Whilst this may be part repetitive hopefully will allow future searches to discover the solution proposed by Ray.

Alec

PS Apologies if this is not directly helpful!

rufuskins wrote:Now I am far from knowledgable on this subject, but I recall posts on this subject before in particular responses by Laurie (LAD491) in which he echoed Ray's comments.

I believe this can also be caused by problems with AI locos - possibly related to start position or time? It can also be caused when the orginal stock is substituted by alternatives that are typically longer, and hence don't fit the siding or similar.

Whilst this may be part repetitive hopefully will allow future searches to discover the solution proposed by Ray.

Alec

PS Apologies if this is not directly helpful!

Thanks for your suggestions Alex.

In all of these situations, the reference ID given in the RigidBody error message refers to the ID number of a Service or Loose Consist, allowing it to be found and corrected. In the problems I am having it does not. It is always in the form of 200xxx and I am yet to find a Service or Loose Consist which has this format of ID.

Try Route Riter\Activities/Stock\Check all Activies\Unused Services Consists.
Right click on the files and choose Move.

You might have a Service or Activity file that is trying to place an item on a route you don't have installed.

Another thought is that you have an activity for an earlier or later version of a route which is looking for a location that does not exist in the route you have.

3rd idea.
Remove all but one of the .act files and see if the problem still occures.
If not, Put them back a few at a time until you find the problem file.

dforrest wrote:
Thanks for your suggestions Alex.

In all of these situations, the reference ID given in the RigidBody error message refers to the ID number of a Service or Loose Consist, allowing it to be found and corrected. In the problems I am having it does not. It is always in the form of 200xxx and I am yet to find a Service or Loose Consist which has this format of ID.

Double check that if it is a loose consist it is not too close to buffers or points!

Alec