Sharpangel

Good news that you have some trails to explore. Many thanks to resolving my own problem. I hope it can give some path to a general solution. Again if you need some specific testing, dont hesitate to contact me.

Morning, All seem to be ok now. Bravo to find the relation with simConnect. Do you need specific tests i can do to help ? Chris

Sorry FSUIPC4.7z

Here is the ini file Chris FSUIPC4969b.zip

You are right for precedent version from 4.939 to 4.966, but this is wrong with this dll. As i said before, when you stop the fly and change plane, each time the last used profile is charged. Thus you need to exit FSX.

I can assign This mean throttle and stick are now recognised. No problem. Just the need to exit FSX to create new profile or to change plane with his profile loaded. For profiles, my mind was to create generic porfiles for axis and then specialized profiles with switches and buttons, but i was wrong. I didn't remember this specific rule for profiles..

Morning, First put-in didn't work, thus i reinstall the original 4.969 then put the b dll version and the error window appeared, say yes and FSX start. I choose basic C172, can open FSUIPC, name profile "Monomoteur" and configure axis. The plane fly correctly. Cant create another profile. I leave the fly and takeoff again, the profile is keeped. Shutdown FSX and load it, Same flight conditions. "Monomoteur" profile is charged, can modify it, cant create another. Thus shtudown and reboot PC. No profile charged. Can create new one. When you stop the fly and change plane, each time the last used profile is charged. Even when you take a plane with existent profile. Cant create another one. Need to exit FSX and reload to empty the profile. Sometimes needed to click twice or more to open FSUIPC. May be a checkbox "exit profile" near "specific profile" could help.

I'am searching. It is about 19h30 here, i leave and come back tomorrow. Chris Récipient d’erreurs 50, type 5 Nom d’événement : BEX Réponse : Non disponible ID de CAB : 0 Signature du problème : P1 : fsx.exe P2 : 10.0.61637.0 P3 : 46fadb14 P4 : FSUIPC4.dll_unloaded P5 : 4.9.6.901 P6 : 5954fce3 P7 : 00051d7b P8 : c0000005 P9 : 00000008 P10 : Fichiers joints : \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER6C01.tmp.dmp \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER6CCD.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER6CCC.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER6CDC.tmp.txt Ces fichiers sont peut-être disponibles ici : C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_fsx.exe_d9106df46df71c2882bd8514b3630c23a21dda_68a774f9_16b672c7 Symbole d’analyse : Nouvelle recherche de la solution : 0 ID de rapport : b8bbfa3e-82cf-4977-be0e-f3788dbde653 Statut du rapport : 268435456 Récipient avec hachage : 91d54bd99477275713b8807ae138d8f5 ____________________________________________________________________________ Récipient d’erreurs 50, type 5 Nom d’événement : BEX Réponse : Non disponible ID de CAB : 0 Signature du problème : P1 : fsx.exe P2 : 10.0.61637.0 P3 : 46fadb14 P4 : FSUIPC4.dll_unloaded P5 : 4.9.6.901 P6 : 5954fce3 P7 : 00051d7b P8 : c0000005 P9 : 00000008 P10 : Fichiers joints : \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER6C01.tmp.dmp \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER6CCD.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER6CCC.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER6CDC.tmp.txt Ces fichiers sont peut-être disponibles ici : C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_fsx.exe_d9106df46df71c2882bd8514b3630c23a21dda_68a774f9_16b672c7 Symbole d’analyse : Nouvelle recherche de la solution : 0 ID de rapport : b8bbfa3e-82cf-4977-be0e-f3788dbde653 Statut du rapport : 268435456 Récipient avec hachage : 91d54bd99477275713b8807ae138d8f5 _____________________________________________________________________ Nom de l’application défaillante fsx.exe, version : 10.0.61637.0, horodatage : 0x46fadb14 Nom du module défaillant : FSUIPC4.dll_unloaded, version : 4.9.6.901, horodatage : 0x5954fce3 Code d’exception : 0xc0000005 Décalage d’erreur : 0x00051d7b ID du processus défaillant : 0x2af0 Heure de début de l’application défaillante : 0x01d2f0e0f7227c4a Chemin d’accès de l’application défaillante : G:\Flight Sim X GOLD\fsx.exe Chemin d’accès du module défaillant: FSUIPC4.dll ID de rapport : b8bbfa3e-82cf-4977-be0e-f3788dbde653 Nom complet du package défaillant : ID de l’application relative au package défaillant :

at start, FSX detect a problem with the dll and ask to run. After answer yes, FSX close and dont start. Chris

We just post together :=) I'll do that as soon as i have the link. Yes, many same problems only in appearence. Chris

Here is the LOG file. FSUIPC4.7z

I named " FSUIPC.ini debug x200000" to indicate that i added theese lines for your analyze as i saw in other topics Debug=Please LogExtras=x200000 I apologize for the omision. Upload of LOG file failed, i will try again in a moment.

Bonjour, I upgraded to 4.969 version for FSX. Running on Win10 64pro. And no more throttle axis, while stick have no problem. I have desinstall/reinstall the hotas and used JoyIDs, but same result. FSUIPC see the throttle but dont give Could you have a look to my files ? Many thanks FSUIPC4 Install.log FSUIPC4.JoyScan.csv FSUIPC4.ini_debug x200000 FSUIPC4.ini_debug x201000 FSUIPC4.JoyScan.csv