mwt Posted December 20, 2023 Posted December 20, 2023 3 minutes ago, Kamil B said: .NET fix tool didn't helped at all. That's nice. I support Affinity ideas since the Designer beta came out. Bought all 3 products to replace Adobe software... And the funny thing is that the Adobe CS 5.5 that I owned years ago is still working after so many years even on Windows 11... I know that this is not a modern software.. But right now, because of the Serif software don't want to run on Windows 11 - the only I can use. I even downgraded to Windows 10 just to check if Affinity can run on older OS - It can't. It doesn't run on current Windows 10 or Windows 11 fresh install. I wonder if they released a final update that broke it. Does affinity offer older v1 releases on the website? Quote
Kamil B Posted December 26, 2023 Posted December 26, 2023 On 12/20/2023 at 11:17 PM, mwt said: I wonder if they released a final update that broke it. Does affinity offer older v1 releases on the website? https://store.serif.com/en-us/update/windows/designer/1/ https://store.serif.com/en-us/update/windows/publisher/1/ https://store.serif.com/en-us/update/windows/photo/1/ I don't think so. It's more like They were using some .NET function that is not available right now in current .NET. Other versions can startup after start up with holding Crtl key and cleaning all data, but You need to do it every time You start Affinity 1 software. That is insane. Same behavior on Windows 10 (current version) and Windows 11 (current version) fresh installs. Thank You Serif. Your marketing was that this is not a subscription software... As We see right now it is. You just don't know when it will stop working and nobody from Affinity Team cares that people have issue with the 1st version of software. Quote
Kamil B Posted December 26, 2023 Posted December 26, 2023 i tried to install other .NET versions (all currently supported by Microsoft - 4.8.1; 6.0.25 and 8.0.0 none of them worked. The issue remains the same. Event log from Windows 10 is similar to Windows 11 : Application: Designer.exe Framework Version: v4.0.30319 Description: The process was terminated due to an unhandled exception. Exception Info: System.AccessViolationException at <Module>.GlyphsInspectorNode.MakeSample(GlyphsInspectorNode*, Kernel.Counted<Raster::Buffer<Raster::Red8,Raster::Green8,Raster::Blue8,Raster::Alpha8,Raster::X5> >*, Kernel.NonCounted<GlyphsInspector>*) at Serif.Interop.Persona.Data.Glyph.Render() at System.Threading.Tasks.Task`1[[System.__Canon, mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089]].InnerInvoke() at System.Threading.Tasks.Task.Execute() Exception Info: System.AggregateException at System.Threading.Tasks.Task`1[[System.__Canon, mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089]].GetResultCore(Boolean) at Serif.Interop.Persona.Data.Glyph.OnRenderComplete(System.Threading.Tasks.Task`1<System.Windows.Media.ImageSource>) at System.Threading.Tasks.Task.Execute() Exception Info: System.AggregateException at System.Threading.Tasks.TaskExceptionHolder.Finalize() As You can see there are 2 options either You buy v2 of the software or go for the other software from other company. The Affinity v1 experience and support (nobody from Affinity Team respond to this issue for days) made me to buy Corel Software. And I know that this is not maybe what I wanted. But this is what I get for cheap. I will get used to Paint Shop Pro 2023. Quote
v_kyr Posted December 27, 2023 Posted December 27, 2023 On 12/26/2023 at 8:45 PM, Kamil B said: Application: Designer.exe Framework Version: v4.0.30319 Description: The process was terminated due to an unhandled exception. Exception Info: System.AccessViolationException at <Module>.GlyphsInspectorNode.MakeSample(GlyphsInspectorNode*, Kernel.Counted<Raster::Buffer<Raster::Red8,Raster::Green8,Raster::Blue8,Raster::Alpha8,Raster::X5> >*, Kernel.NonCounted<GlyphsInspector>*) at Serif.Interop.Persona.Data.Glyph.Render() at System.Threading.Tasks.Task`1[[System.__Canon, mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089]].InnerInvoke() at System.Threading.Tasks.Task.Execute() Exception Info: System.AggregateException at System.Threading.Tasks.Task`1[[System.__Canon, mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089]].GetResultCore(Boolean) at Serif.Interop.Persona.Data.Glyph.OnRenderComplete(System.Threading.Tasks.Task`1<System.Windows.Media.ImageSource>) at System.Threading.Tasks.Task.Execute() Exception Info: System.AggregateException at System.Threading.Tasks.TaskExceptionHolder.Finalize() Seems to be a Glyph (aka font...) related problem here, as the exception occurs for ... Exception Info: System.AccessViolationException at <Module>.GlyphsInspectorNode.MakeSample(GlyphsInspectorNode*,Kernel.Counted<Raster::Buffer<Raster::Red8,Raster::Green8,Raster::Blue8,Raster::Alpha8,Raster::X5> >*, Kernel.NonCounted<GlyphsInspector>*) at Serif.Interop.Persona.Data.Glyph.Render() at System.Threading.Tasks.Task`1[[System.__Canon, mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089]].InnerInvoke() at System.Threading.Tasks.Task.Execute() ... so probably for some font no sample glyph (node) can be created as the app crashes then at that point. Does this happen when you open the Glyph Panel? Quote ☛ Affinity Designer 1.10.8 ◆ Affinity Photo 1.10.8 ◆ Affinity Publisher 1.10.8 ◆ OSX El Capitan ☛ Affinity V2.3 apps ◆ MacOS Sonoma 14.2 ◆ iPad OS 17.2
Kamil B Posted December 27, 2023 Posted December 27, 2023 No. This happens on the fresh install of current version of Windows 10/11 with the fresh installation of affinity software. Just when I try to open any of affinity app at all. I didn’t install any additional fonts or plugins. I can’t even open glyph panel because app doesn’t work at all. It crashes just after opening it. Quote
Kamil B Posted December 27, 2023 Posted December 27, 2023 59 minutes ago, v_kyr said: Seems to be a Glyph (aka font...) related problem here, as the exception occurs for ... Exception Info: System.AccessViolationException at <Module>.GlyphsInspectorNode.MakeSample(GlyphsInspectorNode*,Kernel.Counted<Raster::Buffer<Raster::Red8,Raster::Green8,Raster::Blue8,Raster::Alpha8,Raster::X5> >*, Kernel.NonCounted<GlyphsInspector>*) at Serif.Interop.Persona.Data.Glyph.Render() at System.Threading.Tasks.Task`1[[System.__Canon, mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089]].InnerInvoke() at System.Threading.Tasks.Task.Execute() ... so probably for some font no sample glyph (node) can be created as the app crashes then at that point. Does this happen when you open the Glyph Panel? No. This happens on the fresh install of current version of Windows 10/11 with the fresh installation of affinity software. Just when I try to open any of affinity app at all. I didn’t install any additional fonts or plugins. I can’t even open glyph panel because app doesn’t work at all. It crashes just after opening it. Quote
mwt Posted December 27, 2023 Posted December 27, 2023 1 hour ago, Kamil B said: No. This happens on the fresh install of current version of Windows 10/11 with the fresh installation of affinity software. Just when I try to open any of affinity app at all. I didn’t install any additional fonts or plugins. I can’t even open glyph panel because app doesn’t work at all. It crashes just after opening it. Same issue for me Quote
v_kyr Posted December 28, 2023 Posted December 28, 2023 13 hours ago, Kamil B said: No. This happens on the fresh install of current version of Windows 10/11 with the fresh installation of affinity software. Just when I try to open any of affinity app at all. Could be then system font scanning at app startup related, does ADe write an own crash report too or does it crash before doing so? For v2 apps ... For v1 apps ... Quote ☛ Affinity Designer 1.10.8 ◆ Affinity Photo 1.10.8 ◆ Affinity Publisher 1.10.8 ◆ OSX El Capitan ☛ Affinity V2.3 apps ◆ MacOS Sonoma 14.2 ◆ iPad OS 17.2
Kamil B Posted December 28, 2023 Posted December 28, 2023 2 hours ago, v_kyr said: Could be then system font scanning at app startup related, does ADe write an own crash report too or does it crash before doing so? For v2 apps ... For v1 apps ... I think that I know now what is the issue that causes this problems. OpenCL hardware acceleration. Especially OpenCL on Intel Graphics like Iris Xe or Arc. 13 hours ago, mwt said: Same issue for me @mwt You probably using integrated intel graphic card on 11th or higer intel CPU. Try to disable OpenCL in Affinity. Hope that this will resolve Your issues. You can use the .NET tool provided by @v_kyr from this post: Quote
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.