Jump to content
The simFlight Network Forums


  • Content count

  • Joined

  • Last visited

Community Reputation

0 Neutral

About danewatson

  • Rank

Profile Information

  • Gender
  • Location
    White Rock, Canada
  1. Yes Dave you are correct. Disabled Controllers, re-calibrated in P3D, then reassigned and re-calibrated in FSUIPC and all is good.
  2. Thanks again Thomas found it and all is now good.
  3. Thanks. Will check it out this evening.
  4. No, I actually did not see where to disable (obviously I missed it). I did do that in FSX, so it makes sense I should do it in P3D. I will check that out, thank you. Will report back.
  5. Yesterday installed P3D v4.1 - install and initial running was perfect - only used the default setup including the built in assignments for joystick, rudder and x-box controller (used for Chase Plane). Then it was time to install my first addon (and most important) - FSUIPC-5 with a successful registration. I then deleted all control assignments in P3D (a blank slate). Then copied over from my FSX-SE my FSUIPC-4 and all my LUA files. Renamed FSUIPC-4 to FSUIPC-5. Then tried to ensure all controls were assigned and calibrated. All works well except my joystick ailerons and elevators - they are jumping all over the place (jittering). I recalibarted my controls in P3D and then recalibrated in FSUIPC - the jittering subsided a wee bit but the aircraft is very eratic in flight as an example if I push forward just a touch on my joystick for down elevator the aircraft reacts with a very abrupt aileron bank. It's not my joystick, because when I shut down P3D and start up FSX evrything is perfect and it was also perfect with the P3D built in control assignments before I installed FSUIPC I have tried everything I know - can you help with this. I am attaching three files - ini, csv, log FSUIPC5.ini FSUIPC5.JoyScan.csv FSUIPC5.log
  6. JoyNames Problem

    Thanks Pete, I did fix that. Deleted all the Helicopter related aircraft and profile and started over from within FSX & FSUIPC. All is now good, now UseProfiles=Yes in the INI file.
  7. JoyNames Problem

    Thanks again Pete. Re. The Helicopter Profiles, the only one re-installed is 1=WILCO-FSTR, the other two are not yet installed. I will review. Dane
  8. JoyNames Problem

    Pete - what can I say but simply THANK YOU YET AGAIN. I now completely understand the problem - due to my new Windows install and because I thought I was doing the right thing by pasting in my previous FSUIPC4.ini file, the settings did not jive. I made the changes and all is excellent. Thank you. PS - I have purchased your FSUIPC5 as I am going to be purchasing P3D v4 next week. Can I copy in my FSUIPC4.ini file and simply change the name to FSUIPC5.ini? Is there anything other file(s) that can or should be copied over?
  9. Due to Windows 10 Version 1709 I had to reset my PC during the installation of Version 1703, then I had to reinstall everything all over again. Everything is working great but I am stumped by by FSUIPC.ini file indicating <<MISSING JOYSTICK>> and also the second and third two lines that are in my saved FSUIPC.ini file get removed when I load FSX. I have attached my ini and my log files for review. LINE 2 MISSING - 0=Radio Switch Device LINE 3 MISSING - 0.GUID={B7441AB0-BD61-11E6-8009-444553540000}) [JoyNames] AutoAssignLetters=No C=Controller (Gamepad F310) << MISSING JOYSTICK >> C.GUID={A628CE50-0254-11E7-8001-444553540000} J=Logitech Extreme 3D << MISSING JOYSTICK >> J.GUID={F7DD4480-BD9C-11E6-8001-444553540000} R=T-Rudder << MISSING JOYSTICK >> R.GUID={D17FC700-30DC-11E7-8001-444553540000} 1=Controller (Gamepad F310) 1.GUID={18ECDE50-CD6F-11E7-8002-444553540000} 2=Logitech Extreme 3D 2.GUID={23DBF0D0-CD6F-11E7-8003-444553540000} 3=T-Rudder 3.GUID={EFC4ACB0-CD6E-11E7-8001-444553540000} FSUIPC4.ini FSUIPC4.log
  10. I don't mean to keep this post going but I just wanted to report my final update to my issue. I got my PC back from my tech guy today and all is well, I did not have to do a factory reset. What I did do was to uninstall the Windows Update KB4038788 restarted the PC, launched FSX-SE and went into the Load Flight... menu under FSUIPC in the ADD Ons - I DID NOT HAVE AN ISSUE. So for those experiencing crashes this may be the cause - if you copy and paste - Windows Update KB4038788 causing FSX crashes and P3D - into a Google search you will see that this is an issue for many people. That's all for my post... Regards, Dane.
  11. Regarding the above thread. My PC is in the tech shop as the technician is trying to resurrect it without me having to do a full factory reset. I have just finished reading three different threads that points to a recent Windows update which is causing FSX, FSX-SE, and P3D to crash - this could very well have been my problem?! Windows Update KB4038788 causing FSX crashes and P3D
  12. Thank you Pete, I will act on all this in a number of days as my computer is not happy. It decided to crash last night and will not restart it seems that I may have to do a complete factory reset and begin the extremely long and frustrating task of rebuilding and reinstalling everything from scratch, that is if I can remember everything - I am not a happy flier at this moment... Regards, Dane.
  13. Thomas, I installed FSUIPC4.971 but it did not solve the problem. I have done a great deal of elimination process and nothing seems to make a difference. What I have found is very strange but I can repeat the Microsoft crash every time - when I go to the ADD-ONS drop down and open the FSUIPC Loaf Flights... and then move my mouse up or down through the various saved flights, that is when it crashes. If I do not move my mouse in the saved flights area it does not crash - like I said I find this very strange. I am including another FSUIPC log as well as my FSUIPC ini file in case you want to have a look. FSUIPC4.ini FSUIPC4.log
  14. Thank you I will do that, then see
  15. FSUIPC4, Version 4.966c I have noticed that sometimes FSX-SE crashes the moment I go into the ADD-ONS Load Flight... when I have the Default Flight loaded. Other flights do not seem to cause this problem. I have attached my FSUIPC4.log for reference EDITED Just edited my info above as well as attaching this error message FSUIPC4.log