Page 1 of 1

TS 2017, Async, and Windows 2010

Unread postPosted: Thu Sep 22, 2016 10:29 am
by OldProf
A few days ago, I sent the following message to DTG support:
"I've been using the EnableAsyncKeys (no leading dash) launch option in Train Simulator for quite a long time, but since Windows 10 came along, it doesn't work anymore. This began before the arrival of TS 2017 and still does not work with TS 2017. A friend who also runs TS 2017 under Windows 10 has told me that it does work for him. Is there some other adjustment that will bring it back to life?

Also, is a complete list of the TS launch options available somewhere? If so, please send me a link or the URL."

Today, I received the following reply:
"It appears from your Ticket, that recent changes made by Windows 10 may have affected your TS 2017 installation changes made by Microsoft are outside our control.

As far as I am aware there is not a list of launch options available for TS 2017."

That DTG would pass the buck to Microsoft does not surprise me, but the absence of a list of launch options leads me to wonder whether DTG has discontinued this feature.

!!det!! "Just the facts, Mam." !!howdy!!

Re: TS 2017, Async, and Windows 2010

Unread postPosted: Thu Sep 22, 2016 11:59 am
by Chacal
Tech support persons are usually very litteral.
He has no document named "TS2017 launch options".
Actually, such a list was never published by DTG. All we know about launch options comes from a few forum posts.

Remember asynch keys conflict with the new advanced braking feature, they both use Ctrl-1 to Ctrl-4.

Re: TS 2017, Async, and Windows 2010

Unread postPosted: Thu Sep 22, 2016 2:01 pm
by OldProf
Chacal wrote:Tech support persons are usually very litteral.
He has no document named "TS2017 launch options".
Actually, such a list was never published by DTG. All we know about launch options comes from a few forum posts.

Remember asynch keys conflict with the new advanced braking feature, they both use Ctrl-1 to Ctrl-4.


Since I seldom drive locos with advanced braking, I had indeed forgotten that. But Ctrl-2, -3, and 5 don't work for me either. Thanks for the reminder, anyway.

Re: TS 2017, Async, and Windows 2010

Unread postPosted: Thu Sep 22, 2016 3:05 pm
by trev123
Is that the command that allows you to increase the time up to 5 times faster ? I used that a lot when you had a long wait at a station or siding. Lost the command when I did a fresh install of Steam and forgot the commands name.

Re: TS 2017, Async, and Windows 2010

Unread postPosted: Thu Sep 22, 2016 3:46 pm
by peterhayes
Tom (OP)
Some of the command line options were "lost" when there was a "steam" update a few weeks ago. Supposedly fixed but some may still not work.
Have you thought about creating a .bat file and create a shortcut on the desktop, using that to open TS2017, with EnableAsyncKeys in it, to see if that allows it to work.
Something like this: Drive:\STEAM\Steamapps\common\Railworks.exe EnableAsyncKeys . Note no hyphen in front of "Enable", just a space.
Worth a try?
pH

Re: TS 2017, Async, and Windows 2010

Unread postPosted: Fri Sep 23, 2016 10:00 am
by OldProf
peterhayes wrote:Tom (OP)
Some of the command line options were "lost" when there was a "steam" update a few weeks ago. Supposedly fixed but some may still not work.
Have you thought about creating a .bat file and create a shortcut on the desktop, using that to open TS2017, with EnableAsyncKeys in it, to see if that allows it to work.
Something like this: Drive:\STEAM\Steamapps\common\Railworks.exe EnableAsyncKeys . Note no hyphen in front of "Enable", just a space.
Worth a try?
pH


That does sound worth a try, Peter. I have to admit, though, that I've forgotten how to create a batch file *!embar*! .

Re: TS 2017, Async, and Windows 2010

Unread postPosted: Fri Sep 23, 2016 4:23 pm
by peterhayes

Re: TS 2017, Async, and Windows 2010

Unread postPosted: Fri Sep 23, 2016 9:25 pm
by trev123
As no one answered my question I found the answer myself. http://forums.steampowered.com/forums/s ... ?t=2960841

Re: TS 2017, Async, and Windows 2010

Unread postPosted: Fri Sep 23, 2016 9:29 pm
by trev123
The command was still in my launch option and has not worked since TS2016.

Re: TS 2017, Async, and Windows 2010

Unread postPosted: Sat Sep 24, 2016 5:59 am
by GreatNortherner
Hi,

I believe there is another workaround that doesn't require creating batch files:

- create a new shortcut to Railworks.exe
- add all desired command line switches to the shortcut's Target field, after the "path-to-RW\Railworks.exe" entry, just like you would with any other game/application

Now use this shortcut to launch the game instead of the one that Steam created for you and it should all work again. (I think).

Cheers
Michael

Re: TS 2017, Async, and Windows 2010

Unread postPosted: Sat Sep 24, 2016 9:54 am
by OldProf
Thanks for the tips, fellows. I opted for Michael's method, creating a new shortcut as follows: "C:\Program Files (x86)\Steam\steamapps\common\RailWorks\RailWorks.exe" EnableAsyncKeys" and used it with the Run As Administrator option to launch TS2017, but when I tried implementing the AsyncKeys none of the key combinations worked.

With Ctrl+1, 2, 3, and 4 usurped by TS braking options, the whole exercise seems pointless anyway, since the Ctrl+5 option was nearly always reckless. That TS programmers couldn't find a different set of control keys for brakes seemed odd, until the techie who replied to my "issue" admitted that she knew nothing about a list of launch options. Phooey!

I do appreciate your efforts, as always.