pegruder

As someone who has used the Oculus Rift for the past month or so in P3D, it truly is incredible. Pulling away from the runway I start to actually feel im being lifted, yet im sitting in an office chair. I will say the only gripe I have is the resolution. However the dev of Fly-inside added a quick zoom mode which helps tremendously. Quick button tap to zoom in to the FMC for instance, make a change and back out again. It's something that needs to be experienced to be believed. Haven't messed with the leap motion controllers. Supposedly you can use your hands to flip switches and turn knobs. Still waiting for XP support though. Side note - I do have a handfull of Go Flight modules. At first its a little weird feeling your way around but eventually I guess the muscle memory kicks in you start naturally going to where you physically have the modules. Although for someone who hasn't invested in to modules, its very easy to look around and scroll with the mouse.

Sweet - Ill tweak this a bit. It was set to a heading deviation of 5 and course of 1.5. Ill bump these up a bit and see how she goes now.

This morning flying from MCO to IAH I kept getting a "You are off course message" I can't for the life of me figure out why as I was headed to the correct waypoint (or at least I thought so). Attached is a screen shot.

I'd say keep in mind due to licensing issues some 3rd party devs require a separate purchase to use their AC in P3D. As mentioned above the FSX version of the NGX will not work, you will need to repurchase the P3D version.

I've had bad experiences with Razer in the past, I steer clear of them - but thats just me. Sounds promising though.

So I've heard. I tried it with fly inside but some people say it doesn't work. Certainly didn't work for me. Ill have to try this on other titles though.

Yea, Its very easy to use with mouse so I don't really see a reason to pop for the leap motion. If there was some sort of glove with feedback that'd be a different story. As a side note - I just realized what the import window option is - and its incredible! I can import my P2ATC window and throw it on the seat next to me and just zoom in when needed to see the map, or if I forget my phraseology. The dev for fly inside really made an incredible piece of software.

For me it was no less smooth than without VR. If anything it was actually more smooth? Made possible I'm sure by the asynchronous time warp feature. What kind of FPS hit for the leap motion? I was considering but I don't think I'd want to lose any FPS over it. Its still easy enough to zoom in and middle mouse scroll to setup everything I'd need. Pretty much makes any goflight modules I have obsolete now - aside from throttles I'd say.

I had the smoothest landing of my FS career last night in to MCO with the 737 NGX because of that level of depth you now have... On takeoff I almost felt g force change when I started rotated away from the runway. Almost a feeling of falling backward I guess. It's really unreal. I saw this post and now I know why it didn't seem to work lol.

So I just got my Rift and decided to fire up P3D with Flyinside and all I can say is wow. With fly inside you can override the native resolution of the rift which makes the sim a little clearer with little to no performance hit. I am running this on a 4790k, 16GB RAM and only a single 970 GTX. (I have two for SLI but VR has had some issues with SLI for me.) Avg FPS for those wondering is around 20-25, which is about my norm in P3D. Its not 100% smooth, but then again neither was P3D in non VR, but the level of immersion is incredible. You truly are transported to a life size cockpit, i nearly found myself reaching for switches and buttons with my hands. Its something to be experienced for sure. I wonder if P3D had native support for VR if it would improve readability of gauges and such. For instance using the Rift with project cars, I can view gauges on the dash a little clearer than in P3D.

I don't know if I'm doing something right now but I haven't really had any issues with ATC losing me since 2.0.1.0. At best due to some crosswinds I've had a few "off course" messages that were nearly immediately followed by "Resume own navi" messages.

After running through the fresh install I'm all set! Thanks again.

Ah ok that makes sense. Ill run through that tonight. Thanks again!

I just upgraded to 2.0.1.0 and still have the same issue. Do I need a full uninstall or can I delete the current database file and then run the upgrade?

I just tried a flight at KIAD, tuned to 135.7 and am getting check frequency. I think I managed to get a screen shot up.

Comes up under the info tab. If I tune 135.70 I get "Check Frequency"

Yes - sorry, I did flop the two. The first 4 settings of my FltPln register are all checked except ATC Gives vectors to IF. Last I checked the AIRAC cycles were sycned between P2A and the JAR FMC. Ill double check again to be sure. I haven't noticed any discrepancys there. It just seems to not detect I've actually passed a waypoint or routing me to waypoints not in my P2A FP. As for changing the P2A FP - i usually change it in P2A so the map lines up with where I am actually going. For some reason (unless Im missing a setting) P2A doesn't seem to update the map with the SID or STAR/APPR information. So if I start following an approach on the map itll appear that I'm off course. Note that P2A doesn't think Im off course in this scenario - or least I dont think so. Its more cosmetic for myself. Side note: I've currently found myself in a loop enroute to ATL with "Contact center on 126.02. When I tune this frequency I am getting "Check Frequency" as the response.

So lately I've noticed a few times that ATC seems to have 'lost' me and basically tells me to turn around. Seems to happen with a variety of flight plans I've used all generated from PFPX or EFASS. An example was today from JFK to ATL, ATC didn't assign a STAR, so after takeoff I went direct to CRI when it seemed to expect to head to DEEZ. I tried using what I thought was a direct to waypoint option in P2A (The D with the Arrow through it), however I couldnt get P2A to see that I wanted to continue on my way (EDIT: Just reread the manual, that was user error.). Ill have to start keeping better track of the flightplans, but there are a few occasions where ATC appears to lose me. Usually occurs on arrival via an assigned SID. Ill input the SID in to the FMC, update the map in P2A by loading it, but then P2A seems to want to direct me a different direction. I'll save the FP and take some screen shots next time this happens, it is very likely I'm skipping something along my route (I'm no real world pilot).

I just tried contacting clearance @ KIAD and the specified freq that P2A appears to be looking for is 135.69. However I think this should be 135.7. PS - P2A is coming along nicely!

Flight plan settings were everything checked except, Force pilot runway, ATC Ignores published speed limits, ATC gives vectors to IF. Alt change lead time (sec) is 30 and vector extended final distance is 2. Flight plan was: KMCO, TRV, JALOP, GISSH, FISEL, FLL.

In P3D v3.2 last night from MCO to FLL, on approach to FLL approach (who didnt provide any STAR) handed me off to tower, (who didnt provide any runway/approach info). I checked active runway via the info tab in P2A which had only dashes. I contacted tower requesting active runway, which replied 10L. I requested landing on 10L and got an exception error and P2A crashed. I can see if I can duplicate this if needed.

Sure thing. Soon as I get home from work I'll send it over. It's lonely up there! :smile:

Has anyone gotten this working? I have the background files but it seems to only play the same file on repeat over and over again. I thought I remembered reading somewhere awhile back it doesn't work in 2.0?

Randomly now since version .14 and still present in .15 P2A seems to freeze and become non responsive. There doesn't seem to be any errors or anything. Just cruising along and notice ATC stopped contacting me. When I click the P2A window is greys itself out with a 'Not Responding' in the title bar. This happened on approach in to LAX (v.14) and now while cruising to SEA (v.15). Running W10 and P3D V3.2.

Thanks for the info. Good times ahead it seems. Starting to be more and more impressed with XP.