General discussion

[buzz456]

I don't and didn't have that .bat file. I launched from the Steam Library. A window popped up and asked for 32 or 64 bit. No muss no fuss.

It's the exact reason why I don't launch it through Steam anymore. Instead, I added a shortcut to the 64 bit version to the side menu.

Gets annoying when trying to fine tune something, and you feel obliged to restart the game several times to be sure it's behaving itself.

Huh?

[SAR704]

When I select TS through the Steam interface (list of games), it shows 'Train Simulator', with play (TS) 32 bit edition, or 64 bit edition. I haven't found a way to set the latter as default though the Steam interface. So I added a shortcut to 64 bit edition to the start menu.

Essentially it removes the need to have to manually select the same option each time, since I am currently using the aforementioned more or less exclusively.

[buzz456]

When I select TS through the Steam interface (list of games), it shows 'Train Simulator', with play (TS) 32 bit edition, or 64 bit edition. I haven't found a way to set the latter as default though the Steam interface. So I added a shortcut to 64 bit edition to the start menu.

Essentially it removes the need to have to manually select the same option each time, since I am currently using the aforementioned more or less exclusively.

Aah, now I understand. There is a exe 64 in the RailWorks folder. I made a shortcut to it and put it on my desktop so now I have both shortcuts there. Since it looks like I will be using the 64 bit all of the time also eventually I will probably get rid of the 32bit one.

[BoostedFridge]

Since it looks like I will be using the 64 bit all of the time also eventually I will probably get rid of the 32bit one.

There are a lot of reports still circulating that laying track in the route editor in the 64 bit version is causing issues, so I'm keeping both around just in case.

[okievokey]

A note of thanks to the folks at VNHRR for the quick work releasing a patch for Springfield Line. Got it installed and all is running as it should.
A word of thanks also to RWA. Now that this site is back up again, I can purchase The Cascadian as I had planned to do.
Doug

[jgvaughan]

Since it looks like I will be using the 64 bit all of the time also eventually I will probably get rid of the 32bit one.

There are a lot of reports still circulating that laying track in the route editor in the 64-bit version is causing issues, so I'm keeping both around just in case.

Not sure what issues those may be. I had about 20% of the 45 miles of track laid in the route I'm putting together. I found some things I didn't like so decided to start again from the beginning. Have been working strictly in the 64-bit version and no issues at all. I've laid over 90% of the route and I haven't experienced any glitches, issues, or 'oh sh*t that doesn't work correctly' situations. I also think the editor performs more smoothly in the 64-bit version, not as 'jerky' from a video perspective.

I've been doing some of the terrain modeling as I've progressed in some of the areas where I'm pretty confident in how the terrain will be there and that has gone well also.

I'd be interested in hearing of any issues that might exist so that I can watch for them.

[Dash7Studios]

I'll hop onto the bandwagon and say a little bit about the 64x bit update.

Let me first sum it up by saying this: I still run 32x bit.

The 64x bit update, once installed with a clean install of the game, seemed decent to start. Slightly improved stability, minuscule frame improvements in some areas. Within the first few drives, however, I was already starting to get crashes. Every time I started to edit a cloned route (no details on what I was doing since it's not being done now), crash. Anytime I tried to open the original one....crash. The editor, which is where I spend most of my in-game time, was an unstable mess.

Then the audio glitches started. In general, sounds no longer faded from side to side when moving the camera. They would just harshly switch from one earcup to another, which sounded awful. Doppler effect was broken, it seemed. And in-cab, when facing a certain way with the camera, my audio would start "popping". It was extremely annoying and 100% broke my immersion level. I went to DTG for help, and they suggested I run the "Setupaudio" program, which I did. And, surprise surprise, it didn't do a dern thing. And to this day I still have not gotten a reply back from DTG on what to do.

So, to make a long story short, the 64x bit update, in my opinion, was rushed and not perfected like it could've been. I honestly have no problem sticking to 32x bit. It just goes to show how much DTG cares about their products.

The end!

[ENR3005]

Since it looks like I will be using the 64 bit all of the time also eventually I will probably get rid of the 32bit one.

There are a lot of reports still circulating that laying track in the route editor in the 64-bit version is causing issues, so I'm keeping both around just in case.

Not sure what issues those may be. I had about 20% of the 45 miles of track laid in the route I'm putting together. I found some things I didn't like so decided to start again from the beginning. Have been working strictly in the 64-bit version and no issues at all. I've laid over 90% of the route and I haven't experienced any glitches, issues, or 'oh sh*t that doesn't work correctly' situations. I also think the editor performs more smoothly in the 64-bit version, not as 'jerky' from a video perspective.

I've been doing some of the terrain modeling as I've progressed in some of the areas where I'm pretty confident in how the terrain will be there and that has gone well also.

I'd be interested in hearing of any issues that might exist so that I can watch for them.

Well I have a bit of a different perspective on this as I am a really happy guy with the 64bit at least from an editing point of view. I have to agree about better performance having recently ripped my route completely apart to rid it of two BNSF routes which non-US residents can't buy, in fact I am not sure Stevens is available to anybody as I keep getting an error when I bring it up. There is nothing worse than the thought of creating a route nobody can use which badly needed a solution to save thousands of hours of invested time. Out of frustration with the old 32bit editor, I have almost quit this sim on a half dozen occasions over the past year after not being successful with swapping out 500 or so different assets from specific selected replacement routes with similar assets. A very painful task of several weeks to do where I would use RWTools (thank you Mr. Simpson, brilliant tool) to replace or remove the majority of assets however manual editing within the route was still required which was a route killer in 32bit with crashing common. It was not until the recent upgrade to 64bit that I have found stability with route editor, in fact it rarely crashes vs it 32bit counterpart and I have been able to repair several ancient problem areas when I originally created the route in 2010. As a result, I can now run those areas in 32bit without crashing. Test scenarios have been run in 64bit and for the most part stable. It may not be perfect but with some tweaking by the DTG folks I think it will benefit all.

[_o_OOOO_oo-Kanawha]

Any news or updates on the 64 bits problems with routes, scenarios and editors?

Many of those bugs seem quite obscure and require a thorough examination, understanding of the source code and programming skills.

Strange these problems haven't been detected by DTG themselves.

Wonder how long it will take DTG to fix the 64 bits bugs.

[buzz456]

Maybe the reason DTG hasn't been able to duplicate the issues for the same reason I'm not having any of these? Maybe someone needs to start a poll to see how many are having some kind of issues and for those of us that are not having any.

[artimrj]

Any news or updates on the 64 bits problems with routes, scenarios and editors?

Many of those bugs seem quite obscure and require a thorough examination, understanding of the source code and programming skills.

Strange these problems haven't been detected by DTG themselves.

Wonder how long it will take DTG to fix the 64 bits bugs.

Maybe you should offer them some help and advice?

[_o_OOOO_oo-Kanawha]

DTG is aware and working on it: https://forums.dovetailgames.com/thread ... post-53473

Some 3rd party providers have already updated their products too.

[artimrj]

So then they did detect the problems eh?

[_o_OOOO_oo-Kanawha]

So then they did detect the problems eh?

There is no evidence to be found in any of the posting in any forum that DTG knew about the 64 bits errors before releasing the update to their customers.

I have a hunch the bug is in use of those sFloat32 variables that define the positions of most elements in the tracks.bin and probably also custom markers etc. in scenario.bin files.
sFloat32 probably means 32 bits floating point numbers, and there have to be only a few mal converted numbers that makes the game crash under 64 bits or render the tracks.bin unusable.

Trying to find and repair those instances in 10.000's of lines of source code is a daunting task and with DTG being so low on resources apparently, might take a while.
It has been a month now, and as always communication is very poor.