Well, for what it’s worth, it seems to have been a fluke or had some trigger condition I didn’t notice. I just completed another, longer, flight where I tested the UNS-1 DTO function three times, and all three times it went direct from my position to the selected waypoint. So I’m not sure what that other instance was about.
2 Likes
Aaand two more fun flights, BUT on these flights, it didn’t capture a single altitude. I have a theory but I don’t have time to test it until tomorrow.
Those who have had problems with altitude capture, are you preselecting with the altitude knob via mouse, or with hardware bindings?
It’s very simple. I bought the Hartman Expert ATR, I bought the premium FS version so I could fly the Saab. I won’t buy any Hartman or Carenado product when they don’t get their act together or don’t care about these planes. With standard planes I kinda accept the 80/20 rule but not with premium or separately bought items. Vote with your wallet.
2 Likes
For what it’s worth, after dozens of flights in this aircraft, I have not once had an issue with it capturing an altitude. I use the mouse on the alt knob on the panel, I’ve never been able to get it functional in Spad to use my Bravo for this specific setting, everything else works for me on the Bravo AP. Another thing I do religiously is use FLC for climb, starting at 180 initially and then dialing it back to 160 after the first few thousand feet. It will climb up to any altitude, up to and including FL250 without issue and captures correctly every time for me. Coming down I have had no issues either, using V/S and a decent rate of 1500ft/min or less.
It’s been a minute since I flew this, I think I may need to dust off my wings and take it out for a few regional flights this weekend. Cheers
You’re hitting on what I’m thinking here… I suspect that if you manage to bind something for altitude selection, it (sometimes, at least) doesn’t capture. I wonder if maybe the altitude displayed on the selector doesn’t actually match the variable set for capture.
I have experienced the altitude not being captured but that was admittedly in SU3. I haven’t noticed it in su4 because I need to have another go in it. Will try and post.
So far my theory bears out. If I use some kind of binding (someone else in this thread or another Saab 340 thread lent me a script for it) to preselect altitude, it doesn’t capture. If I just turn the knob with my mouse, it does capture. I’ll test again on tomorrow’s flight. Right now it’s time to hop into the Duke.
1 Like
Been getting my head around the Saab and having to look for the small wins in the plane after being spoilt by so many top 3rd party developers….
Enjoying flying it…
However…
How does one engage the APP when doing a ILS and can I use raw navigation regarding using VOR or is the PFD and interface buggy regarding switching from gps to nav.
There is a video by 330driver i think his name is with the saab340. It’s the most recent one I think he has done where he uses all the avionics in a landing.
It would be great to have a paint kit for the SAAB 340.
2 Likes
Late to the party - there’s a group of buttons on a panel on the left of the AP, the top right of which looks like a rotator switch for ‘set source’ (or something to that effect). Click it and you will see the source change in the display to LOC and it will follow the NAV radio for lateral and glidescope with Approach selected.
Switching on the Left avionics crashes my GPU, any ideas why?
I’m not sure what’s been done since 2021, but, there are three registers for Baro. The B key sets all three to current outside Barometric pressure. So, above 18K’ you need to set each Baro to 29.92 by hand. The B key will mess this up. At least that’s how it used to work.
Technically, in the past (since FSX and probably earlier), Register 1 was used by the altimeter, Register 2 was used by the autopilot, and register 3 by the transponder by default. Of course, any dev can use each of the registers for whatever they want, so, there may be differences there. Also, Working Title has done a bunch of work since 2021 on the whole avionics system, so, things may have changed since then.
But, as I noted, yes, you need to set baro to 29.92, unless you see a specific button to set it to STD in the avionics.
1 Like
That’s correct. You cannot depend on this forum for reporting bugs to Carenado.
They have their own Zendesk forum on their website for reporting bugs. For their Microsoft planes however, it likely gets muddy, and, while it’s possible they’ll react to bugs for their Microsoft products from their own Zendesk support platform, but, I would also report any bugs to Microsoft’s Zendesk platform. It’s highly likely Carenado only responds to those bugs that Microsoft tells them to fix for their Microsoft products, like the Saab 340. Secondarily, you can also report bugs to the bug forum here, too, but, as you note, eh, 1. they only respond to bugs that multiple people confirm to see, and 2. Even then, I don’t know how well they are tracked and added to the backlog. They do say they tag posts that have gotten into the bug reporting system. I don’t think it means it’s actually in the backlog though.
And, as has been mentioned many times, if you get a report from a Zendesk report that a bug has been “Fixed”, it absolutely hasn’t been fixed. All that “Fixed” means is that the bug has been acted upon. You can’t tell if it’s been marked duplicate, has been accepted as a bug, or has been rejected for a variety of reasons. All it means is somebody read it and did something… who knows what? Nobody has any idea why Zendesk decided on this nomenclature, but, it is what it is.