Flexman

An RMI shows you your instantaneous QDM and QDR of the tuned VOR. A localizer does not emit radials that an on board equipment can read comparing phases. Localizers work on a whole different principle (depth modulation), so there's nothing for an RMI to point at.

My seating position when using the rift is the position a real pilot would have while at his station. Yes, you can lean to the side and around to see the key, but the problem is the clicking with leapmotion (you use your actual hand in the air. It's impossible to press the CDU key without arming the speedbrake. I've had no issues with the Rift. I'm not a super long flight kind of guy but I've flown probably 3 hours without taking it off once and it does not get warm anywhere where your face touches the headset. Summer is coming, so we'll see how sweaty my face gets when it's hotter than it is now. No eye strain. At all. You need a good graphics card though as, in order to make all screens readable at normal seating distance, in an airplane like PMDG's, you need to set a very high resolution. I've a 980ti and it works perfectly. Should have waited for the GTX 1080 probably.

I sent a ticket already. Here's a better depiction of the problem.

I will. I'll let you know how it goes.

Guys, trust me, it's not the camera. The lever is just in the wrong "up" position, period. This is what's happening. See the physical stop circled in red? That's where the speed brake take-off warning switch is. That thing is correctly modelled in the NGX. In the real 737, the lever, when pushed fully fwd, stops there. What's happening with the NGX is that the lever continues to pivot into that thing. The lever is correctly modelled but the rigging is not. The lever is traveling FWD more than it should. You can see for yourself. Just place the camera next to the speed brake from the side, push it forward, and you'll see it going as if that chunk wasn't there. Shouldn't be hard to fix. It must be a single value in some text file.

That's what I suspect. It's not that big a deal though. Seriously, you guys can't possibly imagine what it's like to fly these things with Oculus Rift. I almost had second thoughts about continuing my pilot training... and then I took the Rift off. That cockpit is a lonely place! I almost feel like I'm doing something very illegal when taking off in a 737 with no second pilot.

Perspective is almost impossible to match now that I don't use ezca. Still... look at it! count the screws on the sides of the speedbrake guide. Look at how much bigger the stab trim guide is. I know it must be have been very hard for PMDG to model a cockpit that feels real without having measured every length and angle in a grounded 737. The cockpit feels close to the real one, but just on a normal screen, like we've been using for years, but now that I'm "inside" that cockpit with Oculus Rift (you're underestimating when I say "I'm in the cockpit") and given that I've spend enough time in the real airplane to know where the speedbrake lever is when my hand is on the CDU, you should at least consider that I have reasons to post this. I don't know. Maybe there are variants. Maybe that distance is something an operator can decide on. Maybe maintenance can choose to fit a bigger stop for the lever. I don't know. All I'm saying is that I know the cockpit is not 100% precise, because it doesn't need to be. But at least, things like these, which are obviously an issue when you're inside the cockpit in VR, should be considered.

That's not how the rift works. With the Rift, your camera is your head. In order to use the CDU, you have to move your head in ways you don't have to in the real airplane. That's what I'm saying. In the real airplane, if you lean towards the CDU, elbow on your knee, you see the whole keyboard. In the NGX, the lever covers some keys.

Again, if this can't be corrected, it's no big deal.

As determined by where the Speedbrake Lever rests in the real airplane when it's in the down position. It's just PERFECT. The cockpit size feels just perfect. You're in there! Frame rates in the oculus rift are hardly a problem when you have a decent computer. I doubt the requisites of P3D with an Oculus Rift are different than P3D on a normal screen. You have to know that head rotation isn't always camera rotation, as there's a dome larger than your field of view, and when rotating your head in it, you're just rotating rift FOV, but not actual in sim camera FOV. If you go beyond that dome, you notice less than 90fps as p3d camera has to rotate, but when you're in it, it's very smooth. There's zero lag. It actually feels like your head is in the cockpit. That dome is large enough to cover the main panel and overhead. Now, head translation does move the camera, so that's game fps, not rift fps. My computer is not bad, so I haven't had a problem. No nausea at all (as long as I fly responsibly). The gauges and even the small text are perfectly readable. I can even set the minimums on the PFD withoug having to lean in. CDU is perfectly readable. You can import floating windows inside of P3D, so you can use Navigraph charts or even the browser without having to take the Oculus Rift off. The way the mouse cursor is implemented in 3d space is also very natural. It takes a little getting used to, but in a few hours, you'll find yourself running through flows as quickly as you'd do in the real airplane: You just look and click. The bottom line is, P3D and the Rift are made for each other. I would never use the sim with a normal screen ever again (not even for IFR training). VR for flight simulation is a big deal. A BIG BIG DEAL. I cried a little the first time I put that visor on and saw myself actually inside that cold and dark cockpit. I've been using flight simulator since version 5.0

Hello, I know there's a post about this issue appearing after some update. Now that I'm using Oculust Rift and Leap Motion, the problem with the Speed Brake being in the wrong position when stowed, has become an issue. When you use Leapmotion and Oculus Rift, you use your hands and fingers to "touch" every switch and knob in the cockpit. Now that the speed brake lever is so low, it covers some CDU keys and it's impossible to press them without touching the speed brake lever. Is a fix for something like this impossible in this point in time?

That is what EGPWS alert mode 4B does. It alerts you of wrong flap settings when landing gear is extended during approach and certain conditions are met. Just like it's done in real life, you should inhibit it by pushing the FLAP OVRD switch on the GND PROX section in the Landing Gear Panel..

Those are names given to fixes defined by PBD or PBPB points by FSX. They are not the real published names. In fact some of these intersections aren't even fixes contained in the AIRAC. In case the default ATC directs you to one of these points, you should find out how to construct the point and draw it in your CDU though place bearing distance or place bearing place bearing points (or by using the FIX page).

Oh wow. I just found out that PMDG777 had an external model... anyway, back to the cockpit.

Two words: Wheel Chocks. PMDG makes VERY powerful wheel chocks.