Jump to content
The simFlight Network Forums


  • Posts

  • Joined

  • Last visited

Profile Information

  • Gender
  • Location

Recent Profile Visitors

1,835 profile views

Morten's Achievements


Newbie (1/14)

  • First Post Rare
  • Collaborator Rare
  • Week One Done Rare
  • One Month Later Rare
  • One Year In Rare

Recent Badges



  1. Hi Mike Good that things has worked out for you now! However I'm not "fixed with the idea there is only one kind of USB hub". Don't know where you got that impression from..? I've had both non powered as well as powered USB hubs through the years and my personal experience haven't been good with any of them as they tend to cause instability with devices randomly falling out as in your case until now where you seemed to have worked things out - at least for the time being. However it is not unusual that providers of USB managed devices advises against USB hubs with their products for the same reason as I have experienced. So in other words, it's not a postulate that I'm eventing here for the occasion! That's all from me, and again, I'm glad that it seems to work for you now! /Morten
  2. Some more useful tips here and facts to take into consideration: https://www.google.com/search?q=how+to+provide+enough+power+to+usb&oq=how+to+provide+enough+power+to+usb&aqs=chrome..69i57.16575j0j7&sourceid=chrome&ie=UTF-8
  3. USB hub?! Not being an expert...but from what I learned hubs are no good! Makes unintended random conflicts. If you ran out of direct USB ports, you'd better off by plugginin a pci usb card into the MB for further DIRECT slots.
  4. Have a look here: https://forums.tomshardware.com/threads/is-it-possible-to-overload-motherboards-usb-controllers.3370120/
  5. Yep. let's analyze 😂.... however, button line is that Saitek hardware yoke is crab! Another affordable alternative could be the yoke: Honeycomb - Alpha Flight Controls. However not sure about reliability here...
  6. Hi Mike I also have a Saitek yoke which is falling out randomly as yours - typically during the most annoying moments, just after taking of or just before before landing! This nightmare has going on during 20% of the times in any flight through 5 years even though controllers are disabled in FS and everything is calibrated inside FSUIPC. Now I've had it here!! so going for a change - either a YOKO PLUS (as the one Peter got, as I understand it) or alternatively a less expensive one as VRinsight Flight Master Yoke III. Cheers, Morten
  7. All good John! Life isn't exactly getting easier for none of us with P3D choosing to do such a basically complete gamechanger update from v4 to an immature v5, which force everyone of us to keep both versions until they get v5 fully working in every aspect! I deeply appreciate all of you developers making a great effort to cope up with this dragging mess! Cheers, Morten
  8. John, I have no more patience to go on with another uninstall/reinstall experiment in order to verify your statement, passing through to your reinstall statement. That is, now when everything is working per copy/past from one folder another, editing XML files and so on - so I rather tend to believe you, as I don't remember my struggle in every detail anymore when tried to install this update. All I know John, is that you at least ought to tie up some of your odd bindings, for instance let one being able to browse to the correct folder in the uninstall phase. Cheers, Morten
  9. John if you are referring to the dialog box as shown down here as a "Browse" option, it is NOT possible to change any path in there! Choosing specifically P3Dv4 brings me to next dialog box which defaults uninstallation through a wrong path, which I'm not able to change.
  10. Hi John Let's end this discussion and stick to the conclusion from Pete that something seems to be wrong with me registry. As straight forward as your installer is, it should be hard to misunderstand. I do not intend to repeat here what I already wrote in detail about my experience with the installation process! The bottom line is that I already tried both installation options: 1. v4 and v5 in the same installation process 2. Separate installation processes for each versions of v4 and v5 The result for both these options, was that the only installation process that succeeded was for v5. The installation for v4 did NOT succeed in any way as the automatic path pointed wrongly into the v5 folder. And as you haven't made it possible for the user to change paths to the correct folder, both installation options turned out to fail for v4. Anyway, for now I made an instant solution for v4, by copying the content from the v5 folder to the v4 folder, and from inside here edited the add-on.xml to correct v4 path. So everything now works perfect! /Morten
  11. Okay Pete, thanks for your profound examination of alternative workarounds... I actually thought of the copying alternative myself, which is the most obvious alternative, for now and here. But if you have some precise input for the registry for the long run, I would appreciate a PM about those values as I'm use to deal with the registry (taken backup prior to this, of course). Besides this, I noticed that your update uninstaller/(reinstaller) had been inside my old P3Dv4 module and partly delete essential files in here and ruined the values for all joysticks in function regarding to P3Dv4. By mounting an earlier image backup and copying files from there into the module folder, I was then able to get things to work again. However this situation is obviously rather inappropriate regarding to future updates from your hand, so I better make changes to the registry as soon as possible! /Morten
  12. THAT did the trick! Have no idea! Nothing done on purpose here from my hand or at least I don't remember. Anyway, now deleted! I have separate folders for v4 and v5 as shown on the attached screenshots. When trying to install both for v4 and for v5 at the same time the installer ignores v4, but installs correctly into the v5 addon folder . When trying to install to v4 alone your auto installer don't point to the correct location - instead it points to v5! (No option here to change directories) Resulting in an empty v4 folder, except for a faulty add-on.xml file pointing wrongly to the v5 path instead of the v4 path (see attachment). Due to those facts mentioned above there's only one Install log regarding to v5, but none whatsoever regarding to v4 (only install log for v5 attached here) Looking into the old module location for v4 everything is untouched here, including the old FSUIPC version 6.0.13 which also shows up in P3Dv4 at present! So how do I get on from here?! /Morten add-on.xml InstallFSUIPC6.log
  13. In addition to the issue, I just upgraded the "latest" FSUIPC version 6.11 version from the official download page http://www.fsuipc.com/ - however when going through the automatic uninstall/ reinstall procedure, latest FSUIPC version now shows up, in both V4 and v5 as 6.0.13...?! Now what is that all about?! Anyway, tried again for a million times, to assign reverse buttons to v5 - still without any luck! Think you got an issue here?!
  14. Hi there As stated before ALL P3D internal controllers are disabled for BOTH v4 and 5, despite this fact and the fact that NO button action regarding the reverse button 9 and 10 is present neither in FSUIPC nor inside P3D internal controllers, reverse buttons 9 and 10 anyway is fully working anyway in v4 (but not in v5)! I've tried several times to assign those two buttons for reverse throttle 1 and 2 v5 inside FSUIPC - without any success. Please guide me, as something seems to go wrong!
  15. Hi John Thanks for your answer. As it is, I copied most of the FSUIPC.ini for v4 into the FSUIPC.ini for v5. Strange however as I can't see any trace of the reverse buttons in either the v4 nor v5 inis/logs..! At the same time I noticed, as mentioned before, that the reverser buttons works as expected in v4, but NOT at all in v5! In addition to this I might add that I previously implemented both versions with a Aerosoft PMDG 777 preset file into the Honeycomb configurator tool. So could it maybe be turns out that this Aerosoft preset file actually overrule certain button configurations disregarded whatever buttons I try to assign trough FSUIPC..?! Cheers Morten FSUIPC6_P3Dv4.ini FSUIPC6_P3Dv5.ini FSUIPC6_P3Dv4.log FSUIPC6_P3Dv5.log
  • Create New...

Important Information

By using this site, you agree to our Terms of Use. Guidelines Privacy Policy We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.