Random Artefacts in FSX:SE and P3Dv3

[topper]

First, I would like to say how amazed I am by the Rift implementation of FSX and P3D with the help of FlyInside. I've gotten my CV1 on Friday last week and I've been testing several games with it. FSX or P3D with FlyInside is definitely one of the better experiences! Thumbs up!

There is however one serious annoyance: random artefacts. These artefacts occur both in FSX:SE and P3Dv3.4 (latest). In FSX:SE it occurs every 30 to 60 seconds and in P3D every 5 to 10. The artefacts appear for a brief moment (millisecond) and look something like when you're watching satellite-TV in a stormy weather - mostly a "white-isch" pixelated area covering around 10 to 20% of the "Rift screen". The artefacts appear independent from head movement, meaning even when I'm not moving my head. I'm hitting around 30-40/90 FPS in FSX and P3D.

Have you experienced anything similar and do you know any fix for this problem? So far, this is the only game where I've had these problems. Thanks a lot!

My Specs:
Core i7-3770
8 GB RAM
nVidia GTX 1060 6GB (latest driver)
Windows 10
FSX:SE with Orbx Global, Vector, openLC Europe
P3Dv3.4 (latest) vanilla
Using FlyInside 1.62 trial

[aurel42]

Cut'n'Paste from another thread (viewtopic.php?f=11&t=2921):

With 372.90 (and all other 372.xx, but not with 368.xx), I get flashes of colored static in high frequency when using the highest resolution.

At the second highest resolution, I get no flashes of static, but occasional white flashes on the right eye, and while they're annoying, they are rare enough, and they feel different enough to assume that it's an unrelated issue.

I have yet to see a GTX1080 user who doesn't get the static at the highest resolution. Conventional wisdom in this forum seems to be it's a Nvidia driver issue, but since it has persisted for several months, I'm starting to think it might not be. Instead of downgrading the driver, I'm now downgrading the resolution instead (to the second highest), because I want the benefit of three months worth of Nvidia bugfixes.

[LCYCowboy]

Using the older 368 drivers completely solves this problem for me.

Try using DDU to uninstall the latest drivers, then download the lat 368 drivers.

[mutley]

I've also downgraded the drivers to 368.xx too.
When installing the earlier driver, always ensure you opt for a clean install.

[admin]

Pretty sure this is a driver bug. That said, it mostly affects FlyInside, so I'm investigating what can be done to work around it

[topper]

Thank's for the quick help! Reverting back to the 368.81 driver did the trick. I will now test P3D and FSX:SE and see which one runs better on my PC. I've purchased a P3D licence lately knowing that they have customer-friendly refund policy. My experience so far has been that FSX:SE runs smoother and faster, but I might have to do some additional tweaking with P3D.

Short notice for the dev: should you need any logs or help tracing the problem with the 37x.xx drivers let me know. I'll be more than happy to help you.

Final off-topic feature request for future FlyInside development: could you please make a mouse scroll up/down joystick button mapping. You'd probably have to simulate a button press as a continuous mouse scroll, but I'm confident you know how to implement it. I think I've read it here somewhere in a post, but I thougth it'll be a good idea to mention it again. This feature would be really helpful for certain knobs and switches.

[aurel42]

Final off-topic feature request for future FlyInside development: could you please make a mouse scroll up/down joystick button mapping. You'd probably have to simulate a button press as a continuous mouse scroll, but I'm confident you know how to implement it. I think I've read it here somewhere in a post, but I thougth it'll be a good idea to mention it again. This feature would be really helpful for certain knobs and switches.

The more logical plan for Dan would probably be to further develop the existing "mouse free" input methods until nobody ever needs to ask for mouse button support again.

While we're waiting for that, you can kinda work around the problem using an AutoHotKey macro that converts button presses into mouse events (I've got buttons for left click, right click, mousewheel up and down).

Sadly, this is far from perfect.

Since FI doesn't register any mouse movements, it will hide the mouse pointer after a few seconds, even though you're busy using it, which means for longer actions (like operating a radio or GPS), you will have to "center mouse", do a few clicks, "center mouse", over and over again.

Also, if the mouse hides while you were just pressing one of the buttons, that button will become stuck until you use it again. E.g. you use "mousewheel up", mouse pointer gets hidden, the selected control receives an endless stream of "mouse wheel up" events, until you "center mouse" and use "mousewheel up" again.

Also, I think starting a few versions ago, the behaviour of "center mouse" seems to have changed (or my usage has changed, not sure). Whenever the mouse pointer is over a "floating window" (either imported from desktop or a P3D/FSX window like ATC), I have to press "center mouse" twice. The first use will put the mouse pointer "back in the cockpit", but not in the center of my view, it takes a second button press to actually center the mouse pointer.

[fulcrum_64th]

Any news on that bug ? Sucks rolling back to earlier drivers as I need the latest for other software I'm running

Kind Regards,

Fulcrum

[Tony]

It's a driver bug, not a flyinside bug I believe ??

Tony

[fulcrum_64th]

yep, mostly probably a card driver bug.I was just curious if the devs or even some nvidia people that seems to be on the forum had some news.

Best

Fulcrum