u/Training_Sail_7550

I presume it has something to do with BeamNG 0.39. Anyone know why this happens and/or how to fix this?

It might look relatively easy, which it kinda is, but most of it is in the engineering it took within Automation. Managing the four pillars of performance: downforce, drag, power, weight-- was hard. there's was minor file editing involved, but only removing a safety feature that slams on the brakes on 6+ g's, and making the battery much more efficient for longer runs.

the idea for a speedrun scene is to require .zip files to be shared with verifications, though that might be complicated-- the only editable things for exports should be removing the 6g measure, and making the fuel/battery quantity greater for longer runs. not sure if it's possible, but you could use an automated file-comparison tool (like WinMerge) to compare an exported zip file to another basic but similar & stock automation build. or, you could make runners have to start the footage from the moment they export the car from automation in the first place.

check out the other videos on my channel, if you're interested in my other runs. https://www.youtube.com/@andreesstuff

i feel like a really good solution would be to just have people required to show exactly what they did after exporting, without cuts. it'd require the runner to re-export every time, but each time the old file gets replaced with the new one anyway