May 1, 201214 yr Commercial Member Not sure if it was solved already, but I've just made Shade to work with Prepar3D v1.3 by renaming prepar3d.exe to fsx.exe and moving all P3D files and folders to the registered FSX location. 1. My FSX was installed in \\H\Games\FSX and Shade worked fine with it. 2. Next step was to move FSX files to another loaction (backup) and install Prepar3D into FSX's folder (same path - \\H\Games\FSX). 3. Rename prepar3d.exe -> fsx.exe and you're good to go. Shade works as if it was original FSX. Artem Crum, EASA PPL•••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••LINDA → Lua Integrated Non-complex Device Assigning•••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••
May 2, 201214 yr Can this moving process be faked by doing the FS registry hack that we use to install add-ons? I'd rather avoid to have to move everything around... Frank Olaf Sem-Jacobsen
May 2, 201214 yr I have changed the registry to have it point to P3D. Shade seems to work because I get the burn in message and completion with no errors. However there is no change in the display. I built a Neon green test to make sure I could see it and it does not appear. Does anyone know which files are supposed to be changed and what folder they are in? EDIT: I found the files and the folder. There are files that have the date and time of the last run of Shade but for what ever reason P3D doesn't seem to use them. Russ
May 2, 201214 yr Author Commercial Member Can this moving process be faked by doing the FS registry hack that we use to install add-ons? I'd rather avoid to have to move everything around... Didn't work in my case. Shade was still looking for old FSX location even if registry was set to P3D folder. Shade seems to work because I get the burn in message and completion with no errors. I could be wrong, but it seems Shade is making it's injection into fsx.exe directly. So, it will not work if you run prepar3d.exe after that. Try to rename prepar3d.exe to fsx.exe and then run P3D with this new exe. Artem Crum, EASA PPL•••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••LINDA → Lua Integrated Non-complex Device Assigning•••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••
May 2, 201214 yr Shade recognizes the registry change and files get updated in the P3D texture folder but do not influence the display at all. I have a FSX.exe( that is really P3D with the name change) and there is still no display influence either. Guess I will have to wait until the Shade gets updated for P3D Russ
May 3, 201214 yr I have it working but not in the way that crum did it. I will make a tutorial and post it, this not only goes for Shade, but many other addons, however it is best that you want to commit to using P3d only, as the way I will explain hijacks all of fsx's directories and certain files addons are tied to.
Create an account or sign in to comment