Whilst this was good advise, I found it was also necessary to delete the entries in the relevant assets folder as well.

If you do this the Asset Editor can sometimes die horribly and just stop working altogether until a random point in the future! Note: DO NOT delete the files in the route of the Shapeviewer folder. If you go to the Assets/Kuju/Shapeviewer folder and delete the appropriate folder in it (ie Scenery) you should be able to get a fresh export without it remembering everything. It's trying to save time recompiling everything on every build, but it's a pain in the ********* butt if you don't get every single part of the export perfect on the first go! if you try and rebuild with a file that's older than the last one it saw, it will ignore it. Sounds like the asset editor and it's infamous caching. Here's a comment from Pete(karma99) which I found invaluable. The problem I wish to draw attention to is caching by the asset editor. It took longer to add the sound than to build and animate the model! As too often, the wiki is worse than useless and only confuses rather than informs, so the only way to go is looking at the work of others, for which Mike Simpsons RWTools is invaluable. I have been trying to add sound to the model and had endless problems. I hadn't intended to post anymore on the subject of the Transporter bridge but I thought I'd give a liitle background on my last few days, in the hope it may help someone else.

The amount of work I put into modelling for Railworks is a good demonstration of how much I like the game, but occasionally it makes we want to tear my hair out. So watch this space for imminent reports of my early demise from RW Physicsitis.

Still, the engine now appears in game, although I get a SBHH system crash if I go anywhere near it! I'm nearly bald with the hair tearing frustration. Since then I have struggled with blueprints for bogies, couplings, brakes, cabs etc etc etc not to mention scripts and csv files, animations and audio. Spent days wondering why it wouldn't show up until I realised you have to have a simulation blueprint before it will appear as an engine. Then I started on making it a working model for the game. Still a bit of work to do on textures and shadows but not bad I thought, for a first loco! The mesh was a mess and took some sorting out but finally I was able to export the loco as a RW scenery model. These were in turn, imported into 3ds Max and I had myself a model of a Cauliflower. dst files into 3DCanvas from which I exported the files in. I had a similar desire when I was doing my MSTS route and as no one expressed an interest in helping, I made my own.ДЄs I understood Ben's frustration I decided to try and resurrect my old model. Ben and I have had some correspondence on the route and he expressed a desire for a Webbs 18' Goods 0-6-0 loco, nicknamed Cauliflower, as they dominated the traffic on the route upto and into, the 50's. Consequently, I was very interested when Ben Yates started to produce a version for RW and a great job he is doing of it.

I spent several years researching the route and developing it for MSTS, but never released it. I live in the Lakes District where there are two railway lines of particular interest, the Furness Railway and, my favourite, CKPR(Cockermouth Keswick Penrith Railway).

Import msts route to railworks