April 29, 20206 yr Hmm, does that look strange to you? Two instances of the GNS430.. What did the panel.cfg look like before the RXP substitution? You should still have the panel.cfg.rxp or something similar.. Bert
April 29, 20206 yr Author [Vcockpit01] Background_color=0,0,0 size_mm=512,512 visible=1 pixel_size=512,512 texture=$test gauge00=JF_PA38_Tomahawk!SystemWatch, 0,0,1024,1024 gauge01=jf_sound!jf_sound, 0,1,1,1 //-------------------------------------------------------- [Vcockpit02] Background_color=0,0,0 size_mm=1024,1024 visible=1 pixel_size=1024,1024 texture=$Radios_2D gauge00=JF_PA38_Tomahawk!SL30, -10,175,765,170 gauge01=JF_PA38_Tomahawk!SL40, -8,479,765,170 gauge02=JF_PA38_Tomahawk!GTX330, -20,610,790,217 //-------------------------------------------------------- [Vcockpit03] size_mm=1024,1024 pixel_size=1024,1024 texture=$GNS530 background_color=0,0,0 gauge00=F1GNS!GNS530, 0,0,950,687,UNIT1.VC gauge01=JF_PA38_Tomahawk!GNS, 1,1,1,1 //-------------------------------------------------------- [Vcockpit04] size_mm=1024,1024 pixel_size=1024,1024 texture=$GNS430 background_color=0,0,0 gauge00=F1GNS!GNS430, 0,0,950,392,UNIT1.VC Rhett 7800X3D ♣ 96 GB G.Skill Flare ♣ Gigabyte 4090 ♣ Crucial P5 Plus 2TB
April 29, 20206 yr Maybe having two identical RXP gauges in the VC is the problem... Try this: [Vcockpit03] size_mm=1024,1024 pixel_size=1024,1024 texture=$GNS530 background_color=0,0,0 gauge00=rxpGNS2!GNS_530_1, 0, 0,950,687 gauge01=JF_PA38_Tomahawk!GNS, 1,1,1,1 Bert
April 30, 20206 yr Hi, The panel.cfg file you're showing and the picture you've posted are making me wondering where is the 530 supposed to be displaying, because I can see only 1 GNS 430 in the VC!?! You have to first check whether it is VC#3 or VC#4 which is supposed to displaying the GNS you see with a bezel in the VC. 1) edit the panel.cfg file like this: [Vcockpit03]// gauge00=F1GNS!GNS530, 0,0,950,687,UNIT1.VC// gauge01=JF_PA38_Tomahawk!GNS, 1,1,1,1 [Vcockpit04]// gauge00=F1GNS!GNS430, 0,0,950,392,UNIT1.VCgauge00=rxpGNS2!GNS_430_1, 0, 0, 950, 392, NO_BEZEL 2) If this doesn't work, try this then: [Vcockpit03]// gauge00=F1GNS!GNS530, 0,0,950,687,UNIT1.VC// gauge01=JF_PA38_Tomahawk!GNS, 1,1,1,1gauge00=rxpGNS2!GNS_530_1, 0, 0, 950, 687, NO_BEZEL [Vcockpit04]// gauge00=F1GNS!GNS430, 0,0,950,392,UNIT1.VC NB: can you confirm you've both the 530 and the 430 products? Edited April 30, 20206 yr by RXP
May 1, 20206 yr Do you mean it would change model on the fly, one using only VC3 and the other using only VC4 for example, so that they don't have to modify the panel.cfg file for both?
May 1, 20206 yr FWIW, I've tried to do this in the JustFlight TB10/20 but with equal lack of complete success. I can get the GNS430 into the GNS VC frame using Jean-Luc's NO_BEZEL entry, but of course the buttons then don't work. So I've settled for having the whole thing inside the frame, so that the buttons do work (although a bit hard to see!). From the panel.cfg section below, you can see I've 'borrowed' a toggle form the Carenado Baron which allows me to click inside the GNS VC screen to bring up the pop-up window. It works for me... [Vcockpit02] Background_color=0,0,0 size_mm=537,290 visible=1 pixel_size=537,290 texture=$GNS430 gauge00=rxpGNS2!GNS_430_1, 0,0,537,290 gauge01=BB58!Toggle_Gps, 247,92,189,112 Cheers, Dave
May 2, 20206 yr 13 hours ago, RXP said: Do you mean it would change model on the fly, one using only VC3 and the other using only VC4 for example, so that they don't have to modify the panel.cfg file for both? Correct.. Bert
May 2, 20206 yr 11 hours ago, davidallen said: FWIW, I've tried to do this in the JustFlight TB10/20 but with equal lack of complete success. I can get the GNS430 into the GNS VC frame using Jean-Luc's NO_BEZEL entry, but of course the buttons then don't work. So I've settled for having the whole thing inside the frame, so that the buttons do work (although a bit hard to see!). From the panel.cfg section below, you can see I've 'borrowed' a toggle form the Carenado Baron which allows me to click inside the GNS VC screen to bring up the pop-up window. It works for me... [Vcockpit02] Background_color=0,0,0 size_mm=537,290 visible=1 pixel_size=537,290 texture=$GNS430 gauge00=rxpGNS2!GNS_430_1, 0,0,537,290 gauge01=BB58!Toggle_Gps, 247,92,189,112 Cheers, Dave What about translating the buttons, using an F1VC.xml file? That has been done in many airplanes, successfully.. Bert
May 3, 20206 yr Thanks Bert. I've found and followed your February thread on the F1VC.xml topic, however, it all looks to be somewhat above my paygrade. I think I'll stay with what I've got... 😀 Having opened all three interior .mdl files with HxD, they don't appear to be formatted in any way I can understand! And as Jean-Luc suggested, there are a lot more buttons on the GNS than on the GTN's! But many thanks, anyway. Dave
May 3, 20206 yr 21 minutes ago, davidallen said: Thanks Bert. I've found and followed your February thread on the F1VC.xml topic, however, it all looks to be somewhat above my paygrade. I think I'll stay with what I've got... 😀 Having opened all three interior .mdl files with HxD, they don't appear to be formatted in any way I can understand! And as Jean-Luc suggested, there are a lot more buttons on the GNS than on the GTN's! But many thanks, anyway. Dave This may actually work by simply telling the RXP GNS to "Use FS GPS commands".. have you tried that? The F1VC xml gauge is used for translating F1 GNS commands to FS GNS commands which can then be read by the RXP GNS. In your case, there is no F1 GNS involved.. Edited May 3, 20206 yr by Bert Pieke Bert
May 3, 20206 yr On 5/1/2020 at 9:01 PM, Bert Pieke said: What about translating the buttons, using an F1VC.xml file? That has been done in many airplanes, successfully.. My bad. In this case, this is not required, because there is no F1 GNS gauge involved, so this is actually bad advice Edited May 3, 20206 yr by Bert Pieke Bert
May 3, 20206 yr Well, thanks to Bert's limitless patience and goodwill, I'm another of his fans whose problem has been solved, and I hope it may help the OP, Mace. This applies to putting the RXP GNS430v2 into the VC of the JustFlight TB10/20, but I imagine it will apply to the JF Tomahawk as well. Together with applying the 'NO_BEZEL' section of the panel.cfg below (amend as necessary to suit your setup), bring up the RXP configuration window in the sim, and make sure 'Use Simulator GPS Commands' is checked. That's all ! [Vcockpit02] Background_color=0,0,0 size_mm=537,290 visible=1 pixel_size=537,290 texture=$GNS430 gauge00=rxpGNS2!GNS_430_1, 0,0,537,290, NO_BEZEL Thanks again, Bert.
Archived
This topic is now archived and is closed to further replies.