I successfully did this some time ago, but am now wondering if DTG .GEOs are protected in such a way this cannot be done?
if I clone the Feather River caboose, put into the SF Peninsula route by adding the files and editing the bins, but have the bins point to the geometry files in Feather River
GreatNortherner wrote:Hi Howard,
As I said above, I haven't actually tested this in practice, but what you wrote might well work.
I did something similar before, recommended by Buzz or PapaXpress back then, in my GP9/SD9 locos that are on my website. They use the sounds from the Kuju assets by aliasing them in the blueprints, but I believe they run without having to tick the Kuju folders in the editor. And if this works with sound blueprints, maybe it does so too with complete wagon or even engine blueprints? Though there are many more elements in those, so also more chances for it to go wrong.if I clone the Feather River caboose, put into the SF Peninsula route by adding the files and editing the bins, but have the bins point to the geometry files in Feather River
Yes, in theory this might work. In theory, the bare minimum you might have to copy is the wagon .bin file if you leave all file references in it unchanged (numbers, couplers, geometry, audio, etc.) Note that repaints still require their separate set of Geo files so that they load their own textures, so a combination of the RW Tools .bat installer and the "split off" .bin file might be required.
Cheers,
Michael
GreatNortherner wrote:There may be a workaround, though I haven't actually tested this. You could try moving only the assets' blueprints (.bin files) to your new provider folder while leaving their internal geometry references intact (still pointing to their original DTG/RSC paths and Geo files). The copy protection should be happy and you could even share the .bin files (which would be technically the same as uploading a repaint with an edited .bin file and that .bat file to copy the Geo files, which DTG does permit).
GreatNortherner wrote:Hi,I successfully did this some time ago, but am now wondering if DTG .GEOs are protected in such a way this cannot be done?
I'm afraid that the "geometric hellscape" you're seeing after migrating the DTG assets is their copy protection at work. Using the .bat file copy method won't help in this case as the copy protection probably checks if the files are in their original location.
There may be a workaround, though I haven't actually tested this. You could try moving only the assets' blueprints (.bin files) to your new provider folder while leaving their internal geometry references intact (still pointing to their original DTG/RSC paths and Geo files). The copy protection should be happy and you could even share the .bin files (which would be technically the same as uploading a repaint with an edited .bin file and that .bat file to copy the Geo files, which DTG does permit).
Cheers,
Michael
PullmanCar wrote:GreatNortherner wrote:Hi,I successfully did this some time ago, but am now wondering if DTG .GEOs are protected in such a way this cannot be done?
I'm afraid that the "geometric hellscape" you're seeing after migrating the DTG assets is their copy protection at work. Using the .bat file copy method won't help in this case as the copy protection probably checks if the files are in their original location.
There may be a workaround, though I haven't actually tested this. You could try moving only the assets' blueprints (.bin files) to your new provider folder while leaving their internal geometry references intact (still pointing to their original DTG/RSC paths and Geo files). The copy protection should be happy and you could even share the .bin files (which would be technically the same as uploading a repaint with an edited .bin file and that .bat file to copy the Geo files, which DTG does permit).
Cheers,
Michael
Am I correct that this means changing all path references to the new provider, but leaving anything that references a .GEO to the original?
A bogey.bin file would point to my provider, and an interiorgeometry or geometry would point to the originaL?
Thank you.
'PullmanCar'
ENR3005 wrote:PullmanCar wrote:GreatNortherner wrote:Hi,I successfully did this some time ago, but am now wondering if DTG .GEOs are protected in such a way this cannot be done?
I'm afraid that the "geometric hellscape" you're seeing after migrating the DTG assets is their copy protection at work. Using the .bat file copy method won't help in this case as the copy protection probably checks if the files are in their original location.
There may be a workaround, though I haven't actually tested this. You could try moving only the assets' blueprints (.bin files) to your new provider folder while leaving their internal geometry references intact (still pointing to their original DTG/RSC paths and Geo files). The copy protection should be happy and you could even share the .bin files (which would be technically the same as uploading a repaint with an edited .bin file and that .bat file to copy the Geo files, which DTG does permit).
Cheers,
Michael
Am I correct that this means changing all path references to the new provider, but leaving anything that references a .GEO to the original?
A bogey.bin file would point to my provider, and an interiorgeometry or geometry would point to the originaL?
Thank you.
'PullmanCar'
For Motive Power and Rolling Stock, provided you have followed the procedure for an old school repaint which is in the original provider's directory, all you need is make a copy of the bin from original provider folder where your repaint is located into your own folder, you don't need anything else. Unlike the example I laid out for route building above, you can rename this bin file to whatever you want, box_car_50ft can become SC Rail box_car_50ft. I would change the description internally under the <BrowseInformation> section to reflect your repaint.
Return to Rolling-Stock Design
Users browsing this forum: No registered users and 3 guests