Atomic Systems

I have encountered a problem. My slip junctions now have high red rectangle after track editing in TS2019/64
I have reported it to DTG but if you edit track please be aware.

Initial reaction to running a QD scenario with modern AI on my route was brilliant!

I then added some more track some where else before going back to the QD and added some more AI to it

The QD crashed to desktop 'Access violation' during loading

reverted to old AI (Fal, Woodhead): same problem
reverted to scenario backup: same problem.
looked at the track in track editor and saw all slip junctions now had a high red rectangle
(I did try another QD which worked but its route didnt involve slips)

Copied out the route with today's days changes and reverted to yesterdays and it now works.
A day lost, oh well.

Regards
Peter

I've just tried laying some track in anew route, stuck in single and double slips and diamond crossings with no bother at all. That suggests you've made a mess of it; however, when then saving a newly created a standard or freeroam scenario for the route the clips were all rendered with no guard rails or frogs, and pathing across them was impossible. No sign of red rectangles though. That conversely suggests that you did nothing wrong and it's a game issue
Feel free to follow up your message to DTG to inform them that the issue has been replicated; that should make them more likely to look at it with some urgency.

Doing the track work and scenario creation in TS 32bit worked as it should, and that route and scenario was playable in 64bit so there's a work around until DTG fix it.
I'll do some more testing after work tomorrow night to see if further editing in 64bit works OK---one of the attractions of 64bit is that we should be able to add more AI services, so it'd be a bit of a deal breaker if we were stuck with 32bit editing.

Thanks Gary

Having slept on it I came to the same conclusion to use TS2019/32 to edit the track.

I reinstated the track damaged but latest scenery version, copied in the previous, working, tracks.bin and reapplied my edits.
Started 19/64 and ran the Banbury QD again with no problems.

To test, I edited track again in 19/64 thirty miles away and not on the QD route.
Reran the Banbury QD and it crashed while loading.
Looked at the track at Banbury. It now had high rectangles and, now you mention, missing guide rails at some but not for all slip junctions.

So I think clicking the grey cube to re-weld track in ts2019/64 can break slips miles away and you may not realize you have a problem.


If you are interested this is the memory usage from Task Manager I saw running my Banbury to Hinksey Yard QD with a slightly more adventurous preload .
Start 4786 MB
Banbury 4862
K.Sutton 4890
Aynho 4904
Fritwell 4507
Heyford 4351
Tackley 3805
Blet. 3832
Kid. 2219
Wolv. Jct 2281
Approach Ox 1816
Ox N.Yard 1894
Ox Shed 2060
Hinksey 2131

Regards
Peter

Tried a route tracklaying session today in the 64-bit version. Other than some issues making track welds all appeared good. However on restarting the route won't play or edit and crashes the game with an Access Violation. Other routes as normal.

Possibly nothing to do with the update but given previous comments it would be wise to back up routes before editing in the 64-bit version.

As a trial I just laid a double slip saved and reloaded the route. All behaved normally.

Mark

Yeah....that's what I found initially. Try running a scenario over it though Mark.

Yes have run a train over the double slip in all directions without any problem.

Mark

I have just seen another chap experiencing exactly the same issues with double slips elsewhere, he has reported to DTG so hopefully they will be aware that multiple users are facing this issue.

I've had the same problem with slips. Anybody having signalling problems? Although my payware routes seem to be OK I have two routes that I'm building, one with JT Modern Signals and the other UK Pro Signals. Signals with single track links are ok but multiple track link signals only have one link and show red even though AWS gives all clear. If I replace a multiple track link signal and restart the scenario it works but if I exit the route and restart my signal only has one track link again.

Have any of you experienced very slow save times when saving after a 64-bit track edit session? My route (15mb tracks.bin) takes about 2mins 40sec to save under 32-bit - but the same change under 64-bit takes a book-reading 12 minutes? Anyone else getting this?

Neil

There are definitely some issues with the editor. I had the same issues with a double slip, but having tried repeatedly until a got a track layout that worked, not none of the signals on that new track are working... I've never had those sort of issues before... and I've had the access violation discussed elsewhere in this forum.

Posts on Railsim de indicate that creation and editing of routes in 64 bit causes problems. But using 32 bit, then running them under 64 bit seems to work ok, apart from some scripts specific to the German route assets. Same with scenarios it would seem. But it doesn't work for everyone as a few get the MSVP error when they try to use 32 bit.

I discovered this for myself this afternoon. I found that the issue I had with signals was that no matter what I did, as soon as I came out of the editor all of the markers were lost.

I tried exactly the same thing with the 32bit and everything worked as it should do!! A simple solution until the issue gets properly fixed.