Ongoing Investigation: SP6 Route Performance & Redraw Issues

Hi everyone, appreciate all the feedback. We are actively working on a solution that will be rolled out quickly. Could I please get a list of core users willing to test an exclusive patch to help confirm whether the new build resolves the issues you’ve been seeing with SP6?

A simple reply with your MyTrainz account will be enough, thanks. I can contact you directly via the linked account email address. If your linked email isn’t correct, please update it to ensure you receive the patch invite.
I'll do it too, if it's not too late. Couldn't reply fast because of time zone differences.
 
Ok guys and girls,

First of all, I want to thank N3V for letting me test a fix.

I've just tested a fix from N3V, and even though this is only just my experience with it, what I can say is, the fix has fixed all of my redraw and performance issues! It was an immediate and massive improvement.

Again, this is only my experience but N3V has restored my faith in them, as it's not only fixed the redraw and performance issues, but the performance also seems a lot better.

I have been very harsh on N3V in this forum thread, mostly because Trainz seemed to be going backward, and, I had to reinstall one of my installed copies (luckily, I have several installs of different builds on my PC) which takes a long time to do but I'm very happy to take back most, if not all that I said. They seem to have done a great job on the fix!

To sum up, things are looking good with the fix, and performance seems to have improved too. I hope others have the same experience and results.
 
Like @cabnz1 above, I have just tested the "fix" on my giant merged route that had some FPS issues in one area. The problem has been fixed and the overall performance has improved. I did do some optimization of the route prior to the fix but that only had a minimal effect.
 
I am impressed. I just went back to a route <kuid2:214658:101010:1> Aylesbury to London Marylebone (Updated) originally reported by @paulper as a problem in SP6.

Take a look at <kuid2:214658:101010:1> Aylesbury to London Marylebone (Updated). Search for "sig 2aH LU LH 4m tall 52" pan around and see if you have any issues.
Ran the original (unedited) route with all the tree splines and billboard trees planted everywhere and there were no rendering or FPS issues in the updated patch.
 
I am impressed. I just went back to a route <kuid2:214658:101010:1> Aylesbury to London Marylebone (Updated) originally reported by @paulper as a problem in SP6.


Ran the original (unedited) route with all the tree splines and billboard trees planted everywhere and there were no rendering or FPS issues in the updated patch.
Thanks @pware . Can report likewise for this route in build 132284, but don't have data to compare before and after FPS.

For my own very detailed route, the re-drawing issue has gone, but FPS is down around 10-15%, particularly in areas that have many Speedtrees. I've made no edits to the route yet, and shall do some further testing later including disabling the Speedtrees. I don't use billboard trees or tree splines so already know these aren't an issue in my route, but on the whole, this looks promising.
 
FPS is down around 10-15%, particularly in areas that have many Speedtrees. I've made no edits to the route yet, and shall do some further testing later including disabling the Speedtrees.
I do not know if it will make any difference but I have replaced most of my SpeedTrees with the new Plant Factory equivalents (where direct substitutes were available). The PF trees use less memory than their SpeedTrees counterparts.
 
Gila doesn't have a whole lot of assets to begin with and the sagebrush assets are being repaired by the content creator.
I will upload my sagebrush assets tomorrow as i want to see if the new build wrecks them , by adding a mod and lod we reduced the triangle count from the millions down to 77 ,000. A number of jvcs older grass groups also caused issues in sp5 if one uses the 2019 fix versions from the dls they solved a myriad of issues.
 
I will upload my sagebrush assets tomorrow as i want to see if the new build wrecks them , by adding a mod and lod we reduced the triangle count from the millions down to 77 ,000. A number of jvcs older grass groups also caused issues in sp5 if one uses the 2019 fix versions from the dls they solved a myriad of issues.
Thank you, Dan. I'm sure they'll be fine in SP5... SP6, well that's another ball of wax all together.
 
Hi everyone, appreciate all the feedback. We are actively working on a solution that will be rolled out quickly. Could I please get a list of core users willing to test an exclusive patch to help confirm whether the new build resolves the issues you’ve been seeing with SP6?

A simple reply with your MyTrainz account will be enough, thanks. I can contact you directly via the linked account email address. If your linked email isn’t correct, please update it to ensure you receive the patch invite.
Count me in as I'd like to test my Midwestern Rails route to see if performance is fixed.

Cheers
 
I am looking at my jvc older grass groups as been mentioned above. A few say "Installed from DLS, obsolete"

Does that obsolete message cause errors?
 
I am looking at my jvc older grass groups as been mentioned above. A few say "Installed from DLS, obsolete"

Does that obsolete message cause errors?
Obsolete assets usually don't cause a problem, but they do take up space. Sometimes there may be a problem with scripted assets, but this is rare.

Your best bet is to delete the obsolete assets.
 
Back
Top