General discussion

[crosstie]

Select CUDA/gpus. It should show there which graphics you are using.

[ex-railwayman]

Right, fine, gotcha, thank you for that, it now shows my GTX1060 6Gb card. In fact, if you tweak a lot of the Global Settings they then show up in the Program settings for each game, I'll have a dabble and see what I can come up with.

Cheerz. Steve.

[mindenjohn]

I have had both 64 and 32 bit crash this afternoon in the same route (Blackwood Creek) with an exception code box coming up asking me to contact DTG customer support. The exception stated an Access Violation whatever that is - are 3rd party routes at risk?

[fecrails]

To change the default GPU, open the Nvidia control panel, select manage 3D settings, select the program settings tab, click the add button, navigate to the railworks 64 bit .exe file and select it, then choose your high performance GPU as the preferred graphics processor in the drop down menu.

Which drop down menu, please, I'm confused now, this is as far as I got, after selecting the railworks64bit.exe, I applied it, but, I can't find a preferred graphics processor anywhere, help.........

Cheerz. Steve.

nVidia settings today.jpg

Looks like you've got things squared away with crosstie's help. I wrote those original instructions from memory away from my gaming PC while on a MacBook.

[buzz456]

I have had both 64 and 32 bit crash this afternoon in the same route (Blackwood Creek) with an exception code box coming up asking me to contact DTG customer support. The exception stated an Access Violation whatever that is - are 3rd party routes at risk?

I haven't run that particular route however I have run several third party routes with no problems so I would say generally the answer is no.

[Overshoe]

I'm really disappointed. I can't find a single thing to whine and cry about. Thanks DTG.

[mikesimpson]

If your Railworks 64 desktop icon does not work, right click it, go to Properties/compatability and tick the box to always run it as administrator. Then the 64 bit version starts fine.

Mike

[buzz456]

I'm really disappointed. I can't find a single thing to whine and cry about. Thanks DTG.

[TheKman]

I have had both 64 and 32 bit crash this afternoon in the same route (Blackwood Creek) with an exception code box coming up asking me to contact DTG customer support. The exception stated an Access Violation whatever that is - are 3rd party routes at risk?

I haven't run that particular route however I have run several third party routes with no problems so I would say generally the answer is no.

Last night, Running the 32 bit, (Have not configured for the 64 yet)Tehachapi Pass crashed and I also got the Access Violation. Turned out that a scenario, Amtrak #11 Coast Starlight Detour, which I got form 3DTrains was the culprit. Tossed it out and all was fine again. Have not looked into why that scenario has a possible problem.

[cnbalasub]

Back to Mike Simpson' message -- I have followed the instructions about right-click the exe of Railworks64 on desktop to open Properties then open Compatibility and put the mark in the box " Run this program as an administrator " then click " Apply " on bottom right of the box. Then I went over to desktop to click the icon of Railworks64 and after click the icon then the message appear " Train Simulator Please login to Steam " Guess that I did not follow properly and I have tried this three times then gave up because of kept asking me to login to Steam. Did I follow the instructions correctly or not? Let me know.

John

[RailWanderer]

I have had both 64 and 32 bit crash this afternoon in the same route (Blackwood Creek) with an exception code box coming up asking me to contact DTG customer support. The exception stated an Access Violation whatever that is - are 3rd party routes at risk?

I haven't run that particular route however I have run several third party routes with no problems so I would say generally the answer is no.

Last night, Running the 32 bit, (Have not configured for the 64 yet)Tehachapi Pass crashed and I also got the Access Violation. Turned out that a scenario, Amtrak #11 Coast Starlight Detour, which I got form 3DTrains was the culprit. Tossed it out and all was fine again. Have not looked into why that scenario has a possible problem.

I had two errors so far, not sure I can blame the scenario on these as it was the base freeroam scenario. The route runs fine in another instance of TS with the same route, the same situation, and moves.

I got the first one while operating a turnout and then again while operating a turntable. Once the loco was past the turnout there was no response with the loco, and after saving the session and trying to resume it I got this message. Same happened with the turntable.



The second one was after coupling to a train with a loco already attached, and the switcher was coupling to the cars to bring them to the storage yard. Once coupled to the train(the switcher) I uncoupled the other loco(the road engine) and proceeded to pull the cars away from the road engine, poof crash. This happened in both x64 and x32 bit modes of the same situation and moves.



Curious, there was a crash report sent on both errors, that's different a text file that tells you the crash report was sent. I certainly hope they can figure it out.

[TheRailWorkshop]

After generating distant mountains from x64 version.
For a moment, I see no black patch lines as earlier in x86 version.

[ex-railwayman]

I have a frame rate showing on my monitor screen now, this is only when I go into the 64-bit version, unsure how I can get rid of it, any suggestions, please?

Cheerz. Steve.

TS19 64-bit.jpg

[RudiJaeger]

Back to Mike Simpson' message -- I have followed the instructions about right-click the exe of Railworks64 on desktop to open Properties then open Compatibility and put the mark in the box " Run this program as an administrator " then click " Apply " on bottom right of the box. Then I went over to desktop to click the icon of Railworks64 and after click the icon then the message appear " Train Simulator Please login to Steam " Guess that I did not follow properly and I have tried this three times then gave up because of kept asking me to login to Steam. Did I follow the instructions correctly or not? Let me know.

John

John, are you trying to start in off-line mode? I posted the following quote in the other (currently) thread, but thought it might be helpful to post here as well. Please see item-6 in my narrative and give it a go:

Full narrative of my upgrade experience follows:

1. Started Steam client (not the sim) and Railworks began performing the update automatically. Afterwards it prompted a restart to update the Steam Client, which I did.

2. Rather than start the sim from the Steam client, I located the new RailWorksx64.exe in the root folder, then right-clicked and selected "properties" and in the "compatibility" tab, selected "run this program as administrator" and clicked "apply". Then again right-clicked on the exe and selected "send to - desktop (create shortcut). Then double-clicked the new shortcut, which started the x64 bit edition as evidenced when selecting the "settings" button, which displayed "v65.6f (x64)" in the lower left corner of the settings window. Started a free roam scenario to test, and all was okay.

3. Went back into settings > tools and selected "clear cache" and "restart". Upon restart, selected "settings" and discovered that the x32 bit version was running instead. Closed the sim and selected the x64 bit shortcut to manually complete the x64 bit restart. Confirmed x64 bit was running in "settings".

4. Checked workshop content by running a scenario on the Bergen - all okay.

5. Checked third-party non-workshop content by running the MRL route - all okay.

6. Exited the sim and Steam Client, then un-plugged the dsl cable to check off-line functionality. Clicked on the x64bit shortcut and was prompted to login to Steam, so that was a "fail". So I clicked on the old x32 bit shortcut, and the "start in off-line mode" prompt appeared as usual, then started the x32 bit version and exited, leaving the Steam Client icon (off-line) in the system tray. Then clicked again on the x64 bit icon, and this time it worked. So, as long as I go into off-line mode using the 32 bit version and exit, I can bring up the x64 bit version (as long as I don't exit the off-line Steam Client). Hopefully this gets fixed soon so we don't have to keep doing the shortcut dance. Other than that, I am very pleased with the process, and look forward to discovering the new capabilities of the x64 bit upgrade.

Afterwards, I discovered it all comes down to the Steam Client allowing for placement of a shortcut on the desktop, which I did years ago, but it's only for the 32-bit version; there is currently no similar option to do the same for the x64 bit version, which must be done using the exe in the root folder. The problem seems to be, the 32-bit shortcut offered by the Steam Client uses a url as it's target, while the user-created x64 bit shortcut targets the RailWorksx64.exe directly. So in off-line mode, the Steam client will recognize the url-based shortcut but not the exe-based shortcut, telling us we must login to Steam. So that's why the url-based 32-bit version has to be started first, to bring up the client; then we can exit and start the x64 bit shortcut with no issues. So until the on-line Steam client offers to create a shortcut for the x64 bit version, this seems to be the best work-around to run x64 bit in off-line mode.

Edit: I should have mentioned; unless I'm route building (google overlay) or updating something, I always keep my gaming rig unplugged and off-line. Just overly-cautious I suppose.

[artimrj]

I start from the Steam Library. A small window pops up and asks for 32 or 64.