+1 That would be a great improvement
Maybe @SinewyDolphin74 can take this feedback ![]()
Maybe this is a dumb thing but, how do you people manage the engine considering that mixture leaning is not properly working? I don’t know how to do it. In the standard arrow, I lean using the fuel flow indicator until it matches what the power setting table says, but in the turbo, you lean, the fuel flow goes up, then goes down again… IDK if they are going to fix this or maybe is related to Asobo. But, currently i don’t really know how to manage it.
I use the FF gauge as well, lean it back until it drops again and then ends up at the desired value. Sometimes I end up in the mixture lever at even <20% with this approach.
They now released version 0.2.0 which should contain some changes. Let’s see if this issue is fixed or at least less pronounced.
I lean the engine by very slowly moving the mixture lever back (leaning the mixture) and closely watching the EGT gauge. At some point when moving the mixture lever, the EGT will peak and then quickly reduce. I then move the mixture lever forwards to where the EGT peaks, and then enrich the mixture slightly. The mixture is then said to be “rich of peak.”
When flying an aircraft without an EGT and with a fix propeller I would lean the mixture until the RPM just started to fall, and then enrich the mixture until I was at peak RPM, and then enrich it just a tad more. When doing this “in real life” it would reduce the fuel flow of the PA28-161 I flew by about 2gph. Of course one of the checks once in the circuit (pattern) for landing was to make sure the mixture lever was fully forward.
Looks like the mixture leaning works properly now in 0.2.0 ![]()
However i will need to test it and see if it matches the tables.
Thanks for your reply
You can bind a key for automatic mixture and it will set it for you, up until yesterday it set the mixture at 4 notches lower than the peak on the egt but you say its now fixed with the update so I’ve yet to test the automatic mixture.
According to the POH, FF should be at 12gph with 75% power but I never managed to achieve less than 15gph on peak EGT, maybe this is the culprit.
Another thing, when it’s raining the required power to taxi is much higher than on dry tarmac, is this normal due to some king of drag? It doesn’t seem to affect takeoff distance, just to start moving when stopped.
Anyone had issues with it not following GPS since the update? I just had this on the Arrow IV. Never been an issue before.
GPS coupling worked for me last night with the new update. Flew from KORS to KRNT. Selector switch to Nav, HDG switch activated, CDI set to GPS.
Edit: Used the GTN750
this is an msfs issue with how the ground friction model works, and is not exposed in the sdk
Afternoon all. I have upgraded to v2, and appear to have a minor issue in that the panel lighting switch doesn’t appear to work (right hand side of centre panel). The other light switch works fine (navigation and radio light switch on left hand side of centre panel). I noticed the same on v7 on the Arrow 3. All worked fine prior to latest updates. Anyone else experiencing this issue? Seems to be linked with the new lighting mod built into the updates.
I also saw this problem on one flight. First the instrument lights did not want to turn on. Then after turning them offf and on again, it worked for a few seconds and then started to flicker. In a second flight I had no problems. Strange! Using non-turbo Arrow version 0.7.1 - non-bundled version. Also tried the Turbo Arrow III. Same thing: sometimes works and sometimes flickers. I have not found any pattern yet.
Thank you for your reply. I have since resolved the issue. I installed 7.1 (&2.1) which released this afternoon, these updates appeared to have fixed the issue. At first when this happened I even checked the circuit breaker panel to see if the lights had tripped! Pleased now resolved ![]()
I was also using todays releasens, so I Think the problem is there. In fact, I have not seen it in the previous versions.
Yes, even though seemingly in my case the reinstall helped me out, it is also clear that there was nothing in the release notes that in any way indicated a fix. Your point kind of reinforces that the issues is still there, as we both had similar issues on latest and past versions. So there is clearly something still underlying that is broken, but at least for now it appears to be working. It’s rather difficult to fly at night without panel lights, but it does add to the excitement whilst fearing they might fail any minute!
Yes it looks like the problem is there in both versions. It is rare that I fly at night, so I have probably just not seen it in the previous version. Only reason I tried it out in todays version was your post. I find that it works if I start out in complete darkness, but at dusk it behaves strangely. Have you experienced the flickering too? I hope that others will try it out too.
Likewise, I only occasionally fly at night also. I haven’t noticed the flickering that you described. However, when I get a chance later I will check it out and try and replicate. Happy flying ![]()
Had no trouble with lighting but the 1st flight this morning had to be reloaded after last night ipdate as the lower left panels were unresponsive I couldn’t start the engine.
No faults to report after the 2.1 update thankfully.
I had to restart MSFS for getting update 2.1 to work. Couldn’t get the engine started. After ignition it ran but fuel pressure got ever less until the engine stopped. I suspect the state saving feature might be responsible as probably the state of an earlier version does not apply well to a newer version. But I’m not sure of course.
So I switched off state saving, restarted the sim and voilà, it worked.
Karl