Hi All
This issue is currently being looked into.
However some further information regarding this as well. In part this is due to cumulative updates to the spline behaviour over time. It wasn't actually related to junctions on curves (I'm not sure where that came from, but it's not the intention). But it's part of bug fixing and updates to spline handling so that they work better (in the absolute sense).
So as to not break routes entirely, we do limit when these updates are used depending on the version the spline was edited/placed in, and/or the version of the spline asset.
So updating to a newer spline asset, or editing the spline (ie replacement, or moving, or deleting and placing again) will result in the updated handling being used.
I have still entered a report as the changes are pretty substantial and are causing issues with routes that are being updated.
That said, this is an example of having the choice of, either never fix/update an issue (because it might break/change something), or make the change/update (which may be needed to implement future updates/changes as well). In this case we have made it so that the update only comes into affect if you perform specific actions, but on an existing route it remains unchanged.
However, we are still looking into this, so as to ascertain what steps can be taken to avoid this.
It's also worth noting that it's been several months since TRS19 SP2 entered beta, and over a month since it was released. And no reports have been received for this, as far as I can find, until the last few days. In all honesty, with situations like this, it's only if something actually gets reported (especially during beta) that we'll know there's an actual issue...
To further reply.
-Please put back Attachment culling (a.attachmentpointname:Cull) via lm files
If you haven't already, please send a report to
https://n3vgames.typeform.com/to/xRdryu so that our QA team can investigate this. Please supply an example asset that does show that this is not functioning correctly.
-A more neutral TRS2019 main menu (or choice)
Currently the route menu is fixed, we may be able to provide the ability to change it in future, but there's no specific plans at this time. TBH I think most will agree that there's more important things to focus on here. The main reason it was changed was to make use of a number of new PBR assets that we have provided in the update for TRS19.
-A route menu that remembers the choice you made before (like it was in SP1)
I tested this here, and it is definitely remembering my selection. It may have reset with the SP2 update, but changing to the desired consist in the 'my content' menu is definitely being remembered here.
-A fixed PB15 (flickering strip on boiler)
I can't reproduce this, could you please provide a screenshot of this.
-Less textures(size)(<50mb in total) in new F7 cab and also RightSide/km/h
The large texture size is necessary to provide both the detail resolution for the cab view itself, and the texture variations for the different liveries required for the F7 cab. The cab allows creators to specify from a range of different textures via a tag in their locomotive, so as to make it more closely match the livery on the exterior model.
-A fix for (pbr)textures closeby in cabs (might be an exporter issue not Trainz)
Could you please clarify for me what this issue is? Do you mean the flickering shadows? If so this is due to the thinness of the 'walls' in many cabs (either due to them being single sided, or being far too thin for Trainz to accurately render the shadows).
-A fix for the double save when exit a route/session (is it even needed?)
If you are referring to saving both a route and session, this is to ensure that any session data that has been created (including industry configurations/changes) are correctly saved.
-A fix for traffic (carz) that get stuck and honk in Surveyor (was ok before SP1)
Again if you can reliably reproduce this, please submit a bug report to
https://n3vgames.typeform.com/to/xRdryu
-A fix for parallel (caternary)spline points going astray since SP2
If this is related to the other spline issues being discussed, please see above. If they have moved without any changes (including bulk-asset replace), then please submit a report to
https://n3vgames.typeform.com/to/xRdryu
-Req: a page in wiki, stating all obsolete script commands, the reason why,
with just as good alternative and example how to use the new ones.
This is unfortunately not something that is within our scope to do. It's simply not possible for us to test all of the available driver commands, and find viable replacements.
-Req: a detailed list of all changes SP2 brought and why.
Unfortunately as TRS19 SP2 evolved over quite a long time (through both a number of Trainz Plus releases, and then the TRS19 SP2 beta itself), we don't have a changelist available in this case.
Regards