We’re happy to announce that the "Asset Groups" bug in SP5 has been fixed with our latest hotfix update! This issue affected the placement of trackside objects on certain splines, but thanks to your reports and our investigations, we’ve resolved it.
What Was the Issue?
The bug was caused by a database repair process that could corrupt asset compatibility data.
It affected DLS and locally installed splines. Builtin and packaged DLC content were unaffected.
What’s Changed?
The hotfix ensures that affected splines and trackside assets now work correctly.
Users no longer need to apply workarounds—the issue has been resolved.
Looking Ahead
We’ve improved our testing and release processes to catch similar issues earlier.
We’ll continue refining our communication to keep the community better informed.
Thank you for your patience and feedback—your support helps make Trainz even better!
***************** Original Post *****************
We are aware of the recent issues affecting some users following the latest SP5 update ( Trainz build numbers ). We want to address your concerns directly, provide clarity on the situation, and outline the steps we are taking to resolve this matter.
What is the Bug and Who is Affected?
The bug affects users across Retail, Trainz Plus, and Beta Tester versions of SP5. Specifically:
Users who have installed splines from the Download Station (DLS) or created/installed splines locally are potentially affected.
Built-in and DLC content remains unaffected.
Surveyor users (both Classic and S20) are impacted, while Driver mode is not meaningfully affected.
The issue occurs when attempting to place trackside objects onto certain splines, which may fail.
How Did This Happen?
The root cause is a bug within the Extended Database Repair (EDR) process, which can corrupt data used to verify the compatibility between splines and trackside objects. Due to the complex conditions required to trigger this bug, it was not identified during four months of internal and external testing.
Future Prevention of Such Bugs
We are implementing several measures to improve our internal and external testing processes:
Expanding our testing to include a broader range of content sources.
Proactively testing the EDR process against diverse scenarios.
Enhancing communication between Engineering and QA teams to better identify potential risks.
Is a Workaround Available?
This step-by-step process within Trainz can restore normal operations for affected builds.
Start Trainz to the launcher.
Click "Trainz Settings".
Select the Dev tab.
Switch on "Enable advanced debug tools".
Close Trainz Settings.
Exit Trainz entirely.
Open Trainz to the launcher.
Developer > "Run TrainzUtil Command…"
Type the following command and then press enter:
flagrepairdatabase patcher
Close the 'Task Complete' window.
Developer > Run TrainzUtil Command…
Type the following command and then press enter:
flagrepairdatabase extended
Close the 'Task Complete' window.
Click "Start Trainz" and wait for the database repair to complete.
In all cases, a subsequent Extended Database Repair will undo the above workaround, requiring the steps to be repeated again.
Patching and Permanent Resolution
Being a complex bug, it has taken us a while to fully unravel the exact cause and impacts. Although the current workarounds are effective, we are committed to releasing a hotfix that will permanently address the root issue. This hotfix will be deployed as soon as we have thoroughly tested it to ensure it does not introduce new problems.
Moving Forward
We understand the frustration this bug has caused and sincerely apologize for the inconvenience. Our team is working diligently to rectify the situation and prevent similar issues in the future. We appreciate your patience and continued support as we improve Trainz.
Thank you for being a valued part of our Trainz community.
Sincerely,
Paul Olsen
Director