https://bugs.documentfoundation.org/show_bug.cgi?id=129062
--- Comment #16 from R. Grafe <[email protected]> --- My solution at the moment: Enabled ForceSkiaRaster Important: After each change in LO start OS new, that was my fault in previous post. No LO process in taskmanager, but maybe something remains in windows cache, I think, and despite that I have disabled such behaviour as far as possible. Maybe it would be helpful when after installation of LO a clearly hint would given for enabling ForceSkiaRaster when LO menus run slow because of lacking hardware acceleration support on older machines? For new users of LO on windows it is surely frustrating, when they install LO based on recommendation and then LO runs slow in comparison to other software. The consequence could be, they go immediately back to MSO or install other Office SW and additionally this damages unnecessarily the reputation. That's why I posted my first comment above, it's frustrating when you always here from open source supporters, "use LO" and you make then right at the beginning a disappointing experience. This should not be. -- LO 26.2 (no hardware acceleration, greyed out ->) Windows 23H2, nearly naked with many portable SW, runs very fast, no problems with other software WDDM 2.6, no graphics driver update possible CPU Typ Mobile QuadCore (8 threads) AMD Ryzen 5 3500U, 3700 MHz RAM 16GB AMD Radeon(TM) Vega 8 Graphics (2 GB of RAM) -- You are receiving this mail because: You are the assignee for the bug.
