Milviz B55 might be available really soon

[tttocs 301]

Any time you change to GPS mode on the RXP you need to change the AP back to NAV mode again or it won't track.

 

I'd have to try this one more time to verify, but it's possible that I got hung up on switching back and forth between VLOC and GPS to test the HSI and didn't notice the AP switching out of NAV. I know I paid close attention to the panel's GPS/NAV switch just in case.

 

HSI doesn't update for me either, but autopilot works.

Maybe this is by design to be realistic? I know some FSX planes like the Duke have HSI driven by GPS as an option, with HSI set manually as the "realistic" option..

 

On the Duke (and through the config file on the RXPs in general) you have the option of allowing the GPS to update the HSI heading at every course change, something not typically implemented on that class of plane/HSI, or doing it manually, but the HSI's CDI is still driven either way as is glideslope on an LPV approach. It's the ability to do LPV approaches (and to do them without AP) that drives me to wanting to use the RXP GPS's as much as anything.

 

Again, I'll revisit all of this pending the changes Milviz is already working on and see how things look at that point. I greatly appreciate their willingness to take a second look at this and make changes and improvements.

 

Scott

[mpw8679 428]

Has any one noticed an audio clicking sound in the background that repeats itself every few seconds?

[Ponk 51]

Yes, and keeps going even when I'm back At the start menu!

[mpw8679 428]

Yes, and keeps going even when I'm back At the start menu!

Hopefully this gets addressed in the SP.

[Milviz 919]

We know about the sound. :(

[mpw8679 428]

We know about the sound.

Ok thanks

[Milviz 919]

I have to ask this question... about the rolling with rudder... at what point is the rolling starting? are you at full rudder? 50%? Please try and be specific because, quite honestly, it's not happening to me unless i hit 100%.... (this doesn't mean we're not looking into "fixing" it...)

[Gareth Patrick 0]

I can do a full barrel roll with about 10% deflection of the rudder!

 

I've checked my controls, re-calibrated them, re-installed the baron, removed all weather, etc. etc. and still with about 10% deflection it just rolls and rolls and rolls. Elevators and Ailerons operate as expected. Other aircraft (and I've got a lot) all operate as expected.

 

Not sure what's going on to be honest.

 

Edit: Just tested your 310R and it has a similar tendency but much slower and very easy to control.

[Milviz 919]

we know what's going on... we're trying to identify if the issue is a: prevalent on all systems (cause we're getting some people, real pilots most of them, are saying that this is normal behavior IRL... IF you throw the rudder hard over...) and b: because we have to make a choice about how to fly this bird... realistically (like the 310... on which we still get complaints of strong pull on takeoff and landing and in the air... which is perfectly normal).... or easier...

 

So...

 

For now, if you have the 310, you can copy that air file over (making the necessary mods to it so that it's a baron 55 and not a C310R) and you should get quite close... The B-55 is, apparently way more stable and "crisp" on the controls... (this is a TEMP fix)

 

Comment removed on this... I had auto rudder on... (oops!)

[tttocs 301]

b: because we have to make a choice about how to fly this bird... realistically (like the 310... on which we still get complaints of strong pull on takeoff and landing and in the air... which is perfectly normal).... or easier...

 

If that's really the situation, I'll choose "b", but what I saw was not real world behaviour. Sorry, I haven't flown the plane in several days now and was mostly focused on other things - probably won't get a chance to fly again until at least tomorrow evening to verify, but hopefully others are chiming in.

 

Scott

[Milviz 919]

there was no choice in the statement... "b:" reflects the situation. That said, needless to say, we want realism. Of course. And we know it's not realistic. We're working on it...

[petefsx 0]

Hi there,

first I thank you very much for this lovely model. I'm sure you will get all stated issues fixed in near future.

Well, that might be another one ;-) I experienced the GNS530 shows no CTRs but restricted areas. Using de-clutter doesn't fix this. GNS430 works as expected.

[CFIJose 5,485]

I did not test it yet, but it should work like that.

Note that I own the RXP GNS 430 & 530 as well as the Unlimited Pack.

If you own just one gauge, you might change only the corresponding part in the panel.cfg

 

Here is my panel.cfg:

 

[Window Titles]

 

Window00=C310 Prelight

Window01=GPS

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

Window03=Reality XP GNS 430 WAAS 2 - RXP_CONFIG_TOOL - DO NOT CHANGE

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

gauge00=rxpgns!GNS430, 640,0,640,268

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

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

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

gauge01=rxpgns!GNS430, 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!C310_DME, 649,32,300,150

 

 

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

[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

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

 

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

 

 

 

 

Day=255,255,255

Night=85,85,85

Luminous=140,140,140

 

[Default View]

X=0

Y=0

SIZE_X=8191

SIZE_Y=3384

 

[Window02]

window_pos=0.510000,0.000000

window_size=0.488281,0.500000

visible=1

ident=15531

zorder=99

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

[Window03]

window_pos=0.510000,0.507177

window_size=0.488281,0.291667

visible=1

ident=15432

zorder=99

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

[Window05]

position=0

window_size=0.078125,0.041667

visible=1

ident=15000

zorder=100

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

 

Here is my RXPGPS.ini:

 

[GNS530]

Popup=15531

AutoPilotMode=2

Radios=2

LinkCdiKey=On

AutoCdiMode=0

AutoApproach=Off

LinkVor=1

LcdStyle=Off

AutoWidth=500

AutoHeight=360

Trainer=

NoKeyClick=Off

DisableRxTx=Off

AutoPowerOn=Off

AutoRadiosOff=On

GndSpdFromDeltaLatLon=Off

AutoCourse=Off

LinkObs=On

ShadinFuel=On

RadioSyncMode=Full

Brightness=-1.000000

CrossFill=On

TCAD=On

FuelType=0

Taws=On

TawsVolume=60

TAWS_ALRT_TYPE_NEG_CLIMB_RATE=0

TAWS_ALRT_TYPE_IMMINENT_OBST_IMPACT_CAUT=0

TAWS_ALRT_TYPE_REDUCED_OBST_CLEARANCE_CAUT=0

TAWS_ALRT_TYPE_IMMINENT_TERR_IMPACT_CAUT=0

TAWS_ALRT_TYPE_REDUCED_TERR_CLEARANCE_CAUT=0

TAWS_ALRT_TYPE_IMMINENT_OBST_IMPACT_WRNG=0

TAWS_ALRT_TYPE_REDUCED_OBST_CLEARANCE_WRNG=0

TAWS_ALRT_TYPE_IMMINENT_TERR_IMPACT_WRNG=0

TAWS_ALRT_TYPE_REDUCED_TERR_CLEARANCE_WRNG=0

CPU=0

HardwareDevice=Off

HardwareIdx=0

[GNS430]

Popup=15432

AutoPilotMode=2

Radios=2

LinkCdiKey=On

AutoCdiMode=0

AutoApproach=Off

LinkVor=1

LcdStyle=Off

AutoWidth=500

AutoHeight=210

Trainer=

NoKeyClick=Off

DisableRxTx=Off

AutoPowerOn=Off

AutoRadiosOff=On

GndSpdFromDeltaLatLon=Off

AutoCourse=Off

LinkObs=On

ShadinFuel=On

RadioSyncMode=Full

Brightness=-1.000000

CrossFill=On

TCAD=On

FuelType=0

Taws=On

TawsVolume=60

TAWS_ALRT_TYPE_NEG_CLIMB_RATE=0

TAWS_ALRT_TYPE_IMMINENT_OBST_IMPACT_CAUT=0

TAWS_ALRT_TYPE_REDUCED_OBST_CLEARANCE_CAUT=0

TAWS_ALRT_TYPE_IMMINENT_TERR_IMPACT_CAUT=0

TAWS_ALRT_TYPE_REDUCED_TERR_CLEARANCE_CAUT=0

TAWS_ALRT_TYPE_IMMINENT_OBST_IMPACT_WRNG=0

TAWS_ALRT_TYPE_REDUCED_OBST_CLEARANCE_WRNG=0

TAWS_ALRT_TYPE_IMMINENT_TERR_IMPACT_WRNG=0

TAWS_ALRT_TYPE_REDUCED_TERR_CLEARANCE_WRNG=0

CPU=0

HardwareDevice=Off

HardwareIdx=0

[sETTINGS]

Dimmer=Off

SimpleMouse=Off

KeyOnFocus=On

Thank you! Now I have the GNS 530 working with the B55. How dow I enable a click to open just the GNS 530 and not the entire stack?

[xplanery 250]

Simply fantastic aircraft. This is probably first general aviation aircraft I have found to actually feel dynamic to fly, not being unrealistically stable like most addon aircrafts are. Stalls & spins modeled very well, and also turbulence really seems to affect this addon like its supposed to.

 

Also visually and every other way probably the best non jet addon that I have ever bought. Milviz will surely get me as a customer for future civilian aircraft releases too.

[Tabs 2,790]

I'm gonna get this - should I buy now or wait for the patch that's been discussed? I have RXP stuff I'll want to put into it...

 

Got some real life flight time in a Baron with one of our beta testers last October and this looks real similar to what we flew!