Atomic Systems

alanch wrote:I suspect that the 64 bit version has only eliminated the crashes caused by the 32 bit memory limit

I think we'd all agree there Alan: as Peter was at pains to point out leading up to this upgrade, it ain't gonna fix duff files!

gptech wrote:

alanch wrote:I suspect that the 64 bit version has only eliminated the crashes caused by the 32 bit memory limit

I think we'd all agree there Alan: as Peter was at pains to point out leading up to this upgrade, it ain't gonna fix duff files!

Probably not just duff files, Gary - I suspect some duff code that has carried over into the 64 bit version. However, if DTG are now looking at the dump files that are automatically uploaded they may squash a few more bugs.

alanch wrote:However, if DTG are now looking at the dump files that are automatically uploaded

I'd expect that there's some kind of filtering in place to only forward/emphasise dumps relating to Steam acquired content, without that there'd be far too many submitted dumps to wade through that it'd make the whole exercise pointless.
I've had a boat load of crashes over the past 3 days---but all through porting scenarios for WCML-London Midlands v4 over to the latest version of the route so it's not surprising things have gone awry from time to time (and time....and time...and time..and time.....). Pointless DTG having those dumps as they wouldn't be able to replicate them, nor could any of us expect them to get involved in something that's not their responsibility.

Gary
I can't see any dump files analysed and uploaded to DTG.
Most of the errors are due to specific internal TS issues, and most dmp files would be absolutely useless to DTG and IMO their analysis would be too difficult.
There too many variables to analyse with the potential of several thousand .dmp files per day, the computing power needed would be enormous beyond my comprehension.
Just a thought!
pH

Yes Peter...information overload!

For any error report to be of value it has to be quite specific--it's no good report after report saying no more than "Railworks.exe stopped working" being transmitted.

peterfhayes wrote:Gary
I can't see any dump files analysed and uploaded to DTG.
pH

I'm only reporting what I've seen - I've had three crashes and each time a report was successfully uploaded to . . . somewhere. I agree they might be swamped but naively I assumed they might have produced some software tools to help analyse these reports.

More in this thread http://forums.uktrainsim.com/viewtopic. ... 1&t=150122

I have found a strange one here, workshop Great Eastern Mainline, it runs fine in freeroam end to end under TS2018, but one scenario I did always crashed at Stratford, the other crashed while in editor mode and would not reload, thinking this sounded like the dreaded 32bit memory issue, left the route until 64bit came along, I had a similar issue with a scenario for WCML midlands that would not load before 64 bit which now runs fine to completion, thinking this would fix Norwich to London, but still would not load, the other scenario I thought was fine as no problems through Stratford only to crash approaching Goodmayers, another scenario that I download also crashed at the same point, which would indicate an issue with the route, but why would free roam be fine, or could it be the placement of stock on a bad section of track, as I have just done another scenario from Norwich to Colchester and it crashed on approach to the station, another scenario which crashed in the editor and would not load was fine until I added static consists at Colchester and I have place another static in the same place as the previous scenario.

Evening,

Anyone had a crash to desktop/Temp Dup message with: -

Exception code 0x0000094

Exception info INT DIVIDE BY ZERO


Have had this twice when trying to place the Caledonia Works Jumbo on the a Worshop route and now have just had it on a Quck Drive just outside Dumfies having driven with the AP Class 40 from Stranraer on the WCoS route


Kind regards
Chris

Dam pain in the butt how can we create things when it will not let you.. Updates should only be allowed when they cause nil, zero, zilch problems!
Or have I just got to solve the Access violation problem myself.. all I am trying to do is delete and old turntable.

ussvoyager wrote:Updates should only be allowed when they cause nil, zero, zilch problems!

So you're saying we shouldn't have any updates?.... in the history of computing there hasn't been a single update to anything that hasn't caused bother for someone.
Use the 32bit editor to remove the turntable.

Gary
Never a truer word:

Microsoft has halted the free Windows 10 October 2018 Update — Windows 10 build 17763, which brought Windows 10 to version 1809. The decision comes less than a week after the October 2 launch, after some users reported the update deleted files from their Documents folder.

https://venturebeat.com/2018/10/06/micr ... 18-update/

pH

gptech wrote:

ussvoyager wrote:Updates should only be allowed when they cause nil, zero, zilch problems!

So you're saying we shouldn't have any updates?.... in the history of computing there hasn't been a single update to anything that hasn't caused bother for someone.
Use the 32bit editor to remove the turntable.

Ah so it's you gptech....
Yes I am saying no more updates..
Causes so much bother updating not worth the trouble... I tried everything to correct it, next am trying throwing PC off the White Cliffs of Dover or running over with Steam Roller....
Anyways am allowed a grizzle after trying for several days to put it right.

OK...so what happens when you select the turntable in the editor?

gptech wrote:OK...so what happens when you select the turntable in the editor?

in 32 bit i get the crash message then the access violation message pop up. In 64 bit just the access violation.
I was changing all the track in an old small route to a newer one, I deleted all the old track until I got to the turntable.. then crash, tried hundred different ways but none worked. I even deleted the old track files etc and unticked the object set filter but the 'ghost' of the turntable or rather just the outline of the track showed.
So.. I just put the new turntable in over it and connected it up. seems to work.
Still no go with the new 64 bit, tried all variations with the built in video card and the nvidea one too, I just get jerky stuttering sound and movement, I'm happy keeping to 32 as it works great.

After TS2019 was launched and I couldn't launch the 64bit version I bit the bullet and updated the Motherboard, CPU, a new SSD and memory. Steam was reinstalled, over the top of the original but leaving the Railworks files alone, now TS will not run at all!

LATER....SORTED but the 64bit will still not run!!

Cheers, Trav.