I’m finding that the game isn’t really crashing for me unless I get something wrong in an AP weather pattern, but then it never really did. I am finding though that doing a simple thing in the editor, like swapping out one consist for another is causing a dump. It’s infuriating. I’m trying to simply swap an Avanti 390 for a default S9BL one in a JT scenario on MML and the minute I fly close to the one I’m trying to replace the thing dumps. The reason? ‘Out of Memory: Scenario’. That’s certainly not what I’d call ‘stable’. It allows me to place the consist at Piccadilly no problem, but move near the other Pendo further down the line and booft, welcome to the desktop again.
Just a thought - MML is not electrified - could trying to run an Avanti 390 on there be part of the problem?
You did read the bit where he said "place the consist at Piccadilly"? Some scenarios have you diving in to or out of Manchester Piccadilly and other AI are electric trains. JT Midland Mainline is not just Sheffield - Derby
^^ This. It’s an AI train. I gave up in the end and used locoswap to change it for the Avanti Half-Livery S9BL version. Very frustrating!
^ This. And the problem seems to be random. On some of my routes I'm getting the new horrid TSW3 style 2 to 3 second Drive-By-View, but yesterday on one old route I was still getting the beautiful long original TSC Drive-By-View. Wondering what others are seeing?
I didn 't notice any change in the TrackSideCamera001.bin definition, so it must be a core feature that has been changed inside GameManager I haven't use this camera often previously, since it puts you in a high viewpoint at random instead of trackside in the berm, making it less suitable for screen recording a lineside video. I believe the new trackside camera doesn't put you on the ground at all, since with the old cam you often ended up behind a wall, or at the foot of the embankment, so perhaps DTG simplified it a bit and above the track's centerline there is less need for panning? An 8 carriage HST still is a tad too long, the camera jumps ahead just when the rear Class 43 passes under you.
On most routes the camera gets put up high because the original design of the camera tried to avoid scenery objects. It was designed for the old Rail Simulator/Railworks routes where there was much less scenery, so the camera could find plenty of empty terrain to be on. But as scenery got denser on newer routes, with much more trackside foilage and trackside equipment, it cannot find empty spots in the scenery anymore, so it will simply spawn above the tracks.
makes sense, and this continuous searching for position by the 4-camera in case the player wants to look through it might have been a waste of CPU cycles now put to different use
Why don't people understand that the update broke the Camera 4 view and DTG are working and testing a Fix?
Drive something really fast.. like 125mph or faster, and take a look. No one planned that... it's like 1 second per camera view
On another note the TSC application is working the most stable for me than I have ever had it running (with ThirdRail running in parallel). It has only taken me over a year to fine tune my pc not to fail me with either a OOM or a Blue Screen!
Just noticed that the in game consist editor just crashes for me. It never was the most stable of things though, and it always took an age to load everything, so never really use it, but as part of just testing things since the update, it seems more flaky than usual for me.
Comments like this confuse the issue for people searching answers especially new players, I assume it was said in jest but please don't.
I'm concerned the second change to the 4 Camera was intentional. The first change following the update was that we lost panning. But we still had a fairly long run time of approx. 20 seconds (depending on the train's speed). But then the behavior of the 4 Camera changed a second time a few days ago, being the run time reduced to 2 to 3 seconds or less. TSW3 is all about the cameras being closer to the train with the inability to zoom out as far as we can in TSC. And I get it. Closer cameras mean faster action. I could be wrong, but I feel like TSW3 is aimed at younger audiences with faster action. I dislike the closer cameras in TSW3 so much, I've stopped playing it. And I'm concerned that the faster action philosophy may now be creeping into the 4 Camera in TSC.
For me it never worked. I theorised it's because the game is trying to load every train into memory and as a result loading my 500GB of trains into 32GB of RAM failed for obvious reasons. I haven't priced it though.
D It is only loading a thumbnail (less than 1kb in many cases) menu of every train you have installed, it doesn't load any DLC until you select it. the real issue is if the VAS and the Physical RAM are showing different or unavailable addresses when you try to edit whatever it is that you want to edit.
I was talking about the consist editor, not stock list. No thumbnails are loaded in the consist editor.
You mean the function QuickDrive => Consists => Create New ? The consist editor crashing is mostly due to incomplete rolling stock. Have you installed any freeware or mods that require copying of files either by a script or by hand, any mods that require shapefile editing? Have you packed assets into .ap files, or unpacked .ap files Notably AP uses this installme.bat script, which needs to be executed for each AP Enhancement Pack separately, before you install the next EP because it overwrites the installme.bat which you have not executed or went faulty because it couldn't find the source files? Have you run LogMate.exe while the game parses its content? The logging often stops just before or at the broken file. You can also find the culprit DLC by deduction, moving half the folders out of the Assets directory, trying to create a consist, swapping the halves, moving ever more folders back into Assets until only the faulty DLC folder remains outside of Assets.
Yes. It worked before the update, and now doesn't, and I had not installed any new DLC that wasn't already present before the update. At the time I tested, my DLC library was identical. I can run logmate later to see where it falls over I suppose. It's not something I'm looking to fix, as I never use it... it's painfully slow... it was just as information if anyone was interested, or a heads up for others to see if there's is different since the update(s).
Did Steam do a file verify around the time the updates were applied? The Steam verify will clear out any files outside of the .ap ones and any reskins will need reapplied.
Nope. In fact, as part of trying to sort something else out, I put my back up back on, and then downloaded the update again. No files were verified by Steam.
I have reskins and the default files are in an *.ap file, like the Class 323, and they are still there.
So even though DTG say they are fixing it - like the fixed the image.png problem -you don't believe them.
New build 64bit DX9 (with Vulkan through RWE2) tested last night, consist editor loaded (would hang at roughly 3/4s the way through initial loading on old build) 48 pages of loco's. Loaded create new consist without issue. Created and even changed my mind, deleting rolling stock, changing order of stock, switching between engines, passenger stock. Consist successfully saved. Played said consist in a QD scenario. I haven't been able to use the consist creator in-game for about a year. One thing I've definitely done differently to most others is I've bulk changed all the loco images to 156x128 .png using IrfanView.
No such luck here. Takes around 5 minutes of loading, then just crashes the game back to the desktop. I never use it though, and certainly can't be bothered changing any more thumbnails, as every other aspect of the game (apart from the ones discusses, like F4 camera view etc.) are working as they should. I hardly ever even use quick drive either.
Has there been any news on a fix on this? I came onto forum looking to see if there was something I was doing wrong. Picked up the expert BR 101 in the sale, I can get the AFB to set the speed, but then it gets stuck - I can't reduce it, change it etc. I hear the clicking noise but there's no movement.
Then pretend it does not have AFB for now and drive it without. More fun as you have to watch the speed
