Jump to content
The simFlight Network Forums

ark1320

Members
  • Content Count

    206
  • Joined

  • Last visited

  • Days Won

    4

ark1320 last won the day on July 27 2017

ark1320 had the most liked content!

Community Reputation

5 Neutral

About ark1320

  • Rank
    Advanced Member

Profile Information

  • Gender
    Male
  • Location
    Colorado, USA

Recent Profile Visitors

1,798 profile views
  1. Hi Thomas, Thanks for the reply. I do understand the numerical precision differences in the offsets, but I don't think the above quote is correct. The P3D SDK shows the max values for both NAV CDI:index and HSI CDI NEEDLE as + - 127, and for both NAV GSI:index and HSI GSI NEEDLE as + - 119. So given numerical precision aside, I think there is a typo in the FSUIPC5 documentation for offset 2AB0 which is currently listed as 2AB0 4 NAV1 glideslope needle (GSI), 32-bit float value, –127.0 up to +127.0 down. According to the SDK the values should be + - 119.0. In summary, the lateral needle range is + - 127, and the vertical needle range is + - 119. Or else I'm really not understanding something. Thx, Al
  2. The FSUIPC5.15 Offsets Status documentation shows: 0C48 1 NAV1 Localiser Needle: –127 left to +127 right 0C49 1 NAV1 Glideslope Needle: –119 up to +119 down 2AAC 4 NAV1 course deviation needle (CDI), 32-bit float value, –127.0 left to +127.0 right 2AB0 4 NAV1 glideslope needle (GSI), 32-bit float value, –127.0 up to +127.0 down Two questions regarding the above: 1. Are offsets 0C48 and 2AAC essentially the same except for the number format/precision? and likewise 2. Are offsets 0C49 and 2AB0 essentially the same except for the number format/precision and the range specified in 2AB0 should be + - 119 as in 0C49 (i.e., the + - 127 in 2AB0 is a typo)? I do realize full scale CDI deviation for a VOR signal is 4 times that for a localiser in terms of degrees, but I'm assuming the sim accounts for this and both full scale deviations will be represented by the + - 127 values. Thanks, Al
  3. Ok, understand. My scripts do make good use of both the single line and multi-line display facilities. As an aside, although there is almost no meaningful information available yet, I fully expect the ability to write scripts will be just as important in the new MSFS sim as it is in P3D. So I'm really hopeful that in about a year or so from now I will be able to go on line and BUY the new FSUIPC6 for MSFS at SimMarket!! Best, Al
  4. Hi Pete or John, I am using Win10, P3Dv4.5, and FSUIPC5.15 A lot of my Lua scripts display values either on the 'green bar' display, or in a simconnect window. For a particular Lua script, I am trying to find a way so that the value it displays remains displayed and is not overwritten by the displays of my other Lua scripts. In FSX there was the 'setowndisplay' option, but unless something has recently changed my understanding is this does not work in FSUIPC5 because there is only one simconnect display window shared by all scripts. Is this still the case or is there a way to prevent a value displayed from one particular Lua script from being overwritten by the displays of other Lua scripts? Thx, Al
  5. I now have a new update! It seems HIDMacros WILL work with the latest version of P3D4.5 (which includes HF2 I assume) if you make sure to run HIDMacros in Administrative mode. I discovered this after spending most of the day trying some other more complicated SimConnect file approaches that have worked for others to get HIDmacros to work with P3Dv4. Maybe Lockheed Martin made some changes in the latest P3D update ? Al
  6. To update and close the loop a bit for anyone else who tries HIDmacros, it turns out it does work pretty much as expected with FSUIPC in FSX. However, I have NOT been able to get it to work in P3Dv4.5 which was the sim I was initially trying it in. Al
  7. Unfortunately, I have not been able to get HIDmacros to send an altered keystroke to FSUIPC. For example, I can get HIDmacros to send the n key when the A key is pushed on the 2nd keyboard, but although Win10 does get the altered keystroke (n), FSUIPC grabs the original key (A). Al UPDATE 23Oct19: HIDmacros does seem to work with FSUIPC in FSX, but NOT in P3Dv4.5.
  8. Reinhard, John, Thanks very much for the info! I played with HIDmacros a bit. One thing I discovered is it initially seems FSUIPC grabs (traps) a key stroke before HIDmacros does, which presents some problems because, if I understand it correctly, FSUIPC either 'takes some action' based on the key if it has been assigned, or passes it directly on to the sim (P3Dv4.5 in this case). So neither FSUIPC or the sim sees the result of the HIDmacro modification. I will keep experimenting a bit. Al Edit: Now, if a future version of FSUIPC could distinguish between two keyboards/keypads that would be VERY useful indeed! 😉
  9. OK, thanks John. I was hoping it might be possible to make use of the Vendor and Product ID info that a USB HID device provides in order to distinguish between two different keyboards, or between a keyboard that includes a numberpad and a separate external numberpad, especially if the devices were from different manufacturers. Al
  10. I'd like to use two keyboards to increase the available key control inputs without having to use key combinations. Is there a way, perhaps using Lua scripts, to distinguish the inputs from the two keyboards? Thx, Al
  11. Hi Pete, I can't seem to find how to specify the formatting of string variables for a CSV file using, I assume, the newline \n character. I know how to do it with numerical variables, but am not having any luck with string variables. For example, using something like file:write(string.format("%-3s %-6s %-5s ", str_var1, \n str_var2, \n str_var3 \n )) I want to end up with the value of each string variable on a separate line in the CSV file but can't seem to get the syntax correct. Thanks for any suggestions, Al
  12. At the end of a flight I'd like to use a Lua script to save a small number of offset values (fuel tank quantities) to be read and loaded at the next sim session. As far as I can tell there are no special facilities for this in the FSUIPC lua library, so I assume I will need to learn how to use standard Lua io methods for reading and writing files. If anyone has any recommendations on how best to proceed or where to look for good examples, that would be most appreciated. Thanks, Al
  13. Yes, I understand. I'm familiar with negative number representation. Thanks, Al
  14. Hello Pete, Does n= ipc.readLvar() assume a particular data format for the value n read (byte, word, floating point, etc), or does it just default to the Lvar's format? I'm asking because if I read an Lvar value and then want to write it to an offset with ipc.writeXX(0x1234, n), I need to decide what XX is (UB, SW, DBL, etc). Best for the holidays, Al
×
×
  • 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.