Description: In the recent dev builds Skia is locked on Windows platform and cannot be disabled. But this makes work virtually impossible as scrolling a sheet takes 1 second or more for even 1 row. Steps to Reproduce: I have a sheet containing 76 rows and columns up to P. It contains Unicode characters (extended Latin alphabet). Actual Results: Smooth scrolling of this sheet is impossible with Skia. In earlier builds when it was possible to disable Skia, the scrolling was fast. With Skia it takes up to 1 second per row to scroll. It is also very slow when the window is resized or maximized, taking more than a second to redraw. Expected Results: Smooth scrolling at the same speed as when Skia is disabled. Reproducible: Always User Profile Reset: No Additional Info: Version: 26.2.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: 1457699096a5f6b25f7a32582e5bdec9deeb0898 CPU threads: 4; OS: Windows 11 X86_64 (build 22631); UI render: Skia/Vulkan; VCL: win Locale: ru-RU (ru_RU); UI: ru-RU Calc: threaded
I can't see the issue with of without 'Force Skia' enable. Version: 26.2.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: 1457699096a5f6b25f7a32582e5bdec9deeb0898 CPU threads: 16; OS: Windows 11 X86_64 (build 26100); UI render: Skia/Vulkan; VCL: win Locale: en-US (es_ES); UI: en-US Calc: CL threaded Have you tested updating the graphics driver, directly from the vendor, instead of the Windows update?
Is it better, if you activate Tools - Options - LibreOffice - View - Force Skia software rendering?
(In reply to Buovjaga from comment #2) > Is it better, if you activate Tools - Options - LibreOffice - View - Force > Skia software rendering? No. With software Skia I lose subpixel font smoothing but in terms of performance, nothing is improved.
(In reply to m_a_riosv from comment #1) > I can't see the issue with of without 'Force Skia' enable. > > Version: 26.2.0.0.alpha0+ (X86_64) / LibreOffice Community > Build ID: 1457699096a5f6b25f7a32582e5bdec9deeb0898 > CPU threads: 16; OS: Windows 11 X86_64 (build 26100); UI render: > Skia/Vulkan; VCL: win > Locale: en-US (es_ES); UI: en-US > Calc: CL threaded > > Have you tested updating the graphics driver, directly from the vendor, > instead of the Windows update? Yes, I have the most recent graphics driver, from Intel.
Please post clip of the 'Display' panel from a run of dxdiag.exe, and copy paste the "Device Properties and Extensions:" segment from a run of vulkaninfo.exe: e.g. ================================= GPU0: VkPhysicalDeviceProperties: --------------------------- apiVersion = 1.4.303 (4210991) driverVersion = 576.40.0.0 (2416574464) vendorID = 0x10de deviceID = 0x2803 deviceType = PHYSICAL_DEVICE_TYPE_DISCRETE_GPU deviceName = NVIDIA GeForce RTX 4060 Ti pipelineCacheUUID = a552de6d-1faf-8ad5-bfbe-abbefffa0211
Created attachment 201713 [details] Dxdiag
Device Properties and Extensions: ================================= GPU0: VkPhysicalDeviceProperties: --------------------------- apiVersion = 4206807 (1.3.215) driverVersion = 1656895 (0x19483f) vendorID = 0x8086 deviceID = 0x5916 deviceType = PHYSICAL_DEVICE_TYPE_INTEGRATED_GPU deviceName = Intel(R) HD Graphics 620 pipelineCacheUUID = 0f3a0c3c-073f-3932-063f-053102350001
OK, drivers are current with Windows 11 WDDM3.1, so Vulkan support is likely correctly configured. Just would note that the available hw resources for this iGPU (Intel HD Graphics 620) is only 128M, with total system memory at 8Gb available shared memory will be constrained which would require swap (dead slow) on this 7th gen Intel CPU. Scrolling a populated calc sheet is a somewhat intense demand on the graphics processing. Probably more performant to avoid attempts to use skia/Vulkan hw accelerated rendering, and use checkbox on Tools -> Options -> View to enable skia software rendering. Compare the two modes and, for now, you could still disable the skia lib rendering and check GDI+ based rendering and check that. Though GDI+ rendering has recently been stripped out to refactor transparency support that GDI+ doesn't support.
(In reply to V Stuart Foote from comment #8) > Probably more performant to avoid attempts to use skia/Vulkan hw accelerated > rendering, and use checkbox on Tools -> Options -> View to enable skia > software rendering. > > Compare the two modes and, for now, you could still disable the skia lib > rendering and check GDI+ based rendering and check that. Though GDI+ > rendering has recently been stripped out to refactor transparency support > that GDI+ doesn't support. Comment 3 already tells us that software Skia doesn't help.
(In reply to V Stuart Foote from comment #8) > OK, drivers are current with Windows 11 WDDM3.1, so Vulkan support is likely > correctly configured. > > Just would note that the available hw resources for this iGPU (Intel HD > Graphics 620) is only 128M, with total system memory at 8Gb available shared > memory will be constrained which would require swap (dead slow) on this 7th > gen Intel CPU. No, I have 16GB of total memory available. The 8 GB is possibly the maximum video memory available to the video adapter at its request. > > Scrolling a populated calc sheet is a somewhat intense demand on the > graphics processing. > > Probably more performant to avoid attempts to use skia/Vulkan hw accelerated > rendering, and use checkbox on Tools -> Options -> View to enable skia > software rendering. > > Compare the two modes and, for now, you could still disable the skia lib > rendering and check GDI+ based rendering and check that. Though GDI+ > rendering has recently been stripped out to refactor transparency support > that GDI+ doesn't support. No difference in performance but I lose subpixel font smoothing with software Skia.
may be it's Win11 only problem?
(In reply to Roman Kuznetsov from comment #11) > may be it's Win11 only problem? It doesn't seem so, look at my comment#1
(In reply to m_a_riosv from comment #12) > (In reply to Roman Kuznetsov from comment #11) > > may be it's Win11 only problem? > > It doesn't seem so, look at my comment#1 Actually, I like it as a Win11 issue and hw/driver issue for WDDM support. Feature evolution as noted: https://en.wikipedia.org/wiki/Windows_Display_Driver_Model