"Rudder seems to effect the plane in similar fashion as aileron, the plane starts to bank if you apply rudder only. The rudder does work but it also generates banking to an extend."

 

That's what's happening to me too. The aircraft banks when I apply rudder. Maybe it just needs some tweaking. Also when I apply the brakes, I don't see the brakes move forward like I do on most high quality payware.

Most people say the Carenado flight model comment based on several years old data .......

 

I realize that, but now that Mr. Stolle has designed the flight dynamics of several of the latest Carenado aircraft, as well as updating the flight dynamics of several older Carenado aircraft, the flight model comments are somewhat "out-of-date" now.

A usage point for throttle control, You can bring both up slowly with the Keyboard shortcut F3

 

The lower right subpanel has the radio stack toggle to place a flat panel in place of the installed 3D version , if the knobs dont line up try adjusting the width of the cfg entry by a few pixels in the 3d set.

"Rudder seems to effect the plane in similar fashion as aileron, the plane starts to bank if you apply rudder only. The rudder does work but it also generates banking to an extend."

 

That's what's happening to me too. The aircraft banks when I apply rudder.

 

+1

 

Rudder induced banking can be so stong that even full opposite ailerons isn't enough to bring the plane back to level. Not that I've ever flown a Baron but it feels a bit strange

 

Maybe it just needs some tweaking.

 

+1 again

A usage point for throttle control, You can bring both up slowly with the Keyboard shortcut F3

 

The lower right subpanel has the radio stack toggle to place a flat panel in place of the installed 3D version , if the knobs dont line up try adjusting the width of the cfg entry by a few pixels in the 3d set.

 

And using fsuipc you could probably do the same for RPM and mixture, I believe there are 'incr'/'decr' commands for those axes, and you could map them to shift-f2/f3 and ctrl-f2/f3.

 

In fact, I think I'm going to do so myself, it'll make flying a lot easier :D

 

Edit: Yep, works great, for anyone else doing the same, bear in mind that MS appear to have gotten 'Prop Pitch Lo' and 'Prop Pitch Hi' the wrong way around (correspond to max RPM and min RPM respectively on the B55

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

 

Sorry if this is a noob question, but what should we take out, or change in order to only use the 530 in the Baron? I know I have to change crossfill=off but what else out of these changes should I change? Also, where do I put the changes of the reality ini? Thanks for the information, and excuse the noobiness :Whistle:

I noticed this posted on the Milviz forum. I tried it and I'm having the same problem. Anyone else experiencing this?

 

Folks, I just did a flight at 8,000 and found a bit of an anomaly. I had max throttles, which produced about 22" manifold pressure. That's about normal of course, but what was an issue was that I couldn't bring the rpm's back below 2450 no matter how far back I pulled the props. Down low it was no problem, and at 8000 when I pulled the throttles back for descent, the rpm's dropped to about 2300 or so. As I descended, I was able to bring the rpm's down further in direct (apparently) correlation with altitude. Of course, you should be able to bring the props all the way back at any time and at any altitude, as you know.

 

Could you folks have a quick look at this and see if you can reproduce this? Many thanks, and again congrats on your new release

Hi c97019

You just change the entries in the panel.cfg concerning the GNS 530, the other gauge remains untouched (gauge01=B55_XMLGauges!FBS_GNS430_2, 0,367,640,262).

The RXPGNS.ini is the same, except that all the entries for the GNS 430 are obsolete.

I noticed this posted on the Milviz forum. I tried it and I'm having the same problem. Anyone else experiencing this?

 

 

Yes. See my post earlier in this thread. Sounds like the same issue.

 

Scott

I can confirm this behaviour. Even at 5,500 the rpms will barely hold 2,400 rpm and won't go any lower. You can pull the prop rpm levers back further and as you descend the rpms will lower. With some changes to the prop characteristics this can be remedied so that they respond at higher altitudes where the air is thinner. I will await the developers work on this since I am sure they will get this fixed.

I noticed this posted on the Milviz forum. I tried it and I'm having the same problem. Anyone else experiencing this?

 

Hi c97019

You just change the entries in the panel.cfg concerning the GNS 530, the other gauge remains untouched (gauge01=B55_XMLGauges!FBS_GNS430_2, 0,367,640,262).

The RXPGNS.ini is the same, except that all the entries for the GNS 430 are obsolete.

 

\

 

Great, I'll try that, thanks a bunch! :)

Right now, I am doing a flight for the VA I´m in. PASI to PAKT in the trusty PA-34 Seneca (Carenado).

Right after that, I´ll make a nice check ride in my new B55 around the Seattle are... :Peace:

I must admit that that's one thing that I felt realair did well, the 'left mouse button controls both, right controls individual' gives you a good way to control without sacrificing flexibility.

 

 

Indeed, it always amazes me that more twins dont use this system - works brilliantly in the Duke

Anyway it's impossible to rotate the larger knobs. I can rotate only the small ones (comm/nav decimals and secondary pages).

 

Confirmed here as well. This would be an almost perfect compromise if the large knobs worked, as all the other controls seem to "poke through" just fine.

 

Scott

Everyone, we will be looking to fix this RPM issue with the SP. Appreciate everyone bringing this to our attention and we will get it resolved.

 

Cheers,

 

Ken