bill1970

I am running P3D with an HTC Vive and the experience is very immersive. PMDG aircraft plus high quality addon scenery requires a lot of CPU and GPU horsepower. I am able to get good results in the P3D native VR on my system (i7-7700 CPU, GTX 1080). I tried Flyinside as well, but found that it didn't help performance and caused blurry textures. Other people have found Flyinside to help performance, so give the demo a try. Bill Rowe

Many thanks to the team at PMDG! I've been enjoying VR flying in P3Dv4 but I've been missing my NGX. Just took it for a "ride around the block" KSEA-KBFI and the performance/immersion in VR is stunning. I'm getting a nice fluid experience with graphic settings as good or higher than P3D V3. LM and PMDG is a great combination that is pretty tough to beat Bill Rowe

I just my HTC Vive and I love the view inside the cockpit. I dont see how to get the mouse to show in the VR cockpit in P3D. Do I need Flyinside to get the mouse control or is it native to P3D and I'm missing some setting. Thanks, Bill Rowe

I'm considering trying VR for P3D/NGX, but I wanted to know how you interact with the controls/buttons/switches in the aircraft. I can probably use my yoke and throttles by feel, but I would think it would be very hard to operate the mouse to active all the other switches, etc. Any feedback/insight would be very much appreciated! Thanks, Bill Rowe

I followed the uninstall/reinstall procedure as described above. When finished with the uninstall, there was no 737 folder in the [sim]/PMDG folder. When install was compete the panel state files are all dated from 2011/2012. The Ops Center confirms that I have the right version 1.10.6436. Shouldn't the date on the panel state files be newer? I am installing the FSX (not Steam) version (the only platform I have installed). When I go into the sim with the default panel state (engines running) everything is fine. I then changed to the LONG panel state and set that as my default. Starting from that state, I went through the normal procedures to get the aircraft ready to go. After engine start, I had the FUEL, FLT CTRL, and ANTI-ICE warnings. If the issue is the old panel states, why is the new installer giving me such old panel states? Can PMDG post a ZIP file of the new panel states so I don't have to uninstall/reinstall (for the 5th time)? Bill Rowe

I had the same issue on a flight in LAX last night. I was following the KEACH1 STAR (FENUK) transition. VNAV was operating and commanded IDLE then HOLD at TOD. I pulled my hardware throttles (Goflight TQ6) back to idle and confirmed idle thrust. Descent proceeded normally toward TEVTE and the 23000B altitude constraint. Approaching TEVTE, I noted that VNAV had not changed the target speed to hit the 280 kt constraint, so I hit speed intervene and dialed in 280 on the MCP. I passed the waypoint a little fast, but nothing major. Next active waypoint was VTU with hard constraints of 250/11000 active in the LEGS page. I hit the MCP speed knob again to get out of speed intervene. VNAV was still commanding 280 knots, which made sense. I used a little speed brake to slow down to 280 as I was still fast. Approaching VTU, I had 11000 set in altitude and IDLE/LNAV/VNAV PATH on the FMA. Again VNAV was going to hit the altitude constraint, but it was going to reach 11000 right at the waypoint (green arc) and there were no green circles indicating a deceleration. I hit speed intervene again and set 250 kt and used the speedbrakes to hit the constraint at VTU. Shortly before reaching the waypoint, I hit the altitude knob to remove the active constraint at VTU (so it wouldn't level off there). This made KEACH the active waypoint, with SADDE right after it (250/10000A). At this point FMA was still showing IDLE/LNAV/VNAV (can't remember SPD or PATH). I released speed intervene again and VNAV went nearly level,as expected since it was at speed (250 kt) and had 15 miles to descend only 1000 feet by SADDE. At this point I got distracted by ATC telling me to switch frequencies. Once, I'd switched, I found that the A/T was commanding full thrust and the plane was climbing at ~4000 fpm. Hardware throttles were still at idle. VNAV was active and the altitude was set to an altitude below the current altitude. Although I have the A/T override to "only in HOLD" my first response was to move the throttles forward and then back to idle, but that didn't have any effect (as it shouldn't have). I ended up having to disconnect the A/T completely to regain control over thrust. Any thoughts? Bill Rowe

I'm running Steve's FX Fixer and using the instructions, I've been able to get VC shadows working in the PMDG 777. I love the effect and Steve's software. However, I have a strange issue when using TrackIR: namely the shadows move around when I move my head even when the plane is not moving. It's as if the light source in the VC is moving with TrackIR Any one else have this experience? Bill Rowe

Since we are getting the weather radar functionality in the (hopefully) near future, can someone with real world experience enlighten us on typical airline practice for using the radar? I'm assuming that it's not on for every flight from takeoff to landing (but I could be wrong). What are the conditions that would lead the crew to turn on the radar or turn it off mid-flight? I'm guessing that flying into a SIGMET area would induce the crew to turn it on. Also, keeping it on for night flight makes sense? Thanks, Bill Rowe

Since we are getting the weather radar functionality in the (hopefully) near future, can someone with real world experience enlighten us on typical airline practice for using the radar? I'm assuming that it's not on for every flight from takeoff to landing (but I could be wrong). What are the conditions that would lead the crew to turn on the radar or turn it off mid-flight? I'm guessing that flying into a SIGMET area would induce the crew to turn it on. Also, keeping it on for night flight makes sense? Thanks, Bill Rowe

I have had these two failures multiple times, and I haven't reached the first maintaince interval (250 hours). What operational errors could be causing frequent failures of these two items. The ENG PRSOV VALVE failures seem way too frequent for an engine that is ETOPS certified, so I feel like I must be doing something wrong. I am running the service based failures and and a factor of 5x (i.e. 1 hour of flight time in the sim equals 5 hours of aircraft wear and tear). Bill Rowe

From the posts you cited above I understand that the doors that are being opened by the PMDG code are correct. My issue is that they are opening when there is no ground equipment nearby and I would like to control when they open (basically take certain items in the PMDG ground ops list out of automatic control) so I open them when the GSX catering vehicles are in position, not whenever the PMDG code wants to do it. I have my default flight set up with cargo and 2L open, all other doors closed, not armed. I'd like ground ops to have control of 2L and the cargo, but manually open and close the doors for catering. Bill Rowe

I've noticed that when I used the ground operations function, the virtual cabin crew open doors 2R, 4L, and 4R, even though there are no ground services at those positions. Is there any way to edit what doors are opened and closed by the ground ops function? It looks kind of silly to have those doors open with nothing there, plus my virtual flight attendants might fall out. I have GSX, so I'd prefer to open the doors as needed to complete catering. Bill Rowe

OK. That makes sense, but if I can't enter an altitude restriction, then how do I enter a speed restriction on a cruise leg where the FMC calculated altitude is the planned altitude (which would be a normal situation since you would file for an altitude that was economical for the weight you were planning). Basically the initial waypoint in the NAT is showing (in small font): .833/FL340 and I want to put .83 Mach restriction through the NAT and then add ECON/ at the last NAT waypoint to return to econ speed. I've been looking at the FCOM vol.2 pg 11.42.28 and it talks about entering a constant speed cruise segment. I've been trying to replicate what is shown there (unsuccessfully). Bill Rowe

I was putting in the constraint as speed and altitude. I entered .84/340 and got "invalid entry" I tried multiple formats for speed (e.g. 0.84, .840) and altitude (340000, FL340) but nothing worked. I couldn't even enter an altitude constraint of FL340 by itself even though the FMC was planning FL340 at that point (I was making the mod on the ground so it wasn't that the waypoint was active). I tried a waypoint later in the route and was able to enter FL340 after the step climb. So there was something about that waypoint (a regular intersection) that the FMC wouldn't let me apply an altitude constraint. I couldn't enter a speed constraint on any waypoint. Bill

I am flying EGLL-KEWR and the flight plan calls for a speed and altitude restriction for the oceanic track portion of the flight (M0.83/FL360) The legs page has the FMC calculated values, which include a step climb in the middle of the NAT. I have tried to override by entering the required speed and altitude at each oceanic waypoint, but I get an "invalid entry" message, no matter now I try to enter it. I can do speed intervene and not perform the step climb until exiting the track, but I'd like the performance calculations (fuel predictions) to be correct. Am I missing something? Bill Rowe