tttocs

Bezel in Turbine Duke

Recommended Posts

As mentioned in another post, I got the 750 set up in my first plane last night.  Installation in the Turbine Duke went smoothly and it worked perfectly on the first flight.  I do have one issue however.  Instead of the nice sculpted bezel that I should see, I have an ugly plain black bezel with no textures in the VC.  Is this what others are seeing, or am I somehow covering up the Duke's bezel?

Scott

Edit:  I am using the NO_BEZEL option.

Share this post


Link to post
Share on other sites
Help AVSIM continue to serve you!
Please donate today!

Hi,

Just a reminder about this feature introduced a few versions back: using 'NO_BEZEL' as a 5th parameter is a shortcut for nobezel=true setting.

Usually, gauge 'rendering' options are in a rendering section which name is prefixed with the gauge name (GTN_750_1) and suffixed with a custom name (no spaces allowed). The custom name is also used as the 5th parameter in the panel.cfg file in order to make a link between a specific gauge instance in the panel.cfg, and the settings. In this section, there are different keys and associated values.

For example:
gauge00=rxpGTN!GTN_750_1,0,0,100,100,MY_COOL_SETTINGS

and:
[GTN_750_1.MY_COOL_SETTINGS]

 

There is special 5th param: NO_BEZEL.

When used, it dispenses to create a rendering section (although you still can), and the gauge instance uses the same settings as the 'DEFAULT' rendering section, but assumes nobezel=true. This saves from having to copy/paste/create a new section in the ini file!

 

Having said this, using nobezel means the gauge renders the screen only. Should the bezel displays 'black', it is possible there was no texture associated and it was designed to 'drape' the gauge bezel onto the 3D polygons, while having the screen centred in the middle?

Share this post


Link to post
Share on other sites

 

Jean-Luc,

2 hours ago, RXP said:

When used, it dispenses to create a rendering section (although you still can), and the gauge instance uses the same settings as the 'DEFAULT' rendering section, but assumes nobezel=true. This saves from having to copy/paste/create a new section in the ini file!

Thanks for the explanation - yes this is the method that I am using.

 

2 hours ago, RXP said:

Having said this, using nobezel means the gauge renders the screen only. Should the bezel displays 'black', it is possible there was no texture associated and it was designed to 'drape' the gauge bezel onto the 3D polygons, while having the screen centred in the middle?

Understood.  My believe was that there was a bezel provided by Real Air and I was doing something that was overwriting it somehow, but I'm now afraid that might be incorrect..  I'll have to go looking to see if I can verify.  I guess I was also hoping that someone else would chime in and say - "yep, that's the way mine is as well and it's the best we can do" or - "mine works fine - you must be doing something wrong".  From the few screenshots I've seen I've not been able to tell if others have a bezel or not.

Thanks,

Scott

Share this post


Link to post
Share on other sites
4 minutes ago, tttocs said:

I guess I was also hoping that someone else would chime in and say - "yep, that's the way mine is as well and it's the best we can do" or - "mine works fine - you must be doing something wrong". 

Scott,

Mine works fine.  

http://2017-12-8_12-0-24-874-L.jpg

 

  • Upvote 1

Share this post


Link to post
Share on other sites
1 minute ago, fppilot said:

Scott,

Mine works fine.  

Mine too.  See Frank's picture as to what mine looks like :).

  • Upvote 1

Share this post


Link to post
Share on other sites

Looks fine here. The GTN bezels match the other avionics bezels.

Spoiler

9e0da3d1693b45128025228d98560d22.jpg

For what it's worth here's what my 2 files look like.

Panel.cfg

Spoiler

// Panel Configuration file
// RealAir Simulations Beechcraft Turbine Duke V2 2014 Update
// Panel and Gauge Programming by Sean Moloney
// Copyright (c) 2014 RealAir Simulations

// ===============================================================================
// IMPORTANT - 'Window01' AND 'Window02' BELOW ARE RESERVED FOR GPS POPUPS AND CAN
// BE OVERWRITTEN BY THE CONFIG PANEL. PLEASE KEEP THIS IN MIND WHEN MANUALLY
// EDITING THIS FILE. IF YOU WANT TO ADD CUSTOM WINDOW ENTRIES, YOU CAN USE ANY
// VALUE FROM 'Window03' TO 'Window 09'.
// ===============================================================================

[Window Titles]
Window00=Main Panel
Window01=RXP GTN750 1
Window02=RXP GTN650 2

//--------------------------------------------------------
[Window00]
file=2D_Help.bmp
Background_color=0,0,0
size_mm=1024,95
position=6
visible=1
ident=MAIN_PANEL

//--------------------------------------------------------
[Window01]
Background_color=0,0,0
size_mm=937,887
window_size_ratio=1.000 
position=7
visible=1
ident=14401
window_size= 0.340, 0.580
window_pos= 0.000, 0.120
zorder=99

gauge00=rxpGTN!GTN_750_1,  0,0,937,887

//--------------------------------------------------------
[Window02]
Background_color=0,0,0
size_mm=937,390
window_size_ratio=1.000 
position=7
visible=1
ident=14403
window_size= 0.340, 0.300
window_pos= 0.000, 0.700
zorder=99

gauge00=rxpGTN!GTN_650_2,  0,0,937,390

//--------------------------------------------------------
[Vcockpit01]
Background_color=1,1,1
size_mm=1024,1024
visible=1
pixel_size=1024,1024
texture=$RAS_Duke_CFG

gauge00=Config!Options,  1020,1023,1,1
gauge01=Config!RealView,  1021,1023,1,1
gauge02=Config!RadioLayout,  1027,1023,1,1
gauge03=RASDuke!InitVars,  1022,1023,1,1
gauge04=RASDuke!1hzCode,  1023,1023,1,1
gauge05=RASDuke!2hzCode,  1024,1023,1,1
gauge06=RASDuke!18hzCode,  1025,1023,1,1
gauge07=RASDuke!NavCom1,  1,2,509,61
gauge08=RASDuke!NavCom2,  1,64,509,61
gauge09=RASDuke!ADF,  4,127,332,49
gauge10=RASDuke!Xpndr,  7,243,305,57
gauge11=RASDuke!Autopilot,  5,177,292,62
gauge12=RASDuke!DME,  4,305,256,46
gauge13=RASDuke!KA285_Annun,  512,2,337,108
gauge14=RASDuke!Annunciator_Turbine,  516,  111 ,226,245
gauge15=RASDuke!Moritz_LCD,  808,133,214,259
gauge16=RASDuke!Fuel_Qty_LCD,  410,128,105,86
gauge17=RASDuke!Master_Warn,  893,1,130,129
gauge18=rxpGTN!GTN_750_1,  2,563,390,460,NO_BEZEL
gauge19=rxpGTN!GTN_650_2,  3,383,390,175,NO_BEZEL
gauge20=rxpGTN!f1vc,0,0,1,1
gauge21=RASDukeTv2_Sound!Sound,  1,1,2,2,\Sound\RASDukeTv2_Sound.ini
gauge22=RASDuke!Sound_Manager,  1,1,3,3
gauge23=RASDuke!Pressurisation,  1024,1023,1,1
gauge24=Config!ModelOptions,  1020,1023,1,1


Day=255,255,255
Night=225,117,89
Luminous=200,200,101

[Default View]
X=0
Y=0
SIZE_X=8192
SIZE_Y=6143

The RadioLayout.xml file in the panel\Config folder.

Spoiler

<Gauge Name="RealAir Radio Layout" Version="1.01" DateModified="2017-11-20 02:20:29">

   <Element>
      <Select>
         <Value>
   (G:Var1) 0 ==
   if{
    (* All GPSes *)
    0 (&gt;L:rasGps500_X,number)
    0 (&gt;L:rasGps500_Y,number)
    0 (&gt;L:rasGns530_1_X,number)
    0 (&gt;L:rasGns530_1_Y,number)
    0 (&gt;L:rasGns530_2_X,number)
    0 (&gt;L:rasGns530_2_Y,number)
    0 (&gt;L:rasGns430_1_X,number)
    0 (&gt;L:rasGns430_1_Y,number)
    0 (&gt;L:rasGns430_2_X,number)
    0 (&gt;L:rasGns430_2_Y,number)
    0 (&gt;L:rasGtn750_1_X,number)
    0 (&gt;L:rasGtn750_1_Y,number)
    0 (&gt;L:rasGtn750_2_X,number)
    0 (&gt;L:rasGtn750_2_Y,number)
    0 (&gt;L:rasGtn650_1_X,number)
    0 (&gt;L:rasGtn650_1_Y,number)
    0 (&gt;L:rasGtn650_2_X,number)
    0 (&gt;L:rasGtn650_2_Y,number)
    (* Unused Radios *)
    0 (&gt;L:rasAudio_X,number)
    0 (&gt;L:rasAudio_Y,number)
    0 (&gt;L:rasNavCom1_X,number)
    0 (&gt;L:rasNavCom1_Y,number)
    0 (&gt;L:rasNavCom2_X,number)
    0 (&gt;L:rasNavCom2_Y,number)
    0 (&gt;L:rasXpndr_X,number)
    0 (&gt;L:rasXpndr_Y,number)
    (* Left Radios *)
    10 (&gt;L:rasGtn750_1_X,number)
    0 (&gt;L:rasGtn750_1_Y,number)
    10 (&gt;L:rasGtn650_1_X,number)
    55.1 (&gt;L:rasGtn650_1_Y,number)
    (* Right Radios *)
    20 (&gt;L:rasAdf_X,number)
    0 (&gt;L:rasAdf_Y,number)
    20 (&gt;L:rasAp_X,number)
    11.2 (&gt;L:rasAp_Y,number)
    0 (&gt;L:rasNavGps_X,number)
    0 (&gt;L:rasNavGps_Y,number)
    1 (&gt;G:Var1)
   }
   </Value>
      </Select>
   </Element>

</Gauge>

 

  • Upvote 1

Share this post


Link to post
Share on other sites
33 minutes ago, bills511 said:

Looks fine here. The GTN bezels match the other avionics bezels.

I have also used Ryan and gang's "f1vc.xml" mod which provides access to the buttons and knobs in the VC.

  • Upvote 1

Share this post


Link to post
Share on other sites
2 hours ago, fppilot said:

Mine works fine.

Thanks Frank, but you left out the "you must be doing something wrong" part. :-)

2 hours ago, bills511 said:

Looks fine here. The GTN bezels match the other avionics bezels.

Yep, more confirmation that I messed up... and I think I know how.  I'll follow up later after I get a chance to actually fire up the sim and check out my "fix".

Thanks to all for jumping in to help.

Scott

Share this post


Link to post
Share on other sites
1 hour ago, tttocs said:

Thanks Frank, but you left out the "you must be doing something wrong" part. :-)

Funny Scott! I like to steer clear of those type statements, LOL! That from someone like me who spent a half-day trying to no avail to get RXP fifth parameter popups to work in the Carenado A36 Bonanza, a model I seldom fly these days. Turned off reflections and the like and never did find success. Reverted to the Carenado toggle_gps type gauge.

Sometimes it is just the challenge..........

Share this post


Link to post
Share on other sites
4 hours ago, tttocs said:

Yep, more confirmation that I messed up... and I think I know how.  I'll follow up later after I get a chance to actually fire up the sim and check out my "fix".

Well, I didn't.  Thought I'd bungled getting the buttons gauge stuff set up in my haste to try things out and that perhaps that was affecting things.  Nope.  Think I'm done for today and will revisit tomorrow.

Scott

Share this post


Link to post
Share on other sites

Well, I'm pretty much at a loss here, but I'm not pretty sure it has nothing to do with the RXP 750 itself.  I've completely uninstalled the T-Duke, made sure everything was deleted and started with a fresh install.  I note that after running the RealAir config program and firing up the sim the plane doesn't have the correct appearing bezel even before I try to modify for the RXP unit.

I am using the new installer and installing to the recommended documents folder rather than inside P3D.  I wonder if I should go back and try to install using the old installer and manually modifying in v4.  Otherwise I'm stumped as to why everyone else seems to have the correct appearing bezel.

Scott

Share this post


Link to post
Share on other sites

New installer should be fine and it also has the new sound fix.
Do you have it looking like this?

Spoiler

 

Share this post


Link to post
Share on other sites
21 minutes ago, bills511 said:

New installer should be fine and it also has the new sound fix.
Do you have it looking like this?

The sound fix wouldn't be an issue, as I have the 64 bit version of the sound gauge and have used it to get the B60 completely functional in v4.  However, if that's not the issue there's little point in going down that road.  Yes, the config screen you show is what I've been using.  Just for grins I've also tried it with dual 750s.

It's almost like I'm missing a texture or two, which is why I tried a complete new install, but I have no idea what or why.

Thanks for trying to help,

Scott

Share this post


Link to post
Share on other sites
27 minutes ago, tttocs said:

It's almost like I'm missing a texture or two, which is why I tried a complete new install, but I have no idea what or why.

In the main Duke texture folder (\Turbine Duke V2 P3D4\SimObjects\Airplanes\RealAir Duke Turbine V2\Texture) I have 160 items. The textures for the GTN are RAS_GTN.dds & RAS_GTN_L.dds.

Can you post a screenshot. I'm curious as to what it looks like.

 

Share this post


Link to post
Share on other sites

I also show 160 files, including the two RAS_GTN... .dds files.  Here's what it looks like in my plane.  Note the countours and beveling from the bezel to the screen which I see in Frank's image are missing here.

 

Edit:  Stand by - an issue with the image displaying.

Scott

 

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now