TS2019 64bit scenario access violation

[alanch]

Never ever had an access violation under 32 but, this is an event brought about by 64 bit. Obviously, it is a dtg problem since it has occurred with this new version of ts imo.

Are you saying that you never had a Dump File message or a crash to desktop while running on 32 bit? That's all the Access Violations are, dressed up with an error message in the 64 bit version.

[smarty2]

Didn't realise that! Thought it was something new to the 64 bit version? Live and learn.

[alanch]

Didn't realise that! Thought it was something new to the 64 bit version? Live and learn.

It sends the reports back to 'home' as well - see the thread here http://forums.uktrainsim.com/viewtopic. ... 1&t=150122

[gptech]

Thought it was something new to the 64 bit version

You're not the only one Martin, many have seen the message and immediately though the sky was falling rather then sitting back and reviewing what had happened---load the game OK; load the route selection OK; select a scenario OK; scenario starts to load but falls over when loading ……………..so it must be a virus, or a faulty RAM module, or DTG making a bóllocks of it---anything but "I wonder if the scenario has a problem?...perhaps I should open it in the editor and see if anything obvious strikes me...."

It's been written more than once, by more than me, that the Access Violation message is a catch all message, covering a multitude of reasons, which is why it's so bloody difficult to track down just what has done it.
We can't discount a connection with the introduction of 64bit of course, the underlying code/system may just be less tolerant of issues/faults (not really a bad thing if it means we start doing things *properly* as a matter of course) but the error message doesn't tell us exactly what those issues/faults may be---that's where we have to roll our sleeves up a wee bit. Those that can't do it/don't want to do it can ask if anybody else could/would.

[shinymac]

Hi Gary and others

OK I think things are getting a bit heated here....thanks to those who have supported my feelings re TS64 bit. Like has been said...I and MANY others just want to boot up TS when they have time to relax...and pick a random scenario from their list...and play it from start to finish without it crashing ! They probably dont have time,patience, or the skills to have to edit and tweak this that and the other..just to get a scenario to work. I do try a LITTLE tweaking with things like RW Tools..but am not willing to delve much into the TS Editor to correct things.

I have ran TS since 2012 and NEVER EVER have I even heard of an "Access Violation" nor experienced one since the advent of TS64 Bit came along .

So from those more knowledgable replies on here...do I detect that it is possible that some scenarios that have worked without problems for years.might now under 64bit..NOT work ? Or am I wrong ?

And for those that asked..I have got 16Gb of RAM but only a GTX 660 graphics card which continues to perform very well considering its age.

Derek

[shinymac]

Incidentally peterhayes...

I dont own TS2109....I am still a poor pauper running TS2019

Derek

[lenfish]

Wonder if the access violation message is in fact a more descriptive SBHH (that told you nothing as to what the actual error was). I say this because on certain scenarios where I used to get an SBHH on loading I now get the access violation on loading both in 32 and 64 bit. Still none the wiser as to the actual cause though.

Regards,

Len

[gptech]

They probably dont have time,patience, or the skills to have to edit and tweak this that and the other..just to get a scenario to work.

Derek, no argument there so your options are to give up on the scenario; notify the provider of the scenario that you think there's an issue; ask if anybody else could look at it or a combination of those. Nobody has said you HAVE to do it all yourself!

I have ran TS since 2012 and NEVER EVER have I even heard of an "Access Violation" nor experienced one since the advent of TS64 Bit came along .

But you've had a "Something bad has happened" or "Failed to create crash dump" message...….essentially the same thing, just a general notification that something has happened to prevent the game running but no further details are available. It could write Hamlet's Soliloquy on screen and you'd know as much about the problem from that.

do I detect that it is possible that some scenarios that have worked without problems for years.might now under 64bit..NOT work

Yes, just as it's possible that the addition of a reskin with a slightly dodgy .bin file could bring the whole game crashing down. There is no cast iron guarantee that everything will work forever. Don't forget we've had scenarios not working after the *normal* yearly updates so 64bit cannot be blamed for every single instance of things not flowing as smooth as we'd like.
Have you found one of those scenarios yet?

but am not willing to delve much into the TS Editor to correct things.

Why not?.....it's as powerful and useful as RW Tools; can do things that RW Tools can't; can make doing some things easier than using RW Tools..... CONFIDENCE, that's all you need. There's no need to dive in and edit a huge scenario at your first attempt, but you've nothing to lose by popping into the editor and looking have you? OK, what you see might be beyond what you know how to do, but could/would point whoever is going to do the *fixing* in the right direction, so just ask.

[gptech]

Derek, have you tried that Chiltern scenario again?

One crash doesn't make it flawed, nor does it make TS2019 flawed...it's only when problems always occur that needs looking at.

[alanch]

I have ran TS since 2012 and NEVER EVER have I even heard of an "Access Violation" nor experienced one since the advent of TS64 Bit came along .

I'll repeat my message from above - are you saying that you never had a Dump File message or a crash to desktop while running on 32 bit? That's all the Access Violations are, dressed up with an error message in the 64 bit version.

My experience is that, with one exception, all the scenarios that I have tried that failed to run in 32 bit, either at the start or later on, now run to completion in 64 bit. A few other scenarios have crashed with exception errors messages, and I'll have a good look at them when I have some time, as Gary suggests.

[shinymac]

Hi Gary, Alan et al

Of course I have had "dump file" errors and crashes before ....so have I missed some important briefing by DTG or the likes...which clearly informs all trainsim users that "access violation" messages are really the same as dump file and many other error messages then ?

Maybe I havent explained myself properly in my other messages...but I dont have the patience or knowledge or interest...to spend time reporting scenario problems to the creator...nor spend time tweaking the TS editor to fix problems when I may make matters a lot worse in doing so.

All you guys are really kind and supportive which I appreciate..but...all I want to do is pick a scenario and......drive a train...period !

Perhaps I am living in a perfect world....but it is what it is.

If anyone can try the scenario that caused my probs recently let me know and I will pass on the name of it in a day or do when I am able.

Thanks guys !
Derek

[peterfhayes]

Derek
I posted my experiences with this JUST Trains scenario (NOT DTG) above. I have now run it 6 times in TS2019 54-bit mode and it does not crash BUT it does in 32-bit mode.
I asked the delicate question were you sure you were in 64 and NOT 32-bit mode, It is easy to do.

You really should contact JT and report this as it is there problem not DTG's

Regards
pH

[shinymac]

Hi Peter

Sorry for any confusion re DTG/Just Trains....my reference to DTG was because this scenario worked fine in 32 Bit...but now didnt when I ran 64bit (and I am certain I was in 64 bit when it crashed !)..so the chances are its not the fault of JT as it ran fine until 64 bit by DTG came along.

Derek

[gptech]

all I want to do is pick a scenario and......drive a train

Have you tried the scenario again?

I dont have the patience or knowledge or interest...to spend time reporting scenario problems to the creator

If you don't report it, that means that only you can fix it....you have to do a little bit of the leg work at least Derek!

so have I missed some important briefing by DTG or the likes...which clearly informs all trainsim users that "access violation" messages are really the same as dump file and many other error messages then ?

Probably...the message first appeared in Vista (I think....may have been Win8 but it's been around for ages) and you'll find hundreds of posts and fixes......all dealing with hundreds of different pieces of software which illustrates how much of a generic message it is. It's not a message from the game, it's from Windows, so it's something that's happened after TS has fallen over---think "failed to create crash dump" which is simply a message saying that the contents of memory couldn't be saved (dumped) to disc to act as a diagnostic aid. In essence that's no different to "Access violation....(because the data at location X,Y,Z no longer exists the location is empty and as you can't read (access) empty memory it's in violation of the access protocol)" It's all just different terminology.

If the Chiltern scenario is 1Y45, then it does have instructions that end with a 'stop at' for the portals rather than a 'final destination' being the portal---whether that is significant is still to be determined, but past experience in editing faulting scenarios suggests that in some cases it is. That's probably/possibly more relevant in 32bit than 64 as 64's greater access to RAM could give the game more latitude when it comes to the 'niggly' type of fault conditions. Once again, these issues need reporting so that those with the patience, knowledge and interest can have a look and maybe come up with a working set of guidelines for the future.
Even if we're all wrong and it turns out to be a real issue buried deep in the game we'd at least be doing something constructive rather than wringing our hands, and time spent gaining information/knowledge/skills is never truly wasted time---it only needs a "oh...I remember doing A,B,C once...let's see if that helps in this case..." when another issue crops up to make looking at stuff now well worth the time.

[gptech]

I have now run it 6 times in TS2019 54-bit mode and it does not crash BUT it does in 32-bit mode

so the chances are its not the fault of JT as it ran fine until 64 bit by DTG came along.

Pistols at dawn?

You both have differing results...what else do you have that's the same but different?……

Your PCs for starters, then the configuration of your PCs, and then the configuration of your installation of TS.....

Can you see Derek that when this kind of *it works for me, but not for you* problem can only be put to bed by working at it?