iniBuilds has updated the marketing page to specify that the systems are models only, and removed the career mode support blurb. I commend them for doing the right thing and updating that description. I look forward to seeing what updates bring down the road.
You can switch to the 650 (PMS or TDS) from the tablet.
If you’re referring to what I’m thinking, you need to go to Default Nav > CDI. That’ll change it to GPS instead of VLOC (Nav 1)
Thanks! I’ll check that next time I fire it up. I’m used to running the full-size 750.
You could toggle the EFB visibility with external software like spadnext or axis and ohs by using the script
(L:EFB_SHOWHIDE_ON,·bool)·!·(>L:EFB_SHOWHIDE_ON,·bool)
That’s fine for people that use those, but it still leaves the rest of us.
Yeah I know, I am baffled too, why there is no clickspot. I just wanted to provide a solution to those, who can use scripts.
Are you talking about hiding the EFB from the yoke?
In that case I can tell you that there is a click spot. The small red button on the right side of the yoke.
Thanks, I will check that out asap.
They definetely fixed some Pre-release Issues (to low Idle NG RPM, left cowl flaps handle triggering also right cowl flaps, to name some).
But especially with the engine simulation something still feels odd. I tested OEI too, and it indeed seems to make no difference at all. Also the torque does not rise in the same proportion as you would decrease the rpm with a constant power lever setting. Power is an function of RPM times Torque times coeffecients. So if you decrease Prop RPM by 10%, torque should rise by around the reciprocal amount (~11%).
And Beta Range is still not modelled correctly.
It is just sad to see such great potential in this addon and seeing inibuilds again coming just a little short of an great addon with this ga aircraft.
Cheers
Minimum throttle doesn’t let the reverse go back far enough. I noticed that pulling the throttles back as far as they’d go made almost no difference in any of the engine instruments. So I changed the minimum throttle in the engines.cfg from -0.15 to -0.25 and now I have both reverse sound and reverse function. I don’t know if the numbers on the gauges are right yet, but it works.
Yeah I noticed the weak reverse too. But I meant, that the correct way of the beta range, with its gradual pitch change, is not modelled. Like in any other turboprop where it is just modelled wrong, it goes already to full reverse pitch, when you pull the lever only a little into beta range.
I bought this today after reading the discussions and reviewing the info on the iniBuilds site, and did an initial flight.
Well, it started well enough, but this autopilot system completely mystifies me. I have over 3,500 hours in MSFS 2020/2024, with all sorts of aircraft (I’ve recently gotten a kick out of the BN2 Islander), and my test flight was a struggle in the last half.
Even though the Nav button was pushed (turned green), and GPS was selected, it only kinda sorta seemed to follow the FP path. Once it got to a waypoint, it generally did not turn to head to the next one.
And altitude…I have no idea how to set the desired altitude, but even if I clicked the Alt mode button (thinking maybe it was just altitude-hold, at least), it still didn’t seem to react predictably - it seemed to chase some arbitrary altitude like 2500, where it would stabilize…until 15 minutes later when it decided to get a closer view of the treetops.
I know on the back of the console, behind the levers, there is an A/P of sorts, but it isn’t intuitive and the iniBuilds “manual” on their site gives -0- instructions on how to use it, or how it integrates into anything else.
A regretted purchase at the moment.
Hi, wondering if this helps, it was posted above 2 days ago by @CptnDoppie …
Is this switch (13) on?
Thank you, but I did check it specifically, having read the thread previously.
It certainly is possible that I’m doing something wrong, but it sometimes seems it sort starts to work, then becomes unreliable, which destroys its utility.
I’ve had no issues with autopilots on the DC-3 or Islander or ATR or other back fitted arrangements; this seems weird and clunky in arrangement, and maybe in operation, but given the lack of documentation in how to use it, I might as well uninstall.
Agree things are weird and clunky where the A/P is concerned. Took an hour flight just now to have another look based on your post. Here are some observations…
- The A/P can intercept and track a VOR radial, but it “swims” much as a student pilot might.
- The GNS430 does not annunciate NAV when tracking a VOR, it stays stuck on GPS
- The GNS430 responds to FMS2 commands from my Octavi IFR-1, so its not likely primary
- I do not know if this A/P or any A/P will track the secondary GPS without a switch to do so
- Like others, I cannot find a GPS/NAV switch or NAV 1/NAV2 switch to drive the A/P
- Altitude hold works, BUT, if one used the pitch wheel to dlimb to cruise, neutralize that first!
After 3 flights and nearly 2 hours flying time, I think I can manage VFR in VMC, but IFR is a no go.
P.S. While I am not pursuing a career in 24, I do wonder what developers had to do to prep DLC aircraft for use in a career, if anything, and the effects on these systems for use in free flight.
You don’t… Once the autopilot is on, you dial in a vertical speed on the pedestal, then when you reach your target altitude, press the Alt button to capture and hold that flight level.
@RazaB took another one hour flight and confirming the above. The A/P leveled off when I pressed ALT and held that altitude without me neutralizing the pitch wheel. That said, was only a 500 fpm climb, so if I were climbing 1,000 fpm or more, I might want to reduce the rate close to altitude, just as a matter of smooth flying. Maybe don’t give up on your purchase yet?