[Solved]Opera screen flickering
-
A Former User last edited by
Hello, folks
I have an issue with Opera that doesn't seem to be that common, nor do I know how to troubleshoot it.
Whenever the mouse cursor goes over an active link on the page and the link in the lower left corner of the page shows up, the browser screen repositions itself by a few pixels. As soon as I move cursor over a link-free area, it resumes initial position.
As nowadays all pages are almost covered in links, this leads to a very upsetting flickering that can become quite bothersome for the eye.Never had this issue with other browsers until now and can't seem to find help for it.
I've recently switched to Opera from Edge and this is a major bump in the switch process
Anyone has any idea why this happens ?Using Opera on an Asus laptop, Windows 10, no extensions installed.
Thanks for the help!
Daniel -
-
A Former User last edited by
Thx for the input!
Reckon video card driver compatibility might be an issue ?
Coz the drivers are all good, recently installed Windows and all original and updated drivers.Thx
-
-
A Former User last edited by
To be honest, I have no idea how to interpret the opera://gpu/ thing or if it has anything to do with the screen flickering.
Anyone that has more knowledge and may help ? I'll paste below what seems to be of importance..Graphics Feature Status
Canvas: Hardware accelerated
Flash: Hardware accelerated
Flash Stage3D: Hardware accelerated
Flash Stage3D Baseline profile: Hardware accelerated
Compositing: Hardware accelerated
Multiple Raster Threads: Enabled
Native GpuMemoryBuffers: Software only. Hardware acceleration disabled
Rasterization: Software only. Hardware acceleration disabled
Video Decode: Hardware accelerated
Video Encode: Hardware accelerated
VPx Video Decode: Software only, hardware acceleration unavailable
WebGL: Hardware accelerated
WebGL2: Hardware accelerated
Driver Bug Workarounds
clear_uniforms_before_first_program_use
disable_discard_framebuffer
disable_framebuffer_cmaa
exit_on_context_lost
force_cube_complete
msaa_is_slow
scalarize_vec_and_mat_constructor_args
texsubimage_faster_than_teximage
Problems Detected
VPx decoding is too slow on Intel Broadwell, Skylake, and CherryView: 616318
Disabled Features: accelerated_vpx_decode
Some drivers are unable to reset the D3D device in the GPU process sandbox
Applied Workarounds: exit_on_context_lost
TexSubImage is faster for full uploads on ANGLE
Applied Workarounds: texsubimage_faster_than_teximage
Clear uniforms before first program use on all platforms: 124764, 349137
Applied Workarounds: clear_uniforms_before_first_program_use
Always rewrite vec/mat constructors to be consistent: 398694
Applied Workarounds: scalarize_vec_and_mat_constructor_args
ANGLE crash on glReadPixels from incomplete cube map texture: 518889
Applied Workarounds: force_cube_complete
On Intel GPUs MSAA performance is not acceptable for GPU rasterization: 527565
Applied Workarounds: msaa_is_slow
Framebuffer discarding can hurt performance on non-tilers: 570897
Applied Workarounds: disable_discard_framebuffer
Limited enabling of Chromium GL_INTEL_framebuffer_CMAA: 535198
Applied Workarounds: disable_framebuffer_cmaa
Accelerated rasterization has been disabled, either via blacklist, about:flags or the command line.
Disabled Features: rasterization
Native GpuMemoryBuffers have been disabled, either via about:flags or command line.
Disabled Features: native_gpu_memory_buffers -
-
-
A Former User last edited by
Disabling hardware acceleration makes any difference?
Hey.
It did make a difference, indeed. I was so sure I've tried that, previously ...
Anyhow, thanks very much for your help! Appreciate it!Have a beer on me!
