n3vpolsen
Administrator
Hi everyone,
We want to provide an update regarding the reports players have made about performance and redraw behaviour since the release of TRS22 SP6.
We know it’s frustrating when content appears to break after an update. Please be assured this is not being ignored—we’re actively investigating and will continue to share updates as we learn more.
Thanks,
The Trainz Team
We want to provide an update regarding the reports players have made about performance and redraw behaviour since the release of TRS22 SP6.
What We Know
- Some users are reporting that routes which worked fine in SP5 now show stuttering, unloading/reloading of scenery, or redraw loops in SP6.
- Especially around major stations or when multiple locomotives/rolling stock are present.
- In at least one test case, replacing a small number of very heavy spline assets resolved the problem. For example, one track asset was found to be 1.5 million polygons with hundreds of draw calls, when tested in ‘performance analysis’ mode in the Preview Asset tool, which is far beyond practical limits. To give a comparison Kickstarter County II uses a track asset with 130,000 polygons.
- Our internal testing has confirmed that a recently introduced memory management system is being triggered more often than we expected in certain routes. This system was introduced to reduce crashes caused by excessive memory consumption. We expect that this is likely the cause of much or all of the reloading/redrawing of scenery, especially splines.
- We are investigating whether the limiter itself is behaving as intended, or if specific assets or scenarios are pushing it harder than expected.
What We Don’t Yet Know
- Why these issues were not reproduced during internal QA or external beta testing.
- The extent to which this is caused by individual high-poly assets versus a broader systemic issue.
- Whether the 'redrawing' affects performance negatively; it's a reasonable assumption that these might be linked but we don't have any strong evidence of that at this stage.
What We’re Doing
- We’re actively reproducing reported cases using both internal and community content.
- We are reviewing routes reported so far, and comparing SP5 vs SP6 behaviour.
- We are gathering more data to determine if the issue lies with the limiter thresholds, specific content, or a combination of both.
- We are reviewing options for improving outcomes via code changes, but we also recognise that some content may need optimisation going forward.
How You Can Help
To move forward, we need concrete examples we can test directly. If you are seeing this issue, please:- Provide the exact route/session name and KUID if from the DLS/DLC Pack, or package your content up and send it to us (Google Drive or other download is fine).
- Indicate in detail where on the route/session the problem occurs. Surveyor coordinates or the exact name of a nearby named object would be most useful.
- Include details such as draw distance settings, framerate at the time, and other graphics settings.
- If you can, take a screenshot or video showing the problem.
- Submit a helpdesk ticket with your details, so we can track and compare reports more effectively.
- If you're significantly affected by this problem, and you use the Windows Trainz Store version of the product, and are willing to help test beta fixes, let us know.
We know it’s frustrating when content appears to break after an update. Please be assured this is not being ignored—we’re actively investigating and will continue to share updates as we learn more.
Thanks,
The Trainz Team