Jump to content
The simFlight Network Forums


  • Content Count

  • Joined

  • Last visited

  • Days Won


Donovan last won the day on October 19 2016

Donovan had the most liked content!

Community Reputation

5 Neutral

About Donovan

  • Rank
    Advanced Member

Profile Information

  • Gender
  • Location

Recent Profile Visitors

1,235 profile views
  1. I use FltplanGo, the GPSOUT facility of FSUICP, over a bluetooth connection successfully and reliably using an Android tablet on P3Dv5.1, as well as FSX and FSX-SE, both on Windows 10 and Windows 7. I don't have any apple devices, but the basic outline is in the thread "Sending GPS data to Android Apps (Bluetooth)" in the user contributions section. If this is the type of set-up you are trying to employ then I'd be happy to outline my setup. Works wonderfully. I would assume it will work with WingX (although I have never used that software), but it works flawlessly with FltplanGo.
  2. Sorry to make a late addendum to the thread, the limit to the max number of lua files has come up before, but in a different context, but I suspect you were already aware of it. You've probably already worked out a solution, but you might want to also look over the thread: It might be useful for you... Or not...
  3. In the same vein, with slightly different syntax is a similar workable method. (Flag set using LuaSet, param) --lights.lua function LightsControl(flag) if ipc.testflag(1) then --TaxiLights ipc.clearflag(1) Taxi=ipc.readLvar("L:AB_TAXI_LT") if Taxi==nil or Taxi==0 then ipc.writeLvar("L:AB_TAXI_LT", 1) elseif Taxi==1 then ipc.writeLvar("L:AB_TAXI_LT", 2) else ipc.writeLvar("L:AB_TAXI_LT", 0) end elseif ipc.testflag(2) then --Landing Lights ipc.clear
  4. Re-downloaded, and installed 4.973 without a problem this evening. No idea what the original error was -- had to have been the loose nut behind the yoke (me... ) Thanks for the speedy reply and all you do! Best, Don
  5. In keeping my FSUIPC current, it appears that the latest update to 4.973 contains 4.972a of FSUIPC.dll. Am I mistaken? The install log appears fine without errors, but the version displayed in FSUIPC.log, and the heading data in the processed FSUIPC.ini still shows 4.972a. Just checking in case I need to do some debugging on my side. Best, Don
  6. Hi Roger, I don't use any Saitek drivers, but solely use FSUIPC4. The Yoke MODE switch, in the following example is B22 (left position="Mode 1"), B23 (center position="Mode 2"), and B24 (right position="Mode 3"). Using The conditional button checking features, I have three modes enabled. This is just a snippet example from the .ini file. You have to manually edit the .ini file to set up the conditional programming. See FSUIPC4 for Advanced Users section "Compound Button Conditions," page 24 and Appendix 1 - "Doing more with your joystick," starting page 50 for the documentation.
  7. Hi Pete, Prior to starting FSX, I setup my flight plan in Opus FSI, then select Export PLN Flight Plan to C:\Users\DBT\Documents\Flight Simulator X Files. I start FSX, which automatically loads the FLT file located as C:\Users\DBT\Documents\Flight Simulator X Files\FSX Startup for Complex Aircraft.FLT . From the Free Flight screen I'll select the aircraft, modify the fuel load, select the departure location, manually load the flight plan into FSX, set the time, and then Fly Now. Once the flight is started at the gate/ramp, I manually start TrackIR, and lastly manually start Opus FSI.
  8. Hi Pete, This is a "small-potatoes" report, and doesn't appear to actually affect any functionality at all, but just in case there is more going on behind the scenes I thought I should let you know. After updating FSUIPC4 to ver 4.971b, the following notation began appearing in the FSUIPC4.LOG: (In RED) ********* FSUIPC4, Version 4.971b (15th October 2017) by Pete Dowson ********* Windows 7 Professional 64 Bit with SP 1.0 reported as Build 7601 (OS 6.1) fsx.exe version = 10.0.61637.0 Reading options from "F:\FSX\Modules\FSUIPC4.ini" Running inside FSX on Windows 7 Module
  9. If you actually want a button sequence, rather than the more standard button combination (shift+key, ctrl+key or shift+ctrl+key) your best bet is a lua script, but I believe it could also be done with a MCRO.
  10. Ahhh, understood ! If the required logic exceeds what is easily accomplished with the button flags, you can always write some short macros triggered by the button presses. We all started with no experience! But, it sure is satisfying in the end when you work it out! The APPENDIX 1: “Do more with your joystick” from the Advanced User Guide is a fantastic reference for button programming. Best in your endeavors! Don
  11. Admittedly I don't have my wits completely wrapped around the entirety of your button programming. I am puzzled about your flag setting and clearing and whether you are actually accomplishing what you intend. FSUIPC will automatically toggle the button flags with sequential presses from (-) to (+) to (-), so I'm a bit unclear of your use of the flag sets and clearing with your assigned buttons, but if you've double checked your logic on this then ok. Re: the F1 Mustang's input.ini file -- I and others have found that it works only via assigned keys as the intermediary, then you can assi
  12. It appears from your illustrations that you're using a single dual rotary for tuning all 4 frequencies (ie COM1 radio, COM2 Radio, NAV1 radio, and NAV2 Radio) If you're using the Input.ini (..\gauges\flight1_garminG1000_Aux\ folder) then you could simply chose to assign your keys & buttons there, making sure no conflicts with native FSX/P3D or FSUIPC assignments, (use the entries PFD_Com_Cursor= , PFD_Com_Swap= , PFD_Nav_Cursor= ,PFD_Nav_Swap= , and the PFD Com & PFD Nav assignments.) If you're like me, and using FSUIPC and "standard" FSX controls, then use Com_Radio_Whole In
  13. Luck had little to do with it, I'm sure! All devices present & accounted for, and functioning as intended! Thank you again for all your efforts! Best, Don FSUIPC4(test_C).ini FSUIPC4(test_C).log
  14. Here's the tests from 4964b. Still difficulties with the second rotary panel recognition. Don FSUIPC4(test_b1).log FSUIPC4(test_b1).ini
  • 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.