by NYWhiskey » Fri Jan 13, 2017 6:07 pm
This is the method I use, it works great for quick loading. It was posted by Matt P. from Dovetail a couple of years ago.
Creating Single Route Installs
If you're developing content then I recommend you create yourself a separate "dev" installation of railworks, it's dead easy.
Create a folder, I use "c:\dev" and copy everything from the railworks folder (so that railworks.exe is sitting in c:\dev). You can leave Assets and Content where they are for now. Now, in your dev folder, ONLY put the route that you're working with and the Assets that you need and NOTHING more. Put your source in the source folder and use the utilities etc from the dev folder - do everything in that dev folder.
Now when you run the packager it'll be extremely quick, the sim will run nice and fast, menus will be clear and free of everything you don't need and generally you'll be far better off. Another key advantage for those who are distributing via Steam is that when you submit your content for upload to steam, it'll get downloaded shortly afterwards on to your machine - if you're developing in the live install it'll overwrite what you're doing. If you develop in c:\dev it won't have any effect, so you'll be able to have your current in-development version and the current on-steam versions accessible.
It's how the teams internally work, and definitely the best way to go.
Matt
Rich Wade
North Eastern Rail Works i7-8700K @5GHz, ROG Maximus X Hero Motherboard, Corsair Vengeance 32GB RAM @3200, Asus RTX 2080Ti, 1TB M2 Crucial SSD, Tri Monitors, 3 HD's = 10TB, Corsair H80i v2 liquid cooler, Win 10 Pro Insider slow track