Jump to content

Archived

This topic is now archived and is closed to further replies.

pmanhart

Any News on the Beechcraft B55 SP?

Recommended Posts

I am testing it as we speak. About halfway from Jacksonville, FL to Newport News, VA. So far no problems. I have no ETA on time myself, but providing I don't run in to any issues I would say a day or 2 at the most. We have already had a few of the other testers run through it, so just doing a QA flight on it myself at this point.

Share this post


Link to post
Share on other sites

tons of stuff... Most of which relates to the RXP integration... and other small stuff that bugged us... even if it didn't bug anyone else.

 

we have also added another plane... the E55... This has a new and different FDE... but it LOOKS the same... so no complaints on that score please...

 

should be interesting... two for the price of one...

Share this post


Link to post
Share on other sites

Nice, looking forward to the RXP integration!

Share this post


Link to post
Share on other sites

Please do remember... we do not (still) support 3rd party stuff. If it works, great, if not... well we did our best...

Share this post


Link to post
Share on other sites

Appreciate your taking the time to give this a whack, and I understand your position relative to support. Don't really expect you to support someone else's product, but... RealityXP integration is a huge selling point for many of us, and any bumps you can smooth on your end to allow that integration will be helpful and appreciated.

 

Thanks,

 

Scott

Share this post


Link to post
Share on other sites

Please do remember... we do not (still) support 3rd party stuff. If it works, great, if not... well we did our best...

 

this kind of attitude seems so common with today's businesses - the idea of lets just serve our customers juuuuust enough to get buy, but whatever we do.. lets never really go all out and LISTEN to what our PAYING customers are saying.. I guess it's easier this way isn't it?

Share this post


Link to post
Share on other sites

Well, I hardly think that's what we're doing. I think, and you may think what you wish on that score, but we try very hard to make sure our product is good enough on its own. If you, the client, wish to add a 4 barrel hemi converter agnositicator to it... how the heck am I supposed to plan and adjust for that?

 

There are so many different agnosticators out there... which ones do we cover? Only the ones YOU like? what about every one else? How many hundreds do we have to make sure work?

 

let me be clear on this one... we make PLANES. The "agnosticators" make products that go in the planes... I would think that it would be up to THEM to make sure that we, the plane makers, have sufficient info so that we can make it work easily. That they don't should be a signal to you (their client) that maybe you should contact them and tell them what you're telling me.

 

In the end, we cannot and will not support what is not made by us, for us or with us. Why would anyone do that?

Share this post


Link to post
Share on other sites

lets never really go all out and LISTEN to what our PAYING customers are saying.. I guess it's easier this way isn't it?

 

Brian, this seems waaay over the top to me, especially prior to seeing what the SP actually brings. I've seen some pretty positive response to virtually all of the issues users have had with the B55 so far (in other words, LISTENING), including comments suggesting that RealityXP integration will be improved. Note that, like others, I have managed to get mine working, albeit with a couple of minor issues.

 

And Colin, I guess I'm confused. I'm NOT a dev (or even close to being one) so I'm speaking entirely from ignorance and a desire to learn, but others offer RealityXP integration ranging from good to outstanding. Do they have something from Jean-Luc that you guys don't?

 

Referencing my comments above, I certainly don't expect Milviz to provide support for someone else's product, but as a customer I do like plane devs to know that RealityXP integration is often a make or break point in my purchase decisions, especially if I'm on the fence a bit and the plane already features a Garmin 430 or 530. Case in point is the 310 - a plane I'm considering but probably would have purchased long ago had I felt more confident about being able to use my 430 and/or 530.

 

Looking forward to the SP, and as always, thanks for listening,

 

Scott

Share this post


Link to post
Share on other sites

I have no idea what they have or do not have. All I know is that it's a real pita to get it to fit right and work right. It could certainly be made much easier by having JL supply us devs with a 3d max model of where the buttons (and their tool tips) go. This would also allow us to better integrate them into our lighting systems... Why he doesn't do this? I will be asking him that very question sometime in the next week as we are going for beers...

 

That said....

 

The 310 works with the RXP set using the radio free panel model. We've no complaints. (note that we've had complaints about the 55 due to there being so many other things in that area and not being able to turn the knobs properly as well as the setup issues)...

 

JL is a personal friend of the guy who coded the B-55 (Chuck). They have arranged something that is supposed to work very well.

 

We do try to make these things work but....

Share this post


Link to post
Share on other sites

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.

 

I have included check code in my avionics that will automatically swap the 3d panel from "ours" to "RXPs." This will allow any or all of the units to be replaced depending on what the customer owns.

 

As far as I'm concerned, that's as much "support" we can offer... :Nerd:

Share this post


Link to post
Share on other sites

It's out for those of you who bought it from our site. Other sites will have it shortly....

Share this post


Link to post
Share on other sites

Thanks for the service pack and for the handy EZdok camera profile; it's perfect.

 

Forgive the dumb question here, but what's the proper way to ensure the use of my RealityXP Garmin units? Do I simply rename the RXP_panel.cfg to Panel.cfg (while backing up the original)?

Share this post


Link to post
Share on other sites

I have no idea as I don't own them....

 

Surely the RXP units came with instructions????

Share this post


Link to post
Share on other sites

I have no idea as I don't own them....

 

Surely the RXP units came with instructions????

 

They do, but I'm simply confused by the different panel.cfg files in your new Baron installation and by the statement by Fr Bill in post #13 regarding the automatic switching of the 3d panel. I'm probably overlooking something obvious, but a simple 1-2 sentence instruction would ensure that I don't "break" something inadvertently. Thanks very much.

Share this post


Link to post
Share on other sites

Sorry... not sure what to do here... I've asked one of the coders to come and comment... but he's off right now... maybe tmrw...

Share this post


Link to post
Share on other sites

No worries, thanks, and meanwhile, I'll experiment...Nail%20Biting.gif

Share this post


Link to post
Share on other sites

Hi Guys,

 

All I did was add the RXP 530 to the panel.cfg - see below. Then I simply used the switch on the panel - just below the lower unit,to display the RXP 530 unit at the top of the stack.Hope that makes sense....as not by FSX at the moment. Hope this helps.

 

Steve

 

 

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

// Built Sunday, June 24, 2012 at 17:41 FSPS Build:21603

 

[Window Titles]

Window00=B55 Preflight

Window01=GPS

 

 

[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=0,0,0

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_GNS430_2, 640,0,640,268

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

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

//gauge02=B55_XMLGauges!FBS_GNS530_1, 0,0,640,468

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

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

 

 

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

[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_GNS430_2, 0,367,640,262

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

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

gauge04=B55_XMLGauges!B55_DME, 649,32,300,150

gauge05=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

gauge01=rxpGNS!GNS530, 0,0,512,374

//gauge01=B55_XMLGauges!FBS_GNS530_1, 0,0,512,374

 

 

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

[Vcockpit03]

file=C310_VC_01_FR.bmp

size_mm=1024,1024

visible=0

pixel_size=1024,1024

texture=$C310_VC_05

 

gauge00=B55_XMLGauges!FBS_GNS430_2, 0,707,640,262

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

gauge02=B55_XMLGauges!BK_AudioPanel, 0,0,640,128

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

//gauge03=B55_XMLGauges!FBS_GNS530_1, 0,103,640,468

gauge04=B55_XMLGauges!FBS_GTX330, 0,571,640,136

 

 

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

[Vcockpit04]

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,106,512,131

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

 

 

 

Day=255,255,255

Night=85,85,85

Luminous=140,140,140

 

[Default View]

X=0

Y=0

SIZE_X=8192

SIZE_Y=3384

Share this post


Link to post
Share on other sites

Thanks, Steve, and I hadn't noticed that switch at all! Meanwhile, here's my edited panel.cfg that includes both the RealityXP 530 and 430, and it seems to be working quite well. A Shift-2 popup of the entire GPS group, including the RealityXP units, is included. Please let me know if this one causes any issues.

 

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

// Built Sunday, June 24, 2012 at 17:41 FSPS Build:21603

[Window Titles]

Window00=B55 Preflight

Window01=GPS

 

[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=0,0,0

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=rxpGNS!GNS430, 640,0,640,268

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

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

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

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

 

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

[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_GNS430_2, 0,367,640,262

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

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

gauge04=B55_XMLGauges!B55_DME, 649,32,300,150

gauge05=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

//gauge01=B55_XMLGauges!FBS_GNS530_1, 0,0,512,374

 

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

[Vcockpit03]

Background_color=0,0,0

size_mm=1024,1024

visible=0

pixel_size=1024,1024

texture=$C310_VC_03

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

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

[Vcockpit04]

Background_color=0,0,0

size_mm=512,512

visible=0

pixel_size=1024,1024

texture=$C310_VC_04

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

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

 

[Vcockpit05]

file=C310_VC_01_FR.bmp

size_mm=1024,1024

visible=0

pixel_size=1024,1024

texture=$C310_VC_05

//gauge00=B55_XMLGauges!FBS_GNS430_2, 0,707,640,262

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

gauge01=B55_XMLGauges!BK_AudioPanel, 0,0,640,128

//gauge03=B55_XMLGauges!FBS_GNS530_1, 0,103,640,468

//gauge02=B55_XMLGauges!FBS_GTX330, 0,571,640,136

 

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

[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,106,512,131

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

 

Day=255,255,255

Night=85,85,85

Luminous=140,140,140

[Default View]

X=0

Y=0

SIZE_X=8192

SIZE_Y=3384

Share this post


Link to post
Share on other sites
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.

 

I have included check code in my avionics that will automatically swap the 3d panel from "ours" to "RXPs." This will allow any or all of the units to be replaced depending on what the customer owns.

 

As far as I'm concerned, that's as much "support" we can offer... :Nerd:

 

Great, thanks for that.

 

I was using it with a popup but this makes it even better!

 

I'll try it out when I get time.

 

Cheers

Share this post


Link to post
Share on other sites

I did think about adding the 430, but only really use the 530 for navigation.

 

For the popup, I assigned a spare button on my saitek set through FSUIPC.

 

Steve

Share this post


Link to post
Share on other sites

The panel.cfg edit seems to work well...here's a snap of the cockpit from this evening's maiden flight with the patched Baron:

 

 

MILVIZ B55 panel by wklockner, on Flickr

 

Thanks Rudi,

 

I was actually unable to get it to work with the Panel cfg provided by Milviz in the SP. Well for a start I don't have the 430, but I had commented that out, and also tried replacing it with their default 430 but that didn't work.

 

But using your config Rudi I was able to get it to work!

You can improve on that further to get a popup if you run the RXP configurator and let it create the Window, then you should be able to use the popup as long as the ID numbers match. But backup your panel.cfg first!

 

Milviz and N4gix - thanks very much for a great integration! The knobs are working beautifully in 3D now.

I know you don't understand it, but us Avionics geeks want the real thing, once we've had RXP we don't go back :)

 

But you know what you've done now, now people are going to ask you to do it in your C310R and King Air as well lol, although now that you know how, why not!

 

For anyone who has only GNS530, here is my Panel cfg. It keeps the Milviz default 430 in place.

It also has the popup setup, so when you click the magnifying glass it will popup.

https://dl.dropbox.com/u/29331868/Beech_Baron_55%20Milviz%20-%20RXP530%20only%20integration.rar

 

Use at your own risk etc.. and backup your configs, etc etc.

 

This is what it looks like with RXP 530, and default 430:

fsx%202012-07-03%2021-40-59-01.jpg

Share this post


Link to post
Share on other sites

×
×
  • Create New...