narrowgauge
92 year oldTrainz veteran
I have been testing the DHR sessions and found a puzzling problem.
Session Sukna-Tindharia works as designed, works through the opening screens and completes the run.
All the others run through the opening screens, get the command to Drive and immediately I am dropped back to the desktop, no error message, nothing. I open a faulty sessions for edit, it is on the screen for 30-40 seconds and the same thing happens. Strangely, that occurs if I 'open for edit' the seemingly correct Sukna-Tindharia session.
Is this common to other installations or is it just mine? T:ane will start again with any problems, doesn't need to do any work with the database.
Comments? I'm running build #76536
Peter
Session Sukna-Tindharia works as designed, works through the opening screens and completes the run.
All the others run through the opening screens, get the command to Drive and immediately I am dropped back to the desktop, no error message, nothing. I open a faulty sessions for edit, it is on the screen for 30-40 seconds and the same thing happens. Strangely, that occurs if I 'open for edit' the seemingly correct Sukna-Tindharia session.
Is this common to other installations or is it just mine? T:ane will start again with any problems, doesn't need to do any work with the database.
Comments? I'm running build #76536
Peter