Hi folks, I used loco swap to swap out the AP/Kuju class 43 for the new AP HST but every time I start the scenario it will OOM on load up. I swapped it back and the scenario loads fine, any ideas as to why this would happen? (Scenario is ATS South Wales Modern- 2U14 PNZ-CDF Central) I did swap out the coaches as well as the loco in the consist if that makes any difference. Thanks guys.
It you read the manual for the AP HST you will see the power cars number will have other characters after it. Swapping power car 43123 with the AP version will not work as it won't have extra required letters/numbers
Does the scenario has a rolling start? If so swapping out stock won´t work, easiest fix is to untick rolling start in the scenario editor (but of course that means you will start standing still).
First thing I did Peter, the numbers are listed in the loco selection i.e when you select the lead car I can pick the number for the livery I want and it has for example- 43029;CF=GWR2. I even made sure to select change number to make sure it wasn't reverting to the standard number. It is only the class 43 that is causing the error, I may just revert to the original loco and try to swap it in editor using a ready made consist from the AP pack.
No it is a standing start. I've added it to another scenario on a different route and it loaded ok so I'm at a loss as to why this particular route doesn't like it.
Right I don't think it's anything to do with the train. I reinstalled the route and tried to edit the scenario and it OOM'ed to desktop so I think it may be the scenario or the route itself. More testing needed and a check on the requirements again.
If it's a freeware scenario. I would suspect that first. The nature of freeware is that it comes with unknown quality control.
Wow the requirements for this seem crazy: South Wales Mainline Modern needs Berks and Hants to Bristol and Penzance V4.1 needs Just Trains – South Western Expressways 1st Iteration (BHBP will not work with the later iteration that’s available on JT’s website) I think I will give this one a pass and stay with the latest version of JT SWE otherwise I will have 2 versions needed on my pc. Hope you find out whet you need to get this working.
Yep it is a large amount if you don't own it, and I find it strange that you have taken the time to tell me about something you don't wish to own. But if you have continued for years to buy stuff that enables you to run it then the question is legitimate. I'm just interested in how I add a loco to a scenario that doesn't seem to want to know.
I have a lot of DLC. I find it strange that it wants the 1st iteration of the JT SWE. I was thinking of downloading it to help troubleshoot, however, taking a backwards step in my files seemed like something I did not want to do. I use locoswap all of the time. Have you tried swapping out another example. Great Western Mainline - Chasing Yellows has an old Kuju 43. I have just tested this swap and it works fine on my rig. Take care
Apologies if my reply came across as terse, after paying out for multiple copies of stuff I was just getting a bit miffed that stuff just doesn't work! And you're quite correct that it is stupid to expect people to buy the same route twice. Thanks for trying to help it is appreciated,
As I mentioned before I swapped out the new AP HST with the Kuju on the scenario Chasing Yellows. I of course swapped the loco AND the matching carriages. Respectfully
I've swapped out the loco in another scenario on the BHBP line and it was fine. I've now tried to edit the scenario in editor but as soon as I press continue to enter editor mode it crashes Strangely I can change the coaches of the driver consist and all of the other stock in the scenario but not add the AP HST I'm wondering if the scenario is bugged although I've never seen a scenario that couldn't be edited even in cloned mode. I'll get in touch with ATS to see if they know of any issues with it.
Have you tried clearing the cache before you run. My first trial recently with the new AP HST on the AP Bedford route spun up correctly, however, when I started the roll I got a OOM error. I cleared the cache and it worked fine on second attempt. This particular scenario and loco are data hungry. A clean cache may help.
I have cleared cache, deleted route, deleted scenarios and re-installed everything again. Everything is as installed from scratch I'm running a 4070ti super with 32gb of ram and a 9700k. I have managed to get into editor mode and select and change the loco but it still will crash as soon as I make a change. I have never had any problems making changes to the many routes that I own but this one is a pain! Edit: the cloned route will not allow me to change the loco, if I do it will crash as soon as I select th AP HST.
I have now tried to select a loco and place it next to the original selection and move over the instruction and it crashes as soon as I place the loco. I'm thinking of re-installing the AP HST as that can only be the problem. Edit. I have redownloaded the loco from AP and it will still crash on selection.
So one part of something does not work so you delete the route then the scenarios? Don't get a car - you would be taking the engine out if a bulb went. Yes, that sounds silly but to remove an entire route because A Scenario or A train does not work is daft.
I have managed to get this working using the OLD AP MTU pack. I believe the scenario was used with the old AP MTU AND the ATS Mk3 Sliding Door Pack (which is no longer available). I have used Locoswap to replace the offending HST items with the previous iterations of AP product. When I tried to use the new AP MTU pack I also witnessed an OOM error!
So it isn't me going mad then! I can get it to run using the old AP pack as that is what is asked for, but the new AP HST does not want to work, I'll raise a ticket with ATS as the route is labelled with his name, if I get it fixed I'll post it on here.
It was the old AP with Sliding Doors. I believe the new AP MTU includes sliding doors. I did get the new AP MTU to load the first time however I had chosen a ‘dead’ end. Guessing would need a rewrite of scenario to use new AP.
I have managed to swap out to the new HST on another scenario in the route and it works fine. I swapped out to a class 50 on 2U14 and it runs fine, so that one scenario doesn't like the new HST, very strange.
