schmoboy

UPDATE: Seems good now. Are there issues with the F1 service currently? I am trying to purchase the 750 from the dnloaded installer and the "Click Here To Purchase" just comes back without an error and still says "You are ready for purchase!" in green above the button. Also the "Click Here to Reinstall" btn says failure to connect. Don't want to continuously click the "Click here for Secure Purchase" for fear of multiple charges.

AUX page 1... Crossfill... Manual Perfect, thanks @RXP

I have dual 430s in the Carenado Baron. I have crossfill enabled on both 430s. When I change the flightplan on the master 430 it auto crossfills over to the secondary 430. Is that how it is supposed to work? I have another plane that has a 530 master and a secondary 430. I have crossfill enabled on both those devices and the crossfill does not happen until I choose Crossfill from the Menu btn while on the flightplan page. Trying to get the Carenado Baron to not crossfill until I tell it to via the Menu. [GNS_430_1] ; comma separated list of render targets. drawto = WINDOW, PANELS ; is the master device if true. MasterDevice = true ; 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 UseCrossFill = true UseSimGpsCmds = true PowerSource = AVIONICS_BUS [GNS_430_2] ; comma separated list of render targets. drawto = WINDOW, PANELS ; is the master device if true. MasterDevice = false ; 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 UseSimGpsCmds = true LinkOto = false LinkHsi = false LinkObs = true LinkVor = true CopilotSide = false UseCrossFill = true

Carenado PC12 Dual 530s [GNS_530_1.PANELS] ; display window if true. visible = true ; show screen only gauge if true. nobezel = true ; display type: WINDOW,PANEL2D,PANEL3D,PANELS frame.type = PANEL3D ; display position and dimension (left,top,width,height) frame.rect = 1492,883,516,378 ; screen only border size (pixels). border.size = 0 ; screen only border color (#RGB or #RGBA). border.rgba = #000000 ; enable mouse clickspots if true, disable if false (use SHIFT to override) usemouse = true ; left mouse button on the screen toggles popup window if true. popleft = true ; right mouse button on the screen toggles popup window if true (requires XP11.1). popright = false [GNS_530_2.PANELS] ; display window if true. visible = true ; show screen only gauge if true. nobezel = true ; display type: WINDOW,PANEL2D,PANEL3D,PANELS frame.type = PANEL3D ; display position and dimension (left,top,width,height) frame.rect = 1492,483,516,378 ; screen only border size (pixels). border.size = 0 ; screen only border color (#RGB or #RGBA). border.rgba = #000000 ; enable mouse clickspots if true, disable if false (use SHIFT to override) usemouse = true ; left mouse button on the screen toggles popup window if true. popleft = true ; right mouse button on the screen toggles popup window if true (requires XP11.1). popright = false

Guessing that there is nothing I can do other than deleting/renaming the RealityXP.GNS.ini file before flying the G1000 variant and renaming/restoring it back when I want to fly the 530430 stack version. I'd like to suggest a feature/enhancement in which the plugin looks for the ini file using the .acf filename which is loaded first. If it does not find one then it can default to the RealityXP.GNS.ini filename. So for the Laminar default 172 there could be two RXP ini files as such: RealityXP.GNS.Cessna_172SP.ini RealityXP.GNS.Cessna_172SP_G1000.ini Then when either one is loaded, the proper config could be loaded, or default to the RealityXP.GNS.ini file if no .acf specific one, or not load at all if there is no default ini file. That would support multiple A/C in the same folder and you could prevent the G1000 variant from even loading one by only having a RealityXP.GNS.Cessna_172SP.ini file. Thanks for the consideration.

I don't have anything in the G1000 panel, but I have a 530 popout window defined which is on a second monitor (simGear). That activates when the G1000 version loads. I don't have separate panel folders for the default 172 do you?

What does one do when there are two different airplanes in the folder? For example the default 172 has a 530/430 stack plane and a G1000 plane. I have a specific RealityXP.GNS.ini for the 530/430 version, but I don't want it to load when I fly the G1000 version because it conflicts with the G1000. Do I physically have to rename/remove the RealityXP.GNS.ini when I want to fly the G1000 version? Would be nice if there was an option to name the RealityXP ini file after the .acf file so dirs with multiple aircraft could have different setups. Maybe that option exists? Thanks for the help.

Carenado F33A XP11 [GNS_430_1.PANELS] ; display window if true. visible = true ; show screen only gauge if true. nobezel = true ; display type: WINDOW,PANEL2D,PANEL3D,PANELS frame.type = PANEL3D ; display position and dimension (left,top,width,height) frame.rect = 9,1279,423,229 ; screen only border size (pixels). border.size = 0 ; screen only border color (#RGB or #RGBA). border.rgba = #000000 ; enable mouse clickspots if true, disable if false (use SHIFT to override) usemouse = true ; left mouse button on the screen toggles popup window if true. popleft = true ; right mouse button on the screen toggles popup window if true (requires XP11.1). popright = false