Hi all, I recently made a copy of a route I had built in the editor to test some changes to the route while still having the original there in case things went awry with the testing. I immediately ran into an issue with the new (copy) route: whenever I open the 2D map in either the route editor, scenario editor, the driver instructions/AI editor within the scenario editor, or while playing a scenario (in the driver mode), when I scroll to a certain area of the 2D map, or zoom out about 14 mouse wheel 'clicks' in the map, the game crashes and gives the usual "Out of Memory" error. I have no idea why this is happening, and it doesn't happen in the original route I built (remember, the problematic route is a copy I made of the original route), nor does it happen with any other route I've built or purchased. Here are all the things I've tried to stop this issue from occurring, none of which have worked: - Restarting my computer - Making a copy of the problematic route and opening the 2D map there (it still crashes) - Deleting all scenarios in the problematic route and loading a completely new one - Deleting all rolling stock from the problematic route in the scenario editor - Running the game in 32-bit (I normally use 64-bit) - Verifying integrity of game files in Steam - Running the game in borderless and windowed modes - Running the game in different resolutions - Removing the problematic route's source file from the Railworks > Content folder, running the game without it, then moving the source file back into the Content folder and running the game again - Disabling RW Enhancer My PC's specs are well within the recommended specs listed by DTG, so I don't think that's the problem. Again, the game only crashes when I scroll to a certain area of the 2D map on this particular route -- not in any other routes in my library. Has anyone else had this same problem, or any possible fixes? I'd really like to avoid having to uninstall and reinstall TSC but I really have no idea what's going on here. Any help is greatly appreciated!
A guess. If it is just the route it is possible that the act of copying it has messed with the core route files. If you do it I would suggest deleting it and trying to copy again. Have you kept the same route name and other obvious stuff like that ? Is the original still a live route so the sim is getting confused ? Prob teaching you to suck eggs but it def sounds like a route files issue at a route rather than scenario or stock level.
You could try clearing the blueprint cache (TSC menu or delete the blueprints.pak file in the Assets folder)) in case the original has referenced any code there. (not sure if verification clears that). You could try running logmate on both the original and the copy of the route to see if there is any differences Any error messages in the Event Viewer or "View Reliability History" or in Dxdiag.txt in either? Run sfc /scannow to eliminate possible windows errors. (Google)
Thanks for the reply. I cleared the cache in the TSC menu, checked for errors in the Event Viewer and Reliability History program (neither showed any TS errors) and ran the sfc/scannow command, which did find and fix some corrupt files but didn't fix the TS issue here. I'm not familiar with LogMate -- I found it in the Railworks folder but don't know how to use it or what to look for. Could you explain? Thanks!
And in case this means anything, the Out of Memory error that pops up when the game crashes says "Fatal error in mode [edit or drive] during update within WINDOWS_MANAGER.
Your route copy is likely corrupt. Have you cloned it? When cloning routes, TS has the habit of moving it a bit relative to its original coordinates - if that's a wanted DRM mechanism to prevent redistributing original content or not, nobody knows. Use TSTools to clone the route, it will create a 1:1 clone, by making exact copies and giving it a new GUID.
Thanks for the reply. I downloaded TSTools and used the Route Building Tools menu to make a clone of the corrupted route, but that didn't work either -- the problem still persists. I checked the route using that same menu and one of the first messages that popped up was that the route template (in this case it's Miami to West Palm Beach) could not be found. That doesn't seem great, but it also said this for other routes I checked that do not have this 2D map issue, so I don't think this is the problem. The next message that popped up said that there was an error on line 2 of one of the files for a platform loft that's used in the route. This error did not appear on other routes I checked that do not have the 2D map issue, so I thought that this particular loft might be the culprit. I went into the corrupted route, disabled the asset pack which contained this loft (in this case it was Soldier Summit) and restarted the game and reloaded the route; that didn't work -- it still crashed. I then went and deleted that particular loft from the route in TSTools to see if getting rid of it entirely would fix the problem, but that didn't fix it either. After deleting the loft and checking the route again in TSTools, the error message about the loft no longer appeared, but now another error appeared, saying that there was an error on line 2 of the .bin file for the trackrule I used in the route. I tried deleting the trackrule file from the route in TSTools, but the 2D map crash issue still remained. I have no idea what to try next. Anything else you (or anyone else) can think of? It's really frustrating, but I truly appreciate your help.
