Jump to content
The simFlight Network Forums

DaveG

Members
  • Content count

    30
  • Joined

  • Last visited

Community Reputation

0 Neutral

About DaveG

Profile Information

  • Gender
    Male
  • Location
    Bedfordshire
  1. FSUIPC v5.122

    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
  2. FSUIPC Window not visible

    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.
  3. 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.
  4. 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.
  5. 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.
  6. 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.
  7. Did you uninstall the old client before installing 4.1? It won't update properly unless you do.
  8. 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?
  9. Mine works fine. Get rid of the Thrustmaster Target software if you're using that. Just install the joystick drivers only.
  10. Have a look here: http://www.prepar3d.com/forum/viewtopic.php?f=6322&t=120861
  11. 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.
  12. I'm on 4.1. I usually upgrade pretty much straight away when an update is released (as long there is an updated FSUIPC version to go with it! )
  13. Thanks for looking into Pete. I did try full screen last night, and as you say it works fine there.
  14. 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.
  15. Hi Pete, Using FSUIPC 5.113 in P3d 4.0.28.21686. 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=423, 3642, 15816, 261 Undocked=8, 661, 1894, 78 Each time P3d was run and the ATIS window opened, then the sim was exited. If I run P3d without opening the ATIS (or anything that uses that window) then there is no change to the entries in the .ini.
×