Lost functionality in the Warrior with SU5
-
Hi all,
I just tried my first flight after the MSFS update and a couple of oddities. The parking brake no longer toggles for me with my assigned switch, it just engages the brake, I have to turn it off with the mouse. And, though I can't swear to it, it appears the Altimeter Set button now just sets the altimeter to the default 29.98 rather than the actual current altimeter. Is anyone else seeing this behavior or am I just special?
Thanks
-
At least for the altimeter thing, try manually setting the weather to something that is not 29.98 and see if it goes to that or to 29.98.
I have the parking brake issue too, even after switching to Legacy cockpit interactions, but I haven't seen the issue with any other cockpit controls.
-
Actually, it appears the window doesn't open anymore either, clicking on it or the lock tab doesn't do anything
-
Oh, the other thing I've found so far is that the cabin heat and air sliders are inoperative now. Again, none of this is JF's fault, just pointing out things that probably need to be addressed if possible in an update. Still love flying the Warrior.
-
No copilot either
-
The anti collision light and landing light are not working for me. Neither is the VOR/DME/ADF working
-
The heat/air, window and parking brake controls will be fixed in the next update.
We can't reproduce any issues with the altimeters, co-pilot, light controls or VOR/DME/ADF. Please contact the support team so those can be investigated futher.
-
Using the Logitech Multi-Panel, I noticed the HDG button on the Logitech hardware doesn't illuminate the HDG light on the autopilot in the cockpit, however, it is still functioning correctly.
-
Another significant issue I noticed when trying to fly yesterday is the lack of functionality for the autopilot. It was stuck on heading mode, I could only change to NAV by holding down the mouse button on NAV. As soon as I released the button, it reverted to HDG. And my altimeter operated normally yesterday, so I don't think it is an issue.
-
After another flight today, the autopilot worked just fine, not sure if the SU5 hotfix repaired it, or it was a one-time glitch, but it all worked well today.
There does seem to be a discrepancy with the altimeters, I had several occasions when ATC said I was above or below my assigned altitude, but I get the feeling that may be an MSFS thing, not an Arrow thing.
-
@Martyn I continued to try to get the copilot back, which disappeared with the introduction of SU5. I can make a copilot appear and disappear using the control pad, but the copilot is only visible in the external view. I also notice that it is not the avatar I selected within MSFS, but I remember this might have been always the case. By swithching the copilot on/off, I do see the impact on the aircraft trim (also lateral), which of course is great. However, the copilot does not appear inside the cockpit anymore (before SU5 this was the avatar that I selected). The same problem occurs in the Arrow III en Turbo Arrow III/IV as well.
-
@vcapra1 I found that the hitbox for the window latch is much higher than before and it worked for me. Try clicking with your mouse at the very top of the hitbox.
-
@katchaplin said in Lost functionality in the Warrior with SU5:
There does seem to be a discrepancy with the altimeters, I had several occasions when ATC said I was above or below my assigned altitude, but I get the feeling that may be an MSFS thing, not an Arrow thing.
This is an MSFS bug and affects all aircraft. With the latest hotfix they fixed the altimeter output on SimConnect to at least fix it for VATSIM etc., but the ingame ATC still sees a different altitude and complains.
That's a known issue and will be fixed in a later regular update as far as I understood. -
@copper hi, thanks, and yes, I saw that in the update schedule. I have Pilot2ATC, have been thinking about trying it, but I've heard FSUIPC has some... stability issues with MSFS, so haven't taken the plunge yet.
-
@pilot_paul Definitely no lights working outside and the GPS100 numberpad does not work.
-
The GPS100 has never had input functionality, something to do with MSFS's programming. It's pretty much display only. For the external lights, they should be tied to the Anti Collision Light switch, if you have the current Warrior. At one point, they were oddly controlled by the cockpit radio light, but that's been fixed with 0.2.0.
