BigVern Posted February 28 Posted February 28 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? 1
BigVern Posted February 28 Author Posted February 28 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.
lewnemejski Posted February 28 Posted February 28 Scenarios were tested before release. Some of the problems are game/engine related, not the scenarios itself. Some players managed to complete the scenarios some not. Mind that scenarios execution are based mostly on your local computer capabilities and game settings. So on your side scenario might not work but for me it could be completely fine. It is almost impossible to test every scenario with different settings and configurations. 1 1
BigVern Posted March 1 Author Posted March 1 (edited) 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. Edited March 1 by BigVern 1 1
Isambard Kingdom Brunel Posted March 1 Posted March 1 What a right load of pony, it's hardware related !!! Talk about making it up on the fly. 🤣 🤣 🤣 1
BigVern Posted 8 hours ago Author Posted 8 hours ago 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.
Recommended Posts