Jump to content
The simFlight Network Forums

mcp5500

Members
  • Posts

    5
  • Joined

  • Last visited

Everything posted by mcp5500

  1. OK that worked for NAV. I had to change your line to this: string.format("1%02X.%02X", STBYNAV2R/256, STBYNAV2R%256) This does show the lagging 0s.
  2. Thanks Pete, OK i see what you are doing. That also will help with the BARO as well. I am testing with the Fight1 Super B200 and it shows the .001th location in the PFD COMS display. thanks so much for your help I will give it a try.
  3. Hi Pete, My first post here and your site is a great help. I have a question. I am creating a LUA Menu Display system that displays the softkeys and controls for all functions in the G1000 PFD. The user uses 1- 2 position switch to move through the menu selections up and down and 1 button to activate the item highlighted. I am working on the last part of this scrip and I have created the NAV1 and NAV2 Radio menus. The menus look like what is below so you can see what i am trying to do: As you can see I am reading offset 311E and converting them for display with: STBYNAV2R = ipc.readSW(0x311E) followed by STBYNAV2 = (string.format("%04X", STBYNAV2R) + 10000) * .01. The issue I am having is in creating the COM1 and COM2 menus and displaying the STBY frq as where 311C and 311A are only 4 BCD digits not 5 (ie 122.225) so the equations above don't give me the 6th digit. Is there a way of getting that .001 position from reading an offset or do I have to follow the users selections to determine that .001 locations value? Also, if you have the time, is there a way to fix the width of the functions above so as not to drop the lagging 0s? Thanks in advance LUA Display G1000 PFD: NAV1 1 STBY FRQ INC <--- 2 STBY FRQ DEC 3 STBY FRAC INC 4 STBY FRAC DEC STBY FREQ = 114.2 (lagging 0s wont display) (Updated with each users press) 5 ACTIVATE STBY 6 BACK 7 CLOSE WINDOW This system works really good over users having to use click-spots in 2D or 3D cockpit
  4. Hi Pete, I am having the exact same problem, I am creating a Linda Lua script that is a menu display for the G1000 PFD. The idea is not to use the mouse to select options in the G1000. I am creating a new window. If i use ipc.setdisplay() 25 times in P2D v2.5 it hangs. I found a work around where i create the display once and put the Title Display line at line 0 using the ipc.display("Display line \n1 \n2,,,). How can i tell if another application created a display so i can then rectreat it again? thanks for your help Creating the display and then calling the text to fill it from other functions. its not complete but here is what i am talking about. function G1000_PFD_Main_Display() -- G1000 PFD: Menu Window Open and Menu Item Toggle: Use On-Press ipc.display("") ipc.sleep(500) if G1_Window == 0 and Main_Panel == 1 then -- Call G1000 Main Window ipc.setowndisplay("G1000 PFD Main Key Select", 45, 25, 10, 10) G1000SK = 0 G1_Window = 1 G1000_Main_Keys_Menu() G1_Window = 1 elseif G1_Window == 1 and Main_Panel == 1 then -- Call G1000 Main Panel Key Selection Window G1000_Main_Keys_Menu() --elseif G1_Window == 0 and PFDL1_PANEL == 1 then -- Call PFD Key Main Window --ipc.setowndisplay("G1000 PFD PFD SoftKey Select", 45, 25, 10, 10) --PFDSK_L1 = 0 --PFDL1_SoftKey_Menu () elseif G1_Window == 1 and PFDL1_PANEL == 1 then PFDL1_SoftKey_Menu () elseif G1_Window == 1 and FDFRMT_PANEL == 1 then FD_FRMT_Menu () elseif G1_Window == 1 and Wnd_Panel == 1 then PFD_Wind_Menu () elseif G1_Window == 1 and PFDALT_Panel == 1 then PFDALT_UNIT_Menu() --elseif G1_Window == 0 and INSET_Panel == 1 then -- Call PFD Key Main Window --ipc.setowndisplay("G1000 PFD: INSET SoftKey Select", 45, 25, 10, 10) --INSETv = 0 --INSET_SoftKey_Menu () elseif G1_Window == 1 and INSET_Panel == 1 then INSET_SoftKey_Menu () end I would need to detect a change to set G1_Window back to a 0. thanks
×
×
  • 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.