@martyn Oh one minor possible QOL thing perhaps, could the announcements in the EFB be ordered by phase of flight, like arm, take off, release, landing, disarm? Very minor quibble of mine.
@martyn Heh... zee button, it does nothink.
If/when you guys add the GTN750 (it is that which the fire fighters used right?) I wonder, if like the paid version of the 750 mod, it would work with it since I think that has some sort of VNAV calculations. Which I presume the real version of the 750 has? Unless its only new iteration that weren't around for the 146.
We're constrained somewhat by the MSFS FDE but we are closely simulating TGTs that are based on real-world data and feedback from our 146 pilots, and the TGTs will be higher in v0.1.3.
Thank you @bburkley .
I was aware of the navigation selector button and its functions.
I just was not able to turn the NAV2 radio ON, but @N293WK set me straight and pointed me in the right direction in the post above.
Thanks again.
Roberto
@bearviation As I told @MartijnCoenen, everything appears to be working but I have only been flying the 146 since I removed the folder from my Community. At least I'm not the only person whom these Navigraph files have been causing issues with. I had to triple check it beforeI confirmed this folder was causing the Naiads issue. Maybe it's to do with what order you install software and something gets overwritten or corrupted? Who knows, if I run into problems with Navigraph functionality with other aircraft I will go down your route with deletion and reinstallation.
@b3lt3r How it's done IRL: ATC tells you where to go.
In lieu of ATC, I'd choose a published departure and arrival if available (non-RNAV), and just connect them with VORs and high-altitude airways. You don't have to follow airways, though they do help guarantee VOR reception.
Same with the DME and GND SPD readouts. Using a fixed-width font would eliminate the constant jumping.
LOVE this plane! Having so much fun with it. A LOT of work!
@martyn Yes, I can see the warning, but only if I am looking at the warning panel. The alarm is the same volume as other warnings and the co-pilot only talks to me some of the time. I just landed at EDDK and the co-pilot made no calls, except to announce the capture of the Glide Slope.
This isn't a deal-breaker and as I am gaining experience on the aircraft it is becoming less of a problem. But I would still like my co-pilot to talk to me when he should.
@jmarkows I am terribly embarrassed to say that I soon realized that I had totally forgotten the operation of this great airplane.
Just completed a full flight.
It was done after watching a few more videos to remember how "really" this airplane flies.
You "tell" it what to do. It doesn't "understand" what you "want" it to do.
You tell it "I want you to keep this IAS or V/S", and it does.
You can't tell it "I want you to get to that IAS or V/S". It's electronics were not that sophisticated.
Other than a "so-so" landing, it was fun to finally accomplish a full flight.
The only issue in VR (which I fly exclusively if I can) as in the past, is the inability to reach some instruments/buttons/dials (ie altimeters barometer dials ) with the mouse.
Controllers don't work well at all.
It is not JustFlight's fault. We can only hope that Asobo will soon address VR in more detail.
Thanks again.
Roberto
