TS2019 64bit scenario access violation

[shinymac]

I will post the name of the scenario I was driving, as soon as I get the chance. I just cant remember at the moment.

It would be appreciated if someone could give it a run to see if they also experience any issues.

Thanks again

Derek

[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.

Just to be awkward.... I've run the scenario through (if it is 1Y45) in both 32 and 64 bit with no bother--admittedly my copy has been edited to use stock in the location(s) I have it installed in, so that could be a factor. If it is though, it does support the theory that failing scenarios may just need a tiny amount of 'fettling' to suit a particular system/set up. That does absolutely nothing to help find a definitive answer of course, being just as vague as the error messages themselves.

[AlistairS]

I have to say TS2019 seems incredibly unstable whether running in 32bit or 64bit... I've been using TS since the days of Rail Simulator and although there's always been the odd occasion where something crashes, it has been few and far between.

Now, it is verging on the game being unusable, Scenario editor crashes with no provocation and although I have had the access violation quite a few times, it also seems to crash in numerous different ways!!! On a couple of occasions it's literally just closed without any message at all... Over the last week I've tried numerous different combinations of routes, stock etc and there is no single cause... I wish I could revert back to TS2018... I was more than happy with that!!!!

[sprulish]

I have to say TS2019 seems incredibly unstable whether running in 32bit or 64bit... I've been using TS since the days of Rail Simulator and although there's always been the odd occasion where something crashes, it has been few and far between.

Now, it is verging on the game being unusable, Scenario editor crashes with no provocation and although I have had the access violation quite a few times, it also seems to crash in numerous different ways!!! On a couple of occasions it's literally just closed without any message at all... Over the last week I've tried numerous different combinations of routes, stock etc and there is no single cause... I wish I could revert back to TS2018... I was more than happy with that!!!!

I can agree with you. I have had the access violations but only on a handful of routes and scenarios. I have been trying to find a common problem and came to the conclusion that my own quick drive and freeroam scenarios were a probable cause and only on a few third party / workshop routes. It doesn't seem to affect all of them, eg, West Somerset members edition, access violation when exiting on all scenarios, Devon Rails / Railways of Devon & Cornwall no problems at all with any scenarios. At the moment I can't seem to pin it down to any thing specific but now the 32 bit version has become totally unplayable crashing at any time and freezing my screen requiring a complete reboot to get out of it. Unlike you I do have a perfectly good TS2018 plus backups on external drives as I never delete or alter a decent previous version until any bugs are ironed out with yearly core updates. I should say that all my routes and scenarios do play well in 64 bit, it is only when I exit a scenario that I occasionally get the access violation. I agree with others that most of these problems are probably caused by us and the way we set up our systems, I don't have any problems with any DTG or other commercial routes so feel it is up to me to at least try to have a go at trying to find the cause as it might be me that has cocked it up somewhere. This forum is always a great place to pick up any hints and tips and I'm pretty sure that with so many people having the same or similar problems, between us we might find a cure.
Lets keep plugging away
Good luck all
David

[wad53]

I will post the name of the scenario I was driving, as soon as I get the chance. I just cant remember at the moment.

It would be appreciated if someone could give it a run to see if they also experience any issues.

Thanks again

Derek

Out of interest, I ran Scenario 1Y45 (seems to the one under discussion here) using both 32 bit and 64 bit.
I had no problems with either version.

Warren

[MikeDu]

I have to say TS2019 seems incredibly unstable whether running in 32bit or 64bit... I've been using TS since the days of Rail Simulator and although there's always been the odd occasion where something crashes, it has been few and far between.

Now, it is verging on the game being unusable, Scenario editor crashes with no provocation and although I have had the access violation quite a few times, it also seems to crash in numerous different ways!!! On a couple of occasions it's literally just closed without any message at all... Over the last week I've tried numerous different combinations of routes, stock etc and there is no single cause... I wish I could revert back to TS2018... I was more than happy with that!!!!

I have to agree with your comments; I am getting this damn message on Quick Drives, Career and Standard scenarios. I get messages about missing assets, which I know are there, because the offending loco or stock is there in plain view in the platform. Sometimes I can be 30 minutes or more into a scenario, which ran fine before the update only to be dumped out of the game because of an access violation. At other times it's as soon ans the scenario loads.
I have been with Train Simulator since it was launched and this is definitely the worst iteration for me and is close to being uninstalled.

[shinymac]

Hi MikeDu

Sorry to hear about your issues but it puts my mind at rest knowing I am not alone in this regard !
As you say, despite what others have said on the stability side...its simply not good enough. Those responsible should have done their homework fully before releasing what is a product not fit for purpose !!

One wouldnt buy for example a brand new car and then be told " if we have missed something when building your car then fix it yourself but let us know how you fixed it afterwards so we can fix any future ones we build"....would they ??

Hope u get sorted mate

Cheers
Derek

[AlistairS]

... I agree with others that most of these problems are probably caused by us and the way we set up our systems, I don't have any problems with any DTG or other commercial routes so feel it is up to me to at least try to have a go at trying to find the cause as it might be me that has cocked it up somewhere.

I am not sure I do agree with this... one of the main attractions of the TS series, and something that has been a big factor in the appeal of TS, has been the huge range and availability of 3rd party add-ons. Without the massive selection of addons the 'house supplied' items would have no where near the appeal.


Whilst I acknowledge that this causes a higher likelihood of having issues, they should shoulder some of the responsibility for compatibility testing and resolving issues that effect the community that they have been earning off for years!!


I hope they send out an update and fix these issues soon!!!!!

[sprulish]

... I agree with others that most of these problems are probably caused by us and the way we set up our systems, I don't have any problems with any DTG or other commercial routes so feel it is up to me to at least try to have a go at trying to find the cause as it might be me that has cocked it up somewhere.

I am not sure I do agree with this... one of the main attractions of the TS series, and something that has been a big factor in the appeal of TS, has been the huge range and availability of 3rd party add-ons. Without the massive selection of addons the 'house supplied' items would have no where near the appeal.


Whilst I acknowledge that this causes a higher likelihood of having issues, they should shoulder some of the responsibility for compatibility testing and resolving issues that effect the community that they have been earning off for years!!
any kind of cause

I hope they send out an update and fix these issues soon!!!!!

I fully understand what you are saying. I am continuing to try all my routes and scenarios to find which run ok and which crash on exit. It has been mentioned earlier that one possibility might be modified tracks.bin files. I have modified mainly heritage routes, changing track textures and adding or updating scenery. At first it seemed to be these routes that were crashing on me having run perfectly well in TS2018. That theory went out of the window as I have been checking different routes and scenarios and I have at least three modified 3rd party routes that run perfectly well across all scenarios. However I have since discovered that Western Lines Of Scotland is now crashing on default scenarios without any modifications being done, so now affecting DTG routes and scenarios which have run without problems before. Since posting last night I am now getting increasingly frustrated and think it is time DTG checked into this with so many people having these problems. The only good thing at present is that 64 bit crashes to desktop so is easier to restart the game where as 32 bit crashes with a complete freeze requiring a full system restart. Last year when updating from TS2017 to TS2018 I had similar problems with crashing on exit and I couldn't use the consist editor. I fixed both issues by replacing the railworks.exe with the one from TS2017 and it has run perfectly since. Tried the same thing again to see if it would fix the 32 bit but no joy this time.
David

[gptech]

When does "so many" become a large enough number to warrant intervention by DTG?
I'll ask the question I've asked every year post upgrade: are those having bother working on an upgraded copy of the game, or did they install a full new copy?
The problems a few folk are having are exactly the same kinds of errors that are reported yearly; in an ideal world things would go smoothly, but this ain't that kind of world.
Derek, expecting DTG to investigate is fine, but what do you expect them to do if they can't replicate the problem?

[sprulish]

When does "so many" become a large enough number to warrant intervention by DTG?
I'll ask the question I've asked every year post upgrade: are those having bother working on an upgraded copy of the game, or did they install a full new copy?
The problems a few folk are having are exactly the same kinds of errors that are reported yearly; in an ideal world things would go smoothly, but this ain't that kind of world.
Derek, expecting DTG to investigate is fine, but what do you expect them to do if they can't replicate the problem?

Gary have you had similar issues and are you suggesting that installing a fresh new copy may help with these issues?
Regards
David

[peterfhayes]

Gary

When does "so many" become a large enough number to war?rant intervention by DTG

Statistically 5% - that's the tolerance on most things in the world, but let's say 1% considering the vagaries of software and PC builds.
I was under the impression that there around 80,000 TS subscribers, 5% would be 4,000 and 1% 800, in both cases DTG would certainly know about it! (I have seen this subscription figure quoted as high as 800,000 so you would need an awful lot of simmers to complain.)

I would also ask how many of those experiencing problems used the EDITOR prior to the problem? We know that the editor has issues.

Theory: Once you have created an access violation via the Editor/Build is extremely difficult to remove it. What you have done is effectively built the "corrupt" code into the start-up procedures which will "lock" the RAM no matter what route or scenario you want to run. When you fire up TS 2019 either 32/64bit POST editor and you have had a problem ("Access Violation")- it loads the startup code but due to your previous access violation it immediately finds a RAM address that cannot be accessed and stops. Access violation. It's like trying to start windows after a BSOD sometimes you can and sometimes you can't, but in Windows in many cases you can fix the problem - not so easy in TS.

How many have NOT used the editor and have seen any issue with a DTG Route/Scenario?

pH

[sprulish]

Gary

When does "so many" become a large enough number to war?rant intervention by DTG

Statistically 5% - that's the tolerance on most things in the world, but let's say 1% considering the vagaries of software and PC builds.
I was under the impression that there around 80,000 TS subscribers, 5% would be 4,000 and 1% 800, in both cases DTG would certainly know about it! (I have seen this subscription figure quoted as high as 800,000 so you would need an awful lot of simmers to complain.)

I would also ask how many of those experiencing problems used the EDITOR prior to the problem? We know that the editor has issues.

Theory: Once you have created an access violation via the Editor/Build is extremely difficult to remove it. What you have done is effectively built the "corrupt" code into the start-up procedures which will "lock" the RAM no matter what route or scenario you want to run. When you fire up TS 2019 either 32/64bit POST editor and you have had a problem ("Access Violation")- it loads the startup code but due to your previous access violation it immediately finds a RAM address that cannot be accessed and stops. Access violation. It's like trying to start windows after a BSOD sometimes you can and sometimes you can't, but in Windows in many cases you can fix the problem - not so easy in TS.

How many have NOT used the editor and have seen any issue with a DTG Route/Scenario?
copying
pH

Peter, I can say that I didn't use the editor and got a few "access violations" right from the start. Last night was the first time I got an "access violation" on DTG's Western Lines Of Scotland which didn't happen last week. It didn't take long for for the editor problem to come to the fore and DTG reccomending using the 32 bit editor. My 32 bit editor is crashing so I used my TS2018 editor instead. Over the last couple of days I have used the 64 bit editor to create some free roam scenarios to see if they worked. Some work perfectly fine and others crash to desktop when exiting using both DTG and 3rd party / workshop routes. Apart from last years upgrade I have never had any issues with core updates so it has become frustrating with the game becoming more and more unstable. Apart from a fresh new install I don't know where to go with this. My knowledge of the technical side is limited but I have not been able to find any kind of common ground as to what's causing the crashes. Would anyone recommend re-installing a new copy and would that help to fix your theory above? Any help is always welcome.
Regards
David

[peterfhayes]

David
A clean install with NO add-ons whatsoever should stop access violations - it would possibly prove if it was a DTG PROBLEM.

Did you use the editor in TS 2018, before the upgrade and also install TS 2019 over the top of 2018?

I would like to see someone try a "CLEAN BOOT" to see if there are still access violations recorded. This is as good a method as there is: https://support.logitech.com/en_us/article/228

I must be one of the lucky ones I haven't seen an access violation error in around 30+ hours of simming, since TS 2019 64-bit was introduced on 2 separate PC's. But I never use the editor and install all 3rd party DLC (incl WS scenarios) manually.

It is not going to be easy to fix this!

Regards

pH

[meonia]

Gptech and indirectly Peter Hayes have inferred that DTG is absolved of any responsibility for the "Access Violations", leaving 3rd party developers and scenario creators holding the bag for any problems. It leaves me wondering whether it will be worth it for them, the third party creators, to continue trying to add to the variety of routes,rolling stock and reskins we have today. Whats the point if all their work crashes with Access Violations they can do nothing about and get no support from DTG since they, DTG, are not required to do so. *sigh*

Mike.