Agent X20

It doesn't look like FSS still has not posted the updated Otter yet. I just raised a ticket on their site this evening to try to find out what's up.

Let me preface this question by stating many new LED screens, and late 9 series and 10 series video cards don't agree with me, and cause eye strain and headaches. This is _not_ a function of refresh rates. There's something about how the backlights function and pixels are rendered that don't agree with me. I'm not alone in this (see http://ledstrain.org, and big threads on the apple forums about people unable to use macbooks) and frankly it's a bummer. Oh and yeah I had my eyes checked, wear glasses etc. My current GPU, an Nvidia 970, coupled with CFL backlight LCD screens work PERFECTLY for me. I can fly P3DV3, Xplane 11, FSX Steam, Rise of Flight for hours with no problems. The same can be said for titles like Farcry 3,4, & Primal, Wildlands, Anno 2070, and loads more besides. BUT P3DV4 is off somehow and makes me feel ill, perhaps better described as seasick. This is despite excellent frame rates 40-100, and having tried a bunch of settings. I cannot put my finger on what's wrong. Whatever it is is subtle. I'm largely resigned to sticking with P3DV3 (with a big investment in scenery, aircraft and utilities) and looking way out to V5, while spending more time in XPlane. I'm disappointed, but there's life in V3 yet right? Still, I'd like to know if anyone else is experiencing similar issues with V4?

It certainly looked like it with my install, and reinstall. Plus I saw a report or two over on the Majestic forum.

I couldn't get any clicks to register, and there were no sounds, combined with the plane being in a half started state. A quick search on the Majestic forum and a reinstall was the answer here as well. Note this is also Win 10 Creator's edition.

Nope, I'm seeing it with a 970.

That's what I thought. It was just that when I did move it accidentally - strange engine/rpm things happened. (The Carenado Do228 is the same). That got me wondering where the control needed to be as it clearly wasn't totally 'disconnected'. Full forward it is!

I did my first flight in the PC12 over the weekend and I too was having immense problems with the plane barrelling forward after start up. As noted above, it seems you need the condition level right back and not in ground idle range. I also found my throttle quadrant's prop pitch was also having strange effects on the aircraft - when I wouldn't expect it to have any effect. I eventually had ok results with the prop pitch full forward.

Recent Nvidia drivers have been causing major memory leaks for many. Check those threads out, and try an older driver - the 376.53 drivers are OK for me. (Note the hotfix drivers didn't help in my case).

PC Aviator now has the new version for download.

I'm experiencing a similar effect at present. OOM after flying 150 miles over FTX NZNI, despite 1.7GB free at the start of the flight. However I don't yet know if it's AS16, ASCA, Nvidia drivers, ChasePlane or GSX causing it. Lots of testing is required to narrow down the culprit. (And yes FTX Vector is turned well down to reduce its footprint, and I've got latest versions of all of the above as well as the very latest Nvidia driver hotfix).

Hi, I've set up a wireless Xbox 360 controller as my ChasePlane control. Trouble is, on longer flights the controller decides to switch itself off after a period of inactivity - after which my view starts spinning left-right. This is presumably due to one of the sticks being my left/right pan control and without the controller being switched on ChasePlane decides it's getting 0 or max input and the view spins. Does anyone have a suggestion on how to stop this - other than periodically using the controller to stop it switching off? It's not really a huge hassle to restart the Xbox controller and restore the view, it's just a nuisance to have to deal with the "woah - there it goes again... turn it back on" bit. Anyone else seen this?

Reboot after the install so the font that it installs registers.

Yep I think you're onto it. I vaguely recall a mixture lever issue a while back with the 228.

Interesting, would you recommend going back up to Max density, to restore AS16 overcast rendering, with distance reduced from 90mi to 80mi to counter the SGSS load? Or leave things at High density and tweak down the distance another notch for another fps boost? I think I'll do some tests... :smile: (At High density I've got enough fps back to go back to 5 layers in AS16 and I'm no longer flying around in endless overcast cloud conditions).

Update on my hassles with wonky airfield graphics, aircraft embedded in the tarmac and offset views, I just loaded the A2A Comanche for a first flight into NZWN and things were screwed up. Then I jumped to NZAA where everything was OK, then back to NZWN and it's all fine. This does suggest there's a bug in P3D in that it works sometimes but not others.