You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I wanted to share an observation regarding a well-known freeze when working with complex vector artwork in Affinity Designer under Wine. The console fills with repeated fixme:d2d:d2d_device_context_DrawGeometry Ignoring stroke style messages, and the application becomes unresponsive.
My use case: print-ready graphic design involving hundreds of vector paths (decorative filigree elements), distressed/textured fonts (e.g. Veneer), and group-level transparency — the kind of workload that reliably triggers the freeze.
Initially, I believed I had found a workaround using WineFix, but after further testing, it proved insufficient.
What I observed at first: after installing WineFix (via the ryzendew installer's "Patch install AffinityPluginLoader" option), the application seemed to remain responsive even under heavy vector load, despite the FIXME messages still appearing. I had isolated WineFix as the changing factor by toggling OpenCL and image quality settings, which had no effect.
However, extended use revealed that the freeze still ultimately occurs. While WineFix's patched d2d1.dll initially appeared to mitigate or delay the problem, it does not fully resolve the freeze triggered by this specific workload.
Environment:
Linux Mint 22.3, kernel 6.17, X11/Cinnamon
ThinkPad X13 Gen 2a, AMD Ryzen 5 Pro 5650U, integrated Radeon (Mesa radeonsi)
I wanted to report this observation in case the interaction between the patched d2d1.dll and this specific freeze provides any useful clues for debugging.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Hi,
I wanted to share an observation regarding a well-known freeze when working with complex vector artwork in Affinity Designer under Wine. The console fills with repeated fixme:d2d:d2d_device_context_DrawGeometry Ignoring stroke style messages, and the application becomes unresponsive.
My use case: print-ready graphic design involving hundreds of vector paths (decorative filigree elements), distressed/textured fonts (e.g. Veneer), and group-level transparency — the kind of workload that reliably triggers the freeze.
Initially, I believed I had found a workaround using WineFix, but after further testing, it proved insufficient.
What I observed at first: after installing WineFix (via the ryzendew installer's "Patch install AffinityPluginLoader" option), the application seemed to remain responsive even under heavy vector load, despite the FIXME messages still appearing. I had isolated WineFix as the changing factor by toggling OpenCL and image quality settings, which had no effect.
However, extended use revealed that the freeze still ultimately occurs. While WineFix's patched d2d1.dll initially appeared to mitigate or delay the problem, it does not fully resolve the freeze triggered by this specific workload.
Environment:
Linux Mint 22.3, kernel 6.17, X11/Cinnamon
ThinkPad X13 Gen 2a, AMD Ryzen 5 Pro 5650U, integrated Radeon (Mesa radeonsi)
Wine: ElementalWarrior build (via ryzendew curl installer)
Affinity v3 (unified install)
I wanted to report this observation in case the interaction between the patched d2d1.dll and this specific freeze provides any useful clues for debugging.
Beta Was this translation helpful? Give feedback.
All reactions