BigVern

As an aside to this, the consist exchange on the original Coal Mine Operations is also borked. If you save the game after doing the shunting move at the terminal to take over the fresh train and change cabs, when you get going and save the run, loading up the train is running backwards and the controls HUD is corrupted with all the steam loco values listed not just the ET22. Unrecoverable. I have submitted a report for the bug forum but it will probably be a day or two for it to show up. Not sure what might happen if you stay in the same cab and effectively drive the second train from there, just using external view. I suspect this might also become an issue on the Lodz Junction run round scenarios where you change cabs to drive the second portion.

After completing the wagon exchange, coupling to the new consist and changing cabs if you save on the second train the load is corrupted. The scenario loads with the train running backwards, the keys don’t work and the controls HUD is distorted showing all the steam loco values as well as the ET22. As such, the scenario cannot be completed. I may try to see what happens if you just remain in the original cab and effectively drive the loco in reverse using exterior view but I’m not overly confident that will work. I’m also concerned this could be an issue on other scenarios where a run round or consist change is required, including the passenger runs on Lodz Junction.

There was also a bundle deal for the original Lodz DLC plus the new route extension and Impuls EMU.

As the title suggests can we please have a few more options when selecting the weather for a single player run. For example cloud without rain rather than just sunny or raining. Or the option to add a small amount of fog or mist without obscuring the whole scenery. In fact, the ideal would be something akin to how TSW does it starting a timetable run, if you disable dynamic weather first, including sliders to adjust the intensity.

In SP it looks like train IC 8320 is the only one routed that way. We could do with a couple of scenarios for the local trains in each direction over that section. The Regional scenarios use the other double track line.

Thanks Jason. Funnily enough that’s the regional run I’m doing at the moment and should pick it up later.

Yes it’s a silly question but I have yet to find the stretch of single track main line which I’m sure was mentioned as being part of the new route extension. Could someone point me in the right direction and also state which (SP and MP) services traverse through this section, please!

We need something akin to free roam or quick drive in TSC or TSW. Or just a very simple GUI scenario editor similar to the one in TSW.

Sorry I don’t buy into the hardware argument. Seems a bit strawman to me. The fact changing the start time at the commencement of the scenario to find it then jumps back to the original timings after the run round, is hardly on the CPU or GPU. Likewise, the save game routine no longer running when it worked fine in the previous version or before the DLC’s is not the fault of the user. Edit: Further to my thoughts above, the bug report has now been published and marked as “Open Sim” on both the timetable reversion and the sudden save game issues. So kudos to the developers for acknowledging as such and not just dismissing as potato PC or user error.

I am leaving all the SP scenarios alone until/if the developers acknowledge the issues and confirm they are working to fix the issues. I did wonder as regards testing whether things worked better on release, but we have had two small patches one yesterday and the other today which may have broken things. It's also a bit annoying that they seem to sit on bug reports for a day or two before they show up on public viewing. I know it's the weekend but you would have thought following a major DLC release which does have issues they would be sorting through the problems.

Sadly the SP scenarios now seem increasingly broken in respect of several aspects, which I have detailed on the SP section along with a (pending) bug report.

As I’m still waiting for my reports to appear for public view in the Bug forum, would further note the save game seems to have stopped working for other scenarios too. I started off IC 7320 and tried to save about half an hour in. Same thing happened… After hitting the save box, game remained in the pause menu. On hitting Esc to return, no confirmation of save in the message box and on going out to the main route menu not registered there either. So until these issues are sorted, looks like SP off the menu at least for the Lodz Jn route. My initial positive thoughts about these two add ons are diminishing rapidly, but unfortunately too late to refund. Got to wonder what sort of testing was done before they were pushed out.

Add to this while waiting for it to be published. IC 7320 with the Ty2 steam loco not saving the game even on the section to Lodz. After pressing save from Pause menu and hitting the window with save details, not being returned to the running screen without hitting Esc, there is no record of a save in the message box and returning to the main menu no save listed under the route/train to load.

Thanks for the heads up. Given the issues I found/reported with the passenger scenario run round, I begin to wonder how thoroughly these SP scenarios were play tested? I thought SimRail developers were better in this respect than DTG, who we are used to pushing out stuff for TSW without adequate QA and testing.

I have a bug report pending in the other forum section but just advance warning to anyone playing the Lodz Junction scenarios where a loco run round is required. Don’t change the starting time when loading the run (e.g. two or three hours earlier) as after you complete the run round move at Lodz. Part 2 of the scenario reverts to the original times when the Timetable window returns. So in my case, I was sat in Lodz at 0840 with the train not due to leave until 1137. (IC 3720). As an aside, once you reach this location it is no longer possible to save the game (also logged in the pending bug report). Have to wonder if this was properly tested, what would happen with effectively two part scenarios using the start time modifier?