I haven't played in quite some time, so thought about setting the game up again - the last time I played it was with some trainer support from here with me having a great time - but now trainer activation alone causes crashing no matter what. Doesn't matter where I am or anything I'm doing in the game, as just having this trainer activated leads to crashing. I did browse back a bit - with other people as of late having experienced similar issues, there seems to be something going on : /
[Edited by Nikhris, 6/5/2026 5:28:40 PM]
We can't replacate this issue. Try turning off the overlay?
if people are getting the game to crash when using the trainer we would need a lot more info to start troubleshooting since multiple people can't replicate the issue[quote2]
Environment = DX12. Game version 4.04. Launched through Steam. On Windows 11. Windows fully up to date. All drivers current and up to date. Nvidia modern GPU with up to date drivers. Trainer launched through Aurora ( Which self updates). Hardware specs that meet the requirements of the game. Overlay disabled. No mods in use.
Triggers = The crashes are inconsistent. They appear in both dx11 and dx12 versions regardless of in game quality settings. Sometimes it will crash once and be able to play for hours on the next launch. Sometimes it will crash over and over right at the menu when activating, making the game unplayable. The trainer options enabled sometimes will cause a crash on a specific option. Other times the enabled trainer options won't matter. Sometimes sprinting or mounting your horse will cause it. Sometimes just standing in a specific place will cause it.
The only thing that is consistent with the crashes is that they are caused by the trainer. Because playing without the trainer, there are no crashes.
I hope this is enough information for you. I'm not sure why you wouldn't be able to replicate the issue. There are certainly enough people reporting the issue for it to not be isolated.
if people are getting the game to crash when using the trainer we would need a lot more info to start troubleshooting since multiple people can't replicate the issue[quote2]
Environment = DX12. Game version 4.04. Launched through Steam. On Windows 11. Windows fully up to date. All drivers current and up to date. Nvidia modern GPU with up to date drivers. Trainer launched through Aurora ( Which self updates). Hardware specs that meet the requirements of the game. Overlay disabled. No mods in use.
Triggers = The crashes are inconsistent. They appear in both dx11 and dx12 versions regardless of in game quality settings. Sometimes it will crash once and be able to play for hours on the next launch. Sometimes it will crash over and over right at the menu when activating, making the game unplayable. The trainer options enabled sometimes will cause a crash on a specific option. Other times the enabled trainer options won't matter. Sometimes sprinting or mounting your horse will cause it. Sometimes just standing in a specific place will cause it.
The only thing that is consistent with the crashes is that they are caused by the trainer. Because playing without the trainer, there are no crashes.
I hope this is enough information for you. I'm not sure why you wouldn't be able to replicate the issue. There are certainly enough people reporting the issue for it to not be isolated.
I don't see you mention you disabled the overlay in trainer settings. Is this off or on?
Also the reason we can't replicated it because we haven't had any crashes with the info we had and tested by.
And crashes that happen hours into the game we don't have to play for as they are inconsistent and not anything we can reliably replicated over and over to figure out the cause.
1 crash at start and 1 crash hours in doesn't provide us with data points to see the cause. It's just random crashes
Overlay disabled. No mods in use. [quote2]
I did mention the overlay being disabled.
Also the reason we can't replicated it because we haven't had any crashes with the info we had and tested by. And crashes that happen hours into the game we don't have to play for as they are inconsistent and not anything we can reliably replicated over and over to figure out the cause. 1 crash at start and 1 crash hours in doesn't provide us with data points to see the cause. It's just random crashes[quote2]
I mean I understand the difficulty in diagnosing an issue that appears to be random. With the common factor being the trainer is in use. I'd probably look at things happening before any options are even toggled. Looking for values that might be getting manipulated before the game makes them valid. It wouldn't be unreasonable to think perhaps setting a value before it's ready causes the game to dismiss it, leading to a runaway loop.