by LoneWolfDon » Mon Dec 19, 2011 1:29 am
Yep, it's a another strange and annoying quirk / bug of RailWorks, and happens often with me when editing routes and scenarios.
Simply exiting the scenario to the Menu, then Play it again will "fix" it (I find it's usually good practice anyways to exit a scenario after editing it, otherwise strange problems like this and other odd problems may occur that normally wouldn't if loading the scenario from the Menu).
Or alternatively, sometimes if you're in free-camera view, "fly-away" a couple of miles, wait a moment (until you notice new scenery items loading in the different area you fly to), then fly-back, and sometimes the missing items will re-load (though this method doesn't always work).