Hose it... start again. Uninstall Steam. Manually remove any folders remaining. Download Steam again, install Train Sim from Steam. Test it works, install all your third party DLC one at a time, testing it works after each one. Pain in the ass, I know, you've been banging your head against this wall for days now, and got nowhere. I still reckon there's a file location conflict, but unless you know what that could be, and why, this will drive you up the wall. Best to spend a day sorting this out once and for all. Once it all works, back up your Railworks folder so you never have to do anything like this again.
If I should reinstall steam, It's probably just easier to wait ~1 week for my new PC and try on there, so I guess ill come back in around a week unless there's any new ideas/things to try?
Yeah, I agree, if it's only a week, I'd do the same. Seriously though... once sorted, back up your railworks folder.
Mine is working perfectly. I seem to remember having a similar issue with another AP model. Class 158. What I discovered was I had to reinstall the dependant pack first then add the AP on top of it in that order! Class 158 DMU from Steam and then add the AP item. Done in the reverse order caused the horrible smoke. Maybe the LNER BR Class 43 and then the AP product? Please contact me if you would like me to send you some exact listings for my files/folders. Glad to help
Uninstall both, install the Kuju then install the AP and see if that helps. Train Simulator: European Loco & Asset Pack
I did read the thread. My point was that it is order sensitive. You need to reload your AP product again after you reload the base software. Respectfully
Suggest you read post #30 of this thread. Craigie-C has already covered this with a step by step detailed procedure.
Man you guys are tetchy. My point was this does not only apply to the Class 43. I also experienced this with Class158 from AP and that the order of install is very important. Respectfully
I wouldn't say we are tetchy, it is just a case of when a detailed possible solution using a step by step process has already been offered we don't see why a repeat suggestion that adds no additional help is required or necessary, especially as it has turned out to have already been tried unsuccessfully for the OP
It's fixed now, maybe it was a file issue, hopefully this doesn't happen again... Thanks for the help anyway