Thanks for reporting. We will take a look at this.

Yeah, physics issures on x64 are known. Especially with trains. I am not sure if a seperate bogey would accually fix this. We would have to check this.

Trains detailing on x64 server was reported in this thread:
https://steamhost.cn/steamcommunity_com/groups/SligWolfAddons/discussions/1/4513255384647889127/

It is an engine issue and has been reported as such:
https://github.com/Facepunch/garrysmod-issues/issues/5968

As far we know we can't do nothing about this, unfortunately. If the server runs on main, prerelease or dev branch, the train physics will be much more reliable.

Interesting. Do you happen to play on a x64-bit server?

Alright, on which maps do you experience this issue?

Nice that you got this solved. Locking as solved.

All right, closing as solved.

Your dupes are most likely outdated and use outdated model path. We do not support legacy dupes when we do much needed changes.

There is no legacy support for saves/dupe/demos. We try to avoid breaking changes. However we will do them if code would get ugly otherwise. Most of the breaking changes are done by now, so more such changes are unlikly to happen again. We won't give any warranties whatsoever, though.

Please fix the saves/dupes/demos yourself if needed.

VRMod_Start / VRMod_Exit might not be reliable. It is buggy in vrmod sometimes. We had to code around it and build a custom hook using a polling technique. Maybe test if the problem changes when the material is applied only serverside or only clientside.

Sure go ahead. It is just an alpha 0 image.