There is something that perhaps is missing in the translation/documentation of this utility.
Quote
DPUmult.exe allows you to save even more time: To this program you can pass a bunch of .ENG files (there is virtually no limit to the number passed). Then you once have to select which data profile you want to use on ALL of these files. With that done, you just have to acknowledge every time a file was passed to the main DPU.exe that you are fine with what you are shown in the evaluation.
Does anybody have an explicit example of how exactly this works?
Back in March, Carlos posted this "http://www.elvastower.com/forums/index.php?/topic/23909-generating-eng-sms-cvf-files-for-orts-without-affecting-msts-behaviour/". The really useful aspect of this is that the original MSTS .eng file does NOT need to be modified to insert Open Rails specific changes. Two thumbs up there!
Which begs the question would this utility not be more useful if it created modifications and placed them in the OpenRails subdirectory of the engine in question?
I have been struggling (okay, lazy, but resolute!) about how our beautiful particle emitter (smoke) requires the wholesale modification of a ton of MSTS engine files to work/look acceptable in Open Rails. In short, it is not terribly "compatible".
Did I miss the point here?