Timeline for Screen lag during GPU rendering
Current License: CC BY-SA 3.0
6 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jul 20, 2017 at 19:52 | history | bounty ended | Ascalon | ||
| Jul 20, 2017 at 19:52 | vote | accept | Ascalon | ||
| Jul 16, 2017 at 22:39 | comment | added | bertmoog | It's the same as if you were gaming on triple monitor system, it wouldn't be right to have one display running at 60fps, one at 25, and one at 40. All three should be synced at 25. | |
| Jul 16, 2017 at 22:33 | comment | added | bertmoog | The registry entry will only keep Windows from resetting the driver. The lag will still be there. Like I said, I don't have another monitor to test, but I'd be interested in knowing if you used the 770 for primary display, rendered on the Titan, and used the Titan for secondary display, if you would see lag. My guess is that you would. I don't know if there's a way to change how Windows handles display interrupts. It might be a single queue for all adapters, therefore, there's no "getting out of line". | |
| Jul 16, 2017 at 20:36 | comment | added | Ascalon | I've heard something along these lines before, so that is probably the case. I guess then I either need to use only the 770 for displays (a hassle, and then I lose my titan for gaming) or try to find some way to tell windows not to keep them all in sync, or whatever it's doing. I've dealt with the problem of it crashing if unresponsive too long in the past. There's a number in the registry you can change for how long windows will tolerate. Perhaps something similar here? | |
| Jul 15, 2017 at 22:37 | history | answered | bertmoog | CC BY-SA 3.0 |