(Another) YARN road piece problem

[nicky9499]

Earlier today I was going about my route creating sessions when I noticed some YARN intersection road pieces were missing. Went back out to check CMP; nope, no errors or warning on these assets. Neither these assets nor the route have been recently modified. Went back into the route for a look, it appears they have just *poof* vanished, leaving behind a bloody mess of invisible splines. The worst part is that it's not a consistent problem either; in some areas these intersections are present, in other parts they're missing. So I had to spend the better part of an hour going through the whole route to check for missing intersections, delete the nonsense splines and manually replace each one, which is bloody infuriating to say the least.

How do I stop this from happening again? It's not the first time YARN/YARNish stuff have screwed up and at this point I am seriously considering ditching the system altogether, however good/comprehensive it may be.

Regards,
Nicholas

 

[Dermmy]

Yarn or Yarnish? You can't mix them up, splines must be the same system as the intersections they are connected to. Use Yarn pre TS09, use Yarnish TS09 and up. I suspect from the slight texture differences between your splines and objects that you have mixed the systems.

Also, is everything on the same layer?

I know it doesn't help to hear it, but I have used the Yarn and Yarnish systems since they came out and find them pretty much bomb proof, the only issue I have found (if it is one) is that if you update a route from Yarn to Yarnish using 'replace assets' to update the splines, the connections to intersections are screwed untill you have manually replaced the intersections. I suspect your problem is in the implementation rather than in the system itself....

 

[nicky9499]

Good day Andy,

Thanks for the comeback. First to answer your questions; the road spline is YARN, the intersection is a cloned version of a YARN one. So yes, both are YARN and everything is on the Route layer. In order to avoid layer problems the Session layer is locked and hidden all the time. Session-specific trains and objects are added to the Route layer then moved "one-way only" to the Session layer using the Properties box. Why cloned, you ask? As documented here, an update to some YARN assets including the ones causing this newest issue have previously caused some even bigger issues in the past. In order to avoid these updates I have cloned the last known good version and used that.

There was no Replace Assets operation anytime recently, the route has been the way it is for months now. So recent modifications can be ruled out. It appears they have just screwed themselves up.

 

[Dermmy]

A couple of points:

Something in your clone is causing the invisible road attached to the intersections to come 'unstuck' from the intrersection object. I have never seen this in either Yarn or Yarnish systems as supplied. When you 'cloned' did you use the 'clone' function in Trainz? I have known that system to cause issues. I always make a copy of an object by dragging the objects folder from the Edit in Explorer window to the desktop, make the changes required out-of-game, then install the new object manually.

Off Topic, but just a comment on your other thread referenced above where you note that if you delete an updated version of an asset on a route the route does not revert to the earlier version. This is always the case on routes and has nothing to do with these specific road systems. It's all to do with the configs: If you update say a rolling stock dependency and don't like the update for some reason you can delete the update and the older version will re-appear. This is because updating the rolling stock dependency did not update the config of the parent asset. The parent asset config still specifies an earlier version so it will cheerfully use whatever version is available equal to or higher than the revision specified in the config. A route config is different. The route config is re-written EVERY save. So if you replace a :2 asset with a :3 asset and save the roue, the :3 asset gets written into the config and the the route will ever after ONLY use the :3 version (or higher) but will NOT use an earlier revision. To revert to an earlier version in a route you must delete every instance of an asset on the route in Surveyor, save, delete the higher version in CM, re-load the route and manually place wharever version is now available. You have to be SO careful on a route to make sure that you like an update and DON'T save the route till you are certain the update is OK...

 

[nicky9499]

When you 'cloned' did you use the 'clone' function in Trainz? I have known that system to cause issues. I always make a copy of an object by dragging the objects folder from the Edit in Explorer window to the desktop, make the changes required out-of-game, then install the new object manually.

Yes, I used the Clone function.
Do you mean opening original YARN asset, copying out everything, editing config including specifying new kuid, then bringing it back in using Import Content function?

if you delete an updated version of an asset on a route the route does not revert to the earlier version.

Yes, I am aware of this.

To revert to an earlier version in a route you must delete every instance of an asset on the route in Surveyor, save, delete the higher version in CM, re-load the route and manually place whatever version is now available.

Yes, this is what I did, except I replaced it with the clones.

 

[Dermmy]

Do you mean opening original YARN asset, copying out everything, editing config including specifying new kuid, then bringing it back in using Import Content function?

It's easier than that. Highlight the asset in CM. Ctrl+shift+E will open a window in Explorer showing the asset folder. Drag the whole asset folder to the desktop. Now you can make any edits required (including a new kuid), then just drag the desktop folder back into any open CM window....

Don't forget to 'commit' (or delete!) the original asset!

 

[p-dehnert]

Better 'revert' the original (Ctrl+R) instead of committing.

Peter