Mojave Sub Tunnels

[QR1408]

The tunnels on the Mojave route are broken. Hopefully this will be fixed sometime as this is payware.

 

[HPL]

I reported that months ago: no response and nothing done. A fixed TRS19 version by hiawathamr is on the DLS.

 

[JCitron]

I reported this back when the route was first released again for TANE.

 

[QR1408]

Yeah thanks for the replies I'll try and find that route or fix it myself.

 

[Forester1]

Did anyone submit a ticket?

 

[DennR]

​ did raise this issue in an email exchange with the developer tram and they said it would be fixed as part of the SP3 update as it was linked to the flicking between summer and winter track that was occurring in the SP3 Beta versions. Clearly that was wrong and no member of staff at N3V checked to confirm that thee two issues were linked.
I have also found that in two of the sessions released as part of the Mojave package one consist is derailed and the session crashes at the start. They are the #991 session and the Mojave to Bakersfield session. Both can be fixed by editing the session to put the offending consist back on the track and saving as a new session but should we be having to do this rather that the developers? The route and sessions worked as released by Joined Rail and in TANE so why continue to make them Payware in TRS19 when they are known to be broken?

 

[ClintClassic]

​ ... I have also found that in two of the sessions released as part of the Mojave package one consist is derailed and the session crashes at the start. They are the #991 session and the Mojave to Bakersfield session. Both can be fixed by editing the session to put the offending consist back on the track and saving as a new session but should we be having to do this rather that the developers? The route and sessions worked as released by Joined Rail and in TANE so why continue to make them Payware in TRS19 when they are known to be broken?

I had purchased a new computer, and installed the "Mojave". Noticed these same issues. Sent N3V a ticket. This was their response Nov. 8th:

"Good Afternoon clintclassic
Thank you for contacting us. This is a known issue in the TRS19 SP4 update, which our team is currently looking into for the next update. We do not yet have a release date for the next update, however any news will be announced either in our newsletter or on our forums ( https://forums.auran.com/trainz/forum.php ).

Please check these helpful pages:

FAQ
Trainz Knowledgebase
Trainz Forums
TRS2019 FAQ

Kind Regards

N3V Games Support Team".

______________________
So N3V is supposedly working on this "known issue" with "Mojave" as well as other Routes and Sessions with this same issue of "derailment(s)" at the very opening of a given Session, inflicted with this anomaly. We will just have to sit tight until SP4; or as DennR says,we fix it ourselves :mop:

 

[DennR]

The issue is not rocket science. Some part of the update has allowed a section of track or switch to be moved very slightly and as a result a consist sitting over that section of track is derailed. I cloned the sessions and set the consists back on track and the sessions work perfectly. This does not need to wait for a future update it needs the sessions fixing and releasing as the next update to their respective kuid's.
There is another issue with two drivers with the same name causing conflicts in at least one session but that is on another payware route and I have submitted a ticket relating to that.

 

[JCitron]

Did anyone submit a ticket?

Back in TANE days when the route as first transferred over. Included in the bug report was the info on the fences through the tunnels and across the ROW along with the inoperative ATLS crossings.

I got a the long worded thank you for submitting message, then crickets.

 

[ClintClassic]

... "This does not need to wait for a future update it needs the sessions fixing and releasing as the next update to their respective kuid's.

Yes. But as I had said also ""Mojave" as well as other Routes and Sessions with this same issue of "derailment(s)" at the very opening of a given Session, are inflicted with this anomaly." (As this problem is a bit widespread) I do not intend to waste too much time fixing routes inflicted with this issues [I will wait until N3V fixes them for me] as first of all, I'll much rather spend my time on my own route; and second this "anomaly" is much worse with one (or more) of the ECML route sessions -and no doubt other routes! The derailment closes the session I attempted to play, then opens the session a second time, then closes again!? Do not have the time for this -cheers!