Trainz Plus Beta TLR Phase 3 - Windows (136192)
- Thread starter n3v_laurence
- Start date
Yep. Happened to me too - for about 20 or 30 seconds. Put it down to new build teething problems.
Subsequent testing has revealed that it cannot be reproduced in Driver when running other sessions or even the same session. So it appears that it may be a first run of the beta only event. I have submitted a bug report.
Anybody noticed something different when saving a session? I'm pretty sure when you saved a session on previous builds it always showed the computer clock time first, then the date, and so on. Now it repeats the same first time and date of the original session, with the current computer clock time afterwards. It makes it hard to tell what session time was saved unless you hover the mouse over the session to see. I'm ending up with multiple saved sessions with the same first time (such as 18:37-04/25/2026-clock time-xxx). Makes it hard to tell which one is which!
A bit of confusion here.
Do you mean saving from Surveyor (saving an actual session) or saving from Driver (a "Driver Game" or "Session Game")?
I just compared these two possibilities in the current beta Trainz Plus (136192) and the current retail Trainz Plus (132284) and could find no difference.
When saving a "Driver Game" from Driver that is the exact order that it still uses - the Clock Time, Date and Session runtime. If this was different in any previous beta (and I never checked to notice) then it has been returned to "normal".
When saving a New Session (not overwriting the existing one, if any) then the same order applies - Clock Time, Date and Session runtime (session runtime will normally be 00:00 when saving a session). Again, if this was different in any previous beta then it has been returned to "normal".
Addendum: Just to clarify something "Clock Time" is the computer clock time, as you mentioned, not the Trainz game clock time.
Last edited:
Pware, I should have clarified it a little better. Previously, Driver Session Saves were as you mentioned; Clock Time, Date, Session Runtime. What I am now getting is like this: First session shows on my 3 saved sessions...18:37-26-04-2026-19:07-26-04-2026-session runtime. Second session: 18:37-26-04-2026-19:50-26-04-2026-session runtime. 3rd Session save: 18:37-26-04-2026-20:11-26-04-2026-session runtime. I honestly don't remember the first clocktime remaining the same on each individual session saved and the actual clocktime shown afterwards. I guess I'll have to reinstall the beta and see if something changed.
EDIT: Obviously, I think I might have fubared something last night. I ran one of my backup driver sessions from a couple of days ago, and then ran a save session (and no overwrite) and named the session like it should. Guess that's what happens when you work late with only one eye open
Thanks for the quick response, Pware! Always great to have a second opinion!
Thanks for the quick response, Pware! Always great to have a second opinion!Yes, I did too. I let it do its thing and it took about 10 minutes to finally load. I'm using old spinning rust drives that may make the load time a bit longer than it is for others.
Older build 3.5 locomotives such as this one here by Trainboi <kuid:648132:89803> ALCo RS-11 LVRR have a funky grey shadow underneath like some of the older TRS12 scenery items did.
Built-in locomotives such as this one by Norfolksouthern37 <kuid2:45324:100337:3> CSX GP38-2 YN-2 (ex-SCL) load up fine.
Built-in locomotives such as this one by Norfolksouthern37 <kuid2:45324:100337:3> CSX GP38-2 YN-2 (ex-SCL) load up fine.
Yes, I noticed that when I checked the locomotive's config.txt. This is invisible in SP5 and below but appears in this version.
n3v_laurence
Moderator
Thanks for the information Re: Black screen - I've been able to get a solid repro of the issue and have passed it to the team. It looks to be related to DB size and speed of drive, based on comments and my successful repro's - so length varies from system to system. It is suggested to let it just run for the moment. It is with the team now for review.
Re: Achievement notification, please double check you were not logged in another instance of Trainz, before starting the Trainz Plus Beta.
Re: Achievement notification, please double check you were not logged in another instance of Trainz, before starting the Trainz Plus Beta.
Last edited:
I just ran a test on that by installing the update on another computer with the Trainz Plus beta after logging off from Trainz and shutting down all other computers. The Achievement notification appeared at exactly the same point in the running of the same session. I have passed that info onto QA.
Similar threads
- Locked
- Locked