Standard vsync was never reliable in fastest possible CPU modes, at least it was never stable on my system, it is only accidental if it appeared to work..
Anyway, new low latency vsync has priority, it needs to work first.
Quote:
|
Also, "Low latency Vsync" in 3.6.1 doesn't require any Cycle exact to work properly.
|
But you said you get blank screen (hang) when using low latency vsync in 4.0b1? So do you mean it does work if cycle exact is enabled but hangs if not?
EDIT: I tried two laptops (one old with nvidia and other newer with integrated intel), worked just fine, actually much better than old low latency vsync. So this is something system specific, only way to get this fixed is to report it with enough details.