Please restore compatible graphics mode

Suty

@Windy9111 Unfortunately, since we are planning some changes in visualizations of our layers, we decided to remove this feature, because it cannot be supported then.
However, regarding to our colleagues, it should be in general quicker not to use it now.

Windy9111

@Suty Unfortunately, I'm sure that now is slower than before (like or similar OFF mode). Please restire that function, the lag is actually evident.

Suty

@Windy9111 Can you provide more information about your HW specification of your device?

Windy9111

@Suty It's the same device I used when everything was running smoothly in "ON" mode. So the problem stems from the latest update, not on my device.
Thanks for the support.

rdo118

@Windy9111 @Suty
This sounds very similar to the lag issue I reported a few days ago. I had the same problem in the past, but it went away when I turned on that setting. Since the setting is gone, I assumed it was always on, but from what I read here, it's always (effectively) off. Which means my problem with lag might never resolve.

schilpat

Hi, we are sorry to hear that you have performance issues without the graphics compatibility mode. We are constantly trying to optimize the app's performance and size, which also involves removing old and deprecated functionality. One of these is graphics compatibility mode, which was introduced many years ago when WebGL (one of our main technologies) did not have that great support among devices and browsers as it does nowadays. Recently, since there was a very small number of users actively using it, we decided to discontinue it because it took quite a significant part of our codebase. Another reason might be that we already have a few WebGL-only layers (radar, satellite, radar+) and that we are trying to incorporate WebGL (gpu rendering) into Windy as much as possible.

However, we would like to dig into the issue and try to solve it or find its source, and ideally help you. For that, we need additional information about your device, without which there is not much we can do. So, if you mind, would you try the following steps and report to us?

Check that graphics acceleration is enabled in your system (if disabled, it might be emulated by your CPU, which might cause the problems)
Check that you are not running power-saving mode
GPU dump
- go to chrome://gpu/ in chrome
- or go to about:support#graphics in firefox
- just paste the link into your browser and send us the report in the response
Browser dump
- go to chrome://version/ and send us google chrome version, user agent, os in the response
Try some webgl sample/benchmark and check, whether the performance issues persist
- e.g. https://webglsamples.org/aquarium/aquarium.html
- or at least https://get.webgl.org/

The issue seems very suspicious since Windy behaves relatively smoothly even on low-end and old devices...

rdo118

@schilpat said in Please restore compatible graphics mode:

about:support#graphics

The fish demo works perfectly fine. My display is limited to 60 Hz, so the demo can't go above that, but I get a steady and smooth 60 fps up to the 15 000 setting. 20 000 gets me 55-57 fps. 30 000 is in the high 30s fps.

Here's the dump:

Features
Window Device Pixel Ratios	1.25
Compositing	WebRender
Font Visibility Debug Info	Windows Platform
Asynchronous Pan/Zoom	wheel input enabled; scrollbar drag enabled; keyboard enabled; autoscroll enabled; smooth pinch-zoom enabled
WebGL 1 Driver WSI Info	outOfProcess: false
inProcess: true
EGL_VENDOR: Google Inc. (NVIDIA)
EGL_VERSION: 1.5 (ANGLE 2.1.19739 git hash: 419cd2c3213b)
EGL_EXTENSIONS: EGL_EXT_create_context_robustness EGL_ANGLE_d3d_share_handle_client_buffer EGL_ANGLE_d3d_texture_client_buffer EGL_ANGLE_surface_d3d_texture_2d_share_handle EGL_ANGLE_query_surface_pointer EGL_ANGLE_window_fixed_size EGL_ANGLE_keyed_mutex EGL_ANGLE_surface_orientation EGL_ANGLE_direct_composition EGL_ANGLE_windows_ui_composition EGL_NV_post_sub_buffer EGL_KHR_create_context EGL_KHR_image EGL_KHR_image_base EGL_KHR_gl_texture_2D_image EGL_KHR_gl_texture_cubemap_image EGL_KHR_gl_renderbuffer_image EGL_KHR_get_all_proc_addresses EGL_KHR_stream EGL_KHR_stream_consumer_gltexture EGL_NV_stream_consumer_gltexture_yuv EGL_ANGLE_stream_producer_d3d_texture EGL_ANGLE_create_context_webgl_compatibility EGL_CHROMIUM_create_context_bind_generates_resource EGL_CHROMIUM_sync_control EGL_EXT_pixel_format_float EGL_KHR_surfaceless_context EGL_ANGLE_display_texture_share_group EGL_ANGLE_display_semaphore_share_group EGL_ANGLE_create_context_client_arrays EGL_ANGLE_program_cache_control EGL_ANGLE_robust_resource_initialization EGL_ANGLE_create_context_extensions_enabled EGL_ANDROID_blob_cache EGL_ANDROID_recordable EGL_ANGLE_image_d3d11_texture EGL_ANGLE_create_context_backwards_compatible EGL_KHR_no_config_context EGL_KHR_create_context_no_error EGL_KHR_reusable_sync 
EGL_EXTENSIONS(nullptr): EGL_EXT_client_extensions EGL_EXT_device_query EGL_EXT_platform_base EGL_EXT_platform_device EGL_ANGLE_platform_angle EGL_ANGLE_platform_angle_d3d EGL_ANGLE_platform_angle_d3d11on12 EGL_ANGLE_platform_angle_device_id EGL_ANGLE_device_creation EGL_ANGLE_device_creation_d3d11 EGL_ANGLE_experimental_present_path EGL_KHR_client_get_all_proc_addresses EGL_KHR_debug EGL_ANGLE_feature_control 
WebGL 1 Driver Renderer	Google Inc. (NVIDIA) -- ANGLE (NVIDIA, NVIDIA GeForce RTX 4080 Direct3D11 vs_5_0 ps_5_0, D3D11-32.0.15.7216)
WebGL 1 Driver Version	OpenGL ES 3.0.0 (ANGLE 2.1.19739 git hash: 419cd2c3213b)
WebGL 1 Driver Extensions	GL_AMD_performance_monitor GL_ANGLE_base_vertex_base_instance GL_ANGLE_base_vertex_base_instance_shader_builtin GL_ANGLE_client_arrays GL_ANGLE_copy_texture_3d GL_ANGLE_depth_texture GL_ANGLE_framebuffer_blit GL_ANGLE_framebuffer_multisample GL_ANGLE_get_serialized_context_string GL_ANGLE_get_tex_level_parameter GL_ANGLE_instanced_arrays GL_ANGLE_lossy_etc_decode GL_ANGLE_memory_size GL_ANGLE_multi_draw GL_ANGLE_multiview_multisample GL_ANGLE_pack_reverse_row_order GL_ANGLE_program_cache_control GL_ANGLE_provoking_vertex GL_ANGLE_request_extension GL_ANGLE_robust_client_memory GL_ANGLE_texture_compression_dxt3 GL_ANGLE_texture_compression_dxt5 GL_ANGLE_texture_multisample GL_ANGLE_texture_usage GL_ANGLE_translated_shader_source GL_CHROMIUM_bind_generates_resource GL_CHROMIUM_bind_uniform_location GL_CHROMIUM_copy_compressed_texture GL_CHROMIUM_copy_texture GL_CHROMIUM_lose_context GL_CHROMIUM_sync_query GL_EXT_EGL_image_external_wrap_modes GL_EXT_base_instance GL_EXT_blend_func_extended GL_EXT_blend_minmax GL_EXT_clip_control GL_EXT_color_buffer_float GL_EXT_color_buffer_half_float GL_EXT_debug_label GL_EXT_debug_marker GL_EXT_discard_framebuffer GL_EXT_disjoint_timer_query GL_EXT_draw_buffers GL_EXT_draw_buffers_indexed GL_EXT_draw_elements_base_vertex GL_EXT_float_blend GL_EXT_frag_depth GL_EXT_instanced_arrays GL_EXT_map_buffer_range GL_EXT_multi_draw_indirect GL_EXT_multisampled_render_to_texture GL_EXT_occlusion_query_boolean GL_EXT_read_format_bgra GL_EXT_robustness GL_EXT_sRGB GL_EXT_shader_texture_lod GL_EXT_texture_compression_bptc GL_EXT_texture_compression_dxt1 GL_EXT_texture_compression_rgtc GL_EXT_texture_compression_s3tc_srgb GL_EXT_texture_filter_anisotropic GL_EXT_texture_format_BGRA8888 GL_EXT_texture_norm16 GL_EXT_texture_rg GL_EXT_texture_storage GL_EXT_texture_type_2_10_10_10_REV GL_EXT_unpack_subimage GL_KHR_debug GL_KHR_parallel_shader_compile GL_KHR_robust_buffer_access_behavior GL_NV_EGL_stream_consumer_external GL_NV_fence GL_NV_framebuffer_blit GL_NV_pack_subimage GL_NV_pixel_buffer_object GL_OES_EGL_image GL_OES_EGL_image_external GL_OES_EGL_image_external_essl3 GL_OES_compressed_EAC_R11_signed_texture GL_OES_compressed_EAC_R11_unsigned_texture GL_OES_compressed_EAC_RG11_signed_texture GL_OES_compressed_EAC_RG11_unsigned_texture GL_OES_compressed_ETC2_RGB8_texture GL_OES_compressed_ETC2_RGBA8_texture GL_OES_compressed_ETC2_punchthroughA_RGBA8_texture GL_OES_compressed_ETC2_punchthroughA_sRGB8_alpha_texture GL_OES_compressed_ETC2_sRGB8_alpha8_texture GL_OES_compressed_ETC2_sRGB8_texture GL_OES_depth24 GL_OES_depth32 GL_OES_draw_buffers_indexed GL_OES_draw_elements_base_vertex GL_OES_element_index_uint GL_OES_fbo_render_mipmap GL_OES_get_program_binary GL_OES_mapbuffer GL_OES_packed_depth_stencil GL_OES_rgb8_rgba8 GL_OES_standard_derivatives GL_OES_surfaceless_context GL_OES_texture_border_clamp GL_OES_texture_float GL_OES_texture_float_linear GL_OES_texture_half_float GL_OES_texture_half_float_linear GL_OES_texture_npot GL_OES_texture_stencil8 GL_OES_vertex_array_object GL_OVR_multiview GL_OVR_multiview2 GL_WEBGL_video_texture 
WebGL 1 Extensions	ANGLE_instanced_arrays EXT_blend_minmax EXT_color_buffer_half_float EXT_float_blend EXT_frag_depth EXT_shader_texture_lod EXT_sRGB EXT_texture_compression_bptc EXT_texture_compression_rgtc EXT_texture_filter_anisotropic MOZ_debug OES_element_index_uint OES_fbo_render_mipmap OES_standard_derivatives OES_texture_float OES_texture_float_linear OES_texture_half_float OES_texture_half_float_linear OES_vertex_array_object WEBGL_color_buffer_float WEBGL_compressed_texture_s3tc WEBGL_compressed_texture_s3tc_srgb WEBGL_debug_renderer_info WEBGL_debug_shaders WEBGL_depth_texture WEBGL_draw_buffers WEBGL_lose_context WEBGL_provoking_vertex
WebGL 2 Driver WSI Info	outOfProcess: false
inProcess: true
EGL_VENDOR: Google Inc. (NVIDIA)
EGL_VERSION: 1.5 (ANGLE 2.1.19739 git hash: 419cd2c3213b)
EGL_EXTENSIONS: EGL_EXT_create_context_robustness EGL_ANGLE_d3d_share_handle_client_buffer EGL_ANGLE_d3d_texture_client_buffer EGL_ANGLE_surface_d3d_texture_2d_share_handle EGL_ANGLE_query_surface_pointer EGL_ANGLE_window_fixed_size EGL_ANGLE_keyed_mutex EGL_ANGLE_surface_orientation EGL_ANGLE_direct_composition EGL_ANGLE_windows_ui_composition EGL_NV_post_sub_buffer EGL_KHR_create_context EGL_KHR_image EGL_KHR_image_base EGL_KHR_gl_texture_2D_image EGL_KHR_gl_texture_cubemap_image EGL_KHR_gl_renderbuffer_image EGL_KHR_get_all_proc_addresses EGL_KHR_stream EGL_KHR_stream_consumer_gltexture EGL_NV_stream_consumer_gltexture_yuv EGL_ANGLE_stream_producer_d3d_texture EGL_ANGLE_create_context_webgl_compatibility EGL_CHROMIUM_create_context_bind_generates_resource EGL_CHROMIUM_sync_control EGL_EXT_pixel_format_float EGL_KHR_surfaceless_context EGL_ANGLE_display_texture_share_group EGL_ANGLE_display_semaphore_share_group EGL_ANGLE_create_context_client_arrays EGL_ANGLE_program_cache_control EGL_ANGLE_robust_resource_initialization EGL_ANGLE_create_context_extensions_enabled EGL_ANDROID_blob_cache EGL_ANDROID_recordable EGL_ANGLE_image_d3d11_texture EGL_ANGLE_create_context_backwards_compatible EGL_KHR_no_config_context EGL_KHR_create_context_no_error EGL_KHR_reusable_sync 
EGL_EXTENSIONS(nullptr): EGL_EXT_client_extensions EGL_EXT_device_query EGL_EXT_platform_base EGL_EXT_platform_device EGL_ANGLE_platform_angle EGL_ANGLE_platform_angle_d3d EGL_ANGLE_platform_angle_d3d11on12 EGL_ANGLE_platform_angle_device_id EGL_ANGLE_device_creation EGL_ANGLE_device_creation_d3d11 EGL_ANGLE_experimental_present_path EGL_KHR_client_get_all_proc_addresses EGL_KHR_debug EGL_ANGLE_feature_control 
WebGL 2 Driver Renderer	Google Inc. (NVIDIA) -- ANGLE (NVIDIA, NVIDIA GeForce RTX 4080 Direct3D11 vs_5_0 ps_5_0, D3D11-32.0.15.7216)
WebGL 2 Driver Version	OpenGL ES 3.0.0 (ANGLE 2.1.19739 git hash: 419cd2c3213b)
WebGL 2 Driver Extensions	GL_AMD_performance_monitor GL_ANGLE_base_vertex_base_instance GL_ANGLE_base_vertex_base_instance_shader_builtin GL_ANGLE_client_arrays GL_ANGLE_copy_texture_3d GL_ANGLE_depth_texture GL_ANGLE_framebuffer_blit GL_ANGLE_framebuffer_multisample GL_ANGLE_get_serialized_context_string GL_ANGLE_get_tex_level_parameter GL_ANGLE_instanced_arrays GL_ANGLE_lossy_etc_decode GL_ANGLE_memory_size GL_ANGLE_multi_draw GL_ANGLE_multiview_multisample GL_ANGLE_pack_reverse_row_order GL_ANGLE_program_cache_control GL_ANGLE_provoking_vertex GL_ANGLE_request_extension GL_ANGLE_robust_client_memory GL_ANGLE_texture_compression_dxt3 GL_ANGLE_texture_compression_dxt5 GL_ANGLE_texture_multisample GL_ANGLE_texture_usage GL_ANGLE_translated_shader_source GL_CHROMIUM_bind_generates_resource GL_CHROMIUM_bind_uniform_location GL_CHROMIUM_copy_compressed_texture GL_CHROMIUM_copy_texture GL_CHROMIUM_lose_context GL_CHROMIUM_sync_query GL_EXT_EGL_image_external_wrap_modes GL_EXT_base_instance GL_EXT_blend_func_extended GL_EXT_blend_minmax GL_EXT_clip_control GL_EXT_color_buffer_float GL_EXT_color_buffer_half_float GL_EXT_debug_label GL_EXT_debug_marker GL_EXT_discard_framebuffer GL_EXT_disjoint_timer_query GL_EXT_draw_buffers GL_EXT_draw_buffers_indexed GL_EXT_draw_elements_base_vertex GL_EXT_float_blend GL_EXT_frag_depth GL_EXT_instanced_arrays GL_EXT_map_buffer_range GL_EXT_multi_draw_indirect GL_EXT_multisampled_render_to_texture GL_EXT_occlusion_query_boolean GL_EXT_read_format_bgra GL_EXT_robustness GL_EXT_sRGB GL_EXT_shader_texture_lod GL_EXT_texture_compression_bptc GL_EXT_texture_compression_dxt1 GL_EXT_texture_compression_rgtc GL_EXT_texture_compression_s3tc_srgb GL_EXT_texture_filter_anisotropic GL_EXT_texture_format_BGRA8888 GL_EXT_texture_norm16 GL_EXT_texture_rg GL_EXT_texture_storage GL_EXT_texture_type_2_10_10_10_REV GL_EXT_unpack_subimage GL_KHR_debug GL_KHR_parallel_shader_compile GL_KHR_robust_buffer_access_behavior GL_NV_EGL_stream_consumer_external GL_NV_fence GL_NV_framebuffer_blit GL_NV_pack_subimage GL_NV_pixel_buffer_object GL_OES_EGL_image GL_OES_EGL_image_external GL_OES_EGL_image_external_essl3 GL_OES_compressed_EAC_R11_signed_texture GL_OES_compressed_EAC_R11_unsigned_texture GL_OES_compressed_EAC_RG11_signed_texture GL_OES_compressed_EAC_RG11_unsigned_texture GL_OES_compressed_ETC2_RGB8_texture GL_OES_compressed_ETC2_RGBA8_texture GL_OES_compressed_ETC2_punchthroughA_RGBA8_texture GL_OES_compressed_ETC2_punchthroughA_sRGB8_alpha_texture GL_OES_compressed_ETC2_sRGB8_alpha8_texture GL_OES_compressed_ETC2_sRGB8_texture GL_OES_depth24 GL_OES_depth32 GL_OES_draw_buffers_indexed GL_OES_draw_elements_base_vertex GL_OES_element_index_uint GL_OES_fbo_render_mipmap GL_OES_get_program_binary GL_OES_mapbuffer GL_OES_packed_depth_stencil GL_OES_rgb8_rgba8 GL_OES_standard_derivatives GL_OES_surfaceless_context GL_OES_texture_border_clamp GL_OES_texture_float GL_OES_texture_float_linear GL_OES_texture_half_float GL_OES_texture_half_float_linear GL_OES_texture_npot GL_OES_texture_stencil8 GL_OES_vertex_array_object GL_OVR_multiview GL_OVR_multiview2 GL_WEBGL_video_texture 
WebGL 2 Extensions	EXT_color_buffer_float EXT_float_blend EXT_texture_compression_bptc EXT_texture_compression_rgtc EXT_texture_filter_anisotropic MOZ_debug OES_draw_buffers_indexed OES_texture_float_linear OVR_multiview2 WEBGL_compressed_texture_s3tc WEBGL_compressed_texture_s3tc_srgb WEBGL_debug_renderer_info WEBGL_debug_shaders WEBGL_lose_context WEBGL_provoking_vertex
Target Frame Rate	60
WebGPU Default Adapter	{
  "navigator.gpu.requestAdapter({})": {
    "info": {
      "architecture": "",
      "description": "",
      "device": "",
      "isFallbackAdapter": false,
      "subgroupMaxSize": 128,
      "subgroupMinSize": 4,
      "vendor": "",
      "wgpuBackend": "Dx12",
      "wgpuDevice": 9988,
      "wgpuDeviceType": "DiscreteGpu",
      "wgpuDriver": "32.0.15.7216",
      "wgpuDriverInfo": "",
      "wgpuName": "NVIDIA GeForce RTX 4080",
      "wgpuVendor": 4318
    },
    "features": [
      "bgra8unorm-storage",
      "core-features-and-limits",
      "depth-clip-control",
      "depth32float-stencil8",
      "float32-filterable",
      "indirect-first-instance",
      "rg11b10ufloat-renderable",
      "shader-f16",
      "texture-compression-bc",
      "texture-compression-bc-sliced-3d",
      "timestamp-query"
    ],
    "limits": {
      "maxBindGroups": 8,
      "maxBindGroupsPlusVertexBuffers": 24,
      "maxBindingsPerBindGroup": 65535,
      "maxBufferSize": 1073741824,
      "maxColorAttachmentBytesPerSample": 32,
      "maxColorAttachments": 8,
      "maxComputeInvocationsPerWorkgroup": 768,
      "maxComputeWorkgroupSizeX": 1024,
      "maxComputeWorkgroupSizeY": 1024,
      "maxComputeWorkgroupSizeZ": 64,
      "maxComputeWorkgroupStorageSize": 32768,
      "maxComputeWorkgroupsPerDimension": 65535,
      "maxDynamicStorageBuffersPerPipelineLayout": 4,
      "maxDynamicUniformBuffersPerPipelineLayout": 8,
      "maxInterStageShaderVariables": 16,
      "maxSampledTexturesPerShaderStage": 64,
      "maxSamplersPerShaderStage": 64,
      "maxStorageBufferBindingSize": 1073741824,
      "maxStorageBuffersPerShaderStage": 64,
      "maxStorageTexturesPerShaderStage": 64,
      "maxTextureArrayLayers": 2048,
      "maxTextureDimension1D": 16384,
      "maxTextureDimension2D": 16384,
      "maxTextureDimension3D": 2048,
      "maxUniformBufferBindingSize": 65536,
      "maxUniformBuffersPerShaderStage": 64,
      "maxVertexAttributes": 32,
      "maxVertexBufferArrayStride": 2048,
      "maxVertexBuffers": 16,
      "minStorageBufferOffsetAlignment": 32,
      "minUniformBufferOffsetAlignment": 256
    }
  }
}
WebGPU Fallback Adapter	{
  "navigator.gpu.requestAdapter({\"forceFallbackAdapter\":true})": {
    "info": {
      "architecture": "",
      "description": "",
      "device": "",
      "isFallbackAdapter": true,
      "subgroupMaxSize": 128,
      "subgroupMinSize": 4,
      "vendor": "",
      "wgpuBackend": "Dx12",
      "wgpuDevice": 140,
      "wgpuDeviceType": "Cpu",
      "wgpuDriver": "10.0.19041.5794",
      "wgpuDriverInfo": "",
      "wgpuName": "Microsoft Basic Render Driver",
      "wgpuVendor": 5140
    },
    "features": [
      "bgra8unorm-storage",
      "core-features-and-limits",
      "depth-clip-control",
      "depth32float-stencil8",
      "float32-filterable",
      "indirect-first-instance",
      "rg11b10ufloat-renderable",
      "shader-f16",
      "texture-compression-bc",
      "texture-compression-bc-sliced-3d",
      "timestamp-query"
    ],
    "limits": {
      "maxBindGroups": 8,
      "maxBindGroupsPlusVertexBuffers": 24,
      "maxBindingsPerBindGroup": 65535,
      "maxBufferSize": 1073741824,
      "maxColorAttachmentBytesPerSample": 32,
      "maxColorAttachments": 8,
      "maxComputeInvocationsPerWorkgroup": 768,
      "maxComputeWorkgroupSizeX": 1024,
      "maxComputeWorkgroupSizeY": 1024,
      "maxComputeWorkgroupSizeZ": 64,
      "maxComputeWorkgroupStorageSize": 32768,
      "maxComputeWorkgroupsPerDimension": 65535,
      "maxDynamicStorageBuffersPerPipelineLayout": 4,
      "maxDynamicUniformBuffersPerPipelineLayout": 8,
      "maxInterStageShaderVariables": 16,
      "maxSampledTexturesPerShaderStage": 64,
      "maxSamplersPerShaderStage": 64,
      "maxStorageBufferBindingSize": 1073741824,
      "maxStorageBuffersPerShaderStage": 64,
      "maxStorageTexturesPerShaderStage": 64,
      "maxTextureArrayLayers": 2048,
      "maxTextureDimension1D": 16384,
      "maxTextureDimension2D": 16384,
      "maxTextureDimension3D": 2048,
      "maxUniformBufferBindingSize": 65536,
      "maxUniformBuffersPerShaderStage": 64,
      "maxVertexAttributes": 32,
      "maxVertexBufferArrayStride": 2048,
      "maxVertexBuffers": 16,
      "minStorageBufferOffsetAlignment": 32,
      "minUniformBufferOffsetAlignment": 256
    }
  }
}
DirectWrite	true (10.0.19041.5794)
GPU #1
Active	Yes
Description	NVIDIA GeForce RTX 4080
Vendor ID	0x10de
Device ID	0x2704
Driver Version	32.0.15.7216
Driver Date	1-26-2025
Drivers	C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_1e8724cced6e93d4\nvldumdx.dll,C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_1e8724cced6e93d4\nvldumdx.dll,C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_1e8724cced6e93d4\nvldumdx.dll,C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_1e8724cced6e93d4\nvldumdx.dll C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_1e8724cced6e93d4\nvldumd.dll,C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_1e8724cced6e93d4\nvldumd.dll,C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_1e8724cced6e93d4\nvldumd.dll,C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_1e8724cced6e93d4\nvldumd.dll
Subsys ID	40be1458
RAM	16376
GPU #2
Active	No
RAM	0
Diagnostics
AzureCanvasBackend	skia
AzureCanvasBackend (UI Process)	skia
AzureContentBackend	skia
AzureContentBackend (UI Process)	skia
AzureFallbackCanvasBackend (UI Process)	skia
CMSOutputProfile	[removed because it was insanely long]
Display0	3840x2160@60Hz scales:1.000000|1.250000
Display1	2560x1440@60Hz scales:1.000000|1.000000
DisplayCount	2
HardwareStretching	both=1 window-only=0 full-screen-only=1 none=0 error=0
GPUProcessPid	43356
ClearType Parameters	\\.\DISPLAY1 [ Gamma: 1.8 Pixel Structure: RGB ClearType Level: 100 Enhanced Contrast: 50 ] \\.\DISPLAY2 [ Gamma: 1.8 Pixel Structure: RGB ClearType Level: 100 Enhanced Contrast: 50 ] 
Font Visibility Debug Info	Windows Platform
Decision Log
HW_COMPOSITING	
default	available		
user	force_enabled	Force-enabled by pref	
D3D11_COMPOSITING	
default	available		
DIRECT2D	
default	disabled	Disabled by default	Blocklisted; failure code FEATURE_FAILURE_DISABLED
D3D11_HW_ANGLE	
default	available		
GPU_PROCESS	
default	available		
user	force_enabled	User force-enabled via pref	
WEBRENDER	
default	available		
WEBRENDER_COMPOSITOR	
default	available		
runtime	unavailable	No DirectComposition usage	Blocklisted; failure code FEATURE_FAILURE_DCOMP_PREF_DISABLED
WEBRENDER_PARTIAL	
default	available		
WEBRENDER_SHADER_CACHE	
default	available		
WEBRENDER_OPTIMIZED_SHADERS	
default	available		
WEBRENDER_ANGLE	
default	available		
WEBRENDER_DCOMP_PRESENT	
default	available		
user	disabled	User disabled via pref	Blocklisted; failure code FEATURE_FAILURE_DCOMP_PREF_DISABLED
WEBRENDER_SCISSORED_CACHE_CLEARS	
default	available		
WEBGPU	
default	available		
WINDOW_OCCLUSION	
default	available		
HARDWARE_VIDEO_DECODING	
default	available		
HARDWARE_VIDEO_ENCODING	
default	available		
HW_DECODED_VIDEO_ZERO_COPY	
default	available		
VP8_HW_DECODE	
default	available		
VP9_HW_DECODE	
default	available		
REUSE_DECODER_DEVICE	
default	available		
BACKDROP_FILTER	
default	available		
CANVAS_RENDERER_THREAD	
default	available		
ACCELERATED_CANVAS2D	
default	available		
AV1_HW_DECODE	
default	available		
REMOTE_CANVAS	
default	available		
runtime	blocked	Disabled without Direct2D	Blocklisted; failure code FEATURE_REMOTE_CANVAS_NO_DIRECT2D
VP8_HW_ENCODE	
default	available		
VP9_HW_ENCODE	
default	available		
AV1_HW_ENCODE	
default	available		
WMF_HW_DRM	
default	available		
GL_NORM16_TEXTURES	
default	available		
Failure Log
(#0) 	CP+[GFX1-]: Managed to allocate after flush.
(#1) 	CP+[GFX1-]: Managed to allocate after flush.

rdo118

@schilpat
And the rest of the requested data:

Name 	Firefox
Version 	142.0
Build ID 	20250811145442
Distribution ID 	
Update Folder 	
C:\ProgramData\Mozilla-1de4eec8-1241-4177-a864-e594e8d1fb38\updates\CAD80AFE5C68F6E7
Update History 	
Update Channel 	release
User Agent 	Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:142.0) Gecko/20100101 Firefox/142.0
OS 	Windows_NT 10.0 19045
Application Binary 	C:\Program Files\[removed for privacy reasons]\firefox.exe
Profile Folder 	
[removed for privacy reasons]
Build Configuration 	about:buildconfig
Memory Use 	about:memory
Performance 	about:processes
Registered Service Workers 	about:serviceworkers
Third-party Modules 	about:third-party
Launcher Process 	Enabled
Multiprocess Windows 	1/1
Fission Windows 	1/1 Enabled by default
Remote Processes 	28
Enterprise Policies 	Active
Google Location Service Key 	Found
Google Safebrowsing Key 	Found
Mozilla Location Service Key 	Found
Safe Mode 	false
Memory Size (RAM) 	63,9 GB
Disk Space Available 	198 GB
Profiles 	about:profiles
Pointing Devices 	Mouse

schilpat

Hi @rdo118 , thank you for the information. That is really weird behaviour considering you are running on high-end HW. That might be a SW issue, from bad drivers, bad OS version, to bad browser version. The issue can affect only specific instructions/operations, which might result into a smooth demo scene but a laggy Windy.

Could you please try a different browser than Firefox? Ideally chrome-based. Thank you!

Alternatively, you could try updating your GPU drivers

rdo118

@schilpat
The problem is in Chrome as well (as I mentioned in my original thread https://community.windy.com/topic/41479/map-is-extremely-laggy-since-the-latest-update/2?_=1755883381930), but it doesn't look exactly the same. Firefox seems to perform the change (zooming in or out or moving a time step), then pause for half a second to a second with a very low-res version of the map, and then draw everything. Chrome seems to do a pause initially, then do the zoom or move, then draw quickly. It's not quite as slow as Firefox, but still much slower than normal, though when I say "normal", I mean how it used to be in Firefox. I detest Chrome and never use it other than for occasional sites that have Chrome-specific features and don't work in Firefox.

I'm on a slightly older driver due to compatibility issues. Nvidia has had a long string of drivers that have messed up a few things, which has made me wary of updating. But drivers from the beginning of this year shouldn't be too old for a modern website. My mobile hasn't had an update of any kind in over a year, and it works fine there.

Well, it was a good run. Maybe time to find an alternative. I've enjoyed Windy, but it's unusable now, and I'm reading between the lines that this is how it is going forward.

rdo118

@schilpat
I'm now on the latest GPU drivers. The laggy behavior is exactly the same.
Something is clearly wrong with your implementation, as this is the only site where this happens.

rdo118

Clearly, this is an issue they're actively ignoring. Either due to incompetence (i.e. "we've started using a function that we've implemented incorrectly but we don't know how to fix it") or because they think it's ok to break the site for a small number of users, as an "acceptable loss".

Wheats

@rdo118 being rude will help...sure try that, yeah.

rdo118

@Wheats They've shown that they don't care, so I'm not going to be nice at that point. They should at least be honest and state clearly that this is something that won't be fixed, and that they don't care. As of now, people could be fooled into thinking they will fix this and renew subscriptions but still be stuck with an unusable service.

Wheats

@rdo118
Catch more flies with honey than with vinegar.

My question is, with your higher end computer...why did you need to use graphics compatibility at all? I don't have a dedicated GPU and Windy runs fine.

Seems to me, that when you noticed a problem in the past but it went away when you turned on that setting is the day something went funky with how your setup communicates with the instructions/operations that Windy uses.

But I'm just a user who shouldn't even have replied in the first place lol

rdo118

@Wheats They're obviously using a feature that isn't well supported or that they have implemented it incorrectly (or both). The old compatible graphics mode eliminated the laggy issue that was introduced in an update a while ago (can't recall exactly when as the fix was quick and easy - then). They have now, in their infinite wisdom, removed that option, and so those of us who are affected are now stuck with a practically unusable version of Windy. My browsers (yes, this affects all of them, with completely different engines) are up to date, my operating system is up to date, my graphics drivers are up to date. The WebGL demo I was asked to run works perfectly. NO OTHER SITE misbehaves. It's blatantly obvious that they've messed up, but they ignore it. Fixing it could take some time, I fully understand that. But not even commenting or responding back with a status or future plan for a possible fix, or a decision to not fix as too few users are affected (which is what I assume is the case), is just pathetic and terrible customer service.

schilpat

@rdo118
Hi, apologies for not responding to the topic. I was on vacation. Regarding the problem you are experiencing, it is challenging for us to debug the issue, mainly because there are no obvious reasons why you should be experiencing such poor performance, considering your hardware.

So first, I have a few more questions:

Is the map laggy even when you are panning without loading new tiles - more specifically, whether the map seems smooth until new tiles are being loaded (lag spikes), or does it have bad frame times (bad fps) all the time?
Does this also happen in radar and satellite overlays?

And second, could you make us favor and perform a little investigation within chrome devtools - in Performance tab? Simply load Windy, click Record button in the left corner and then perform some interaction with the map (interaction you reported to us as being laggy), let's say for 5-10 seconds. After stopping the recording, look for tasks that took too long and that eventually caused dropped frames. Among these tasks can be e.g. readPixels, texImage2d, texSubImage2d... And send us a screenshot of the flamegraph (including the frames row for context), ideally with a detailed view of the lag spike.

E.g. like this:
Screenshot 2025-09-15 at 16.06.00.png

Here is a little guide on chrome flame graph. https://medium.com/slalom-blog/flame-graphs-in-chrome-devtools-a-guide-for-front-end-developers-b9503ff4a4d

Thank you for your patience and cooperation.

rdo118

@schilpat

This is all about loading stuff. When I zoom or pan or use the timeline scrub for forecasts, new tiles are being loaded, and that's where it all breaks down. It takes ages, and while the interface is waiting for the new tiles, everything is frozen. Just panning around very gently inside the tiny area where all the tiles have loaded already, is fine. No lag there.

I'm using Firefox, not Chrome. I did the equivalent thing in Firefox and there's nothing in the results any living being can make sense of. It's like a mega tetris with random colors. There are a few hundred different bits of code or procedure names plattered all over it, and that's simply impossible to compile into anything useful.

However, the latest update is about half as laggy as the current version at the time I created my first post. So something you've changed was in the right direction. It's still unbearably laggy, but there is a difference.

Here's the Firefox tetris:

And the equivalent in Chrome, quite possibly even worse than the Firefox one:

rdo118

I was mistaken. The improved performance seems to be caused by the performance recording process. Something that that process/mechanism is doing makes the site work slightly better while capturing performance data. Now that I tried to use the site normally, the lag was just as before. So, no improvement after all.

schilpat

@rdo118
Hi, thank you for the provided information. I had an idea of what the problem could be, and the first screenshot probably confirmed it - the readPixels function used within our forecast WebGL rendering pipeline. It is mandatory within our current pipeline, which was implemented many years ago based on WebGL1, and this approach was necessary and totally valid at that time. This function (gl.readPixels) can indeed be problematic; however, it is used with care and as little as possible. However, in case of using high-res screen(s), the performance could eventually degrade. To assure you, there were no changes in the pipeline in the last 3-4 years.

We are not going to do any modifications to the old pipeline since we are already working on a new one, which does not use any of these problematic functions at all. This will take some more time, so as a temporary solution, I can advise lowering your resolution (in case you are using multiple displays or e.g., a 4 K display) or setting browser zoom to e.g. 150-200% (in Firefox it is in the hamburger menu top-right).

Thank you for your patience.