September 16, 20205 yr Hi, How do I pop-up the GNS530/430 from Milviz's C310 Redux plane? I couldn't find the answer after reading the manual. I also google searched and found suggestion for editing the panel.cfg and RealityXP.GTN.ini but this didn't work for me. Ideally right clicking the screen (not the bezel) on the panel should pop-up the 2D panels and likewise right clicking on the 2D windows should close it. Also, how do I make the power/on of button on both units functional? Not sure why this doesn't work automatically and why we have to google search. I have the latest versions of the plane, RealityXP (all), and Windows 10 Pro. Thank you. Hardware: i7-8700k, GTX 1070-ti, 32GB ram, NVMe/SSD drives with lots of free space. Software: latest Windows 10 Pro, P3Dv4.5+, FSX Steam, and lots of addons (100+ mostly Orbx stuff).
September 21, 20205 yr Just saw this post... lets continue in this thread. Yes, you can set up the ini file to give you a popup window.. either left click or right click, your choice. As for power on, the GNS usually is set to power on with avionics power. What are you seeing? I have not touched the 310 in some time, but do have it installed, so we can do some comparisons if needed. P3D or FSX? And which panel config? The GNS530+430? Edited September 21, 20205 yr by Bert Pieke Bert
September 21, 20205 yr Author @Bert Pieke and @fppilot My pc specs or platform are in my signature. But in case you are not seeing it, I have the latest versions of the Milviz 310R Redux, the RXP GNS v2 and GTN, P3D v4.5, and Windows Pro.. I only have the GNS actually installed in the 310 (the GTN is installed in the PC but is not being used in any plane). My Norton anti-virus is disabled. I've read the Users Manual for the GNS and scanned the Garmin manual for the 530, and know how to setup the gauges in the Addons menu as well as how to right click the top edges of the 2D panels to get to the configuration menus. I didn't touch or change anything in the configuration menus. The 530 is the Master device and the 430 is the 2nd device. Below the 430 is the WX Advantage. Since I installed these gauges a long time ago but just tried to use the GNS recently, I don't remember if the WX Weather Advantage gauge, which apparently works, is the default that came with the 310 or if I it is the unit I bought and installed separately. I believe it is the former (the default). 1. The 530 and 430 automatically turn on after both engines are running and after I toggle up the 'Avionics Master' in the 310. 2. All the buttons on the 530 and 430 in the virtual cockpit work (eg. CDI, OBS, MSD, Menu, CLR, ENT, cursor buttons, etc)..... EXCEPT the C and the V knobs on the LEFT side of both panels. 3. The C and V knobs can be turned or adjusted but not turned on or off in the 2D panels. 4. For the pop-up issue, I checked the popright value in the file RealityXP.GNS.ini and changed it to "popright=14401", but just noted that there is no "ident=xx" field in the vcockpit0x sections of the panel.cfg file. Thank you both for the quick reply. Hardware: i7-8700k, GTX 1070-ti, 32GB ram, NVMe/SSD drives with lots of free space. Software: latest Windows 10 Pro, P3Dv4.5+, FSX Steam, and lots of addons (100+ mostly Orbx stuff).
September 21, 20205 yr 5 hours ago, oneleg said: 4. For the pop-up issue, I checked the popright value in the file RealityXP.GNS.ini and changed it to "popright=14401", but just noted that there is no "ident=xx" field in the vcockpit0x sections of the panel.cfg file. Well I see you have run through a great checklist. You found a critical item was not checked but you did not mention results. I sincerely hope the missing ident= variable is the cause. Please let us know. We enjoy seeing success. The 310 Redux did come bundled with a version of the wx gauge that had use limited to that one aircraft. Like you I also purchased the separate retail version. I lost my FSX system in early August and with my new system migrated to FSX SE as an interim step, awaiting MSFS 2020. I have been unable to use that wx gauge in SE. I get a message that it is not compatible with my version of the simulator. I decided to just remove it from my 310. I only had the retail version installed in one other aircraft that I have not installed in the new system, a bit exhausted from all of the activity surrounding attempts to rescue my previous system, build and install a new system, and look forward to a new simulator. It has been quite an experience, and it certainly is not yet over. It appears REX has abandoned that wx gauge. Edited September 21, 20205 yr by fppilot Frank Patton Corsair 5000D Airflow Case; MSI B650 Tomahawk MOB; Ryzen 7 7800 X3D CPU; ASUS RTX 4080 Super; NZXT 360mm liquid cooler; Corsair Vengeance 64GB DDR5 4800 MHz RAM; RMX850X Gold PSU;; ASUS VG289 4K 27" Display; Honeycomb Alpha & Bravo, Crosswind 3's w/dampener. Former USAF meteorologist & ground weather school instructor. AOPA Member #07379126 "I will never put my name on a product that does not have in it the best that is in me." - John Deere
September 21, 20205 yr Author On 9/21/2020 at 7:20 AM, fppilot said: Well I see you have run through a great checklist. You found a critical item was not checked but you did not mention results. I sincerely hope the missing ident= variable is the cause. Please let us know. We enjoy seeing success. @ fppilot and @Bert Pieke Good Morning! I have no results yet. I wish I could say that I succeeded but it's still not working: I still have no pop-ups and the C and V knobs on the panels in the virtual cockpit of the 530 and the 430 are still unresponsive. I probably still need to change or add the appropriate "ident" value in the panel.cfg of the 310 for both the 530 and 430 installed in the Milviz C310 Redux. I don't know if these files will help but I am including the contents of the three GNS RXP log files found in my Documents folder below appended. After those three files below, I also attached the contents of the "panel.cfg" and the "RealityXP.GNS.ini" file for the 310. ----snip, snip---- rxpGnsSim.dll.log file: 20/09/21 13:42:33.053 12160 - ] # rxpGnsSim64.dll version 2.4.21.0 20/09/21 13:42:33.053 12160 INFO ] 20/09/21 13:42:35.668 12160 INFO ] using: F:\P3D\SimObjects\Airplanes\MV_C310R\checklist.gns 20/09/21 13:42:35.730 13096 INFO ] G530.1 - TRAINER 3300 20/09/21 13:42:35.736 12160 INFO ] using: F:\P3D\SimObjects\Airplanes\MV_C310R\checklist.gns 20/09/21 13:42:36.025 13096 INFO ] G430.2 - TRAINER 3300 20/09/21 13:51:05.165 13096 INFO ] FPL not found in: C:\ProgramData\Garmin\GNS Trainer Data\GNS\ 20/09/21 13:52:13.504 13096 INFO ] FPL not found in: C:\ProgramData\Garmin\GNS Trainer Data\GNS\ rxpGNS2.gau.log file: 20/09/21 13:42:30.834 12160 - ] # rxpGNS2.dll version 2.4.21.0 20/09/21 13:42:30.834 12160 INFO ] rxpGNS2_menu.dll.log file: 20/09/21 01:42:15.451 11768 - ] # rxpGNS2_menu.dll version 2.4.21.0 20/09/21 01:42:15.467 11768 INFO ] edit panel: F:\P3D\SimObjects\Airplanes\MV_C310R\panel\panel.cfg XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX ---- contents of the panel.cfg file for the Milviz 310 Redux plane ---- Spoiler // This Panel.cfg file created by FS Panel Studio panel editor utility - http://www.fspanelstudio.com // Built Wednesday, February 09, 2018 at 16:48 FSPS Build:22767 //-------------------------------------------------------- // RXP GNS530/430 + WX //-------------------------------------------------------- [Window Titles] Window00=Main Panel Window01=Throttle Window02=C310 Prelight Window03=Reality XP GNS Unit 1 (managed) Window04=Reality XP GNS Unit 2 (managed) [VIEWS] VIEW_FORWARD_WINDOWS=MAIN_PANEL,THROTTLE_PANEL,GPS_PANEL VIEW_FORWARD_DIR=10.000, 0.000, 0.000 //-------------------------------------------------------- [Window00] Background_color=0,0,0 size_mm=1680,1050 window_size_ratio=1.000 position=7 visible=1 ident=0 window_size= 1.000, 1.000 window_pos= 0.000, 0.000 //-------------------------------------------------------- [Window01] Background_color=0,0,0 size_mm=296,547 window_size_ratio=1.000 position=8 visible=0 ident=10030 window_size= 0.176, 0.514 window_pos= 0.834, 0.486 zorder=2 gauge00=C310_XMLGauges!C310_ThrottleQuad, 0,0,286,547 //-------------------------------------------------------- [Window02] Background_color=0,0,0 size_mm=500,243 window_size_ratio=1.000 position=0 visible=0 ident=70 window_size= 0.400, 0.324 window_pos= 0.000, 0.040 gauge00=C310_XMLGauges!C310_Preflight, 0,0,500,243 //-------------------------------------------------------- [Window03] size_mm=100,100 window_pos=0.712891,0.000000 window_size=0.287109,0.393461 visible=1 always_visible=1 zorder=99 background_color=0,0,0 ident=15531 gauge00=rxpGNS2!GNS_530_1, 0, 0,100,100 //-------------------------------------------------------- [Window04] size_mm=100,100 window_pos=0.712891,0.393461 window_size=0.287109,0.227039 visible=1 always_visible=1 zorder=99 background_color=0,0,0 ident=15432 gauge00=rxpGNS2!GNS_430_2, 0, 0,100,100 //-------------------------------------------------------- [Vcockpit01] file=C310_VC_01.bmp size_mm=1024,1024 visible=0 pixel_size=1024,1024 texture=$C310_VC_01 gauge00=MV3DSound!MV3DS, 0,0,1,1,SimObjects\\Airplanes\\MV_C310R\\panel\\C310R_Sounds#25 gauge01=rxpGNS2!GNS_430_2, 0,452,640,262 gauge02=C310_XMLGauges!KR 87 ADF, 0,715,640,134 gauge03=C310_XMLGauges!C310_DME, 649,32,300,150 gauge04=MilVizC310!EDM700_L, 663,200,339,339 gauge05=MilVizC310!EDM700_R, 662,547,339,339 gauge06=C310_XMLGauges!C310_Logic, 693,11,1,1 gauge07=rxpGNS2!GNS_530_1, 0,0,640,452 gauge08=KAP140_HSI!MV_KAP140Servos, 0,0,1,1 gauge09=KAP140_HSI!MV_KAP140Display, 0,852,640,163 gauge10=Console!console_RXP_GNS530_430_wx, 0,0,1,1 gauge11=TrueGlass!Core,0,0,1,1 gauge12=RealLight!Core,0,0,1,1 gauge13=AMSInterop!AMSInterop,0,0,1,1 //-------------------------------------------------------- [Vcockpit02] file=C310_VC_02.bmp size_mm=512,512 visible=0 pixel_size=1024,512 texture=$C310_VC_02 gauge00=C310_XMLGauges!FBS_GTX330, 0,0,512,135 //-------------------------------------------------------- [Vcockpit03] Background_color=0,0,0 size_mm=1024,1024 visible=0 pixel_size=1024,1024 texture=$VCNL_1 texture00=RL_0, 0,0,1024,1024 //-------------------------------------------------------- [Vcockpit04] Background_color=0,0,0 size_mm=1024,1024 visible=0 pixel_size=1024,1024 texture=$VCNL_2 texture00=RL_1, 0,0,1024,1024 //-------------------------------------------------------- [Vcockpit05] Background_color=0,0,0 size_mm=1024,1024 visible=0 pixel_size=1024,1024 texture=$VCNL_3 texture00=RL_2, 0,0,1024,1024 //-------------------------------------------------------- [Vcockpit06] Background_color=0,0,0 size_mm=1024,1024 visible=0 pixel_size=1024,1024 texture=$VCNL_4 texture00=RL_3, 0,0,1024,1024 //-------------------------------------------------------- [Vcockpit07] Background_color=0,0,0 size_mm=1024,1024 visible=0 pixel_size=1024,1024 texture=$VCNL_5 texture00=RL_4, 0,0,1024,1024 //-------------------------------------------------------- [Vcockpit08] Background_color=0,0,0 size_mm=1024,1024 visible=0 pixel_size=1024,1024 texture=$VCNL_6 texture00=RL_5, 0,0,1024,1024 //-------------------------------------------------------- [Vcockpit09] Background_color=0,0,0 size_mm=1024,1024 visible=0 pixel_size=1024,1024 texture=$VCNL_7 texture00=RL_6, 0,0,1024,1024 //-------------------------------------------------------- [Vcockpit10] Background_color=0,0,0 size_mm=1024,1024 visible=0 pixel_size=1024,1024 texture=$VCNL_8 texture00=RL_7, 0,0,1024,1024 //-------------------------------------------------------- [Vcockpit11] Background_color=0,0,0 size_mm=1024,1024 visible=0 pixel_size=1024,1024 texture=$VCNL_9 texture00=RL_8, 0,0,1024,1024 //-------------------------------------------------------- [Vcockpit12] Background_color=0,0,0 size_mm=1024,1024 visible=0 pixel_size=1024,1024 texture=$VCNL_10 texture00=RL_9, 0,0,1024,1024 //-------------------------------------------------------- [Vcockpit13] Background_color=0,0,0 size_mm=1024,1024 visible=0 pixel_size=1024,1024 texture=$VCNL_11 texture00=RL_10, 0,0,1024,1024 //-------------------------------------------------------- [Vcockpit14] Background_color=0,0,0 size_mm=1024,1024 visible=0 pixel_size=1024,1024 texture=$VCNL_12 texture00=RL_11, 0,0,1024,1024 //-------------------------------------------------------- [Vcockpit15] Background_color=0,0,0 size_mm=1024,1024 visible=0 pixel_size=1024,1024 texture=$VCNL_13 texture00=RL_12, 0,0,1024,1024 //-------------------------------------------------------- [Vcockpit16] Background_color=0,0,0 size_mm=1024,1024 visible=0 pixel_size=1024,1024 texture=$VCNL_14 texture00=RL_13, 0,0,1024,1024 //-------------------------------------------------------- [Vcockpit17] Background_color=0,0,0 size_mm=1024,1024 visible=0 pixel_size=1024,1024 texture=$VCNL_15 texture00=RL_14, 0,0,1024,1024 //-------------------------------------------------------- [Vcockpit18] background_color=0,0,0 size_mm=512,512 visible=0 pixel_size=512,512 texture=$C310_VC_03 gauge00=MV_WX!WX, 0,0,512,361 //-------------------------------------------------------- [Vcockpit19] background_color=0,0,0 size_mm=2048,2048 pixel_size=2048,2048 texture=$Int_TG_0 texture00=TG_0, 0,0,2048,2048 //-------------------------------------------------------- [Vcockpit20] background_color=0,0,0 size_mm=2048,2048 pixel_size=2048,2048 texture=$Int_TG_1 texture00=TG_1, 0,0,2048,2048 Day=255,255,255Night=85,85,85Luminous=140,140,140 [Default View]X=0Y=0SIZE_X=8192SIZE_Y=6143 XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX ---- contents of the RealityXP.GNS.ini file for the Milviz 310 Redux plane ---- Spoiler [GNS_430_1]; is the master device if true.MasterDevice = falsePowerKnob = DEFAULT_ONUseSimGpsCmds = true; comma separated list of read only settings.locked = UseSimGpsCmdsUseLegacyVars = trueFuelType = AVGAS; connects to: 'PFC_STACK','PFC_430','PFC_530' or any '#PID' (#D002 for PFC_430); no value connects to first found, 'OFF' disables connection.HardwareDevice =; hardware selector number or -1 to disable.HardwareIdx = -1 [GNS_430_1.DEFAULT]; show screen only gauge if true.nobezel = false; screen only border size (pixels).border.size = 0; screen only border color (#RGB or #RGBA).border.rgba = #000000; display mouse tooltips if true.tooltips = true; enable mouse clickspots if true, disable if false.usemouse = true; enable alternate click-spots (left CCW, right CW, middle Push) if true.usealtmouse = false; auto-resize dimension (width,height)refsize =; left mouse button on the screen toggles popup window by ident (ex: GPS_PANEL or 225).popleft =; right mouse button on the screen toggles popup window by ident (ex: GPS_PANEL or 225).popright =; adjust brightness (0 to 100)brightness.bezel = 50; offset brightness (-100 to +100)brightness.screen = 0 [GNS_530_1]; is the master device if true.MasterDevice = truePowerKnob = DEFAULT_ONUseSimGpsCmds = true; comma separated list of read only settings.locked = UseSimGpsCmdsUseLegacyVars = trueFuelType = AVGAS; connects to: 'PFC_STACK','PFC_430','PFC_530' or any '#PID' (#D002 for PFC_430); no value connects to first found, 'OFF' disables connection.HardwareDevice =; hardware selector number or -1 to disable.HardwareIdx = -1UseCrossFill = trueUseFailures = truePowerSource = ALWAYS_ON [GNS_530_1.DEFAULT]; show screen only gauge if true.nobezel = false; screen only border size (pixels).border.size = 0; screen only border color (#RGB or #RGBA).border.rgba = #000000; display mouse tooltips if true.tooltips = false; enable mouse clickspots if true, disable if false.usemouse = true; enable alternate click-spots (left CCW, right CW, middle Push) if true.usealtmouse = false; auto-resize dimension (width,height)refsize =; left mouse button on the screen toggles popup window by ident (ex: GPS_PANEL or 225).popleft =; right mouse button on the screen toggles popup window by ident (ex: GPS_PANEL or 225).popright = 14401; adjust brightness (0 to 100)brightness.bezel = 50; offset brightness (-100 to +100)brightness.screen = 0 [GNS_430_2]; is the master device if true.MasterDevice = falsePowerKnob = DEFAULT_ONUseSimGpsCmds = true; comma separated list of read only settings.locked = UseSimGpsCmdsUseLegacyVars = trueFuelType = AVGAS; connects to: 'PFC_STACK','PFC_430','PFC_530' or any '#PID' (#D002 for PFC_430); no value connects to first found, 'OFF' disables connection.HardwareDevice =; hardware selector number or -1 to disable.HardwareIdx = -1PowerSource = PANEL_ON [GNS_430_2.DEFAULT]; show screen only gauge if true.nobezel = false; screen only border size (pixels).border.size = 0; screen only border color (#RGB or #RGBA).border.rgba = #000000; display mouse tooltips if true.tooltips = false; enable mouse clickspots if true, disable if false.usemouse = true; enable alternate click-spots (left CCW, right CW, middle Push) if true.usealtmouse = false; auto-resize dimension (width,height)refsize =; left mouse button on the screen toggles popup window by ident (ex: GPS_PANEL or 225).popleft =; right mouse button on the screen toggles popup window by ident (ex: GPS_PANEL or 225).popright =; adjust brightness (0 to 100)brightness.bezel = 50; offset brightness (-100 to +100)brightness.screen = 0 Edited October 12, 20205 yr by RXP Hardware: i7-8700k, GTX 1070-ti, 32GB ram, NVMe/SSD drives with lots of free space. Software: latest Windows 10 Pro, P3Dv4.5+, FSX Steam, and lots of addons (100+ mostly Orbx stuff).
September 21, 20205 yr Good morning to you too! First thing to do, is to match up the ident numbers between the panel windows and the ini file, they do not currently match. Suggest editing the ini file to: [GNS_530_1.DEFAULT]......; right mouse button on the screen toggles popup window by ident (ex: GPS_PANEL or 225).popright = 15531 and [GNS_430_2.DEFAULT].....popright = 15432 Edited September 21, 20205 yr by Bert Pieke Bert
September 21, 20205 yr Second question is whether you want to use the right mouse button... you can also assign these values to popleft, and use the left mouse button, your call. I would blame the mismatch on Milviz, they are known for not taking responsibility for 3rd party GPS integration, even when they provide the files.. can be very frustrating. Lastly, your power buttons.. as best I know they are not simulated, and you should not expect them to work. You can set the GNS gauges to power up with the battery or with the avionics switch, again, your call. BTW, you can always pop up the GNS windows with shift+4 and shift+5 if you cannot access them otherwise.. Let us know how you make out! Bert
September 21, 20205 yr 2 hours ago, oneleg said: [Vcockpit01] file=C310_VC_01.bmp size_mm=1024,1024 visible=0 pixel_size=1024,1024 texture=$C310_VC_01 gauge00=MV3DSound!MV3DS, 0,0,1,1,SimObjects\\Airplanes\\MV_C310R\\panel\\C310R_Sounds#25gauge01=rxpGNS2!GNS_430_2, 0,452,640,262 gauge02=C310_XMLGauges!KR 87 ADF, 0,715,640,134 gauge03=C310_XMLGauges!C310_DME, 649,32,300,150 gauge04=MilVizC310!EDM700_L, 663,200,339,339 gauge05=MilVizC310!EDM700_R, 662,547,339,339 gauge06=C310_XMLGauges!C310_Logic, 693,11,1,1gauge07=rxpGNS2!GNS_530_1, 0,0,640,452 gauge08=KAP140_HSI!MV_KAP140Servos, 0,0,1,1 gauge09=KAP140_HSI!MV_KAP140Display, 0,852,640,163 gauge10=Console!console_RXP_GNS530_430_wx, 0,0,1,1 gauge11=TrueGlass!Core,0,0,1,1 gauge12=RealLight!Core,0,0,1,1 gauge13=AMSInterop!AMSInterop,0,0,1,1 Also the entries for the two gauges in the [vcockpit01] section of the panel.cfg file lack the necessary 5th parameter... Frank Patton Corsair 5000D Airflow Case; MSI B650 Tomahawk MOB; Ryzen 7 7800 X3D CPU; ASUS RTX 4080 Super; NZXT 360mm liquid cooler; Corsair Vengeance 64GB DDR5 4800 MHz RAM; RMX850X Gold PSU;; ASUS VG289 4K 27" Display; Honeycomb Alpha & Bravo, Crosswind 3's w/dampener. Former USAF meteorologist & ground weather school instructor. AOPA Member #07379126 "I will never put my name on a product that does not have in it the best that is in me." - John Deere
September 21, 20205 yr 18 minutes ago, fppilot said: Also the entries for the two gauges in the [vcockpit01] section of the panel.cfg file lack the necessary 5th parameter... ??? Bert
September 21, 20205 yr On 9/21/2020 at 1:23 PM, Bert Pieke said: ??? I experienced issues when attempting to use the default in some aircraft and found 100% success following this method from page 14 of the user's manual: ------------------------- The automatically generated RealityXP.GNS.ini file in the aircraft folder has [GNS_###_#.DEFAULT] sections for each device found in the panel. Each gauge sibling uses the default settings from this section, for example [GNS_530_1.DEFAULT]. Should you want a particular instance of the gauge (one sibling) to use other than 'DEFAULT' settings, a new named section must be created and the gauge 5th parameter must be set to this new section name. For example, to set the VC instance to render without a bezel (screen only): copy and paste the gauge 'DEFAULT' section to the end of the RealityXP.GNS.ini file, change the suffix from 'DEFAULT' to 'NO_BEZEL' then edit the new section settings. -------------------------- From the end of my .ini file: //-------------------------------------------------------- [GNS_430_2.TOGGLE_430] popleft = 15531 [GNS_530_1.TOGGLE_530] popleft = 14531 From my panel.cfg file: (note: my window## sections are numbered to conform to a yoke setting I use, and my pos and sizes are custom configured to size and position the popups where I want them) Spoiler //-------------------------------------------------------- [window05] window_pos=0.772135,0.829121 window_size=0.227865,0.170868 visible=1 zorder=99 ident=15531gauge00=rxpGNS2!GNS_430_2,0,0,100,100, TOGGLE_430 //-------------------------------------------------------- [Window07] window_pos=0.772135,0.538195 window_size=0.227865,0.290937 visible=1 zorder=99 ident=14531gauge00=rxpGNS2!GNS_530_1,0,0,100,100, TOGGLE_530 //-------------------------------------------------------- [Vcockpit01] file=C310_VC_01.bmp size_mm=1024,1024 visible=0 pixel_size=1024,1024 texture=$C310_VC_01 gauge00=MV3DSound!MV3DS, 0,0,1,1,SimObjects\\Airplanes\\MV_C310R\\panel\\C310R_Sounds#25gauge01=rxpGNS2!GNS_430_2, 0,452,640,262, TOGGLE_430 gauge02=C310_XMLGauges!KR 87 ADF, 0,715,640,134 gauge03=C310_XMLGauges!C310_DME, 649,32,300,150 gauge04=MilVizC310!EDM700_L, 663,200,339,339 gauge05=MilVizC310!EDM700_R, 662,547,339,339 gauge06=C310_XMLGauges!C310_Logic, 693,11,1,1gauge07=rxpGNS2!GNS_530_1, 0,0,640,452, TOGGLE_530 gauge08=KAP140_HSI!MV_KAP140Servos, 0,0,1,1 gauge09=KAP140_HSI!MV_KAP140Display, 0,852,640,163 gauge10=Console!console_RXP_GNS530_430, 0,0,1,1 gauge11=TrueGlass!Core,0,0,1,1 gauge12=AMSInterop!AMSInterop,0,0,1,1 Edited October 12, 20205 yr by RXP Frank Patton Corsair 5000D Airflow Case; MSI B650 Tomahawk MOB; Ryzen 7 7800 X3D CPU; ASUS RTX 4080 Super; NZXT 360mm liquid cooler; Corsair Vengeance 64GB DDR5 4800 MHz RAM; RMX850X Gold PSU;; ASUS VG289 4K 27" Display; Honeycomb Alpha & Bravo, Crosswind 3's w/dampener. Former USAF meteorologist & ground weather school instructor. AOPA Member #07379126 "I will never put my name on a product that does not have in it the best that is in me." - John Deere
September 21, 20205 yr Sure, you can do that.. but lets do it the simple way first.. 🙂 It should work just fine. Bert
September 21, 20205 yr On 9/16/2020 at 10:00 AM, oneleg said: Hi, How do I pop-up the GNS530/430 from Milviz's C310 Redux plane? Did you get it working? 🙂 Bert
September 22, 20205 yr Author 6 hours ago, Bert Pieke said: Did you get it working? 🙂 @Bert Pieke Yes, the pop-ups work. Thank you very much. I have follow-up questions: 1. Which panel configuration files do the popright values come from eg. the 15531 in "popright = 15531"? Are these constants or reserved values (by RXP) or are they arbitrarily selected and that's okay so long as they are the same to the ident= value? 2. The 2D panels display up or are open when loading the plane. How do I make them visible only when desired or popped-out? 3. The 530 automatically turns on (unlike the 430) when the plane loads. Why? The battery is not even on when the plane is 'cold and dark'. How do I default to the 'off' state? The Power buttons on the left side of the 530 and 430 have tool tips when the cursor is hovered over them which seems to indicate that they are supposed to be functional. But you said they are non-functional, can you please confirm? Hardware: i7-8700k, GTX 1070-ti, 32GB ram, NVMe/SSD drives with lots of free space. Software: latest Windows 10 Pro, P3Dv4.5+, FSX Steam, and lots of addons (100+ mostly Orbx stuff).
September 22, 20205 yr 2 hours ago, oneleg said: @Bert Pieke Yes, the pop-ups work. Thank you very much. I have follow-up questions: 1. Which panel configuration files do the popright values come from eg. the 15531 in "popright = 15531"? Are these constants or reserved values (by RXP) or are they arbitrarily selected and that's okay so long as they are the same to the ident= value? 2. The 2D panels display up or are open when loading the plane. How do I make them visible only when desired or popped-out? 3. The 530 automatically turns on (unlike the 430) when the plane loads. Why? The battery is not even on when the plane is 'cold and dark'. How do I default to the 'off' state? The Power buttons on the left side of the 530 and 430 have tool tips when the cursor is hovered over them which seems to indicate that they are supposed to be functional. But you said they are non-functional, can you please confirm? You are welcome! Lets see if I can answer your questions.. 1. These are the common numbers that RXP tends to use, but you can change them to whatever you like, as long as they match. 2. in Window03 and 04, delete these lines visible=1 always_visible=1 You can replace it by visible=0 3. Check the power options for each of the GNS gauges in the RXP settings window and adjust them to your preference. Your ini file shows the current settings as PowerKnob = DEFAULT_ON and PowerSource as ALWAYS_ON. If you change the PowerSource to Avionics On, and PowerKnob to DEFAULT_OFF you should be able to do what you are looking for. See User Manual page 11.. I believe the default for the PowerKnob is Volume only.. in which case the power button is inop. Edited September 22, 20205 yr by Bert Pieke Bert
September 22, 20205 yr BTW.. you said earlier that you also have the GTN750 installed.. I actually use the GTN750 in my C310... something to consider as an option.. 😉 Bert
Archived
This topic is now archived and is closed to further replies.