I got a error message saying INT DIVIDE BY 0 is there a way you guys could fix this? Reply if you know please.
I have the suspicion you're in the wrong forum. This is TS2022, not TSW2. It is a different game, like Samuel L. Jackson and Laurence Fishburne are different actors. And as a bug report, this is rather useless as you give no information. It's like calling 911 just saying "There's a fire" and hanging up.
Possible causes in any game Because TS scenarios can be written using 32-bit and 64-bit code a very few of the 32-bit scenarios don’t play well when running in TS 64-bit mode. Technically It is basically an error due to differences in 32 bit and 64-bit RAM access addresses. The code may try to allocate RAM addresses for both 32 and 64-bit but the difference reported is zero, causing an Integer Divide by Zero Exception. In TS20XX it is usually caused by a corrupt scenario or from an outdated driver, sound, graphics, etc. Difficult to fix. It can be idiosyncratic i.e. tied to a particular computer. This error message could also be caused by a computer or software limitation or conflict with computer memory. Usually results in an OOM/Access Violation/SBHH error. Does it occur in both TS 32-bit and TS 64-bit modes? Does it occur if you start your computer in "SAFE" mode? (google) It is such a volatile error that the same scenario may well run again without the same error Can we see what "View Reliability History" reported? Some of the possible limited fixes to try: Remove an offending scenario Update all drivers Run dxdiag (and look in the log txt file) Run sfc/scannow/DISM; etc Make sure the computer date and time are correct.
Peter, Could you describe what you mean by "64-bit scenario"? There is no 64-bit scenarios technically, all numbers are encoded as boolean, int32 or float32. The format has not changed. A scenario.bin from Kuju's RailSimulator in 2007 does not look different than a recent one. And a scenario created on 32-bit will not have different data than a scenario created on 64-bit. A scenario can indeed use such an amount of memory, because of the number of assets/rolling stock placed, that requires it to be run in Railworks64.exe. So apart from the memory needed, there is only one scenario known to me that does not work in 64-bit. Introduction to the Turbine/Sherman Hill - the issue here is not really the scenario data but the fact it uses a rolling start, which is a saved game which leads to derailment in 64-bit. I suspect a rounding issue in the position/direction/speed vectors.
Torf There are many scenarios on the workshop that state that they will only run in 64-bit, - and since 2018/19 I [resumed that many scenarios would be created using the 64-bit editor. It was a generalised statement giving an example of why you COULD see an integer divide by zero error.
There's nothing more to say. Btw, have never seen divide by zero on TS. And we hijacked this thread and the threadstarter is over the hills.
South Wales Coastal has one of these in the first scenario. I get an INT DIVIDE BY ZERO on the drive to Newport in that run. Everything else runs in 64-bit.
Interesting. Will look into that. Can you provide the scenario name and which incarnation of South Wales Coastal it's in?
The names are all service numbers. It's the one that goes from Cardiff to Holyhead, but naturally, you stop as far as Newport. I was on the original South Wales Coastal. I eventually loaded it in 32-bit instead and cleared just fine. BTW, this Cardiff to Holyhead is, in fact, part of why I thought Chester to Shrewsbury would be a good idea. A full run to Holyhead via merge is possible!
