Jump to content
The simFlight Network Forums

ark1320

Members
  • Content count

    172
  • Joined

  • Last visited

  • Days Won

    4

ark1320 last won the day on July 27

ark1320 had the most liked content!

Community Reputation

4 Neutral

About ark1320

  • Rank
    Advanced Member

Profile Information

  • Gender
    Male
  • Location
    Colorado, USA

Recent Profile Visitors

881 profile views
  1. Hi Pete, In general, does FSUIPC update offset values (such as airspeed, altitude, flight control positions, radar altitude, etc) from FSX at the sim rate (about 18Hz), or only when a particular offset is accessed via one of the ipc.read commands, or perhaps only when FSUIPC detects an offset value has changed? Thanks, Al
  2. Hi Pete, Does the ipc.display and setowndisplay combination work in P3Dv4? I recall there have been some issues with this in the past. I'm trying to help a friend but unfortunately don't have P3D myself for testing. Scripts I've written using ipc.display that work in FSX on my friend's machine are not displaying anything in P3Dv4. Thanks for an update on this, Al
  3. I forgot to mention I'm using the boxed FSX, but it sounds like in this case the answer is the same regardless of which sim is being used. Thanks for the response, Al
  4. Hello Pete, Is there a way to control the transparency of the window created by the ipc.setowndisplay command? I would like to reduce the transparency to increase readability of the info displayed in the window. Thanks, Al
  5. Yes, a good lesson! Thanks very much for the help. Al
  6. Hi Pete, Below is information from the FSUIPC4.LOG files for the Baron 58 and B737. Al Baron B58 1141 SimConnect_Open succeeded: waiting to check version okay 1141 Trying to use SimConnect Acc/SP2 Oct07 1141 Opened separate AI Traffic client okay 3563 Running in "Microsoft Flight Simulator X", Version: 10.0.61472.0 (SimConnect: 10.0.61259.0) 3563 Initialising SimConnect data requests now 3563 FSUIPC Menu entry added 3594 C:\Users\Al\Documents\Flight Simulator X Files\Default Safe Flight Baron 58 35L KCOS.FLT 3594 C:\FSX\SimObjects\Airplanes\Beech_Baron_58\Beech_Baron_58.AIR 4219 Monitor IPC:060C (U8) = 0 50313 Aircraft loaded: running normally now ... 50313 User Aircraft ID 1 supplied, now being used 50641 System time = 18/10/2017 16:30:02, Simulator time = 11:49:47 (17:49Z) 50641 Monitor IPC:060C (U8) = 2 50641 SimRead: 060C="IS GEAR RETRACTABLE" INT32: 2 (0x00000002) 51406 Aircraft="Beech Baron 58 EPAV" 51641 Starting everything now ... 51719 ASN active function link set 51719 Ready for ActiveSky WX radar with additional data B737 1109 SimConnect_Open succeeded: waiting to check version okay 1109 Trying to use SimConnect Acc/SP2 Oct07 1109 Opened separate AI Traffic client okay 3609 Running in "Microsoft Flight Simulator X", Version: 10.0.61472.0 (SimConnect: 10.0.61259.0) 3609 Initialising SimConnect data requests now 3609 FSUIPC Menu entry added 3625 C:\Users\Al\Documents\Flight Simulator X Files\Default Safe Flight Baron 58 35L KCOS.FLT 3625 C:\FSX\SimObjects\Airplanes\Beech_Baron_58\Beech_Baron_58.AIR 4297 Monitor IPC:060C (U8) = 0 59859 C:\FSX\SimObjects\Airplanes\B737_800_Default_Modified\Boeing737-800.AIR 139719 User Aircraft ID 1 supplied, now being used 140015 System time = 18/10/2017 16:40:14, Simulator time = 11:49:47 (17:49Z) 140015 Monitor IPC:060C (U8) = 2 140015 SimRead: 060C="IS GEAR RETRACTABLE" INT32: 2 (0x00000002) 140797 Aircraft="Boeing 737-800 EPAV" 141000 Starting everything now ... 141094 ASN active function link set 141094 Ready for ActiveSky WX radar with additional data 141156 Plug-in thread table check:
  7. Pete, The default a/c I tried were the Baron 58 and the B737. Al
  8. Yes, I get the value 2 for a number of different default and add-on a/c. I guess as you say it is a case of non 0 means true. I'll be careful to code accordingly in the future. I don't know how I managed to post in the wrong forum this time -- sorry. Thanks for the help, Al
  9. Hi Pete, When debugging some code I found that when reading offset 060C with ipc.readUB(0x060C) for an a/c with a retractable landing gear the value returned was 2 instead of 1 as specified in the offset documentation. Is this just a simple documentation typo, or perhaps is there some additional significance (some characteristic of the landing gear) associated with the "2" versus the "1" ? With a fixed gear a/c the value returned is 0 as expected. Thanks, Al FSX with SP2, FSUIPCv4.971, Win10
  10. I think I understand now. If I have three functions assigned to one button or key and want two of them to be general and one profile specific, I just need to put the two general function assignments in the General section of the FSUIPC ini file, and put all three function assignments in the a/c profile specific section of the FSUIPC ini file. Thanks for the help Thomas. Al
  11. Hi Pete, If under the General button area of FSUIPC.ini I assign three functions (gear down and two Lua scripts) to button 19 as shown below, all works well. 450=PY,19,C66080,0 -{GEAR_DOWN}- 451=PY,19,CL95:R,0 -{Lua Landing_Params}- 452=PY,19,CL52:R,0 -{Lua AppchAltCalls}- However, if I make one of the Lua script assignments Profile Specific to aircraft A by moving it from the General area to aircraft A's button assignment area, only that script works for aircraft A, the two remaining button 19 functions under the General button area no longer work for aircraft A. I assume this is because in some sense I have made button 19 itself profile specific to aircraft A rather than just the associated Lua script. Do you see anything I can do to resolve this issue? Thanks, Al FSX, FSUIPC 4.971, Win10
  12. Hi Pete, Are the FSUIPC4 Offsets at the same locations in FSUIPC5? I'm trying to determine if it is reasonable to expect that most Lua scripts written for FSX using FSUIPC4 will run in P3Dv4 using FSUIPC5. Thanks, Al
  13. HUD Parameters for FSX

    HUD Parameters for FSX HUDparameters.lua is a Lua script that displays flight parameters in a small text window that pops up when the script is selected by an assigned key or button if the aircraft is in the air. Parameters displayed are: · Indicated Airspeed (IAS. Kts) · True Airspeed (TAS, Kts) · Ground Speed (GS, Kts) · Mach# (when above a user settable altitude, currently 25000ft) · Altitude (ALT, ft) · Radio Altitude (RA, ft) · Vertical Speed (VS, ft/min) · Vertical Speed per Nautical Mile (VS/NM, ft/NM) · Attitude Indicator pitch (AI, degrees) · Flight Path Angle (FPA, degrees) The top of the script contains user settable values for the size and location of the display, the altitude above which the a/c Mach# will be displayed (default is 25000ft), the data update interval in milliseconds (default is 2000), and whether or not data is to be logged in HUDparameters.log (default is 0, off). These values can be set using a text editor like NotePad. A registered copy of FSUIPC is required to execute the Lua script. Simply copy the script to the Modules folder of FSX and use FSUIPC4 to assign a key, button or switch to toggle the script on and off. The script turns off if the aircraft is on the ground. HUDparameters.zip
  14. My understanding is FSW is built on FSX to some degree, but in general FSX addons, a/c, etc are currently not compatible with FSW. Al
  15. Hi Pete, Has DTG made any effort to coordinate with you regarding using FSUIPC with their soon to be released 64 bit FSW sim? If not, FSW is likely a non-player for me, Thx, Al
×