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.

just type in minutes. For a 1 hour turnaround, you type in 60.

The 747 is the only jumbo. Any airplane stops being ugly at the very moment you fly it, or when you come close to it either by someone letting you in the cockpit for enough time or when you have some sort of professional relationship with it (cabin crew, maintenance, flight student, MCC training, TRT). You can fall in love even with the 757 if any of those things happen to you. I grew up spending hours at my local airport watching the 737-200 after school. Hours and hours. It's my favourite airplane to date. Then I worked as cabin crew in 777s in Emirates. PMDG777 has brought back good memories (and some tears even). It's all about how one experiences a particular airplane

I have As2012 and it's not really THAT different. Potato potahto.

Seee how it shakes a little when it penetrates? That what I want!!!! I doubt it will be like that visually. Volumetric clouds would require a 200 Yottaherz processor to work in FSX's world.

Back when ACES was still open, some head developer had a development blog (P. Taylor was he?). He would tell the comunity all about the progress they were making with SP1 and DX10 preview and all of that. Those days, Flight Simulatior was still an alive project that continued getting better. On one of his posts, he explained how little FSX cares about the graphics card you use. Probably, between your card and a GTX Titan, there's only a 4 or 5 FPS difference on an identical system. I still use my GTX580. 2 weeks ago I upgraded my CPU from an i7 950 (first generation i7) to a 4770K, which I overclocked to 4.2 but then decided to keep it at stock for now. Just that CPU upgrade gave me some 25 extra FPS (along with maxed out ram and a speedy Samsung 840Pro SSD). If FSX was a properly programmed piece of software, with today's modern use of DX and CPU instructions, then it would make all the sense in the world to consider a GPU as a definitive factor in the software's performance. Since FSX relies purely on CPU brute force I'd say, look into optimizing your current build and invest in anything but a new GPU (unless you also use other applications with proper code). I would give it another year and keep my money in my pocket at least until Broadwell comes out.

Suspended water or ice also cause radar echoes. Water doesn't need to precipitate for radars to depict it. Entering a cloud and seeing the cockpit shake like in real life would be a dream come true. Seeing it on the radar, even more so. I wish ezca would finally evolve into a less cluttered application that just replicates real life head movement with no more than 2 or 3 adjustment sliders.

Oh my god, there are so many ways to overcome your problem without asking THE DEVELOPER to put a hidden click spot. Options: -Assign the CDU a different panel slot (So it's not shift-2 since you've already assigned it) -Use FSUIPC to map a button to that new shortcut. -Drag the CDU to a second display (if you don't have one, buy the cheapest second monitor you can find). -Get AirDisplay and use an ipad or any tablet as a super realistic touch CDU. -Get TrackIR so you can actually look at the CDU by turning your head. . . . Wait for some more years for when the Occulus Rift becomes a thing.

http://www.dubaiairport.com/en/Pages/home.aspx

Just like in the 747, you have to use Heading Select to fly VOR radials. You have to enter the VOR and radial in the RTE page in the CDU and the RAW data will be displayed along with a representation of your radial on the ND. You'll also have to anticipate the turn based on your GS and the degrees you are off the desired track.

What do you mean? I myself have a crashy FSX and am using FSUIPC's built in autosave. Whenever FSX crashes, I'll just reopen it and load the last autosave that FSUIPC generated. After loading the autosaved flight, the 777 is configured exactly as it should. This even works in flight. The only downside of using the autosave is that whenever FSUIPC does the saving, at the interval you set it to, there's a small 4 second freeze which is a little annoying when it happens during take off or landing.