I’m a Scenario Developer and know pretty much jack snot about the technicalities of Routes and Route Bulilding, but a while back in conversation with Warwick-Rail he told me of his frustration with RWINFO and that it wouldn’t filter by Route Dependencies (preloads). This made it a pain-in-the-hole for finding Scenery assets etc. So, under his guidance, I wrote a Route-Assets Manager to allow easier access and methods for locating Route Assets (Scenery etc.) In general, the the software constructs a Route-Assets database (as it does for Stock and Weather Assets) for quick and easy lookup and obviously, the larger your system is, the heavier the processing is going to be, though it is manageable. On my modest system of about 30+ Routes I have a total of just over 26k Route Assets, though Warwick has something like 170k (he has 375+ Routes). Whilst ALL Route Assets on the system can be shown (though may take a while to load for large setups) it is more usual to interrogate the Route Assets for a particular Route in question filtered by its Dependencies (preloads). Below are the Route Assets available for the North London Lines (BR NSE) based on its Dependencies. The DLC can be expanded to individual items (and as before, blue items are in packed .ap files)... With a comprehensive search facility... Note: I have found some assets do not have a Category properly defined so these are grouped in their Type prefixed by ‘z’ to sort at end (i.e. zLoftSection etc.). And there you go. Oak trees available for the North London Lines (BR NSE) route... Plus a List option for the selected items (or all) and can generate a CSV export file... As I say, Route technicalites and Route Building are one of my least understood sub-systems, so looking for a few expert Route Developers to take the software for a spin and give me some constructive feedback. PM me if interested. FastLeg
Plus a Route-Asset Properties page can be shown for any item. The {Explore} option opens an Explorer for quick access to the source folder (which may only be the location of the *assets.ap file if packed). And a {Serz XML} option to generate an up-to-date .xml file inside the source folder (if the item is packed, the xml will be generated in a temp folder for copying/inspection etc.).
TSTools does something like this in creating a list of all the assets used in a route - although the output is crude by comparison Will your "APP", not sure what to call it, also tell you what is missing from a route? TSTools is good but it is sometimes difficult to use.
Just a bit, if not always (no offence Mike).. That's why I wrote this thing... I call it software. But yeah, especially in terms of missing Dependencies (Route Preloads) Or at a glance for multiple routes... (Blue routes are packed maincontent.ap, and Green are Workshop
