SimFx

Just to let everyone know: All is fine in 737 land again. In the end it was indeed a problem with controls setup. For whatever reason my Honeycomb Bravo sent wrong signals when flaps were being set higher than 15, although it was not obvious, since neither the flaps indicator nor the visual aircraft model showed anything unusual. I reinstalled the 737, then deleted and reconfigured the Bravo controls one by one, initially suspecting speed brake, then trim signal problems. I the end the flap lever was the culprit, and after deleting and reconfiguring its binding all seems to work again. Even the numerous CTD's have not re-appeared for the last handful of flights. Thanks a lot for all your helpful and highly instructive input!

I knew that that had to be coming ;) - you put it into nice words at least :) But for one: I don't feel like flying each and every 737 approach manually. Just like in real life, the automation is a part of the experience, isn't it? Also, with all the profound and extremely professional and valuable input in this thread.. it is hard to believe that every single of the many thousand 737 users out there has this deep an understanding of the systems (AoA, pitch, CG intricacies etc.). Many, if not most users won't probably set up their flights exactly and in every detail as per the book (or per dispatch, for that matter :) ). And still my guess is that most sim flights can be conducted in a somewhat decent way up to a fully automated ILS landing if so desired. But maybe I am mistaken, and this kind of simulated complex aircraft requires way more than just basic knowledge and has become less accessible to the very interested, long-time, but still casual, amateurish and time-restricted user. That said, I have now flown the same flight, with perfectly correct setup!! :), 6 times. For some reason I CTD'ed on five of them, generally when pushing a knob on the ACP (HDG SEL, LVL CHG..). One flight I completed, but again when I set flaps to 30 while flying at 150, the alpha floor would intervene and command speed up. Again, AoA was way too high. I switched off AP and AT and landed the aircraft, but some 20 knots over ref speed at touch down. I then flew the same flight with the Fenix, and it went beautifully. So my guess is that the problem, or at least some part of the problem, might in the end still be related to my Pmdg setup. I will try to un- and reinstall the 737 and see if that helps, hopefully not losing all my Honeycomb controls config.

I have watched the video (was not aware of it before) and it is now fully understood that it is necessary to "set payload" and "set fuel" after the Simbrief plan is imported. It did not seem obvious right away, at least not to my elderly mind 🙂 I have tried three flights so far, now all with the correct values set up, but frustratingly ended up CTD'ing on each occasion just before entering or having just entered the approach phase, so I still can't report how goes. Stearmandriver pointed to the fact that the AoA is way out of the green band, which it obviously is. Solution would be to put it where it belongs 🙂 but just how could I interfere in the AoA without going out of automated flight?

Thanks to all of you for that lot of precious information! Especially the body angle/pitch concept being highly interesting. Indeed, I seem to have had a misunderstanding concerning the Pmdg EFT. It imports the correct fuel and payload/pax/gw values from Simbrief and shows them on the import screen of the FMC. However when requesting the automatic PERF INIT, it uses the values set in FS, which in my case where all at max. Hence a huge weight/fuel/payload/pax difference. So even with the automatic EFT import, you need to set the fuel/payload stuff in FS manually. Done that, then I tentatively flew a short hop with no payload or pax, a gross weight of just 42 and 3.5 tons of fuel, 2 tons remaining on landing. Indeed, the landing went way better and left me an operational speed window. But still: My ref speed for F30 being 118, I was slowing down to 130, flaps 30. It went fine for a few seconds, then the lower amber line flickered upward, the A appeared in the speed setting window, the aural warning was triggered and I had to temporarily speed up to above 150 to make the A disappear and silence the warning. So problem still not entirely solved, but definitely getting closer 🙂

Right you are. Amateurs flying complex airliners for an hour or two to relax after their office work.. desaster must be lurking right around the corner ;)

Hi MDFlier and thanks for your input! Indeed, following your explanations the speed values and management seem to be slightly below optimal 🙂 Still, wouldn't there always be a speed window (be it small) in between the upper/lower red and amber tapes that would allow the aircraft to fly safely in a flaps 25 config? In the Approach ref page I did not fill in the gross weight; it was set by default I think. I just set landing flaps to 30 with a resulting ref speed of 133. I agree that dispatch seems not to have had its best day (somewhere the numbers might get messed up inbetween Simbrief and the PMDG FMC), but nor did the PIC who signed those papers before take-off. As per your suggestion I'll setup the same flight with about half the fuel, and will also have all the payload taken out 🙂 Will report back how it goes!

Hi Farlis, in fact I have very little add-ons running: We love vfr and a local scenery, and FSLTL traffic injector. But your observation is interesting: If it is somehow related to my system, the problem might also show up on the Fenix, so I'll try the same flight in the A320 one of these days. As to the amount of fuel.. well I did simply let the Pmdg FMC import it from what Simbrief calculated. But now I might have stumbled on a little bug in the Pmdg Simbrief importer routine: It seems to have loaded not what Simbrief gave as required block fuel, but rather the maximum fuel value. Might be interesting to check on this some more. I'll report back if I have any findings in either direction. Thanks!

Please have a look at the image below. Flaps 25, speed set to 150.. the aircraft logic does not seem to accept any valid speed. On the PFD, the amber minimum manoeuver speed tape and the max manoeuver tape touch each other (one continuous amber line between the red-dotted limit speed ones); no proper speed range left in between them.. On every occasion the aircraft then issues an aural "speed off" warning and automatically starts to accelerate. Happens on every single flight, and busts every landing, unless I land at flaps 15 or below. The speed selector windows shows either an "A" or a "B", so obviously ANY speed seems off. What could I be doing wrong?

You should not be overly worried. I run the G2 on a 2070 Super and with most settings to high, TAA and LOD to 100 I achieve between 20 and 25 fps in the Kodiak. In the 152 or by reducing some settings I can get over 30, but I prefer the visual quality and find around 22 fps very flyable and enjoyable. Rest assured, VR is a league of its own and an absolutely amazing experience. I for one could never go back to 2D.

Amazing work, both the pylons/powerlines and the lifts mod! Thank you very much for enhancing our flying experience even more. If you want/need pics of Luxembourg/Benelux type of pylons, feel free to ask anytime.

I suggest you update to the latest OpenXR runtime 109.2111.18007.0 It seems to have solved the problem for me.

I can confirm the exact same problem, but it exists since SU6 for me and I hoped that SU7 might eventually solve it. But no. I reported to Zendesk a couple of days ago, waiting for an answer.

One more here. Same problem. I am flying in VR which was pretty decent before on my 2070S, but now with STOP -GO -STOP -GO at 1 sec intervals it is utterly unuseable. Turning off Multiplyer might have solved or lightened the problem somewhat.. I'm still experimenting with settings. Voted for the issue over at FS forum.

Have you ‚bought‘ the World Update in Marketplace?

Several more downloads waiting for you. Microsoft Store with 1 Gb, main update in the sim 23 Gb, Content Manager (updates a couple challenges plus some US and Japanese airports 0,5 Gb, Marketplace for the World Update 5 Gb. Seems quite a cumbersome update process for any newcomers.

Xbox Insider Hub not available :(

Right. I am not on my PC either, but from memory I definitely have HDG, NAV, APP, ALT, and VS buttons working just fine. On top of that, speed, vertical speed and heading can be dialled in, altitude does not unfortunately. Not being able to dial in an Altitude is what annoyes me most, especially in VR fiddling with the cockpit Alt dial is a real pita.

If you like to, defining your own is a real quick process just by pressing CTRL-ALT 1, CTRL-ALT-2 etc. In that case no need to wait for an eventual update..

Indeed ALT does not work. But I have some mode buttons on my Bravo actually working, and they also have the corresponding cockpit AP switches working and lighting up, so it can be done.

Quote from Justflight‘s Craig on their forum: Whilst this is not a support forum, please submit all bugs to the below link https://support.justflight.com/support/home However we are currently aware of this issue and are looking into it.

They are aware of the problem and hopefully find a way to fix it. Meanwhile as a workaround try to close your right eye, seen with the left eye alone the cursor will be correctly placed. Quite uncomfortable, but at least does the job temporarily :)

Ok, never had that before, so a new experience for me 🙂

Guess they are preparing the update as we speak. When I try to load the sim it now comes up with a warning ("Your package is out of date" ..) This is followed by the Press any key message (which I thought had gone for good), followed by an error message ("Access to the content servers is currently unavailable"..). Finally a new startup screen shows up (TBM over clouds and snow-covered mountains) leading to an on/off flickering unuseable main menu. Only option is to quit :) Hopefully this is temporary and short, so let's give them some air to breathe while getting the update implemented.

VR in Aerofly is quite a step above FS in terms of playability. The cockpits are excellent, the instruments much more readable and the frames a whole lot higher. A great introduction to what VR can do in flight simulation! But of course you miss out on the fabulous FS scenery, on worldwide coverage, on the great looking live weather, on air traffic and much more. As much as I enjoy Aerofly, I find it hard to return to it after having fiddled around with FS long enough to obtain acceptable performance on my medium rig.

How could I forget about the trim wheel! It has been the feature that first and foremost attracted me to this hardware. Not that it is much needed in airliners flying, but I'm flying a lot of GA where correct trimming is essential. Well, with the Bravo it has gone from pita to pleasure 🙂