Page 1 of 1

Monitor Not Detected

PostPosted: Wed Oct 12, 2016 1:52 pm
by Polaris
I've been enjoying FlyInside for a few months without any issues, until I updated to the most recent version. I'm now unable to use it as my primary monitor is not being detected for some reason. I haven't modified the hardware since it was working. I simply updated P3D and FlyInside and the error appeared. I've done a clean install of both, but it hasn't helped.

log.txt
(161.87 KiB) Downloaded 468 times

Error.png
Error.png (7.81 KiB) Viewed 15715 times

Re: Monitor Not Detected

PostPosted: Sat Oct 15, 2016 8:25 pm
by CyberCub
I also get the exact same error after installing the 1.62 update :(

GTX 980 / Core i7 6700k / Win 10 Pro 64bit

Re: Monitor Not Detected

PostPosted: Tue Oct 25, 2016 1:34 pm
by admin
I take it that the tip regarding "Device Manager" didn't help, and no monitors are marked as disabled?

Does down-grading to a previous FlyInside version (1.52, 1.6, etc) fix the issue? That'll help determine whether this is a FlyInside code regression or some sort of new/different setting.

Re: Monitor Not Detected

PostPosted: Wed Oct 26, 2016 7:38 pm
by CyberCub
admin wrote:I take it that the tip regarding "Device Manager" didn't help, and no monitors are marked as disabled?

Does down-grading to a previous FlyInside version (1.52, 1.6, etc) fix the issue? That'll help determine whether this is a FlyInside code regression or some sort of new/different setting.


I will try a downgrade version and let you know.

Re: Monitor Not Detected

PostPosted: Wed Oct 26, 2016 7:48 pm
by CyberCub
admin wrote:I take it that the tip regarding "Device Manager" didn't help, and no monitors are marked as disabled?

Does down-grading to a previous FlyInside version (1.52, 1.6, etc) fix the issue? That'll help determine whether this is a FlyInside code regression or some sort of new/different setting.


Ok I resolved the issue. I use splashtop to stream from pc to my tablet at night. Turns out splashtop adds its own monitor driver in place of true monitor drivers and that was causing flyinside a headache. I had to uninstall splashtop so the normal monitor drivers would show up and everything fine even with 1.62.

With that said you might want to add something that checks for your typical streamers that do this. I think LogMeIn also does something similar.

Re: Monitor Not Detected

PostPosted: Thu Nov 03, 2016 3:12 pm
by trapdoor
I literally installed FlyInside for the first time today and had the same issue (Vive, FSX:SE). I have TeamViewer installed and had to uninstall it just to get past the error window you showed. I tried closing TeamViewer and also disabling the background service, but neither worked. I use TeamViewer on a near-daily basis so this isn't a good long term solution for me.

Hope you guys can get this sorted out. If you do, I'll be purchasing a license because it seemed to work well once I got it going.

Thanks,
TD

Re: Monitor Not Detected - Resolved

PostPosted: Thu Dec 08, 2016 8:52 pm
by CyberCub
Bumping this for dev attention. We found the reason for the error noted which looks like folks using software like team viewer, splash top etc which install special drivers as "monitors" causing fly-inside to not be happy.

Re: Monitor Not Detected

PostPosted: Tue Dec 13, 2016 10:27 am
by admin
So we've been looking into this. It only happens if you have the "TeamViewer Monitor Driver" installed. For now you can remove this, and both TeamViewer and FlyInside work happily (we use TeamViewer ourselves) :) That said, we're working on improving compatibility.

Re: Monitor Not Detected

PostPosted: Sat Dec 17, 2016 12:59 am
by CyberCub
admin wrote:So we've been looking into this. It only happens if you have the "TeamViewer Monitor Driver" installed. For now you can remove this, and both TeamViewer and FlyInside work happily (we use TeamViewer ourselves) :) That said, we're working on improving compatibility.


Thanks glad to hear. For now I just don't use Splashtop for the time being. http://www.splashtop.com/ if you are not familiar with it. It also causes the same monitor issue like team viewer.