Jump to content

Sign in to follow this  
DAL1850

GNS530 in Duke B60

Recommended Posts

Hello and Happy New Year.

 

I am experiencing a curious problem with the RealAir Duke B60 and the Mindstar GNS530. I currently have the RealAir panel configured (via their configurator) for the RealityXP 530 and have modified it to swap the RXP gauge for the Mindstar 530 (I have a dummy rxpGNS.dll in my gauges folder). This allows the gauge to properly display in the VC, however the hotspot does not seem to work properly. By contrast, if I configure the Duke for the default GNS 500 and make the same edits to the panel.cfg, the hotspot works correctly but the gauge does not display correctly in the VC.

 

Below is my panel.cfg for the Duke (configured for RXP 500) w/ my Mindstar edits:

// Panel Configuration file
// RealAir Simulations Beechcraft Duke B60 2013 Update
// Panel and Gauge Programming by Sean Moloney
// Copyright (c) 2013 RealAir Simulations

[Window Titles]
Window00=Main Panel
Window01=Reality XP GNS 530 WAAS - RXP_CONFIG_TOOL - DO NOT CHANGE
Window02=Blank

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

[VCockpit01]
size_mm=1024,1024
pixel_size=1024,1024
texture=$RAS_Duke_CFG
background_color=1,1,1

gauge01=Config!Options, 1020, 1023, 1, 1
gauge02=Config!RealView, 1021, 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=Config!AdfDip, 1026, 1023, 1, 1
gauge08=RASDuke!NavCom1, 1, 2, 509, 61
gauge09=RASDuke!NavCom2, 1, 64, 509, 61
gauge10=RASDuke!ADF, 4, 127, 332, 49
gauge11=RASDuke!Xpndr, 7, 243, 305, 57
gauge12=RASDuke!Autopilot, 5, 177, 292, 62
gauge13=RASDuke!DME, 4, 305, 256, 46
gauge14=RASDuke!Annunciator, 886,131,137,262
gauge15=RASDuke!KA285_Annun, 512,2,337,108

// ===============================================================================
// 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=rxpGNS!GNS530, 1, 660, 504, 364
gauge19=MPI_GNS!GNS530, 1, 660, 504, 364, 1:1:-1
gauge20=RASDuke!Blank, 0, 0, 1, 1
gauge21=RASDuke_Sound!Sound, 1,1,2,2,./SimObjects/Airplanes/RealAir Duke B60 V2/Panel/Sound/RASDuke_Sound.ini
gauge22=RASDuke!Sound_Manager, 1,1,3,3
gauge23=RASDuke!Pressurisation, 1024, 1023, 1, 1

[Color]
Day=255,255,255
Night=225,117,89
Luminous=200,200,101

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

[Window01]
window_pos=0.739583,0.000000
window_size=0.260417,0.300000
visible=0
ident=15531
zorder=99
;gauge00=rxpGNS!GNS530,0,0,100,100
gauge00=MPI_GNS!GNS530,0,0,100,100,1:2:15531

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

Any ideas why my VC hotspot won't activate Window01 in this setup?

 

Thank you for your help!

 

J


Jason Barlow

 

Broadcasting from 1984 via Flux Capacitor operating at 1.21 Jiggawatts!

Share this post


Link to post

Upon closer inspection, it looks all mouse clicks are not forwarded to the VC gauge. Only the 2D gauge responds to mouse input.

 

Has anyone had success integrating the 530 into this aircraft?


Jason Barlow

 

Broadcasting from 1984 via Flux Capacitor operating at 1.21 Jiggawatts!

Share this post


Link to post

Bueller? Bueller?


Jason Barlow

 

Broadcasting from 1984 via Flux Capacitor operating at 1.21 Jiggawatts!

Share this post


Link to post

Your ident is incorrect. It should be 11013...

//--------------------------------------------------------
[Window01]
Background_color=0,0,0 
size_mm=937,910
window_size_ratio=1.000  
position=7
visible=0
ident=11013
window_size= 0.340, 0.580
window_pos= 0.660, 0.420
zorder=99

gauge00=MPI_GNS!GNS530,  0,0,800,581,1:2:11013
  • Upvote 1

Fr. Bill    

AOPA Member: 07141481 AARP Member: 3209010556

Interests: Gauge Programming - 3d Modeling for Milviz

Many Thanks to All That Donated To Our Server Drive!

Share this post


Link to post

You posted over the holiday period, I have been on vacation time, which means I haven't been here. Sorry that didn't fit your timetable of expectations... but, there it is. :smile:

 

Bill has answered your question and unless there's some hidden overlay capturing all mouse input... that should fix it.


Ed Wilson

Mindstar Aviation
My Playland - I69

Share this post


Link to post

 

Your ident is incorrect. It should be 11013...

//--------------------------------------------------------
[Window01]
Background_color=0,0,0 
size_mm=937,910
window_size_ratio=1.000  
position=7
visible=0
ident=11013
window_size= 0.340, 0.580
window_pos= 0.660, 0.420
zorder=99

gauge00=MPI_GNS!GNS530,  0,0,800,581,1:2:11013

Thanks, Bill.

 

Does that mean GPS_PANEL is not 225 but 11013 or is that ident special to the Duke (i.e. can I use that ident in any aircraft I want to use the GNS530)?

 

Found this:

 

http://www.avsim.com/topic/455599-gns530-2d-popup-clickspot-issue-b55-solved/


Jason Barlow

 

Broadcasting from 1984 via Flux Capacitor operating at 1.21 Jiggawatts!

Share this post


Link to post

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
Sign in to follow this  
  • Tom Allensworth,
    Founder of AVSIM Online


  • Flight Simulation's Premier Resource!

    AVSIM is a free service to the flight simulation community. AVSIM is staffed completely by volunteers and all funds donated to AVSIM go directly back to supporting the community. Your donation here helps to pay our bandwidth costs, emergency funding, and other general costs that crop up from time to time. Thank you for your support!

    Click here for more information and to see all donations year to date.
  • Donation Goals

    AVSIM's 2020 Fundraising Goal

    Donate to our annual general fundraising goal. This donation keeps our doors open and providing you service 24 x 7 x 365. Your donation here helps to pay our bandwidth costs, emergency funding, and other general costs that crop up from time to time. We reset this goal every new year for the following year's goal.


    18%
    $4,530.00 of $25,000.00 Donate Now
×
×
  • Create New...