PA-28R Arrow III

Sorry if this is a dumb question, but is it correct that the markings on the TAS scale count by 20 until 140 and then by 10 (i.e. 100, 120, 140, 150, 160 ...)? This doesn't seem right (and it wasn't like this before) but maybe it is actually correct.

Also, if I'm not mistaken, TAS=IAS at ISA, which (i think) is when the 0's are lined up on the top of the TAS wheel, which is not the case in v0.3.0

If anyone else was wondering, I also had this issue with other aircraft, like said above looks like a msfs issue. Was a new patch update today for the sim. Will see if that fixes some issues :)

Thanks for the feedback

@KC-Pilot Now only one appears. At one point there were two.

wohoo - confirmed fixed with 0.3.0 :)

Thanks!

Agreed!! :) Another great update. Happy to have my compass back, and airspeed seems to be up!

@Fabbi said in v0.3.0:

@roland_lfor
Oh my god, I never checked the fuel tanks, and I just sitting there in the cockpit wondering why that engine would not start :grinning_squinting_face: :man_facepalming_medium-light_skin_tone:

Simply follow the new checklists and you'll be good ;)

@copper thanks, I missed that discussion, very nice.

Update 0.3.0 has fixed all the issues I was having. Good to have the plane back! Thanks again for the suggestions.

Thanks for the advice. An uninstall followed by an install fixed it.

@RetiredMan93231 Thanks, will do!

This should be fixed in the next update.

@copper Thank you for that!

Assuming you are using the Direction Indicator (-not the HSI)

Test scenario once you are airborne @ cruise altitude:
1- Press 'D' key, so the DI indicates exactly the heading of the whiskey compass
2- Adjust the DI heading bug in front direction
2- Turn On the autopilot in HDG mode
3- Observe: the autopilot follows exactly the heading set with the DI bug which is correct
4-Turn the left knob on the DI (Gyro calibration drift) so the DI bug turns about 90° left or right
5- Observe: the aircraft heading maintained by the autopilot does not change at all!

I'm not sure that someone can convince me that this is a normal behaviour ;)

@Tigerclaw said in Arrow III e Saitek X52 Pro:

Not not curious at all, the Saitek drivers aren’t really designed for today’s simulation.
If you’ve got it working by using Windows drivers, that’s all good then yes?

... let's say that it works even if the rudder jerks .. for example on taxis you can't turn with progression but suddenly and this ruins the simulation ... also with the Win 10 Drivers the Properties Window doesn't work 'of the Saitek ... this is curious?

@vcapra1 No i don t i use the Honeycomb yoke and it works will all others:)))

@Delta558 said in Taking off:

If the sim reads from the control surface (as we are regularly told), then when that stops moving there should be no further effect.

If the sim is using the actual control surface for the flight model, which is implied by the previous Asobo videos I have seen on the "modern" flight model behavior, then yes, it will not have any further effect when it reaches maximum deflection... but if it only takes half of the joystick or pedal movement to reach that point, then the joystick is twice as sensitive as it should be!

But, if it works like X-Plane, where the visual model animation and the actual flight model are completely separated, and only the visual deflection for the rudder is doubled, not the flight model rudder deflection, then it would not affect the actual joystick sensitivity... I don't really know which way this sim actually determines the flight model, but the visual animation is clearly wrong...

@sluflyer06 That is a good question. Anyhow there is a clear error in the official config file now, as the attribute exists twice with different values:

[FLIGHT_TUNING] engine_wash_on_roll =1 engine_wash_on_roll =0

As a software specialist, my assumption is that with this setting the result is that the parameter's actual value will be 0. Which is probably not the intention of JF.

@Shifor Not all HSIs are slaved, so it most definitely could drift.

Do you see different behaviour with default MSFS aircraft?

This one's really good as well:
https://www.youtube.com/watch?v=O68u05JZXL8