X2381-Wheel Slip
#1
Posted 03 August 2014 - 03:00 AM
I have just installed the latest X2381 and now when I try and move a train, and I have tried different activities, after I release the brakes and throttle up, the wheel slip notice comes on and the trains will not move at all.
In one activity I have two units and 40empty autoracks and I can not move the train?
I have attached the log in case there is something that I'm doing wrong but I have not had this problem before.
Thanks for any help.
Tim
#2
Posted 03 August 2014 - 03:21 AM
Correction. The update affects steam as well. I have a heavy test train powered by steam. Prior to this update, the engine would start this train. With this update the physics are out by a long country mile. The engine starts in a boiler priming state and will not move the train. With both steam and diesel affected I suspect that everything else is also affected in some way. Testing should have picked up these faults.
This post has been edited by copperpen: 03 August 2014 - 09:36 AM
#3
Posted 03 August 2014 - 03:21 AM
Wheelslip comes up on notch 2 on an engine with wheelslip control.
#4
Posted 03 August 2014 - 05:33 AM
#5
Posted 03 August 2014 - 08:46 AM
For Diesel locomotives, it now believes the mass of the locomotive is more or less the mass of the fuel.
I'll try to find where this problem comes from.
#7
Posted 03 August 2014 - 09:15 AM
#8
Posted 03 August 2014 - 09:34 AM
Serana, on 03 August 2014 - 09:06 AM, said:
OK. Now can you fix the steam locomotives. Some start with priming boilers, some start with blown plugs and some seem to be ok. All should be starting with 8 inches of water in the glass, but this is not so. levels vary from 8 inches and priming to 0 inches and out of water. The OK ones only have 3.1 inches in the glass.
#9
Posted 03 August 2014 - 10:04 AM
The rolling stock code is sometimes organized weirdly, that's why we had those bugs after a reorganization.
#10
Posted 03 August 2014 - 11:29 AM
Serana, on 03 August 2014 - 10:04 AM, said:
The rolling stock code is sometimes organized weirdly, that's why we had those bugs after a reorganization.
That is what testing is supposed to pick up. No code should ever be released with a bug like this in it.