Jovet, on 05 January 2017 - 08:09 PM, said:
Be sure you save those non-DXT files, because DXT compression is destructive (some detail is always lost, like making copies of copies). I wouldn't mind giving the non-DXT files a go myself... I don't care about the disk space cost.
Absolutely! I'm a firm beliver of redundant backups of backups of backups! I intend to keep a master (uncompressed) copy for myself (whether or not I actually use it), just in case I need to go back and tweak something later. In most cases, I have my original source and pre-ACE files backed-up as well (in *.psd, *.bmp, or both), since even an uncompressed ACE file can introduce some artifacts. When the time comes, you're certainly free to use the uncompressed version, although we'll need to come-up with a means of distribution (heck, even the compressed version will likely be sizable, so I'll need to figure out where to even put it).
Master Chief, on 06 January 2017 - 08:49 AM, said:
As to DTX1 compression, I'm not familiar with the process for doing this; are you using Route Riter? I tried compressing what I have so far (terrtex files only) with RR, and with approx. 850 files, I saved only about 250 Mb after the compression (assuming I did it correctly).
Yes, I use Route Riter (which in turn uses AceIT, I believe) to compress all texture files in a route to DXT1 en-masse. How much space the compression saves depends on how detailed the texture is, but I roughly estimate the process reduces the size about 50-60%, which will really add-up with 1000+ terrtex files. I'm pretty sure Route Riter will compress ALL texture files of a route at once, and there are many object textures I definitely don't want compressed, so I'll need to backup and restore whatever files I don't want compressed later.
Master Chief, on 06 January 2017 - 08:49 AM, said:
I have noticed that, at least in the San Diego area, the route is always evolving - more tracks installed, double-track in most locations now if not all the way, new sidings at Oceanside, etc. New signals, too.
Yeah, it'd almost be a full time-job keeping the MSTS version up-to-date with all of that changing! That's part of the reason I'm informally sticking to a date of 2009-ish for the route, which I think is around the time you first relesed the route, anyway.
SP 0-6-0, on 06 January 2017 - 11:38 AM, said:
About the ROW, If I am not mistaken the new route editor TSRE5 has a feature that allows for painting the row. Not sure how it works? Might be able to avoid all those Mosaic files.
I don't have any experience using TSRE yet, but I would imagine that, to maintain MSTS compatibility, it would still paint the terrain across multiple terrtex files, as Mosaic does now. I think where the real benefit with TSRE's method is with time-saving and ease-of-use, where you can just paint directly onto the terrain while editing the route (vs going back & forth between route editor, Mosaic, and the image editor).