I had a play around with a couple of scripts to make it easy to switch between the two texture sets.
I dropped these into the following folder, just above where the two texture sets sit:
Each DOS script has the following line, one for the “clean” version, and one for the “default” worn one:
xcopy .\Clean\* ..\SimObjects\Airplanes\JF_PA28_Arrow\TEXTURE.VC\
xcopy .\Default\* ..\SimObjects\Airplanes\JF_PA28_Arrow\TEXTURE.VC\
Do not put both lines in the same script, one goes in one, one goes in the other. If they are both there it will simply ensure the last line is the one that “wins” as it were, but wouldn’t actually break anything.
The script assumes it will be in this location, and expecting the two folders to be in the same folder as the script itself. It then goes one folder up, the two “…”, and then back down to the folder where the textures are.
I left the option to automate the “do you want to overwrite this file” off so you can see what it does. It should ask you this:
Pressing “Y” will overwrite all 14 files. I played around with this in the developer mode, and one annoyance I found was simply reloading the aircraft doesn’t actually load the plane with the new texture set. To do that I had to switch to a different plane, then back again. Then it would show me whatever script I last ran.
I made a backup copy of the plane in case, but I have the original installer anyway.
If you do play around with this in the Developer mode. even opening it, and closing it while flying is enough to ensure that flight will not be logged. So if you want to avoid that, make sure you load a new flight with Developer mode off. Something else I noticed that is likely a bug is that closing the developer mode via the menu at the top left will still leave developer mode on the next time the sim launches. To turn it off for the next session, go to the General menu, and turn it off there.
If you still have permissions problems, you can run the script with “admin” rights. I did not have to do this with the MS Store version.
