Follow along with the video below to see how to install our site as a web app on your home screen.
Note: This feature may not be available in some browsers.
I'll do it too, if it's not too late. Couldn't reply fast because of time zone differences.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.
Added you to the group and forwarded the instructions.I'll do it too, if it's not too late. Couldn't reply fast because of time zone differences.
The patch is (currently) only for the Trainz Plus (Windows) and TRS22 (Windows) versions.I would test it too, but I have the Steam version...
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.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.
Thanks @pware . Can report likewise for this route in build 132284, but don't have data to compare before and after FPS.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.
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.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 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.Gila doesn't have a whole lot of assets to begin with and the sagebrush assets are being repaired by the content creator.
Thank you, Dan. I'm sure they'll be fine in SP5... SP6, well that's another ball of wax all together.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.
Count me in as I'd like to test my Midwestern Rails route to see if performance is fixed.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.
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.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?