Strobelight - LightBoost Utility for AMD/ATI and NVIDIA

[Wizard]

(08-22-2015 07:35 PM)ToastyX Wrote:  

(08-21-2015 05:23 AM)Wizard Wrote:  Well the OS detecting the override was just a guess. It's possible that that is just how windows 10 starts. Once it boots it shows the login screen for about 8 seconds, and won't let me use the keyboard until it flickers on and off. The flicker is a lot shorter in duration than if I were to just run restart.exe and restart the graphics driver.

I DO use geforce experience, but do not use samsung magician. I guess I could 'try' to uninstall geforce experience, but I refuse to use that as a solution since I do like a lot of the things that geforce experience does, but I will test uninstalling it to see if that fixes the problem, for debugging purposes.

Does the flicker happen if you run restart.exe and then "Scan for hardware changes" in the Device Manager? If not, then it's not related to the GeForce Experience problem.

Just tried that now, ran restart64.exe then scanned for hardware changes, and no flickering happened. At least we narrowed that down.

(08-22-2015 07:35 PM)ToastyX Wrote:  

(08-21-2015 05:23 AM)Wizard Wrote:  

• Splashtop (same as teamviewer)
  

Check the Device Manager under "Display adapters" and make sure there are no mirror drivers or anything other than your video card. Mirror drivers create virtual devices that can interfere with EDID overrides. Splashtop has a mirror driver available, but I don't think it's installed by default. Someone had issues with LogMeIn's mirror driver.

The only thing listed under Display adapters is my GPU. NVIDIA GeForce GTX 780 Ti.

(08-22-2015 07:35 PM)ToastyX Wrote:  

(08-21-2015 05:23 AM)Wizard Wrote:  EDIT2: Tried using DDU again and reinstalling the graphics driver WITHOUT Geforce Experience. Same problem. A couple of other things I just thought of. I'm using the SWAPPED version of the strobelight because I still do like to use 3d vision every now and then.

That explains why you were getting the message. The swapped version checks for 121/111/101 Hz instead of 120/110/100 Hz. I was asking if the default non-strobed refresh rates were available because the regular version wouldn't give that message even if the EDID override wasn't loading, although the strobing options won't work correctly.

So does this mean that I should try the regular version to see if it will fix the problem?

(08-22-2015 07:35 PM)ToastyX Wrote:  

(08-21-2015 05:23 AM)Wizard Wrote:  Some other probably unimportant info: I added scaled resolutions in CRU, since I do like to play SOME games in lower resolutions. I am also using the -off parameter since I don't want it starting up strobed. My main monitor is the VG248QE which I want strobelight to work with, and I have two other monitors connected as well.
None of these things should be causing the issue though. Any other suggestions that I could try would be great. By now I would have assumed it was windows 10's fault, but you're sure that's not the case?
I can't be the only one having this issue on windows 10 can I? Any other input is appreciated.

I haven't seen any issues with Windows 10. It's been working fine with AMD, and I just tested it with the latest NVIDIA driver (355.60). Everything works as expected even with GeForce Experience installed. I even tested the swapped version to make sure.

Thanks for checking that out, I appreciate it. I really don't know what else to try though. I've even done a full reinstall of windows at some point, to no avail.

Another thing I just thought of. Is it possible that my monitor's driver (the driver for the device under 'Monitors' in the Device Manager) could be interfering with the EDID Override? I installed a windows 8 driver for my VG248QE because there wasn't one for windows 10, and in the past I used a windows 7 one.
Or is it possible that because I have so many scaled resolutions in CRU, it causes windows to not understand the override and ignore it. I only added the ones that were there by default though, but I don't fully understand how the custom extension block works. I'm just grasping at straws here.

Normally I wouldn't care about something so trivial as running restart64.exe on boot, but the fact that it isn't working properly makes me think there's something wrong with my setup, plus debugging helps you out too, so I get the satisfaction of knowing my setup is correct, and I don't have a bad driver etc, and to help you determine if there's a problem within your program so someone else doesn't run across this issue.

Thanks for your quick replies! I wasn't expecting this much help for a free product! I really appreciate it!

EDIT. So I did some more debugging in CRU. Every time I restart my displays with restart64.exe, it will add an inactive monitor EDID profile to the list. Is that a sign that there's something wrong with my monitor driver?