alphons10

Excuse my ignorance. There are 2 reasons I did not supply the LOG file. 1. I assume you mean the log file in Modules, where there are two. FSUIPC.log and FSUIPC4install.log ?? 2. If I am not mistaken, the only log file which would help would be the one created when the crash happened. (while FSX was running and I was using FSUIPC with the PMDG 737). If this is so, I am afraid I would not know where to find it. The crash happened when I was using Version 4.966c. And this was the last time I could start FSX with FSUIPC. However the first thing I did was to delete 4.966c and download and install 4.968 thinking that this might help and cure the error. ( See the first 2 error messages, one mentions the old version the other one the new version. So the log file with the crash info was in the old version which was deleted. The new Version never crashed - either it did not get loaded at all because FSX only started without FSUIPC or if I tried to include FSUIPC in the FSX startup procedure it crashed right away. So what I have now is the is the log file from the new version which has never crashed. It is attached but I doubt if it will be helpful. Thanks. FSUIPC4.log FSUIPC4 Install.log

Again thank you for your help. I can report partial success. 1. Attached the new ini file 2. I followed your suggestion to look on the PMDG side of things. I updated the 737NG to latest version via the automatic .updater. 3. I then started FSX without any Joystick or throttle connected, got the same error message, however I answered YES ( to use FSUIPC) anyway, and this time a new window opened asking me if I want to run FSUIPC. Long story short, FSX started normally, I loaded the 737 copied my FSUIPC ini file from the old version into modules in order to have all the assignments. and voila - it worked perfectly. I took off climbed to 10.000ft. and put her on autopilot for a couple of minutes to see that everything checked out. So far so good. Now to the NOT SO GOOD: Went and clicked "end flight" and now got the message: "FSX stopped working" - "Microsoft will end the program" . I ran FSX with a couple of other addon aircrafts and they work fine and I can end flight and program without any trouble. It is only and every time when I fly the PMDG 737NGX and try to end the flight or exit FSX - that FSX stops working. The good news is - Now it´s not your problem anymore - I mention it only in case anybody has a similar case. If you are interested I attach the event viewer Application Log which shows the app crash. 4. Now will have to start searching on the PMDG forum how to proceed to get rid of this nuisance. 5. A last question, To remove the 3rd device which was probably another Joystick or maybe the same before I used Joyletters, I guess all I have to do is just delete those entries from the ini file ?? Thanks for you help FSUIPC4.ini WinEvent_AppLog.txt

Thank you very much for getting back to me. Unfortunately the above advise did not work. I removed (unplugged) both throttle and joystick as well as deleting drivers to see if FSX would at least start and accept FSUIPC. ( Just as a side note I am only using generic drivers, don´t like the Saitek ones, having everything assigned to FSUIPC this worked like a charm) However FSX would not load and gave me the same erro message FS has detected.......a problem with: FSUIPC4.968 as in pic above. Don´t know what else to try especially as everything functioned normally for a year now. I have not added any addons or hardware, same stick, same throttle. Here is a more detailed run down how FSX froze. I added some buttons and re calibrated some axis on 3 or for aircraft's. I did not restart FSX between changing every aircraft just " Select aircraft" to load it and do my mapping in FSUIPC. So far everything worked fine. Last I selected my PMDG 737. It loaded however did not show any instruments, they were all black. However FSUIPC opened without a problem and I wanted to check if my axis are working correctly. Ailerons and elevators showed OK and I decided to better restart FSX and relaod PMDG to have the instruments working. I could close the FSUIPC screen but when trying to shut down FSX it suddenly went dead. and did not recover within at least 5 min. only alternative was Task manager which did the trick. And from there onward the error occurred - the rest as explained in my previous 2 messages. If it´s any help, I have a backup of my ini file before updating to 4.968 which I attach. this is the last working version. Thank you in advance for your help Al FSUIPC4.ini

Sorry maybe I wasn´t clear enough. The error happened with with the older version 4.966c but when I could not fix it I updated immediately to the latest ( see attachment) 4.968 but with no effect, same problem. HERE AGAIN A SHORT SUMMARY: I run Windows 10 64 / FSX-SE / FSUIPC4.968 registered version / UTX / GEX / Aircrafts; PMDG,A2A,Realair,F1,Majestic DML.XML attached FSX froze/crashed while assigning more axis and button functions to FSUIPC 4.966c for various aircrafts. It happened while having the PMDG 737 on screen. Shutdown of FSX which was only possible via Task Manager. Restart FSX same error message. If answer to error message is NO FSX runs without a problem. (But none of the FSUIPC funcions work of course) If answer is YES, FSX does not start and crashes right away. Moved FSUIPC.DLL to Desktop temporarily to see if it helps.Restart PC. NO change. Updated FSUIPC to version 4.968.Restart PC FSX ask me if I want to run this program ( as it always does with new addons). answer :YES 10 sec. later the error message appeared again now referring to the new version 4.968 Deleted all files FSUIPC files from FSX Modules, started FSX now without FSUIPC without any problem. restart PC Reinstalled FSUIPC 4.968 - same error message. Restart PC. deleted all entries which pointed to FSUIPC from FSX.cfg. Restart PC Problem persisted, same error message - answer YES crashed FSX - answer NO FSX starts but no FSUIPC. thanks dll_XML.txt

I have Windows 10 / FSX-SE / FSUIPC4.968 Until yesterday I had a smooth running system and nearly everything mapped for FSUIPC Version 4.966c. I needed to assign some additional tasks to some of the axis as well as come buttons on various aircraft's. I carried out some changes and finally wanted to change some FSUIPC mappings in my PDMG 737. That´s when suddenly FSX stopped working and froze on me. I could only shut it down via the Task manager. When restarting the PC, FSX would not start any more and give the the error message: Flight simulator has detected a problem.................... with FSUIPC4.DLL ( see attached pic) First I tried to delete the DLL file in modules and FSX started no problem, however nothing worked because I have everything assigned via FSUIPC. So I took the opportunity to update FSUIPC to the latest version 4.968. I deleted everything and reinstalled Version 4.968. When starting FSX it first ask me if I want to run FSUIP to which I answered yes, but than after a few seconds thje same message popped up again: Flight simulator has detected a problem.................... with FSUIPC4.DLL When answering no it stars without a problem, but when answering yes to run FSUIP , FSX crashes. So somehow deleting and reinstalling FSUIPC was not enough. But from here on I have no clue what to do ?? Thanks in advance for your help. PS: I tried to delete all FSUIPC entries from the trusted section in FSX.cfg to see if it helps, but no same error window !

This is just a note to say THANK YOU SO MUCH FOR YOUR SUPPORT. But I also wanted to report the success - that (for the moment) everything is back to normal and working. And that´s how I did it: 1. I deleted all known SAITEK drivers as well as I could find or identify them. However this alone did not solve the problem 2. I then tried one of the steps explained in one of the attached old messages you sent me. I went into "JoyID" and change the assignment for the Saitek throttle unit to another (random) one. And low and behold everything is back to normal and me - a happy Camper. Thanks again Alphons

I updated to 4.963 but without success. I did reassign all axis and buttons totally from scratch in the new PC, it is not the ini file from the old one. Well it really isn´t a new pc I just did a clean Windows install and purchased FSX-SE. And as I mentioned before the throttle assignment axis as well as the assignment of all buttons worked flawlessly and I used it on several flights. But of of a sudden it only executed the assignmets of the joystick. I wonder if reinstalling FSX-SE completely would be of any help. Because it doen´t make any sense to me that FSX-SE lets me assign the X55 throttle no problem, as well as the Thrustmaster Joystick. yet FSUIPC has no problem with the Thrustmaster Joystick it only doesn´t seem to see the X55 throttle unit.

Sorry I forgot to include the Log file last time: In the meantime I tried a few mor things, but neither the Axis nor the buttons of the Saitek X55 throttle can be assigned in FSUIPC, FSUIPC4.log

Yes, I mean " not seen in the assignment tabs". i.e.: when I load an aircraft and I move the aileron the assignment shows up in the FSUIPC axis., same with elevator and rudder, yet when moving any axis on the throttle nothing happens in FSUIPC and the axis windows stays empty, Thanks Here is my ini file. FSUIPC4.ini

I installed FSX steam today and setuo everything like I had in my boxed FSX version. Windows 10 , Thrustmaster M16000T as Joystick, Saitek X55 HOTAS Throttle ( not using the X55 Joystick it is not smooth enough for my taste). No specific drivers installed . Deleted all axis and button assignments in FSX and programmed everything the way I had it on my old system. Did a couple of trials and everything worked like a charm, FSUIPC axis, buttons , calibration, so I started reinstalling my addons. A2A C182 and 1 addon airport. Now suddenly the Saitek X55 throttle unit was not recognised by FSUIPC. I fiddled around finally removing the ini file to see if by building a new one it would help - but nothing. Finally ,I reassigned the throttle axis, prop pitch and mixture control for the X55 throttle in FSX and it worked without any problem. In other words the X55 is recognised by FSX. Problem is I´d like to assign everything back to FSUIPC which gives me better results and it fine tunable. What can I try next to get my throttle back in FSUIPC ? THANKS IN ADVANCE

SOLVED/ I just upgraded to the PRO version of the Dash-8. And as on all my other aircraft I assign all Controller (X-55 Rhino) functions to FSUIPC without any problems. I tried the same with the new Pro version. Elevator, Rudder, both throttles all other buttons which I assigned from my X-55 Throttle/Stick combination work, only the aileron does not move at all. I deleted the Dash-8 entries in the ini file and setup new, but without success. Nothing else in FS is assigned to the Saitex X-55, not do I use their software. ( I ran my PILOT version of the dash-8 without any problem with the same setup for month.) I attach my ini file, hoping for some help on the issue. AFTER RESTARTING SEVERAL TIMES THE AILERON SEEMS TO WORK, AT LEAST FOR NOW / THANKS FSUIPC4 - Shortcut.lnk

Plugging it in directly instead of the hub did the trick. YOU SAVED MY DAY !! THANK YOU SO MUCH

Two days ago a strange phenomenon started to happen in my FSUIPC. When I open the FSUIPC Window in any of the already setup aircrafts or even with a new one, in the axis assignment window as well as in the button assignment window things start happening automatically. Assigned and non assigned buttons of my appear automatically in their windows. Buttons with assignments with their respective function and non assigned ones just pop in and out of the window. Changing frequency between 5 and 12 seconds. There seems to be no apparent pattern to it. In flight this leads to uncontrolled landing gear or flaps retractions or extensions. It all seems to happen on Joy 0 which is the throttle controller part on my Saitek X-55 Rhino. When the simulator is in PAUSE it happens less frequently. I unplugged the joysticks, did several restarts, but the problem still exists. Has anybody had a similar experience and/or any advise how to fix it ?? Thank you

Thank you so much for your input - and yes, now everything works like a charm. But let me just explain how I got into this situation in the first place: Of course I assigned yoke and throttle via the axis assignment. However when trying to assign the pan view I checked the "Send direct to FSUICP calibration" instead of the "Send to FS as normal axis". Therefore I did not find any "Pan view" in the drop down menu but did find one on the right side. So it´s not so much a matter of ignoring the manual, but rather not being careful what boxes are checked. Thank you however for dedicating me your time and especially solving my problem. Al

Sorry, I might be too dumb to set it up so it´s working. I assigned it in axis - the result is I can pan up only ( and quite jagged). I attach a pic. What did I do wrong or not do at all ? THIS IS A SCREENSHOT OF HOW I SET IT UP Thanks a lot