Thanks Ricky for the repro steps - just tested three times in a row but alas, didn't get the crash. What OS are you using?
How come Mixed 4 survive not getting the R6025 error first time?Now to test the Stadium Derby.
Quote from: Purple44 on January 19, 2017, 03:21:20 PMHow come Mixed 4 survive not getting the R6025 error first time?Now to test the Stadium Derby.Maybe you didn't move the car enough after countdown on Mixed 4? or did you do a whole race?So far I haven't found a track that did not crash after Stadium Derby. Bad blimp, shame on you.
IT WAS THE FREAKING BLIMP ! EDIT: I also tired Gravel 1 and Speedway 1 as second track after Stadium Derby - both times *CRASH*.
Here my results of testing the Stadium Derby:With just 1 AI:Stadium Derby, then Tarmac 1 - no R6025 errorStadium Derby, then Gravel 1 - no R6025 errorStadium Derby, then Speedwayl 1 - no R6025 error
Don't think it's just the animated objects, ...
Could you test that again by any chance? with restarted WF maybe?
I spoke to soon. I saw this R6025 error last night online at Space server when track got change to the new Mixed 3 - route 2 and crash my game. But I was the only one in the server that crash.
K, I did a retest and still got same result with 1 AI and restarting WF each time:With just 1 AI:Stadium Derby, then Tarmac 1 - no R6025 errorStadium Derby, then Gravel 1 - no R6025 errorStadium Derby, then Speedwayl 1 - no R6025 errorCHANGELOG:* Added new spectators to a few selected tracks.Was not the Oct Build the first Build to bring back spectators in the stands? Could this be where the problem lies Bugbear?