Jump to content
The simFlight Network Forums


  • Content Count

  • Joined

  • Last visited

  • Days Won


Everything posted by DaveG

  1. I've set my throttles up as "Throttle1 Axis Set Ex1", "Throttle1 Axis Set Ex2" etc, and the prop pitch as "Prop Pitch Axis Set Ex1" which seems to work fine. Only issue for me with this is the "map 1->12, 2->34" option on the calibration page doesn't work with these. Also, if you have the PMDG AFE turned on, in some situations he overrides your throttle commands, so they don't appear to work.
  2. If you haven't bitten then bullet yet and reinstalled, you could try MSFS Add-on Linker, available at flightsim.to. That let's you install add-ons anywhere and then links them to the community folder. https://flightsim.to/file/1572/msfs-addons-linker
  3. Thanks for the update John. Is it safe to assume I can use my existing ini file & profiles with V6?
  4. I just disable controllers entirely in p3d (there's a checkbox for it) and assign everything via fsuipc.
  5. There's some lines from the begining of the DLL.xml posted above. If that's the complete contents then that would cause the XML not to be read.
  6. Theyll be custom coded items, rather than default commands.
  7. Sorry, I don't know the answer to your problem.
  8. Erm, just backup your FSUIPC5.ini before updating. My ini had been with me since fsx days.
  9. To use ON/OFF/ON switches, in FSUIPC you can set the command to be sent when the button/switch is released, so you would set one ON position to your fuel pump Hi (make sure it's not set to repeat) then set the fuel pump OFF command to sent on switch release. Do the same for the fuel pump Lo position.
  10. Pete is on holiday until the 23rd. See the post at the top of this page.
  11. Have a look in this thread : http://forum.simflight.com/topic/84933-prepar3d-v42-simconnect-and-fsuipc-5123c/ Thomas posted links to both 5.122 and 5.123b
  12. I use 5.122 at the moment with no problems. Updated to 5.123c and had the issue mentioned here with the dialog not showing. Went back to 5.122 and all is OK again.
  13. I don't know if you are aware, but Justflight have a Vulcan in development that looks set to be a step or two up from the old Iris model both in terms of modelling and systems. No idea how far off it is, but it may be worth looking at.
  14. Many addons use custom code outside of the default. It would be impossible for FSUIPC to include a list of everything for every addon. I expect the Vulcan fuel panel uses a mixture of default and custom code. You'll probably need to write some simple custom code yourself to interface with Iris code. Have a look at LINDA (https://www.avsim.com/forums/forum/424-linda) That may make assigning the switches easier and it includes an excellent tracer to find out what actually happens when switches etc are operated.
  15. No problem Pete. Don't want to change anything in the windows control panel as that will affect everything and the sensitivity is OK elsewhere. I may load up the software that came with the mouse and see if I can do anything on a per-application basis.
  16. Hi Pete, I'm using FSUIPC 5.122a in P3d 4.1. I have controllers disabled in P3d which stops the built-in mouselook from working, so I've enabled it in FSUIPC instead. Works fine, but it's rather sensitive. Is there any way to reduce the sensitivity? I've look in the docs but couldn't see anything. Just wondered if there is an undocumented option, or maybe I just missed something. Cheers.
  17. Did you uninstall the old client before installing 4.1? It won't update properly unless you do.
  18. Sounds like.a classic case of conflicting controls. You say you've cleared all the assignments in P3d, but have you tried disabling the controllers entirely in P3d?
  19. Mine works fine. Get rid of the Thrustmaster Target software if you're using that. Just install the joystick drivers only.
  20. Have a look here: http://www.prepar3d.com/forum/viewtopic.php?f=6322&t=120861
  21. If you install p3d v4.1 over the top of v4.0 it will not install properly. You'll need to uninstall the v4.0 client first, then install v4.1.
  22. Thanks for looking into Pete. I did try full screen last night, and as you say it works fine there.
  23. Hi Pete, hope you had a good holiday. I do run in windowed mode usually although the window is maximised and does not move. I use 2 monitors, one for P3d, with other related programs on the other. I'll try full screen tonight and see what happens.
  24. Hi Pete, Using FSUIPC 5.113 in P3d There seems to be a possible bug in FSUIPC positioning of the green message window (used for ATIS etc). Each time P3d is run and the message window opened it's positioned further down the screen. I see the location is held in the FSUIPC.ini, and this value is changed when P3d is exited. Here's the relevant part from 3 successive runs: [Window.Message Window] Docked=186, 1798, 15850, 261 Undocked=8, 661, 1894, 78 [Window.Message Window] Docked=304, 2720, 15833, 261 Undocked=8, 661, 1894, 78 [Window.Message Window] Docked=42
  • 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.