235: No More Basic Scheme

Found this free utitlity, FSX Scheme Fix, at Flightsim Estonia where I purchased a copy of its FSX to P3D Migration Tool recently.

Don’t know about you, I am quite annoyed by the Windows switching to Basic Scheme while FSX is loaded.   This freeware eases my pain.

Regarding the company’s FSX to P3D Migration Tool, a bit disappointed so far.

Don’t get me wrong, I am not saying that the tool is bad.   It does greatly simplify the process of installing FSX addons onto P3D V1 or V2.   However, I don’t like to be unaware of what files are installed onto my system.  In particular, the tool will modify the basic file handling structures of both simulators, which then acts in a way I don’t feel comfortable with.

Furthermore, the tool still couldn’t guarantee a P3D incompatible addon to be P3D compatible after migration.   Success or not still depends on the addon itself.

For example, in Orbx’s Orcas Island and Diamond Points areas where I previously migrated the addons to manually are having problems of autogen object disappearing.   Problems remain via the tool.

Not sure the real cause yet.   Perhaps there are files “non-transferrable”.   Will further explore.

7 thoughts on “235: No More Basic Scheme

  1. THANKS TOM, THAT FSX SCHEME FIX IS EXCELLENT. I KNEW SOMETHING WAS GOING ON AND I KNEW I DIDN’T LIKE IT BUT I DIDN’T KNOW WHAT IT WAS. NOW I KNOW AND NOW I’M HAPPIER AND I SWEAR I GETTING BETTER SIM RESPONSE AS WELL. MAYBE MY IMMAGINATION BUT I THINK IT DID IMPROVE THINGS A BIT.

    Like

    1. Hello Rick and everybody,

      Could you help me please… I purchase The “FSX scheme fix” on flightsim estonia website but it’s ” temporarily not avaible”..
      It’s very important for me to get that file because I built a curved screen and the warp switch off during flight caused by that aero windows theme..
      Could you send to me by e-mail please.

      Jean-lou

      jlou974@yahoo.fr

      King regards

      Like

  2. Tom,

    I could kill virtually all blurries by assigning (i) all cores (yes, really all including core 0) (ii) high process priority to Prepar3Dv2 via an external tool. This was a hint on the LM forum and worked quite well for me. However, keep in mind that I exclusively fly the slow C172. I don’t have an idea if this works with e.g. a high-speed 777 300 feet above ground (just to name an extreme scenario). Of course you have to keep in mind that this way you assign all ressources of the machine to just one program. I always reboot after finishing a flight.

    I’d suggest just checking if it helps by making both settings in the task manager after starting the program. If so, you can set it either via a tool or via the command line permanently. In addition, I am not sure 2.2 will react the same way, as these optimizations are continually worked upon by LM.

    Kind regards, Michael

    Like

  3. Thanks Tom, for the headup . I did not know this tool.

    Concerning the Migration tool, I can share your experience. The tool itself is clever and I never experienced it causing any trouble on my system. However, I would advise against installing any non-Prepar3Dv2-fit Software into Prepar3Dv2. Notably, ORBX actively discourages this. Not only can you expect not all functions to work (notably Orca’s Island and Diamont Point might well use use some Flow Technology which ORBX is only in the process of porting right now). It even might introduce instability into your system, where you never can say what’s on the root. I had Prepar3Dv2 excellently running until the point where I installed a whole bunch of legacy Aerosoft sceneries, when CTDs started to appear. This may be a coincidence, who knows, but I can’t exclude the ported sceneries (often introducing code into dll.xml and/or exe.xml or effects code or what else) being responsible for the trouble.

    I wait for Version 2.2 due on Monday for a complete re-install and decided to re-install FSX (with SweetFX) just for those sceneries not being Prepar3Dv2 fit.

    Kind regards, MIchael

    Like

    1. Hi Michael,
      Thanks for the note about the Migration tool, especially about ORBX’s addons in which I normally fly.
      I didn’t get the tool earlier because I didn’t want to install something I had no idea of. That’s why I used to manually put the scenery into P3D myself. One reason I got the tool mostly out of curiosity if it really makes a difference. So far, no, not to those I found problematic.
      You are right that dll.xml and Prepar3D.CFG are in some ways different from those in FSX. All Objectflow files installed by Orbx in dll.xml crash the system. Also, I found the newer the Orbx files, the more likely they are incompatible with P3DV2. Obviously we will have no choice but to wait for Orbx to release compatible installers.
      Yeah, I am excited to get v2.2 on Monday and will do a complete reinstallation as you plan to do.
      P3D looks stunning on multi-monitors.
      BTW, do you encounter blurry issue? It is sometimes quite significant on my setup and I am working around to fix it. Any suggestions are welcome.
      Tom

      Like

Leave a comment

This site uses Akismet to reduce spam. Learn how your comment data is processed.