Leaderboard

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

Don't know honestly, last thing i did today, i reinstalled the aircraft again, tried it, didn't work. Grabbed the Gizmo from the trash, replaced the one that was installed and now i am flying again ......... Whatever bugged there (user included) i'd call it solved for me now. Thank you for your patience and help !!!! Now its SPACEX DM-2 time. (which possibly gets scrubbed again for WX ) Oliver

I was able to recover the old plugin Gizmo64.plugin-20.05.29.0708-beta from the trash-can and installed that one. Back in business for now. Back in the air soon. FYI @Litjan Thanks for the idea: @safeflight_ Just wondering why the stable gizmo didn't fix it/work ??!! Oliver

Yes, I was going to say the same. Did you try the most recent betterpushback? https://github.com/skiselkov/BetterPushbackC/releases

That is great news. I have been flying sims for years, but I am new to both the IXEG and this past week, new to VR. I have to say that I can't believe I waited this long to get into VR flying and I am excited to see that you're working hard to bring this unique experience to the update. I want to echo the other posts and thank you for all the hard work you put into this simulations. It can often be thankless work, so just know that it's appreciated.

Thanks. Its my favourite plane. Absolutelty excellent. Hope others are to follow.

Problem solved. I saw on another post a similar problem when using Gizmo v2. So I rolled back to the stable version and got the menus back. Thanks for your help.

Hi and thanks for the nice words and the feedback. I totally agree about the vortices - we are using "default Laminar Research" particle effects for now - I really want to update those, though - and make better vortices (at the right spot and only the right conditions) and also APU heat blur, fire extinguisher bottle effects, better touchdown smoke, etc. I also noticed the flight-altitude problem with the mousewheel, I will enter a ticket for Tom to look at it. I am not sure about the Vspeeds - we may have coded this so that the take-off v-speeds get erazed from the EADI speed tape if you enter the approach speeds. I really don´t remember how the FMS handled this on the real 737-300, I never did that ;-) It is also quite possible that the behaviour was changed, I am sure the Zibo is using a much more modern software standard for their FMS. Cheers, Jan

Turn off any AI you have running. We're trying to figure out why this is happening with co-operation from Laminar.

I will have one of my pretty young lady copilots do the voiceover for you guys...

Mmerelles is helping us put this into the plane for everyone. Right now we are clarifying with Laminar Research why the cockpit.obj file we exported from Blender chokes up the VRconfig.txt - there is one extra word in there ("none") that we need to support our new way to define our manipulators, but Laminar´s VR code does not handle it well (as you all found out). So while it is absolutely fine to enjoy what mmerelles is coming up with right now, we will try to solidify this with his help and then include it for everyone by default. Cheers, Jan

When you're on the map on the nav display, use the inner cursor on the FMS knob to move through the different sub-pages.