TerryS

2d for me is really smooth with much higher fps than v4. VR is not usable for me. Using Steam VR with a Valve Index and latest drivers, image in VR jitters really badly and really strains my eyes. Also cloud reflections in water display on one eye and not the other which adds to the discomfort. I too am waiting for a new password on the P3D site so I can post there. I keep monitoring but they haven't even acknowledged a problem with VR yet, saying they haven't seen these effects! I think the flood gates might open on their forum of issues with VR when they get their act together with forum access.

Like a few other people here, VR (Valve Index) is unusable for me owing to severe flickering. The actual FPS is much better than v4 and the image imo is sharper than XP but the flickering would give you a sore head. I tried to post on P3D forum as well but haven't received a pw reminder after 5 hours. I don't think their servers are capable of dealing with the demand.

Thanks Chock, probably drive now in case I buy loads of stuff!

I'm coming from Gloucestershire, don't know whether to drive or catch the train, train will be cheaper but less convenient, whats the parking like?

I'm flying P3Dv4.1 in VR with Oculus Rift and Flyinside. When I trim the aircraft using a programmed hat switch it physically trims, nose up/down as expected however the trim wheel doesn't move in the cockpit nor make any sound. It does animate and make a 'whishing sound' when on autopilot. I've searched the forum but couldn't find anything. It's not a big deal but I was just wondering if I'd missed something obvious.

Wish I hadn't started reading this, I normally fly Easyjet (as a passenger) from Bristol to Belfast but next week am flying Birmingham to Belfast on a Q400 Flybe because the parking was too expensive at Bristol! I hope my seat isn't beside the prop :)

Hello, I have the 737 and 777 for P3D installed and, well, they were working! I have a lot of other addons and today I updated P3D from 3.1 to 3.2 by uninstalling and reinstalling the client only to save me having to reinstall everything. Needless to say P3D now crashes on start-up with the faulting module being ai_player.dll. I have tried everything to resolve this by disabling all ai and scenery which contains ai but its too hard now and not worth wasting any more time. I cant get past the loading screen. I have decided to do a complete reinstall but I know from previous experience that I must deactivate the 777 and 737 through the FMC. What happens if I cant even load P3D, how do I deactivate? Is there any other way? Its a bit of a pain having to wait on the license being authorised again and I was told off the last time in a nice way! Terry

Yes, I found that out by reading more posts, it's 'CMeteoXml.dll' so I stopped it from loading in the DLL file and the plane works now. My main issue is now with performance. The FPS is ok but this aircraft causes major stutters and frame drops on my system. In comparison, the PMDG 737 and 777 have higher FPS and are silky smooth. My system is a 6700K Skylake OC to 4.6 and a Titan X 12Gb with P3D on an SSD. The settings in P3D v3 are set to achieve smooth results with the 777 (not extremely dense) which I thought was the most demanding aircraft I had - until now.

I created a Prepar3D v2 folder and dll.xml and fooled it into installing into that but as Jay says, the carenavigraph.dll stops P3D3 from starting. It works ok if you stop the carenavigraph.dll from loading so it is not compatible with P3D3.

Decided to download the new installer for the 737 P3D thinking I could have a quick flight before I went to bed. Uninstalled the previous version and have started to download the new version @ 9 kb/s! Cancelled and tried again but the browser is telling me over 3 days to download! I'm in the UK on 150Mb/s cable and it takes me 10 mins to download the whole of P3D so I assume the server is overloaded. Someone earlier mentioned 1982, well not long after this I had a 14.4K modem which was quicker than this. Oh, its just picked up speed, 4 mins now so if anyone else is initially very slow it does pick up after about 5 minutes. Might get a flight after all Terry Shields

I sold an EVGA SC Titan and bought an EVGA SC 780 Ti. The 780 Ti is more powerful than a Titan for gaming by about 10% which I verified playing Arma 3. Didn't notice any difference with FSX considering it has only half the VRAM and I'm running 2560 x 1440 + 1024 x 768 touchscreen. No memory problems flying over VFR London with Horizon VFR Scenery, Ultimate Traffic and NGX 737. Now I'm contemplating switching to Prepar3d which is why I'm checking these forums.

Hi Paul, Ithink the autopilot should disconnect automatically when it detects touchdown, however it doesn't touchdown therefore the autopilot remains on. It will not disconnect manually either and the aircraft just flys along 5ft off the ground. I now think it's a problem with the airport scenery as I just flew into EGGD (Bristol) and the autoland worked perfectly. I've run AFD scanner to see if there are any duplicate sceneries but everything checks out. I'll just avoid EGNT for a while, or manually land. Up until recently I always manually landed but I find the autoland quite interesting especially in poor visibility and because I'm not used to it. Thanks Terry

Hi, I have the same problem but I read somewhere on these forums that it's a problem with FSX itself and there is no workaround at the moment. I just hit the 'q' key twice to reset the sound or mouse click anywhere on the main panel. Terry

Hi Andrew, I wish it did then I could manually land it but no matter what I do, the controls don't respond. I thought it may have been a symptom of the 'panel freeze' however I've installed the hotfix and it made no difference. Thanks Terry

Hi everyone, I've been scratching my head over this one and I can't figure out what I'm doing wrong. I'm attempting an autoland at Newcastle, UK (EGNT). Both NAV radios are tuned to correct ILS frequency, both course dials set, speed correct, flaps correct, barometer set, both autopilots on, both FDs on etc. The NGX flys the approach perfectly down the GS with 'GS' in green and 'flare' in white letters. About 10 feet from touchdown, the aircraft begins to flare and the white 'flare' turns to green. That's it. The aircraft flys along the runway at about 5 feet altitude and wont touchdown. Eventually it turns gently to the right and lands in the terminal! I've tried to turn the autopilots and autothrottle off just prior to touchdown however despite the switches moving it seems as if the autopilot still has the aircraft and I cannot regain control, where's the ejection handle. Has anyone else encountered this or is it just me who thinks they know what they're doing but really hasn't a clue. The landing gear was down BTW and I've installed the hotfix. Terry