Atomic Systems

Glad its not just me then.
Rich, do you think deleting several of the later services around the London area might help the freezing issue? I doubt its a resource problem as i have plenty of fast ram.

I've twice ran the 6Y60 scenario, and never encountered any issues, with the exception of this on the 2nd run:



What's even more strange is that as soon as the train had passed, the body re-appeared

Hi Alex

I've edited your post to show a link, as all embedded screenshots must be in jpg format.

Ash

jrnyfan4life wrote:I've twice ran the 6Y60 scenario, and never encountered any issues, with the exception of this on the 2nd run:



What's even more strange is that as soon as the train had passed, the body re-appeared

I have had that on an FCC passing at haywards heath, pop out of the cab and back in and it re-appears?

That's exactly what happened to me. Strange goings on indeed.

That could well be a TS2012ism or a 377 model problem, most likely the former. Seems to be really odd for that to happen, though, never seen something like that myself!

It appears only the couplers are showing up for some reason. I had this same issue, it's something to with copying the right .geopdx or whatever it is.

There's a JT class 60 scenario that does that as well, cant remember which one but its one of the bundled Ox-Pad ones.
Whilst your at a red light near Didcot a train of couplers overtakes you.

Dave

By the way, if anyone makes up a scenario using the earlier class 59 reskins of the ARC, Hanson etc, be aware you might get a broken consist error message.

Appears the way out of this is to alter the .dcsv file for the reskin so that the line

<Name d:type="cDeltaString"></Name>

is changed to

<Name d:type="cDeltaString"> </Name>

ie a space where normally the locos number would go. Then the error message will naff off. Found this on a previous thread after getting the error message.

Rgds Ron

I think the problem with the hang on the hanson scenario is an errant Ai losing its path 2Y89 10:13 Victoria to Caterham.

jrnyfan4life wrote:I've twice ran the 6Y60 scenario, and never encountered any issues, with the exception of this on the 2nd run:



What's even more strange is that as soon as the train had passed, the body re-appeared

That couplers issue is a strange one, it seems to happen when you stay in the same place for a while so in this case, waiting at Haywards Heath until 09:55.

I thought that weird buffer-only thing was a generic railworks oddity rather than scenario or train specific?

i've had it a handful of times with different units, on different routes - most strange.

I've seen it on WCML a few times.

B

phat2003uk wrote:That couplers issue is a strange one, it seems to happen when you stay in the same place for a while so in this case, waiting at Haywards Heath until 09:55.

johnnywilliam wrote:I thought that weird buffer-only thing was a generic railworks oddity rather than scenario or train specific?

i've had it a handful of times with different units, on different routes - most strange.

bdy26 wrote:I've seen it on WCML a few times.

B

I may be wrong, but I recall somebody last year deducing that if it was happening outside of the missing .geopcdx case (i.e. incomplete copying of files when installing of a reskin) then it was an issue to do with AMD/ATI graphics processors. I think the root cause was either a couple of shaders not working properly or with adaptive anti-aliasing being switched on in the Catalyst Control Centre.

My memory may be wrong, so please sing out if you're seeing it on a Nvidia card and I'll stand corrected (or at least consider there's another cause I previously didn't know).

If it's happening as a train approaches and then reappearing as it goes past, that would point to a LOD issue with the textures involved. That's a content problem that should be reported to RS.com.

I have not experienced this problem on London to Brighton so far but do suffer from it on occasions on WCML north especially when you are sitting in a loop waiting for faster traffic to pass by. Sometimes you see a train of couplings approaching – changing quickly to another view and back again will often sort it but it is an another of those annoying TS2012 problems and frustrations. I have a feeling it may be related to memory since I suffer from it a lot less now since I have been using the 3 Gb switch.

Sorry to hear of others having problems with Richards’ excellent Class 59 scenario from Ardingly. I completed this without major incident although frame rates suffering a little in the suburbs due to the amazing intensity of the AI traffic. Otherwise the only problems that I noted were that on coming to a stand at signal T331 outside Haywards Heath prior to running round the train you can in fact get permission to pass the signal with Tab – but not a good idea as the route is set for a southbound electric unit into platform 1. Once that train has stopped and departed the signal does then clear ok. The other thing I noticed was that on approaching East Croydon I was overtaken by a 377 unit on the up fast which appeared to have its doors open although in motion? Otherwise, and excluding a SPAD on the flyover at Selhurst, which was obviously my own fault, the scenario worked through to completion without incident. Just goes to show what can be achieved – let’s hope it all remains in tact after tonight’s upgrade!

Peter