• How To Uninstall Fsuipc Fsx

' Install complete FSUIPC version 4.938a 38a for FSX, FSX-SE and Prepar3D versions 1.4 and 2.0-2.4 - Deletes orphaned profile entries from INI - Keeps axis assignments for new profiles if so requested - Fixes error in Lua mouse.wheel function. Provides OOMcheck=Quiet option (no audible VAS warning) - Single byte offset 3124 gives P3D EXE version number, 10-14, 20-24. Installs and operates with the FSX Steam Edition FSUIPC version 4.938a only, with Mouse Macro making now working in FSX-SE: - If you already installed 4.938 you can just copy this DLL into the FSX Modules folder.' I got RC working using the referred fsuipc4 in my reply. My desktop is a WinXP Pro-32 with just two gig of ram. At first starting RC blanked the FSX display making it transparent.

One of the most commented on issues with FSX Steam Edition, following its release, has been that it was not compatible with Pete Dowson’s FSUIPC4 utility. FSUIPC now supports FSX: Steam Edition. First published on pcpilot.net. Pete Dowson, creator of the invaluable and powerful flight sim utility FSUIPC.

I cleared out RAM of unnecessary tasks. The problem was still there so I tried all with FSX windowed and it worked. I then restarted FSX-SE, went full screen, loaded a plan into a parked default B738. I alt-tabbed to the window with the RC shortcut and loaded it. I loaded the same FSX plan into RC and it worked perfectly for weather and clearance, no video issues. That's all I could test at this time due right now to my cramped desk space.

Be sure that you display screen is filled without black curtains. If so window FSX and go back to full screen. Before loading RC and starting it. The order of procedure appears to be important!

Load your flight in FSX and then load you plan into the FSX planner to give you a nav display of your choice. Then load RC and select the plan file, followed by starting RC. Switch back to the FSX display and you should be good to go. Before I proceeded with finding the video fix I detailed, I found if I alt-tabbed to another app and back, FSX blanked on return.

How To Uninstall Fsuipc Fsx

I did not start RC for this to happen so it is not specifically a quirk in RC or fsuipc windowing's facilities. I did find the video settings in FSX after the fix and they were correct. Apparently they were not correctly detailed in the Steam install process, hower I recal in installing FS9 there were similar problems. I am now in the process of getting ADEX working. It appears that some elements are missing from the Steam FSX SDK specifically the BGL compiler.

I do have it from FS9 SDK and it might be the same. At least ADEX loads a bgl for editing now. I'll also be checking ai-smooth 1.2 since some RC users implement that to get ai protection and spacing on approach to reduce take-off queues so RC can squeeze in between approaching ai. I have one more 'eccentricity' in general I found with the STEAM environment. When adding scenery, I found I needed to either install it in the existing AddOnscenery folder or my preferred method of creating my own 'Common FSX AddOn Scenery folder' within the FSX folder for scenery.cfg to load it correctly.

Apparently any such add-ons must be within the Steam Applications FSX environment to be accepted at load time. Just another FYI related to get scenery mods loaded and recognized by RC. (RC does not have to be loaded into the Steam environment).

There are a number of changes with FSX:SE compared to 'legacy' FSX - registry keys are different, install locations are different, support file (AppData and My Dcocuments) locations are different. A number of add-ons will have real problems with this, even before you get into version numbers and Simconnect versions! Obviously Pete will have to comment specifically regarding FSUIPC, but it will be a not insignificant change for developers to support FSX:SE and it may be a while, if ever, before a lot of add-ons are supported on it. Unfortunately my development PC finally died this afternoon. There's been an intermittent mobo fault on it for a while and Ihave a replacement PC on the way, but it isn't due till next Tuesday, and by then I will be tied up with family for Christmas.

Then I'm away till 4th Jan. I'll get on to FSXSE as soon as I can after that, but it'll take me a day or two to get the new PC into shape - and re-download FSXSE. So, sorry, it could be around 9th Jan by the time I have something. Sent from my iPhone! I've managed to recover my Development PC enough to do some initial investigation. Originally I thought FSX SE compatibility was just going to be an installer revision, to find the right Registry entries and paths, but I now see that FSX has been recompiled with a later version of MS development tools, so it's going to be a bigger job than I thought. In other words, it is unlikely to be just a weekend job as I thought at first.

I'm afraid that even if things go well on this invalided PC, Christmas, New Year and family take precedence over the next two weeks. So the estimate of 9th Jan I gave above is still really the more realistic one. I'm pleased to report that after a day of struggling (Friday) I got my development PC working well enough to do some work. I just dare not switch it off or I think it won't come on again!

It is crippled - it won't run P3D because I had to substitute an older non-DX11 video card. But it was okay for testing with FSX and FSX-SE, FSUIPC Version 4.938 is now available, and works as best as I can make it with FSX-SE.

The installer copes with both ways FSX-SE installs (free-standing or alongside FSX Boxed), and all the hooks appear to work except for the full wind-smoothing fiddle (rarely used these days with such good weather programs), and the 'G3D crash' patch. In the latter case the code in that area has changed and i'm not sure whether the fix would still be needed in any case. Feedback on any of the FSUIPC facilities would be useful, but I may not deal with it now for a week or two!;-) Oh, the latest version of MakeRunways, also available, also copes with FSX-SE's possibly different SCENERY.CFG location too. Happy Christmas!

I'm pleased to report that after a day of struggling (Friday) I got my development PC working well enough to do some work. I just dare not switch it off or I think it won't come on again! It is crippled - it won't run P3D because I had to substitute an older non-DX11 video card. But it was okay for testing with FSX and FSX-SE, FSUIPC Version 4.938 is now available, and works as best as I can make it with FSX-SE. The installer copes with both ways FSX-SE installs (free-standing or alongside FSX Boxed), and all the hooks appear to work except for the full wind-smoothing fiddle (rarely used these days with such good weather programs), and the 'G3D crash' patch. In the latter case the code in that area has changed and i'm not sure whether the fix would still be needed in any case. Feedback on any of the FSUIPC facilities would be useful, but I may not deal with it now for a week or two!;-) Oh, the latest version of MakeRunways, also available, also copes with FSX-SE's possibly different SCENERY.CFG location too.

Happy Christmas! Pete About the FSUIPC Module, I couldn't install it to Prepar3D v2.4.

It only found FSX and FSX Steam Edition. By the way, I almost forgot about the installer for FSX Steam Edition. I got an error saying 'Your FSX-SE installation is not suitable for this version of FSUIPC.

You may need to install an update from Microsoft.' However, it says that it installed into FSX-SE okay afterwards when in reality, it isn't. I also noticed from the installer this text: INSTALLATION FOR FSX-SE: SetupPath='D: Microsoft Flight Simulator X ' Checking version of the FSX-SE EXE.

Version 10.0.61637.0 (Need at least 10.0.62607.0) According to this, the installer thought FSX-SE is the FSX directory despite it wasn't.