Anyone know why....

[photons66]

...this is happening please?




I have only just noticed it this morning whilst testing the route and it didn't exist in that place previously. Trains run fine over it and the route doesn't crash RS.

Thanks in advance.

[777fred]

It happens in mine when I have deleted abit of track before removing the train.

[photons66]

Thanks for the explanation, Fred.

Anyone with a potential remedy or solution most appreciated.

[Ryosuke]

just remove the engine?

[photons66]

The 55 in the picture is not the cause of the blip. It was meant as testing the blip to see whether or not driving over it causes a derailment or a CTD.

I have no trains in the immediate vicinity of the blip so I'm unsure as to why its happening.

[bigvern]

I have had this occur quite frequently during my route building exercises. Sometimes the section of track will draw so far then vanish, other times it will not appear in its entirety. Seems to happen where you are working with multiple track rather than single track. The only workround I have found is to delete the section which has gone invisible then either try and place from the other end or maybe lay a short section elsewhere at the correct height/radius and then use the "join" function to connect it to the offending node. If you try and extend from the original node it just goes invisible again.

Guess it ought to be logged as a bug at RSDL but I never got round to it. I don't see it as a memory leak or anything as I have had the problem occur right after starting the computer and loading RS.

We all know that RS code has no relation to MSTS but it is reminiscent of the old MSTS bug where sections of track could become invisible and a track database rebuild was required to restore them.

[photons66]

I will give your suggestion a try. Thanks Vern.