RWTools packaging

[Toripony]

While packaging the latest COA route, I've been working with Mike Simpson on some improvements to the route asset packaging process of RWTools. Every time he would "find and grab" more files, I would identify more that it was missing. I fully expected to reach a point where he just could not get them all, but he kept proving me wrong every time. He just sent me an email that has left me saying, "Well, I'll be....!" Not only does it now collect seasonal asset textures, "third referenced" assets, and loft shape textures, it even grabs signal scripts! I just have to share this note/news with you all:

Hi Tori,

I have updated RW_Tools and put v2.3.14 on my site.

This one now checks all .geopcdx, .xsec, .ban and .lua files.

I have packaged your route using it. The content folder is identical to yours.

The only items missing from the Assets package were the GN-Telegraph poles. This is because they use a non-standard method of naming the files – the file name which appears in the tiles in the Loft Tiles folder are for example gn-telegraph_16-loft.xml but they need a file named gn-telegraph_16.bin as well as gn-telegraph_16-loft.bin – I have not seen this anywhere else, so am not sure if this is correct or not.

All the ground textures are now copied correctly

Regards, Mike Simpson
Penrith, NSW, Australia
http://www.rstools.info

Mike, you are amazing! Thanks so much for making it possible to do what I do!

[artimrj]

When I packed my assets the other day, the poles were missing but the wires were still there. On the GN poles. The signal scripts were also missing. And the crossing gates too.

[Toripony]

Yes, Bob, those are some of the issues I passed along to Mike including my missing junction rail caps and ground textures and apparently this newest version now grabs those, too. When Mike said his test "...content folder is the same as yours", he means after I worked on my package to add missing files by hand. This latest version is the 5th or 6th upgrade he released in the past 2 weeks, all of which pertained to packaging. With each iterration more files were gathered automatically and I did less manual collecting. In fact, Mike said this part of the tool has been rewritten.

Until I try this, I'll assume there is still one caveat in using this technique, that is the necessity to remove a few files from "non-default default" content folders, such as RSDL Foliage01 or RSC Apstation and some others... these come with the game but aren't part of the original Kuju set and aren't tagged as such in the game code so they get captured. It only takes a minute to remove them though.

But, I'm beginning to speak out of turn here... I should leave these assumptions to Mike to confirm or at least wait until I've run this latest version myself. I just wanted to share this info so anyone who might be packaging a route could consider this method instead of the RW Package Manager method. Both methods have their upside and downside, but for my route the RWTools method is better because choosing all of those many assets "by hand" (~4000 files) using Package Mgr. takes up to three days. And if a mistake is made, it has to be started over from scratch. With the RWTools method, files can be added/removed from the package after its made because it is a simple zip file. Even if I make a major change to the asset set, a complete repackage only takes about 30 minutes. I've also learned that items can be removed from the Assets Used report before running the Package This Route's Assets routine so they won't even be packaged in the first place.

[GreatNortherner]

Hi,

This is exciting news, many thanks to Mike for his never ending endeavors to improve RW_Tools (and with it the fun and possibilities of building, editing and using routes/scenarios/assets). I always liked the packager for the very same reason you just mentioned, and if it works even faster and precise now then this is quite simply fantastic.

Mike!!!

The only items missing from the Assets package were the GN-Telegraph poles. This is because they use a non-standard method of naming the files – the file name which appears in the tiles in the Loft Tiles folder are for example gn-telegraph_16-loft.xml but they need a file named gn-telegraph_16.bin as well as gn-telegraph_16-loft.bin – I have not seen this anywhere else, so am not sure if this is correct or not.

Not sure if that helps in any way, but seeing these are my assets that cause the "last hiccups" maybe I can try and explain how I came up with this naming.

The telegraph pole/wires lofts used on the COA use the following objects:
- the actual loft (gn-telegraph_16-loft.bin and xsec)
- the poles as start, mid and end geometry objects (gn-telegraph_16.bin and geopcdx)

To compare, here are the file names for the telgr poles with modeled 3D wires (which are not on the COA, as far as I now) These use:
- all transparent loft (gn-telegraph_16-loft-w.bin and gn_transloft.xsec)
- poles with attached wires as start and mid objects (gn-telegraph_16-w.bin and geopcdx)
- pole without wires as end object (gn-telegraph_16.bin and geopcdx)

The poles with loft wires can be found on the 3.x versions of the Big Horn route.

Hope this makes some sense.
Cheers,
Michael

[kevarc]

Mike has always been great to work with. I have been using his products since the first day I got into MSTS and RW_TOOLS is an indispensable tool for RW.

[mikesimpson]

Following all the feedback from Tori, I think the package option is now 100pct in v2.3.15 which I uploaded today. The telegraph poles were the last ones to appear :-)

Mike

[artimrj]

Thanks Mike, I am going to test it out on my route again tonight. Sure is a nice package you have made for us.