oskrypuch

CONFIRMED. That fixed it. Thanks. * Orest

I just read about the Nov 1st vs Nov 3rd 7.4.18 update issue. I have the former. Could that potentially be the problem? * Orest

Nope, the dot net refresh did not help. Same crash again. * Orest

On spec, I ran MS's Dot Net Framework repair tool. It did force a download and reinstall of .NET. * Orest

It is happening most flights now, FSUIPC (MS2020, registered FSUIPC7 v 7.4,.8) just shuts down. Only at cruise so far, and usually only once per flight (so not frequent). I can restart it, and very oddly, on start up my Parking Brake is enabled. Flying the PMDG 738. The "work" FSUIPC_WASM.ini file has been amended to stop LVar rescans, as per the message down forum. For good measure also amended the "base" .ini file. IAC, here is the crash report ... - System Provider [ Name] Application Error - EventID 1000 [ Qualifiers] 0 Version 0 Level 2 Task 100 Opcode 0 Keywords 0x80000000000000 - TimeCreated [ SystemTime] 2024-11-23T18:20:41.3350036Z EventRecordID 180664 Correlation - Execution [ ProcessID] 0 [ ThreadID] 0 Channel Application Security - EventData FSUIPC7.exe 7.4.1.8 67249226 VCRUNTIME140.dll 14.36.32532.0 c94bf788 c0000005 00000000000012fb 4284 01db3dcb6be4e527 C:\addons\FSUIPC7\FSUIPC7.exe C:\WINDOWS\SYSTEM32\VCRUNTIME140.dll 432ff2ce-3d5d-4ffb-bba2-85ab9dd87ad2 Is that any help? The other FSUIPC crashes are much the same, from the Windows event log. * Orest

That is a negative -- to "Using...GFDEV64.DLL" in the LOG file. Had a look, and indeed that DLL is not in the modules directory. I could have sworn I had put it there. Found it eventually in the GoFlight directory, so it got dumped into the wrong spot. All working now. Thanks for helping out. * Orest

Is there anyone that has been successful in making definitions in FSUIPC, of GoFlight buttons, running in P3D v4? * Orest

I have been reading this thread with interest. My problem is that no simple buttons and switches from Go-Flight modules are recognized in registered FSUIPC in P3D v4.1. Everything worked fine in P3D v3.4. Buttons are correctly recognized by FSUIPC from Saitek yoke and pedals and quadrant. I purchased and installed FSUIPC v5.121b. Everything else seems to be working. I installed the latest GFConfig as referenced above. Curiously there is NO v4 tab, just one P3D tab. I changed the directory to the new v4 install. The GoFlight bridge DLL is in the P3D v4 dll.xml file. But, there was no GFdev64.dll anywhere. I downloaded that file from the link above, and put it in the P3D v4 modules directory, along with the FSUIPC files. Still, makes no difference. Buttons are not recognized in the FSUIPC buttons assignments page, for GoFlight Modules. What am I doing wrong? * Orest

Isn't it great!! I'm delighted myself too. It just took a bit of persistence & thought, and a lot of head scratching. * Orest

Couldn't wait until tonight, checked at lunch. DELETED the modules\DLL directory, with the copied in 430W simulator files (the alternate solution) The 430W files had already been deleted from the .EXE directory (the initial solution) INSTALLED the new FSUIPC DLL (4812b) Started up FSX, no error messages, no "files not found" message. Selected an aircraft with the 430W installed, all worked as it should. This has finally been put to rest! * Orest

Outstanding Pete. A very satisfying end to a bit of a head scratcher. Will test that tonight, and report. * Orest

tick, tick, tick ... YES, #2 works as well. Erased all those moved files from the RXPGN1AE.exe (c:\Users\yourname\AppData\Local\Reality XP\RXPGnsSim\) directory and then moved all the contents of the original trainer directory (C:\Garmin\GNS400W\Trainer\*.*), instead to that new modules\DLL directory. Works just fine indeed! EXCELLENT!! The villagers are singing and dancing in the streets! * Orest

Yes, a real A-HA moment for sure! Sweet when you hit it. For me #1 works, will try #2 as well, as it is a little cleaner. * Orest

Bummer. What were you experiencing before? Does your default bootup aircraft, have any RXP modules installed? * Orest

I'm still not sure what is triggering this, and what role the two different versions of FSUIPC are playing. This error has been triggered by other issues as well (totally unrelated to FSUIPC), from my google searches. It may be some sort of timing change during initial load, with different programs or different versions of programs running, who knows. I am going to have a good look at the RXP registry entries, and see if cleaning all those out and reinstalling it might also fix this. Kind of hard to link swapping in a different version of a different program (FSUIPC in this instance) as somehow affecting this lookup. We will probably never know the mechanism. What is clear, is that this is not a single one-off issue, as a number of folks have been affected. The good side, is that all my RXP stuff is back now, and that anyone else that is similarly affected, are also likely to be able to get their setup fixed up as well. * Orest