Leaderboard

this is FYI only, in case you're curious.....without a doubt, the speed is too great (bigger turn radius, earlier turn point, later rollout point) to finish the turn before passing KK371, but probably just barely.....and I suspect that our bypass code isn't being run since the next waypoint is a runway, which is a bit of a special case waypoint. I will revisit our bypass code to check it out and under what conditions it runs, but it does need to run and would fix this issue. -tkyler

Since the 1.3 update was released, we've been working to fix all the squawks that have been reported since the release. I want to extend my thanks to all who report items. While folks may wonder why we do or do not catch things, I can assure you the list is quite long of things we have to check constantly and I'm actually somewhat proud of the effort. Supporting VR and also integrating the mousewheel involved a little over 300 manipulators, each of which having anywhere between 3-9 parameters to enter/ check....easily over 2500 "fields" to look at when making these conversions, and that's just checking the manipulator interaction, not even checking their usability in VR, with mouse, with hardware, prefs on/off while also catering to cockpit builder needs, etc. The good news is once configured properly, things stabilize, so each successive update gets more reliable than the last, but being this is our first relatively big "conversion update" with features sprinkled in, the only way we'll really catch it all is with the community inputs. So....we are getting close to releasing our 1.31 patch, which definitely includes the reversed scrollwheel fix. We have several other fixes in addition and much better VR support also though some straggling VR features remain. After this patch, we will begin working on the FMS also with other items, whereas up till now, it was about just getting all our new workflow and converted stuff back to normal with XP 11.50 and Vulkan/Metal. I've seen a few posts facebook posts about the IXEG overshooting flybys. We do not have wind factors in our FMS code currently, Turn points are calculated with no wind so any form of tailwind on turns may cause the plane to go wide. Bankangle for lnav calcs are taken at 25º of bank, leaving a little margin if you have the bank limit set to 30º. We do track the crosstrack deviation from the route though, so if there's roll margin, the plane should track still with some tail/crosswind; however, late entries in higher winds will probably run wide. Given the outstanding VNAV work to be done, we did not implement the wind factorization as of yet. As we begin our FMS work, we'll focus on the holds and VNAV somewhat simultaneously. Improved algorithms there will naturally be reflected in the progress page output. Once we get some traction with our VNAV / holds, we'll start factoring in the wind corrrection to the route calculations, which will hopefully snap everything into place. -TomK

Hi everyone, starting today I will aim to make a video every week for your viewing pleasure...talking about IXEG development, flying our aircraft, showing you procedures, techniques and various other stuff. Stay tuned to this channel!

You better hurry then. NDBs are fun

Hi Marcin, that is not the way it should be - but probably coded that way back then. The regular "pointers" should always display in all modes. When the VOR/ADF pushbutton is on, these pointers will be replaced by the segmented lines in MAP and CTR MAP modes. When Nils coded this, he probably understood that "when button is pressed, only show these lines in MAP and CTR MAP modes"... Thanks for pointing this out - I will put it on the list. Lets see what happens first - all NDBs getting abolished or us fixing it . Cheers, Jan

Well yes it seems that older Gizmo versions crash my system in combination with SMP, better pushback and IXEG 737. Glad I saved a later Gizmo verion (20.05.22.0320) that came with latest IXEG 737 setup package and with that version of Gizmo the CTDs are gone.

Hey @HoroX thanks for the answer so fast. Yes in this Moment i do that and BetterPushback works again. Thanks and sorry for my Post above. Bye

I would like to add... the next update of the Saab (before v2.0) will work in Vulkan/Metal. And that update will be free to all current customers.

@tkyler Hi and thank you guys for the v1.3 release. I'm here with a small (I hope) request: I made a librain integration for the previous version and I'm adapting it to v1.3. Everything is working except for the avitab z-depth obj, as you can see from the attached images. Would it be possible to have a solid surface for the tablet where the avitab window is rendered, in order to mask correctly the librain surfaces? Thank you in any case.

That’s fine with me. Thanks for taking your time. I will contact you after the purchase.

Cooper! This solved the problem!, Now I got 42 frames inside and 34 frames outside!. The plane flies great like the real one does! congrats! Chemanuel

Hi Robert, you will notice that the "linearity" setting is gone from the control setup - you can make a "response curve" now. This is what mine looks like: Cheers, Jan