Page 1 of 2
Something Weird with WS Scenarios

Posted:
Wed Dec 19, 2018 10:56 am
by qwhite451
I finally got around to get TS2019 updated to the 64 bit version which works fine untill i started downloading WS Scenarios after they were installed i got some sort of Access Violation went to the steam forums looked around could'nt really find the help i was seeking so i got rid of all the Scenarios i downloaded the game started working correctly.Im wondering if Ws scenarios are breaking the game and causing the Access Violation? Is there anyone else having this sort of issue
Re: Something Weird with WS Scenarios

Posted:
Wed Dec 19, 2018 2:10 pm
by buzz456
What’s WS?
Re: Something Weird with WS Scenarios

Posted:
Wed Dec 19, 2018 2:50 pm
by _o_OOOO_oo-Kanawha
WS is Steam Workshop probably.
It is my experience that downloaded Workshop scenarios are sometimes corrupted by Railworks' unzip dll.
Have you tried checking your scenarios with NameMyRoute.exe from the Railworks root folder?
Fire it up and it will produce a list of all your routes and scenarios.
Click on the little [+] boxes to expand the listing per route.
Any scenario that shows errors is corrupted in the fields that NameMyRoute.exe checks.
Note the UUID (the large number) and search for the original .zip file in the Steam\steamapps\workshop\content\24010 folder by the first 8 positions of the UUID.
Open that .zip file, and drag its contents into the Railworks folder, overwriting the already present.
Click View => Refresh and hopefully the scenario will now show clean.
There was an undisclosed maximum number of Workshop scenarios you can subscribe to, but perhaps this limit has been upped in 64 bit Railworks.
Re: Something Weird with WS Scenarios

Posted:
Wed Dec 19, 2018 6:02 pm
by peterhayes
Edwin
Don't you need to unpack the 'routeproperties.xml' first from any route that has an .ap file structure? Or does namemyroute still display any WS scenario in an unpacked .ap file route?
In each scenario you are looking for a line of text similar to this:
[Scenario GUID reading ScenarioProperties.xml failed – ‘.’, hexadecimal value 0x00, is an invalid character. Line xx, position xx]
That is the scenario(s) that may be corrupting TS 2019
pH
Re: Something Weird with WS Scenarios

Posted:
Wed Dec 19, 2018 6:42 pm
by buzz456
Name my route does not show anything on stuff in the .ap
Re: Something Weird with WS Scenarios

Posted:
Wed Dec 19, 2018 7:31 pm
by ChrisOnline
RW_Tools has an optino in the menu to extract each RouteProperties.xml file from the Route .ap files to make them all visible
Re: Something Weird with WS Scenarios

Posted:
Wed Dec 19, 2018 7:57 pm
by qwhite451
i wanted to test my theory so i decided once again to bork my game so i went downloaded just one scenario from Steam i got an instant access violation now the game won't start with either 32bit or the 64 bit exe so i have to uninstall and reinstall the game again
Re: Something Weird with WS Scenarios

Posted:
Wed Dec 19, 2018 9:35 pm
by buzz456
qwhite451 wrote:i wanted to test my theory so i decided once again to bork my game so i went downloaded just one scenario from Steam i got an instant access violation now the game won't start with either 32bit or the 64 bit exe so i have to uninstall and reinstall the game again
Actually unless something real strange is going on all you should have to do is uninstall that scenario and the game should run again.
Re: Something Weird with WS Scenarios

Posted:
Wed Dec 19, 2018 10:07 pm
by qwhite451
I tried that and it won't start even after i removed the scenario deleted the entire 24010 folder just to make sure nothing was left behind double checked the route the scenario was for to make sure it was gone the game will start..but it won't go past the loading before the screen blinks and the crash reporter thing flashes and then i have to kill the game through the task manager and the access violation thingy is present
Re: Something Weird with WS Scenarios

Posted:
Thu Dec 20, 2018 9:22 am
by ChrisOnline
TS2019 loads in two stages:
1. Load the game engine etc
2. Update the Scenario Database
Stage 2 starts when the splash screen appears and text at the bottom tells you it is updating the scenario database
If you get to the splash screen and that text, then you know the game engine itself has loaded fine, and any problems you have are almost certainly related to the scenarios. That may be a specific problem scenario, may be volume of scenarios. I have also found that sometimes a workshop scenario only partially downloads, causing an error when you try to open up, so check any recent Workshop scenarios
So if you get to "stage 2" then reinstalling the game is fruitless and quite silly, as it will cause all sorts of hassle with reskins, 3rd party work, your own tweaks, and so on, all unnecessarily. Avoid at all cost!
Here's something else to try:
1. Copy and paste-back your Routes folder (so you get one called Routes - copy)
2. In the Routes folder, delete ALL routes expect one with limited scenarios, maybe TestTrak or whatever. Make sure you keep all the files in the root of the folder
3. Now there are virtually no scenarios. See if TS2019 opens OK to the main menu
If it works OK (and it will be fast due to the lack of scenarios), that is further evidence that the scenarios are the problem. You can either go back to the original Routes folder and try your luck further, or progressively copy over Route folders from the "copy" to the now current folder. Once you hit a problem, you may have identified a source of trouble.
BTW once open, the game will reinstall automatically some further routes and also workshop scenarios, but over time. Don't let that deistract you from the issue at hand
Chris
Re: Something Weird with WS Scenarios

Posted:
Thu Dec 20, 2018 10:57 am
by buzz456
Good information Chris!

Re: Something Weird with WS Scenarios

Posted:
Thu Dec 20, 2018 12:57 pm
by qwhite451
After fighting with it yesterday for the better part of the day i tried something different i went bought a busload of marketplace scenarios mini packs whatever they are called installed every single pack not one time did it throw the access violation error...so for the meantime i'll play with those but im very grateful for the help that was given here
Re: Something Weird with WS Scenarios

Posted:
Tue Jan 15, 2019 5:02 pm
by gtrtroger
I wanted to come back to this. Last night I had this issue. Had downloaded some Workshop scenarios and went to run the sim...instant crash. Ok. This has happened before. I deleted (unselected via sim) the scenarios I had just downloaded. Re ran the sim....crash. Ok, ran RWInfo and check scenarios for each route and found a bunch of Workshop scenarios that the game didn’t even list plus the ones I just deleted. So, I ran the RWInfo Export Scenario tool and it created a cvs file with a total of 996 scenarios! Humm. So, I manually hunted down every Workshop Scenario listed and removed it by the roots. I re ran the RWInfo Export Scenario tool and it now reported 898 scenarios. Ran the sim and it started up just fine.
Now, the remaining scenarios are either “Career”, “Standard” or “Freeroam” only. I figure I have maybe 40 scenarios that I’ve either downloaded from RWA, created myself, or got from friends. That means that approximately 850 scenarios came from/with DLC....amazing!
So, what happens when I buy more DLC (with accompanying scenarios) and reach a total of 996 (+/-) scenarios and crash again???? I think we are vastly approaching some kind of program variable (like SCENARIO_LIMIT) within the sim which needs to be examined by DTG to see what will happen as we move forward.....mainly because this is NOT a Access Violation Error as reported, but because we could be in for some big trouble in the not to distant future.
What say you?
Re: Something Weird with WS Scenarios

Posted:
Tue Jan 15, 2019 5:47 pm
by buzz456
Where is the best place to D/L RWInfo from?
Re: Something Weird with WS Scenarios

Posted:
Tue Jan 15, 2019 6:05 pm
by buzz456
I just D/L this nifty program.......Where have I been?..... and discovered I have just under 2000 scenarios so that doesn't appear to be the problem.