TS2018 won't open

[gptech]

but I do not know how to decode it from technical speak to fix it

A little late, but possibly handy for in the future....

Let's look at the non-technical bits...

Code: Select all

[Data Management 07:19:07] Trace cRecordSet.cpp : 367 = Record set marked modified 1
[Engine 07:19:07] Trace Pc\cHcDisplayManagerPc.cpp : 596 = Creating device

The game's found a data record that it recognises as being modified...
then it starts creating/loading a device---could be anything; keyboard, mouse, graphics card, RailDriver....

Code: Select all

[Engine 07:19:08] Trace Pc\cHcDisplayManagerPc.cpp : 611 = Failed to create hardware vertex processing d3d device hr: -2005530516
[Engine 07:19:09] Trace Pc\cHcDisplayManagerPc.cpp : 623 = Failed to create mixed vertex processing d3d device hr: -2005530516

Then it fails to create something to do with hardware --- a big clue, you've recently changed some hardware.
More clues..."vertex", associated with graphical routines...for d3d read Direct 3D, part of the DirectX routines...see where it's all pointing?

I've had to wait almost 7 weeks from start to today with DTG

Are you surprised?...to replicate the issue they'd have to swap out their hardware and make exactly the same error that your system has suffered from---practically impossible to do as the *error* is almost certainly not entirely due to you having done something really wrong--your local security policies are unique to your machine, so if they were involved in any way it'd be even less likely to be replicated. It's not been a game error/problem either, you can't expect DTG to support every glitch on a PC that can result in the game not running.

within 24 hours on here the community has got me going again.

It's also not DTG's fault that it took you almost 6 weeks and 5 days before asking in here ---you'll always get good/better support from any user group for any application; the users have more time to delve into things, more minds to bounce odd ideas about, more 'real world' experience of the application and it's foibles than any support department, will collectively have managed to break the application in many more ways than the producers have ever imagined testing for......and more importantly, more scope for getting lucky or for dropping on the weird combinations of changes that fix things.

[alanch]

Such a simple thing which means I've had to wait almost 7 weeks from start to today with DTG

An afterthought - if you tell DTG about this solution they may not take so long to respond next time someone reports a similar problem. May not . . .

[peterfhayes]

Alanch
Good point. Something along the lines.

If you change your video card at any time - you should first remove the old drivers via Windows install the latest drivers for the new card.
Close Steam and TS.
Navigate to \STEAM\steamapps\common\RailWorks\Content and delete/rename the playerprofiles.bin file.
All video settings are now default.
Restart Steam and TS.
In TS reapply your settings as required.

The problem is that it may only be a solution for some systems, ie the initial issue is idiosyncratic and may have nothing to do with changing the video card, and the fix may not work.

This solution was used in FS9/FSX way back in he day, by ensuring that FS9/FSX.cfg file did not contain references to the old and the new card

[gptech]

Would a driver removal really be sound advice when upgrading a 10xx card to another ?

[peterfhayes]

Gary
Apparently it would to make sure no remnants of the old card are left behind - again the advice is from the FS9/FSX era.
Really in practice probably not but it does cover all of the bases. So optional.
I recently upgraded from a GTX 970 to a 1080 - did nothing and everything in TS was fine - BUT - if you have problems you may neeed a more intensive solution.
pH

[gptech]

....to make sure no remnants of the old card are left behind - again the advice is from the FS9/FSX era.Really in practice probably not but it does cover all of the bases.

Not if it's an official DTG statement though Peter; they support TS as it is today, on today's hardware/OS and it would be foolish for them to post advice that probably has no real effect in that context---I didn't un-install drivers when I moved up to a 970 from a 960; remember NVidia's drivers cover a huge range of models/levels.
Nothing wrong with an employee of DTG passing the tip/information on as his/her own personal suggestion, when all else has failed, but as it's well outside of DTG's support commitment/remit they'd never do it officially--and rightly so.
Things that were the 'done thing' in the past often don't need doing as time passes--clearing the cache is no longer something that has to be done when installing a reskin for example, though we still suggest it often out of habit.

Completely removing an old driver still has some merit if going from nVidia to AMD or vice-versa, but even then not something that everybody would have to do. If I recall rightly AMD changed how their installer works to completely remove any traces of the drivers, so using tools such as CC Cleaner is no longer needed.
That raises another point as to why DTG can't/won't support the resolving of issues such as this officially---if a *fix* calls for other software to be used they'd have to be in a position to officially support/endorse such software.

[peterfhayes]

Gary
Good points - I agree totally!
For me removing a driver for an older card is a bit like DTG's universal solution of verifying the game cache - it will work sometimes and not others and it (under normal circumstances) does no harm! So why not do it?

pH

[gptech]

Unfortunately peter that's now how the support side of IT works---it's not about fixing anything but being able to flag a support request as actioned.

"I'm having bother with your game"
"Verify the cache"

gets that ticket off the system, much better for the official figures than

"I'm having bother with your game"
"Remove playerprofiles.bin and let the game build a new one"
"Tried that, didn't work"
"Check your drivers, download "Magic PC fixer"
"How do I get that to work?"
"I'll check the manual....I'll get back to you"
"Hello....3 days ago somebody said they'd get back to me..."
"and just what is your problem sir?"
"I'm having bother with your game............."

[alanch]

Gary
Good points - I agree totally!
For me removing a driver for an older card is a bit like DTG's universal solution of verifying the game cache - it will work sometimes and not others and it (under normal circumstances) does no harm! So why not do it?

pH

But in this case it was totally irrelevant as the problem was with Playerprofiles.bin, which one would think they should know about.

[gptech]

But in this case it was totally irrelevant as the problem was with Playerprofiles.bin, which one would think they should know about.

But was it?

Thank you Alanch for the answer, and thank you tnleeuw01 for pointing it out again

You provided PlayerProfiles, but Tim wrote

It seems that sometimes the OS no longer sees the NVidia card and tries to start all games on the CPU's built-in GPU

which is a Windows issue, nothing to do with the game.

Going back to

which one would think they should know about.

two of us have posted about not having any bother after a GPU upgrade, so is the PlayerProfiles effect one caused by the local security settings in force rather than a known issue within the game's code? If the latter, then it ain't DTG's responsibility and they can't nor won't give *official* recognition to workarounds that we may have heard of/figured out.

[JunGRail]

Hello all

Sorry to dig up an old thread but I am having this issue too and followed alanach's advice but to no avail. It seems nvcuda.dll fails upon launch with the latest Nvidia driver 398.xx

I thought problem solved but still no problem

[749006]

Hello all

Sorry to dig up an old thread but I am having this issue too and followed alanach's advice but to no avail. It seems nvcuda.dll fails upon launch with the latest Nvidia driver 398.xx

I thought problem solved but still no problem

Roll back to an earlier version of Nvidia and see if that cures the problem