Leaderboard

Another weekly update. The rather rigorous testing of route editing over the last week had brough forth a few more issues, not unexpected during such a substantial rewrite though... but without a doubt, there are substantially less issues with route editing. Jan's last round of route testing, he was unable to get a gizmo crash when changing procedures aggressively and could swap any procedure at any time. Our goal here is for folks to not be scared of to push any buttons on the procedures page during descent / approach for fear of a gizmo crash, and be confident they'll get the route they expect. So, for example, you can select a STAR and transition.....and fly that without knowing your arrival... and then select your arrival later and it'll just get "added" to your routing. I know I say this every time, we have not begun the VNAV rewrite though....so we can't say how the VNAV predictions will turn out just yet. We have a very small list of issues to wrap up, which I will be trying to tend to this weekend so we can get this patch out asap. After, I will examine the waypoint restrictions and then finally analyze the VNAV and set upon improving that feature. -tkyler

Cool, yes unfortunately it's one of those sporadic events so it might take a few tries to hear it.

I was pulling my hair on this one as well, couldn't figure out why ILS G/S wasn't captured or why VOR/DME wasn't working. Turns out I had the same problem: my Saitek switchpanel configuration was acting up. After I disconnected the panels and disabled the xsaitekpanels plugin, it works like a charm. So, thanks for reporting back here @teban13 :-)

I wish the motion under friction was about 1/10th what it is now. It's a great system they added but the throttle still moves too quickly.

It's ironic that a few of you are wanting it back. I was getting quite a few DM's on Facebook, and I think a few here, also, asking for it to be lessened or removed. That it was too hard to land and take off. I'll discuss with Saso and ask him if it can be made as an option or just to bring it back as before.

Most assuredly NOT a P.O.S.! Maybe someone just needs to go back to playing xbox.

In a market flooded with simplistic and half baked products the complexity and popularity and "this is all i fly now" opinions of the TBM users says otherwise.

Ok..another week gone by. 60 more hours of rewrite on the FMS route editing and guess what, we're still easily 95% of the way done Seriously, we are into the more hardcore route editing features now, the really fringe type of data entry patterns...changing your mind "mid transition" selection for example, or selecting a STAR, then approach, going to other pages, then coming back to select another STAR, then TRANS, then swap to a runway with an extension, then shortcut points, etc. Testing earlier in the week had us redesign some other algorithms and we figured we should just power through the work now so it gets done right and we can move on to VNAV without worrying about fragile route editing. With the algorithm structure in place, what remains is simply comprehensive testing/debugging of those algorithms via diverse route entry patterns until the route builds as expected in all cases, for both Navigraph and Aersoft datasets. As soon as that happens, we'll get the patch out. We're working on it daily. -tkyler

Hallo @novato X11 Open then IXEG 737 Classic Folder Example = D:\XPlane11\X-Plane 11\Aircraft\X-Aviation\IXEG 737 Classic search the .acf File B733.acf - Please make a copy of this File outside the X-Plane11 Mainfolder. I use Notepad++ and open then B733.acf File Search the Line: P _gear/0/_gear_type 2 Change the Value from 2 to 3 Save the .acf File and start XPlane11 Load the Plane and BetterPushback works fine. Sorry for my crap english. Bye Bye Ernst