Native GpuMemoryBuffers have been disabled, either via about :flags or command line.ĭisabled Features: native_gpu_memory_buffers Limited enabling of Chromium GL_INTEL_framebuffer_CMAA: 535198Īpplied Workarounds: disable_framebuffer_cmaaĪccelerated rasterization has been disabled, either via blacklist, about :flags or the command line. ![]() Some drivers are unable to reset the D3D device in the GPU process sandboxĪpplied Workarounds: exit_on_context_lostĬlear uniforms before first program use on all platforms: 124764, 349137Īpplied Workarounds: clear_uniforms_before_first_program_useĪlways rewrite vec/mat constructors to be consistent: 398694Īpplied Workarounds: scalarize_vec_and_mat_constructor_argsįramebuffer discarding can hurt performance on non-tilers: 570897Īpplied Workarounds: disable_discard_framebuffer Hardware acceleration disabledĭrivers older than 2009-01 on Windows are possibly unreliable: 72979, 89802, 315205 I rely heavily on my dual monitor setup with DisplayLink.Ĭanvas: Software only, hardware acceleration unavailableįlash Stage3D Baseline profile: Hardware accelerated I don't know if this is directly attributable to DisplayLink or not - it's very hard to say but since the Windows 10 update, things have really impacted me negatively. Here's the GPU status reported by the Chrome browser if that helps. ![]() Hi Alban, WebGL crashes with the latest update.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |