plug_nickel

I've tried "slicing & dicing" P3Dv3 until I'm blue in the face and still haven't been able to accomplish what the OP is asking. At this point, I don't think it can be done, however; I still " kick the can" on an older pc just for the he** of it. What I have found that works for me is installing P3Dv3 on system drive and ALL scenery, including Orbx, on a separate drive linking paths back through ProgramData. No symlinks are necessary. Once I've got system drive where I want it, I image it. I do the same thing with my scenery drive. As a final backup, I also keep a master copy of Lockheed @ ProgramData and Roaming as well as Orbx @ Local. There are some concessions. I don't update P3D scenery or content, just the client. Since I'm running several dedicated scenery installs and specific simobjects, not updating those is of no concern to me. The only folder I have to watch is Autogen when updating the client. Orbx and a few other installers update that folder and so I run it exclusively from the scenery drive. Should I lose system drive or it becomes corrupted, I'll reinstall the image. Same goes with the scenery drive. If P3D goes south, all I have to do is reinstall P3D and if necessary, reset the license, and then copy over the backup ProgramData folder. Reinstalling any scenery isn't needed. Al aka plug_nickel

....and, if I might add, neither is this approach: F:\Prepar3D v2 G:\Prepar3D v2 Scenery Test (which consists of the following folders removed from P3Dv2 root): Autogen (Default) Effects/texture Scenery (Orbx) (Default) SimObjects ( all Default or whatever you prefer) Sound Texture (Default) Weather What I've found is that P3Dv2 can be fully manipulated like FSX without having to use symbolic or hard junction points. FTX Central fully updates manually or through the FTX Central GUI. The way P3Dv3 1.0 is structured, this is also possible. It much more involved in initially setting up. I'm currently in the process of tracing what is written and what is over-written in Texture, Global and World scenery folders. It seems that the majority of P3Dv3 default files are left intact; however, it's to early to tell. Actually, it's kind of like setting up IL-2 1946 and fully merging Modact 5.30, HSFX7, 4.12.2m Stock and C.U.P. into one install. Cheers and have a very Merry Christmas or Holidays. oops...forgot one!

I've been using FXAA in P3D along with nVidia Inspector without any ctd's. So I tried something different, once again, to see if SweetFX would run. I copied SweetFX v1.3.3 into my stock copy of P3D; no add-ons, mods no nothing. I then bak'd "dxgi.dll" and "dxgi.fx" and then flushed the shaders for P3D to rebuild. I did not start nVidia Inspector. Upon loading P3D, the green FXAA indicator box appeared upper left corner and P3D fully loaded w/o ctd. I took a 10 minute flight in the Mooney and then exited. Does this mean SweetFX is fully initializing or is it just the FXAA anti-aliasing mode? Can someone else try this and confirm? plug_nickel

Final input regarding having separate copies of P3D. I don't have FSX installed, so I use the FSX-2-Prepar3D tool for installations and simply keep it activated. All works well. Currently I have: P3D Master; PNW; PFJ RTTM; C_NRM; Oceania AK_CAN Military P3D has now been reduced to only a shell to save hdd space and has been renamed to .bak_stock in order to maintain any .dll files. All copies are fully functional and the ORBX FTX Central, files, etc, are independant of each other. I have one Prepar3D.exe to run, one master XML file for ORBX Objectflow, FSUIPC, A2A Accu-Feel, one Prepa3D.cfg file and separate scenery.cfgs. To run any of the scenarios, I rename that folder to Prepar3D and swap in the correct scenery.cfg file. The load times have been greatly reduced since I'm only enabling one scenario at a time and only the required scenery. All base scenery files not being used have been removed. To update, or add anything, I rename that folder to Prepar3D, enable FSX-2-Prepr3D if required and install. The whole point of this exercise was to see just how lean an install per scenario I could achieve that could be potentially imaged for use in a future ram drive build. I just hope P3D v2 isn't "code bloated" when it's released and that everything I have will be Dx11 compatible. plug_nickel

Well to update, I now have the following: 1) Prepar3D installation; 2) Working copy of Prepar3D called P3D PFJ RTTM which consists of Orbx Pacific Fjords, PAKT, CYBD, CZST, Tongass Fjords X and Return to Misty's Moorings. Getting it to load correctly was completely counter-intuitive; not like setting up copies of FSX and was a "pita". Now I need to see if I can get OpusFSX demo working with both, but not until I take something for the freaking headache. plug_nickel

Has anyone configured P3D for separate or dedicated flight scenarios? Way back when, I had several FSX copies for different configurations: military, general aviation, bush, etc, along with corresponding scenery. Just thought I'd ask before starting the "trial and error" method. plug_nickel