4 hours ago, Bert Pieke said:

The thing with JustFlight is that they may support the F1 GTN and GNS... (based on their documentation), but if indeed you can get the GNS frame to show up, with a dark screen, we all know that substituting the RXP unit for the F1 unit is a piece of cake.

I am going to put a GNS 530 in my TB20 (which right now has a GTN in the panel) and document my steps..

I did indeed get their GNS frame to show up, but I didn't bother posting a pic because, well, it would probably make more sense at this point to simply get the gauge to show up.  Then later maybe deal with the frame...although dealing with that may be further than I want to take this...and their xml for their bezel controls isn't exposed, it all seems to be integrated into their gauge dll.

The texture they call behind the frame is $GNS430, and that isn't working if I use that texture as the "screen" for my VC RealityXP gauge.  It's really strange.  It is almost like they are doing something behind the scenes -- programatically -- that is keyed to the F1 unit somehow.

4 hours ago, Bert Pieke said:

OK, that does not work, because my TB20 only has two choices:  Standard panel and GTN650/750.

https://imgur.com/a/s9CSfvf

What options do you have?

BTW.. not only the panel.cfg gets switched, but so does the interior model file..

The Tomahawk has three choices: Standard panel, GNS430/530, and GTN650/750.

That's correct -- the interior VC model file gets switched as well.  I even looked inside the mdl file using a handy-dandy tool, for any possible texture names...I did see $Radios_2D, but as you can see from my pics earlier in this thread, that is the background for the COM1/xponder gauges and not that blank area.

I did submit a support ticket as to the proper texture name, rather than post in their forums.  I think if I posted in their forums, I'd get no response, or a response telling me that the aircraft doesn't support RXP.  😄

I believe you are overthinking this... Suggest you stop looking behind the curtain and just use their tools to get the job done. 

1 hour ago, Mace said:

I did indeed get their GNS frame to show up, but I didn't bother posting a pic because, well, it would probably make more sense at this point to simply get the gauge to show up. 

If you can get the GNS frame to show up, you are done with the JF tools.. Now instead use the RXP addon pulldown to replace the F1GNS by the equivalent RXP unit.  Job done

47 minutes ago, Bert Pieke said:

If you can get the GNS frame to show up, you are done with the JF tools.. Now instead use the RXP addon pulldown to replace the F1GNS by the equivalent RXP unit.  Job done

That was one of the first things I did, and -- no joy.  

I think JustFlight are doing something differently here.  Maybe they will have some insight on the support ticket I submitted.  It's really not that big a deal to me, as I don't mind using the RXP as a popup, especially in this type of aircraft...essentially a trainer and runabout type of aircraft.  Still, I'm a guy that likes to know why something works or doesn't work, and I can't figure this one out.

11 minutes ago, Mace said:

That was one of the first things I did, and -- no joy.  

 

What do you mean: No joy?

When you went to replace, did you see the F1GNS lines, and did you substitute them by RXP equivalents?

1 minute ago, Bert Pieke said:

What do you mean: No joy?

When you went to replace, did you see the F1GNS lines, and did you substitute them by RXP equivalents?

Yes, I did that.

"No joy" = did not work.   "No Joy" is a term you might use when responding to ATC, saying that in effect you do not see the traffic.

Of course I used their model switcher, their panel toggle, and then used RXP's Wizard to substitute.  That was the first thing I did.  The RXP equivalents are all happily sitting in the panel.cfg right now, yet I'm not seeing the GNS in the VC.  It should be displaying, as the popup works fine.  My thought is that something in their gauge dll is tied to the F1 GNS only.

As you can see in the earlier posts, I was able to get the GNS to appear in the VC via my own manual edits, but that was a last resort, as the "normal" methods of using the RXP Wizard were not working.

12 minutes ago, Mace said:

Of course I used their model switcher, their panel toggle, and then used RXP's Wizard to substitute. 

Sounds like you've got it all figured out.. 

And yet, the only screenshot that matters, the one with the GNS frame in the panel seems to have gone missing..

Edited April 28, 20206 yr by Bert Pieke

19 minutes ago, Mace said:

  My thought is that something in their gauge dll is tied to the F1 GNS only.

 

In that case, have you tried adding a dummy F1GNS.dll file to your Gauges folder?

19 hours ago, Bert Pieke said:

Sounds like you've got it all figured out.. 

And yet, the only screenshot that matters, the one with the GNS frame in the panel seems to have gone missing..

See below.

7 minutes ago, Mace said:

See below.

OK, so that is what you want.

Now, are you telling me that you cannot substitute the dark F1 GNS 430, by a nice RXP equivalent?

Edited April 29, 20206 yr by Bert Pieke

19 hours ago, Bert Pieke said:

In that case, have you tried adding a dummy F1GNS.dll file to your Gauges folder?

That is not working either.

If I had it "figured out", it would be working, and this thread would not be here.

The above picture is after using JustFlight's mdl/panel switcher, and after using RXP's wizard.  Popup works.  VC does not.  As requested, a pic of JustFlight's bezel, and after using RXP's "Setup Aircraft" tool.

1 minute ago, Bert Pieke said:

Now, are you telling me that you cannot substitute the dark F1 GNS 430, by a nice RXP equivalent?

I cannot.

OK, what does the Vcockpit section of the panel.cfg look like at this point?

Can you post a copy?

[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=rxpGNS2!GNS_430_1, 0, 0,950,687
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=rxpGNS2!GNS_430_1, 0, 0,950,392