nirgal76

Problem with GTN display

Recommended Posts

Hi,

i have a problem with GTN display.

i use a NO_BEZEL for the GTN integrated into the VC (with a NO_BEZEL section into RaalityXP.GTN.ini) and a GTN using the DEFAULT section for Popup window.

the NO_BEZEL use a brightness offset of -50 (because of HDR) and Popup one a brightness offset of 0

if the popup is not displayed, the VC GTN seems to flickering between the brightness of both section (it use the the good one and one time every 2 second or something like that, it uses the one of the DEFAULT section)

if the popup is displayed, both unit (VC and Popup) are using brightness of DEFAULT section (and so, no more flickering)

it happens on all aircrafts.

For testing, i have put the same brightness to both section and no more flickering.

So, i think GTN using another section than the DEFAULT one read both sections and this cause a conflict.

Here are my files :

panel.cfg

Quote

// RealAir Legacy P3D 2016

[Window Titles]
Window00=Main
Window01=Flight1 Garmin GTN750 U1 - DO NOT MODIFY
Window02=Blank

[VIEWS]
VIEW_FORWARD_DIR=0.000, 0.000, 0.000

//--------------------------------------------------------
[Window00]
size_mm=1024,1024
position=0
BACKGROUND_COLOR=0,0,0
visible=0
ident=15552

//--------------------------------------------------------
[Window01]
Background_color=0,0,0
size_mm=937,887
ident=14401
window_pos=0.660, 0.000
window_size=0.340, 0.580
zorder=99
gauge00=rxpGTN!GTN_750_1, 0, 0,937,887

//--------------------------------------------------------
[Window02]
size_mm=1,1
position=0
visible=0
ident=15600
BACKGROUND_COLOR=0,0,0
gauge00=RASLegacy!Blank, 0, 0, 1, 1

//--------------------------------------------------------
[VCockpit01]
size_mm=1024,1024
pixel_size=1024,1024
texture=$RASLegacy_CFG
background_color=1,1,1

gauge01=Config!Options, 1020, 1023, 1, 1
gauge02=Config!RealView, 1021, 1023, 1, 1
gauge03=RASLegacy!InitVars, 1022, 1023, 1, 1
gauge04=RASLegacy!1hzCode, 1023, 1023, 1, 1
gauge05=RASLegacy!2hzCode, 1024, 1023, 1, 1
gauge06=RASLegacy!18hzCode, 1025, 1023, 1, 1
gauge07=Config!RadioLayout, 1027, 1023, 1, 1

gauge08=RASLegacy!NavCom1, 1, 2, 509, 61
gauge09=RASLegacy!NavCom2, 1, 64, 509, 61
gauge10=RASLegacy!ADF, 4, 127, 332, 49
gauge11=RASLegacy!Xpndr, 7, 243, 305, 57
gauge12=RASLegacy!Autopilot, 5, 177, 292, 62
gauge13=RASLegacy!DME, 320, 197, 256, 46
gauge14=RASLegacy!VM1000C, 579, 0, 445, 446
gauge15=RASLegacy!Annunciator, 0, 305, 453, 68
gauge16=RASLegacy!AOA_Pro, 347, 131, 106, 63
gauge18=RASLegacy!Master_Warn, 457, 271, 108, 107

// ===============================================================================
// IMPORTANT - 'gauge19'. 'gauge20, 'gauge21', and 'gauge22' BELOW CAN BE OVERWRITTEN 
// BY THE CONFIG PANEL. PLEASE KEEP THIS IN MIND WHEN MANUALLY EDITING THIS FILE
// IF YOU WANT TO CHANGE THE GPS ENTRIES AND DON'T WANT THEM OVERWRITTEN IN ANY 
// CIRCUMSTANCE THEN CHANGE THE GAUGE NUMBERS. EG - CHANGE 'gauge 19' TO 'gauge22'
// ===============================================================================

gauge19=rxpGTN!GTN_750_1, 2,563,390,460,NO_BEZEL
gauge20=RASLegacy!Blank, 0, 0, 1, 1

gauge21=RASLegacy_Sound_V2!Sound, 0,0,1,1, D:\Addons_P3D\RealAir\SimObjects\Airplanes\RealAir Legacy V2\Panel\Sound\RASLegacy_Sound_V2.ini
gauge22=RASLegacy!Sound_Manager, 0,1,1,1

gauge23=RASLegacy!Oxygen, 1,1,1,1
gauge24=RASLegacy!Gauge_Backlight, 811,446,213,213
gauge25=RASLegacy!Gauge_Backlight_Screens, 794,447,16,16


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


Day=255,255,255
Night=255,255,255
Luminous=201,64,64
 

RealityXP.GTN.ini

Quote

[GTN_750_1]
; is the master device if true.
MasterDevice = true 
; selects COM/NAV Radios '1' or '2'.
RadiosPair = 1
; uses computer time if true, simulator time otherwise.
ComputerTime = false
; reduce screen update rate by half.
ReduceRate = false
; integral lighting percent (0 to 100)
Rheostat.Display = 72
; integral lighting percent (0 to 100)
Rheostat.Buttons = 75
; connects GPS to HSI if true.
LinkHsi = true 
; connects GPS to HSI course if true.
LinkCrs = false
; connects HSI OBS to GPS if true.
LinkObs = false
; connects GPS to VOR if true.
LinkVor = true 
; connects GPS to Autopilot if true.
LinkOto = true 
; connects CDI key to NAV/GPS switch if true.
AutoNavGps = true 
; enables automatic GPS/VLOC selection.
AutoSelect = true 
; selects VLOC NAV '1' or '2'. '0' selects same source as 'RadiosPair'.
AutoNavSource = 0
; sets device power source: ALWAYS_ON,AVIONICS_BUS,MAIN_BATTERY
PowerSource = AVIONICS_BUS
; connects GPS to Shadin Air Data computer if true.
UseAirData = true 
; connects GPS to Shadin Fuel Data computer if true.
UseFuelData = true 
; connects GPS to Audio Panel if true.
UseAudioPanel = true 
; connects GPS to Transponder if true.
UseTransponder = true 
; connects GPS to RYAN 9900BX if true.
UseRyanTcad = true 
; sets TCAD sound alerts volume in percent: 0 to 100.
RyanTcadVolume = 50
; enable device failures if true.
UseFailures = false
; uses Simulator GPS commands if true.
UseSimGpsCmds = false
; updates Simulator GPS flight plan if true.
LinkSimGps = false
; use legacy mouse (left CCW, right CW, middle Push) (override instances settings)
UseAltMouse = false
; sets transponder VFR code (octal default: #1200).
VFRcode = #1200
; sets fuel type: AVGAS,JETA,JETB,DIESEL
FuelType = AVGAS
; sets ownship icon type: 
; AUTO,LOW_WING,HIGH_WING,KIT_PLANE,TURBOPROP,TWIN_ENGINE,SINGLE_JET,BUSINESS_JET,2BLADES,3BLADES,4BLADES,ARROW
OwnshipIcon = AUTO
; sets TAWS type: TERR,TAWS_B,TAWS_A
TawsMode = TERR
; sets TAWS surface: HARD,HARD_SOFT,WATER,ANY
TawsSurface = HARD_SOFT
; TAWS minimum runway length (feet)
TawsMinLength = 40
; TAWS approach air speed (knots), -1 (auto detect Vref: 95)
TawsApprSpeed = 95
; TAWS maximum flap extension speed (knots) or -1 (auto detect Vfe: 130)
TawsFlapSpeed = 130
; TAWS maximum gear extension speed (knots) or -1 (auto detect Vle: 0)
TawsGearSpeed = 0
; HSI lateral deviation scale factor.
CdiScale = 1
; HSI vertical deviation scale factor.
GsiScale = 1
; sets voice type: MALE,FEMALE
VoicePref = MALE
; sets master sound volume in percent: 0 to 100.
MasterVolume = 100
; selects the default database: 0: 'Garmin (North America)', 1: 'Jeppesen (Worldwide)'
NavDbType = 1
; selects the CPU running the trainer process: 1 to 32
; 0: last core, -1: automatic.
CpuAffinity = -1

[GTN_750_1.NO_BEZEL]
nobezel = true
; 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
; enable touch beyond screen bounds if true, clip if false (GTN native).
extendtouch = true
; auto-resize dimension (width,height)
refsize = 
; left mouse button popup ident  (ex: GPS_PANEL or 225) (disables touchscreen when set).
popleft = 
; right mouse button popup ident (ex: GPS_PANEL or 225).
popright = 
; adjust brightness (0 to 100)
brightness.bezel = 0
; offset brightness (-100 to +100)
brightness.screen = -50

[GTN_750_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
; enable touch beyond screen bounds if true, clip if false (GTN native).
extendtouch = true 
; auto-resize dimension (width,height)
refsize = 
; left mouse button popup ident  (ex: GPS_PANEL or 225) (disables touchscreen when set).
popleft = 
; right mouse button popup ident (ex: GPS_PANEL or 225).
popright = 
; adjust brightness (0 to 100)
brightness.bezel = 100
; offset brightness (-100 to +100)
brightness.screen = 0
 

nb : I don't know if GNS have the same problem, i didn't test. I will do tomorrow if it can help

Share this post


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

Hi, there is indeed a limitation with the 'screen offset' brightness for now. It was never meant to have distinct screen brightness, only distinct bezel brightness. Unfortunately, we have to default create a section with all possible settings for our customers to pick up the ones of interest when making a copy, but we should have better documented this.

Nevertheless, it is a good suggestion and I'll see what I can do.

As for the clickspots (missing), it is an oversight already fixed in the (ever) coming update.

Share this post


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

Hi, there is indeed a limitation with the 'screen offset' brightness for now. It was never meant to have distinct screen brightness, only distinct bezel brightness. Unfortunately, we have to default create a section with all possible settings for our customers to pick up the ones of interest when making a copy, but we should have better documented this.

Nevertheless, it is a good suggestion and I'll see what I can do.

As for the clickspots (missing), it is an oversight already fixed in the (ever) coming update.

having the same brightness for both is a problem with HDR  than makes VC unit very bright compare to popup's one.

it is not a big issue as GTN works fine (and i repeat, i'm very surprised how it don't affect performance of the sim, it's a really good job, even with several units displayed) but for the future, it could be great to have this kind of configuration to work. 

So, in the TODO list at low priority ;)

For the clickspot, yes, i'm sorry, i see that just after posting, and it's a good news ;)

Share this post


Link to post
Share on other sites

Hi Nirgal, and thank you for your kind words!

The purpose of the brightness offset setting is to effectively compensate for this drawback in the FltSim platform. 

Nevertheless, since it is not possible to set this per-instance, it is a short sighted omission on our end, and I'll see how the best we can make it work as needed.

This is not a problem in XP11 and there is no need for these hacks by the way ;-)

Share this post


Link to post
Share on other sites

Thank you for your explanation

Here is what i propose than could satisfy me when using 2 instances of the same unit (each using its own section in INIT file (for example, "DEFAULT" for popup and "NO_BEZEL" for VC ) : (when you will have some hours to lose ;))

-when both instance are displayed,. use the same brightness (the one of DEFAULT section)
- when there is only one instance displayed (so the VC one), use the brightness of the section for this unit (NO_BEZEL).

(I had tryied XP but i don't like how graphics looks like, and i don't want to lose some addons i have under P3D)

But the better i could do is to give up HDR because it doesn't satisfy me. Drawbacks are bigger than advantages.

 

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