Skip to content
View in the app

A better way to browse. Learn more.

The AVSIM Community

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

Any News on the Beechcraft B55 SP?

Featured Replies

Hey Guys,

 

I have the Reality XP 530 and 430 and used this panel.cfg.

 

I can't seem to get anything to work.

 

Nothing powers up and if use shift + 2 to bring up the pop up then the 2 units are transparent in the middle..

 

any help would be appreciated.

 

Dave

  • Replies 44
  • Views 8.2k
  • Created
  • Last Reply

Top Posters In This Topic

Do you have an rxpgns.ini file in the B55 folder?

 

Edit: In thinking about this a bit more, if you're getting transparent displays it probably means that the underlying Garmin trainer app is not getting fired up. Lots of things that could be going wrong there, but a bit out of my knowledge range as to good troubleshooting. You might try over on RealityXP support forums: http://www.simforums.com/forums/reality-xp-unofficial-forum_forum12.html . If you're seeing this, I bet you'll have the same problem on other aircraft.

 

Scott

Nice panel mod, Scott, and I'm now using yours...works great, thanks.

 

Dave, using the RealityXP config app, make sure that the proper path to the Garmin trainer to entered correctly into the RXPGNS.INI file that's created by that app. This .ini file should be in your Baron's Panel folder, and the RXP GNS units use it to find and run the trainer, which provdes the functionality of the units themselves. The trainer should have been installed when you installed the RealityXP units themselves.

Wayne Klockner
United Virtual

BetaTeamB.png

 

  • Commercial Member

Just as an FYI, the base code for the integration was and is Chuck's so best thank him as well!

Please contact oisin at milviz dot com for forum registration information.  Please provide proof of purchase if you want support.  Also, include the username you wish to have.
 

Just as an FYI, the base code for the integration was and is Chuck's so best thank him as well!

 

The fact that integration completely works now is, of course, all due to you guys and I know we all appreciate it. So, my thanks specifically to Chuck.

 

Like others, I wasn't sure what had and hadn't been done in the SP and some experimentation and modification was necessary to get it all to work for me. Not trying to take credit from anyone here, just share what I found actually worked for me in order to help out.

 

Scott

  • Moderator

Okay, I'm going to chime in here to explain the somewhat unusual number of [VCockpitnn] entries...

 

========================

1. [VCockpit01]

....[VCockpit02]

The entries in these two sections use the default 3d mesh and will display the included B55 avionics gauges.

 

========================

2. [VCockpit03]

....[VCockpit04]

The entries in these two sections are only used for RXP alternate gauges, and will display the special 3d mesh that will align the knobs correctly for the RXP 530 and/or 430. Simply commenting out the 530 and/or 430 gauge entries in the two sections of #1 above will automatically cause these alternate 3d meshes for #2 to appear, and display the RXP units correctly.

 

========================

3. [VCockpit05]

....[VCockpit06]

The entries in these two sections are only used for the "Free Radio" flat panel that will be seen using the switch on the lower part of the copilot's side of the main panel. You could actually put anything you want here that will fit, even a completely different set of avionics! You need not concern yourself with these two sections at all, unless you just want to experiment. They will never be loaded or seen unless you "flip the switch..."

Fr. Bill    

AOPA Member: 07141481 AARP Member: 3209010556


     Avsim Board of Directors | Avsim Forums Moderator

The fact that integration completely works now is, of course, all due to you guys and I know we all appreciate it. So, my thanks specifically to Chuck.

 

Like others, I wasn't sure what had and hadn't been done in the SP and some experimentation and modification was necessary to get it all to work for me. Not trying to take credit from anyone here, just share what I found actually worked for me in order to help out.

 

Scott

 

Same here, and thanks, Chuck! Works and looks fantastic!

Wayne Klockner
United Virtual

BetaTeamB.png

 

Will buy it today or tomorrow, looking forward to finally getting to try it out!

vpa159.png
Wayne's config didn't properly drive the HSI for me - a problem I had with some of the example panel.cfg files before the SP as well. The order of 430 and 530 matters.

 

Here's my panel.cfg with 530 and 430 and popups enabled. You may want to reposition the popup positions to taste, but this seem to be working well. Note, you must have an rxpgns.ini with idents that match for the popups to work. Usual disclaimers apply about backups, risk etc.

 

Hope this helps,

 

Scott

 

 

Hi Scott

 

What specifically makes the HSI work?

 

Is it just the order?

 

530 first or 430?

 

Cheers

 

 

What specifically makes the HSI work?

 

Is it just the order?

 

Seems to be. It's "Window01", the popup that gives you the whole avionics stack, that matters. Put the 430 as gauge00 in the popup, and the 530 as gauge02 (basically a straight replacement for the default 530 and 430 in the stock panel.cfg) and the HSI won't work. Reverse these and make the 530 gauge00 and the 430 gauge02 and it works fine.

 

Scott

Thanks mate, I'll do that.

 

 

We have included an RXP_panel.cfg file specifically for the RXP integration, as well as a 3d panel specifically for RXP so that the knobs will line up and function properly.

 

Hi Bill,

 

I've been having a bit of a thread over at the Reality-XP forums about my issue geting the units to work properly other than using my own simple replacement method using FSPanel Studio

 

If you can be bothered, the thread is here: http://www.simforums...496.html#249496

 

I am using the follwing config, kindly supplied by Jim Hodgkinson. It doesn't work as detailed in the last post in that thread. You can read that my simple replacement method shows the units but not all the click spots and buttons work, as you describe in your post above:

 

// This Panel.cfg file created by FS Panel Studio panel editor utility - http://www.fspanelstudio.com

// Built Thursday, July 12, 2012 at 12:43 FSPS Build:22767

 

[Window Titles]

Window00=B55 Preflight

Window01=GPS

Window02=Reality XP GNS 430 WAAS - RXP_CONFIG_TOOL - DO NOT CHANGE

Window03=Reality XP GNS 530 WAAS - RXP_CONFIG_TOOL - DO NOT CHANGE

Window04=Reality XP DropStack

 

 

[VIEWS]

VIEW_FORWARD_WINDOWS=MAIN_PANEL,THROTTLE_PANEL,GPS_PANEL

 

VIEW_FORWARD_DIR=10.000, 0.000, 0.000

 

 

 

//--------------------------------------------------------

[Window00]

Background_color=0,0,0

size_mm=500,243

window_size_ratio=1.000

position=0

visible=0

ident=70

window_size= 0.400, 0.324

window_pos= 0.000, 0.040

 

gauge00=B55_XMLGauges!B55_Preflight, 0,0,500,243

 

 

//--------------------------------------------------------

[Window01]

Background_color=255,255,255

size_mm=1280,650

window_size_ratio=1.000

position=2

visible=0

ident=GPS_PANEL

window_size= 0.710, 0.552

window_pos= 0.290, 0.480

 

gauge00=B55_XMLGauges!FBS_KR 87 ADF, 640,268,640,134

gauge01=B55_XMLGauges!FBS_KAP140, 640,402,640,163

gauge02=B55_XMLGauges!FBS_GTX330, 0,468,640,170

gauge03=rxpGNS!GNS530, 0,0,640,468

gauge04=rxpGNS!GNS430, 640,0,640,268

 

 

//--------------------------------------------------------

[Window02]

Background_color=0,0,0

size_mm=156,105

position=7

visible=1

ident=15431

window_size= 0.313, 0.210

window_pos= 0.687, 0.527

zorder=99

 

gauge00=rxpGNS!GNS430, 0,0,100,100

 

 

//--------------------------------------------------------

[Window03]

Background_color=0,0,0

size_mm=244,250

position=7

visible=1

ident=15531

window_size= 0.488, 0.500

window_pos= 0.510, 0.000

zorder=99

 

gauge00=rxpGNS!GNS530, 0,0,100,100

 

 

//--------------------------------------------------------

[Window04]

Background_color=0,0,0

size_mm=25,15

position=0

visible=1

ident=15000

window_size= 0.050, 0.030

window_pos= 0.000, 0.000

zorder=100

 

gauge00=rxpDrop!Stack, 0,0,100,100

 

 

//--------------------------------------------------------

[Vcockpit01]

file=C310_VC_01.bmp

size_mm=1024,1024

visible=0

pixel_size=1024,1024

texture=$C310_VC_01

 

gauge00=MilVizC310!MilVizC310_XMLSound, 657,4,17,16

gauge01=B55_XMLGauges!FBS_KAP140, 0,767,640,163

gauge02=B55_XMLGauges!FBS_KR 87 ADF, 0,630,640,134

gauge03=B55_XMLGauges!C310_DME, 649,32,300,150

gauge04=B55_XMLGauges!B55_Preflight, 0,0,1,1

 

 

//--------------------------------------------------------

[Vcockpit02]

file=C310_VC_02.bmp

size_mm=512,512

visible=0

pixel_size=1024,1024

texture=$C310_VC_02

 

gauge00=B55_XMLGauges!FBS_GTX330, 0,376,512,136

 

 

//--------------------------------------------------------

[Vcockpit03]

Background_color=0,0,0

size_mm=1024,1024

visible=0

pixel_size=1024,1024

texture=$C310_VC_03

 

gauge00=rxpGNS!GNS430, 0,1,1024,433

gauge01=GPS_POP_UP!GPS_POP_UP, 298,120,432,204

 

 

//--------------------------------------------------------

[Vcockpit04]

Background_color=0,0,0

size_mm=512,512

visible=0

pixel_size=1024,1024

texture=$C310_VC_04

 

gauge00=rxpGNS!GNS530, 0,8,512,384

gauge01=GPS_POP_UP!GPS_POP_UP, 110,55,291,213

 

 

//--------------------------------------------------------

[Vcockpit05]

file=C310_VC_01_FR.bmp

size_mm=1024,1024

visible=0

pixel_size=1024,1024

texture=$C310_VC_05

 

gauge00=MilVizC310!MilVizC310_XMLSound, 657,4,17,16

gauge01=rxpGNS!GNS430, 0,568,640,287

gauge02=rxpGNS!GNS530, 0,117,640,451

gauge03=rxpGNS!GMA340, 0,2,640,115

 

 

//--------------------------------------------------------

[Vcockpit06]

file=C310_VC_02_FR.bmp

size_mm=512,512

visible=0

pixel_size=1024,1024

texture=$C310_VC_06

 

gauge00=B55_XMLGauges!FBS_KAP140, 0,137,512,131

gauge01=B55_XMLGauges!FBS_KR 87 ADF, 0,268,512,106

gauge02=B55_XMLGauges!FBS_GTX330, 0,1,512,136

 

 

 

Day=255,255,255

Night=85,85,85

Luminous=140,140,140

 

[Default View]

X=0

Y=0

SIZE_X=8191

SIZE_Y=3384

 

To summarise my issues, if I use the above config I can see and use the units fine in shift-2, 3 and 4 popups.

 

I can only see the default unit 3d models with no labels and blank screens (the don't work at all) in the VC. Doesn't matter which way the switch is flipped. The units are just blank.

 

There are a couple of photos on the simforums post to illustrate what I'm talking about.

 

I love this plane, and am so glad you had the time and patience as a team to get the RXP integration sorted, and I'd really love to be able to use it properly :smile:

 

I have the GNS WAAS unlimited pack so would like to be able to get them working together.

 

Where are the files you speak of in your quote? They don't seem to be in the panel folder..

 

Many thanks,

 

jake

 

EDIT: I just looked in my aircraft.cfg file and it says:Milviz B55 v1.0 FDE

 

I bought it from AVSIM..I have been told the download was updated, so I downloaded the updated file, which had the same name (V1U) but it looks like it is still version 1?

 

thanks again :smile:

JAKE EYRE
It's a small step from the sublime to the ridiculous...Napoleon Bonaparte
newSigBetaTeam.gif
lancairuk.jpg

In fact, I almost certainly don't have SP1 as I don't have/see an E55 anywhere!

 

Let me check the download again...I downloaded it about five times already!

JAKE EYRE
It's a small step from the sublime to the ridiculous...Napoleon Bonaparte
newSigBetaTeam.gif
lancairuk.jpg

EDIT - please ignore this post. I had pre SP-1. It all now works with Scotts config above. Sorry to be a bother :smile:

JAKE EYRE
It's a small step from the sublime to the ridiculous...Napoleon Bonaparte
newSigBetaTeam.gif
lancairuk.jpg

Create an account or sign in to comment

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.