FPM Pacific Surfliner problem
#21
Posted 14 October 2018 - 12:14 AM
Hi Derek,
in the meantime I added further wording to my last post, please read.
in the meantime I added further wording to my last post, please read.
#23
Posted 14 October 2018 - 03:15 AM
Ai trains do not have to have the notches section, and have not in the past.
Why are we getting this crash now?
One full run on Pacific Surfliner has been done.
Working through the other crash activities.
Why are we getting this crash now?
One full run on Pacific Surfliner has been done.
Working through the other crash activities.
#24
Posted 14 October 2018 - 03:42 AM
I think that the quickest way to narrow it down would be to run each individual consist from an activity that is crashing in Explorer mode. If necessary just start and stop the train.
Hopefully this will identify any ENG/WAG files that might be contributing to the crash.
Hopefully this will identify any ENG/WAG files that might be contributing to the crash.
#25
Posted 14 October 2018 - 04:26 AM
#26
Posted 14 October 2018 - 09:47 AM
Csantucci, on 13 October 2018 - 11:57 PM, said:
Hi Peter,
pls take note that in x.4261 you have changed also ContentManager.csproj. In fact this is a strange thing that occurs also to me. Since the last changes made by James in the Content Manager, everytime I build with Visual Studio, it modifies ContentManager.csproj.
pls take note that in x.4261 you have changed also ContentManager.csproj. In fact this is a strange thing that occurs also to me. Since the last changes made by James in the Content Manager, everytime I build with Visual Studio, it modifies ContentManager.csproj.
It has happened to me on compiling from a brand new checkout of X4259.
Dennis
#27
Posted 14 October 2018 - 10:50 AM
Csantucci, on 13 October 2018 - 11:57 PM, said:
pls take note that in x.4261 you have changed also ContentManager.csproj. In fact this is a strange thing that occurs also to me. Since the last changes made by James in the Content Manager, everytime I build with Visual Studio, it modifies ContentManager.csproj.
It's slightly odd, maybe due to different Visual Studio versions? I'm on 2017. I don't think it matters though, so it's not a problem that it got committed.
#28
Posted 14 October 2018 - 10:55 AM
I first reported the original problem in http://www.elvastowe...-class-105-dmu/ where nobody had any idea of why this was happening. I since installed a fresh version of the route and problem disappeared, I did however retain the original because it was on a different drive. Now testing the original install using X4621 this also starts without error.
#29
Posted 15 October 2018 - 12:17 AM