zxjinn Posted September 5, 2023 Posted September 5, 2023 (edited) Hello, I'm a new Affinity user. I installed Designer 2 and Photo 2 and unfortunately neither of them work. I've trawled the forums here for details on how to fix what I'm experiencing and unfortunately nothing sounds exactly like what I am encountering, and none of the fixes I've tried have worked. Let me go through what I did and what I'm seeing. But first, the system: Brand new install of Windows 10 LTSC (21H2), build 19044.3324 Hardware: Dell 3060 (SFF) Processor: Intel Core i5 8500T GPU: Intel UHD 630 Memory: 16GB Storage: 1TB NVME SSD Windows update says the system is fully up-to-date What I did: Downloaded the .exe version of both programs (Designer 2 and Photo 2), both are version 2.1.1 the msix installers were not recognized as anything runnable Installed both programs without changing any settings, ie they are installed to the default locations. No errors during install that I saw Ran Designer 2 and inputted my license information Where it went wrong: After launching Designer 2, I click New > Create and select any canvas of any size, or any Sample then click "Create" or "Open" (depending on the selection) The app will think for 1-5 second, then just disappear with no error What I've tried, that didn't work: Installed the latest Intel display driver The file was named 101.2125, but after being installed it says the graphics driver version is 31.0.101.2125 Booting Windows into Safe Mode Neither of the apps open at all in Safe Mode Running the app as an administrator Running the app with the `--no-ocl` flag Holding ctrl while the app is launching and disabling/resetting all kinds of settings Some specific settings I tried individually: disable hardware acceleration, deactivating affinity 2 apps (then later re-activating them) Deleting the %appdata%\Affinity folder Settings > Performance > Hardware acceleration (on or off, didn't matter) Some final thoughts and observations from my digging: One thing I noticed is that in Settings > Performance > Renderer, the list is empty with nothing to select In %appdata%\Affinity\Designer\2.0\CrashReports\attachments there was a file called attachment_Log.txt that had a few things in it, one relates to the my previous comment of not having a renderer: Quote [DXCore] Found 2 adapters Intel(R) UHD Graphics 630 Version: 30.0.100.9864 IsHardware: Yes Supports D3D12 Feature Level 12.0: Yes HardwareID: PCI\VEN_8086&DEV_3E92&SUBSYS_085C0000&REV_00 LUID: 0x10248 Microsoft Basic Render Driver Version: 10.0.19041.2788 IsHardware: No Supports D3D12 Feature Level 12.0: Yes HardwareID: PCI\VEN_1414&DEV_008C&SUBSYS_00000000&REV_00 LUID: 0x106A3 [DXGI] Enumerating adapters Intel(R) UHD Graphics 630 HardwareID: PCI\VEN_8086&DEV_3E92&SUBSYS_85C10280000&REV_00 LUID: 0x10248 Microsoft Basic Render Driver HardwareID: PCI\VEN_1414&DEV_008C&SUBSYS_00000000&REV_00 LUID: 0x106A3 [OpenCL] Found 1 platforms: Name: Intel(R) OpenCL HD Graphics Vendor: Intel(R) Corporation Version: OpenCL 3.0 [OpenCL] Found 1 devices for platform Intel(R) OpenCL HD Graphics: Intel(R) UHD Graphics 630 Vendor: Intel(R) Corporation Version: OpenCL 3.0 NEO Integrated: true Detachable: false Installed the other thing was the last two lines in the file, which made me think it was the cause of the crash but I actually have no idea Quote Wintab: Failed to load Wintab32.dll Wintab: Failed to create tablet context I was able to install Photo on another computer that is the same Windows version, Windows 10 LTSC (21H2), build 19044.3324, and it worked flawlessly On that same computer, the list of renderers looks complete: it has the GPU and WARP listed Looking in the Windows Event Viewer, I see 3 entries at the time of the crash (see attached) I've fiddled with this for a couple of hours and now I'm out of ideas. Any input for how to get this working would be much appreciated! Thank you affinity-designer-crash-windows-event-viewer.evtx Edited September 5, 2023 by zxjinn Quote
v_kyr Posted September 6, 2023 Posted September 6, 2023 2 hours ago, zxjinn said: ... Deleting the %appdata%\Affinity folder Settings > Performance > Hardware acceleration (on or off, didn't matter) ... Well as far as the app is installed & you run it, but the %appdata%\Affinity folder is none existent (hasn't been recreated), this can for sure give side-effects for the app behavior during it's runtime here. As certain settings are read/written also from files under that directory stucture. The performance settings XML file is here just one example. 2 hours ago, zxjinn said: the other thing was the last two lines in the file, which made me think it was the cause of the crash but I actually have no idea Quote Wintab: Failed to load Wintab32.dll Wintab: Failed to create tablet context That's what the EVTX dump file tells too, do you have any tablet drivers etc. installed (?) ... Quote ... Description: The process was terminated due to an unhandled exception. Exception Info: System.Runtime.InteropServices.SEHException at <Module>.Serif.Interop.Persona.UserInterface.DocumentRenderWindow.{ctor}(Serif.Interop.Persona.UserInterface.DocumentRenderWindow*, TabletContext*) at Serif.Interop.Persona.UserInterface.DocumentRenderControl.BuildWindowCore(System.Runtime.InteropServices.HandleRef) at System.Windows.Interop.HwndHost.BuildWindow(System.Runtime.InteropServices.HandleRef) at System.Windows.Interop.HwndHost.BuildOrReparentWindow() ... As you already messed around in the initial installation, you should uninstall the app completely and afterwards install it freshly/newly. Also make sure then that the %appdata%\Affinity folder has been correctly recreated. Here's the complete error dump backtrace of your EVTX file ... Quote Record 1 <?xml version="1.0" encoding="utf-8"?> <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event"> <System> <Provider Name=".NET Runtime"> </Provider> <EventID Qualifiers="0">1026</EventID> <Version>0</Version> <Level>2</Level> <Task>0</Task> <Opcode>0</Opcode> <Keywords>0x80000000000000</Keywords> <TimeCreated SystemTime="2023-09-05T16:44:26.815362Z"> </TimeCreated> <EventRecordID>1858</EventRecordID> <Correlation> </Correlation> <Execution ProcessID="0" ThreadID="0"> </Execution> <Channel>Application</Channel> <Computer>DESKTOP-ONU46G9</Computer> <Security> </Security> </System> <EventData> <Data>Application: Designer.exe Framework Version: v4.0.30319 Description: The process was terminated due to an unhandled exception. Exception Info: System.Runtime.InteropServices.SEHException at <Module>.Serif.Interop.Persona.UserInterface.DocumentRenderWindow.{ctor}(Serif.Interop.Persona.UserInterface.DocumentRenderWindow*, TabletContext*) at Serif.Interop.Persona.UserInterface.DocumentRenderControl.BuildWindowCore(System.Runtime.InteropServices.HandleRef) at System.Windows.Interop.HwndHost.BuildWindow(System.Runtime.InteropServices.HandleRef) at System.Windows.Interop.HwndHost.BuildOrReparentWindow() at System.Windows.Interop.HwndHost.OnSourceChanged(System.Object, System.Windows.SourceChangedEventArgs) at System.Windows.RoutedEventArgs.InvokeHandler(System.Delegate, System.Object) at System.Windows.RoutedEventHandlerInfo.InvokeHandler(System.Object, System.Windows.RoutedEventArgs) at System.Windows.EventRoute.InvokeHandlersImpl(System.Object, System.Windows.RoutedEventArgs, Boolean) at System.Windows.UIElement.RaiseEventImpl(System.Windows.DependencyObject, System.Windows.RoutedEventArgs) at System.Windows.PresentationSource.UpdateSourceOfElement(System.Windows.DependencyObject, System.Windows.DependencyObject, System.Windows.DependencyObject) at System.Windows.PresentationSource.OnVisualAncestorChanged(System.Windows.DependencyObject, System.Windows.Media.AncestorChangedEventArgs) at System.Windows.UIElement.OnVisualAncestorChanged(System.Object, System.Windows.Media.AncestorChangedEventArgs) at System.Windows.Media.Visual.ProcessAncestorChangedNotificationRecursive(System.Windows.DependencyObject, System.Windows.Media.AncestorChangedEventArgs) at System.Windows.Media.Visual.AddVisualChild(System.Windows.Media.Visual) at System.Windows.FrameworkElement.set_TemplateChild(System.Windows.UIElement) at System.Windows.Controls.ContentPresenter+UseContentTemplate.BuildVisualTree(System.Windows.FrameworkElement) at System.Windows.StyleHelper.ApplyTemplateContent(System.Windows.UncommonField`1<System.Collections.Specialized.HybridDictionary[]>, System.Windows.DependencyObject, System.Windows.FrameworkElementFactory, Int32, System.Collections.Specialized.HybridDictionary, System.Windows.FrameworkTemplate) at System.Windows.FrameworkTemplate.ApplyTemplateContent(System.Windows.UncommonField`1<System.Collections.Specialized.HybridDictionary[]>, System.Windows.FrameworkElement) at System.Windows.FrameworkElement.ApplyTemplate() at System.Windows.FrameworkElement.MeasureCore(System.Windows.Size) at System.Windows.UIElement.Measure(System.Windows.Size) at System.Windows.Controls.Grid.MeasureCell(Int32, Boolean) at System.Windows.Controls.Grid.MeasureCellsGroup(Int32, System.Windows.Size, Boolean, Boolean, Boolean ByRef) at System.Windows.Controls.Grid.MeasureOverride(System.Windows.Size) at System.Windows.FrameworkElement.MeasureCore(System.Windows.Size) at System.Windows.UIElement.Measure(System.Windows.Size) at System.Windows.Controls.Control.MeasureOverride(System.Windows.Size) at System.Windows.FrameworkElement.MeasureCore(System.Windows.Size) at System.Windows.UIElement.Measure(System.Windows.Size) at System.Windows.Controls.Grid.MeasureOverride(System.Windows.Size) at System.Windows.FrameworkElement.MeasureCore(System.Windows.Size) at System.Windows.UIElement.Measure(System.Windows.Size) at MS.Internal.Helper.MeasureElementWithSingleChild(System.Windows.UIElement, System.Windows.Size) at System.Windows.Controls.ContentPresenter.MeasureOverride(System.Windows.Size) at System.Windows.FrameworkElement.MeasureCore(System.Windows.Size) at System.Windows.UIElement.Measure(System.Windows.Size) at System.Windows.ContextLayoutManager.UpdateLayout() at System.Windows.ContextLayoutManager.UpdateLayoutCallback(System.Object) at System.Windows.Media.MediaContext.FireInvokeOnRenderCallbacks() at System.Windows.Media.MediaContext.RenderMessageHandlerCore(System.Object) at System.Windows.Media.MediaContext.RenderMessageHandler(System.Object) at System.Windows.Threading.ExceptionWrapper.InternalRealCall(System.Delegate, System.Object, Int32) at System.Windows.Threading.ExceptionWrapper.TryCatchWhen(System.Object, System.Delegate, System.Object, Int32, System.Delegate) at System.Windows.Threading.DispatcherOperation.InvokeImpl() at MS.Internal.CulturePreservingExecutionContext.CallbackWrapper(System.Object) at System.Threading.ExecutionContext.RunInternal(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean) at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean) at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object) at MS.Internal.CulturePreservingExecutionContext.Run(MS.Internal.CulturePreservingExecutionContext, System.Threading.ContextCallback, System.Object) at System.Windows.Threading.DispatcherOperation.Invoke() at System.Windows.Threading.Dispatcher.ProcessQueue() at System.Windows.Threading.Dispatcher.WndProcHook(IntPtr, Int32, IntPtr, IntPtr, Boolean ByRef) at MS.Win32.HwndWrapper.WndProc(IntPtr, Int32, IntPtr, IntPtr, Boolean ByRef) at MS.Win32.HwndSubclass.DispatcherCallbackOperation(System.Object) at System.Windows.Threading.ExceptionWrapper.InternalRealCall(System.Delegate, System.Object, Int32) at System.Windows.Threading.ExceptionWrapper.TryCatchWhen(System.Object, System.Delegate, System.Object, Int32, System.Delegate) at System.Windows.Threading.Dispatcher.LegacyInvokeImpl(System.Windows.Threading.DispatcherPriority, System.TimeSpan, System.Delegate, System.Object, Int32) at MS.Win32.HwndSubclass.SubclassWndProc(IntPtr, Int32, IntPtr, IntPtr) at MS.Win32.UnsafeNativeMethods.DispatchMessage(System.Windows.Interop.MSG ByRef) at System.Windows.Threading.Dispatcher.PushFrameImpl(System.Windows.Threading.DispatcherFrame) at System.Windows.Application.RunDispatcher(System.Object) at System.Windows.Application.RunInternal(System.Windows.Window) at Designer.Application.Main(System.String[]) </Data> <Binary></Binary> </EventData> </Event> Record 2 <?xml version="1.0" encoding="utf-8"?> <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event"> <System> <Provider Name="Application Error"> </Provider> <EventID Qualifiers="0">1000</EventID> <Version>0</Version> <Level>2</Level> <Task>100</Task> <Opcode>0</Opcode> <Keywords>0x80000000000000</Keywords> <TimeCreated SystemTime="2023-09-05T16:44:27.041541Z"> </TimeCreated> <EventRecordID>1859</EventRecordID> <Correlation> </Correlation> <Execution ProcessID="0" ThreadID="0"> </Execution> <Channel>Application</Channel> <Computer>DESKTOP-ONU46G9</Computer> <Security> </Security> </System> <EventData> <Data>Designer.exe,2.1.1.1847,6486f32a,KERNELBASE.dll,10.0.19041.3324,6967c799,c06d007e,000000000002cf19,1434,01d9e0177aadc0bb,C:\Program Files\Affinity\Designer 2\Designer.exe,C:\Windows\System32\KERNELBASE.dll,9ed14916-fb50-425c-8009-9ea3423db3e7,,</Data> <Binary></Binary> </EventData> </Event> Record 3 <?xml version="1.0" encoding="utf-8"?> <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event"> <System> <Provider Name="Windows Error Reporting"> </Provider> <EventID Qualifiers="0">1001</EventID> <Version>0</Version> <Level>4</Level> <Task>0</Task> <Opcode>0</Opcode> <Keywords>0x80000000000000</Keywords> <TimeCreated SystemTime="2023-09-05T16:44:29.702698Z"> </TimeCreated> <EventRecordID>1860</EventRecordID> <Correlation> </Correlation> <Execution ProcessID="0" ThreadID="0"> </Execution> <Channel>Application</Channel> <Computer>DESKTOP-ONU46G9</Computer> <Security> </Security> </System> <EventData> <Data>1211667807912112543,4,APPCRASH,Not available,0,Designer.exe,2.1.1.1847,6486f32a,KERNELBASE.dll,10.0.19041.3324,6967c799,c06d007e,000000000002cf19,,, \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER9CD3.tmp.dmp \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERA187.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERA197.tmp.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERA1A5.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERA1C5.tmp.txt,\\?\C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_Designer.exe_2a7f6d6017ced24c968eb7368df4f40109a3c83_44b36d8d_b37301a7-5368-411a-a7fc-d08146d135ea,,0,9ed14916-fb50-425c-8009-9ea3423db3e7,268435456,3124d431fe05b27c60d0b5739c60b19f,0</Data> <Binary></Binary> </EventData> </Event> 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
tau Posted September 6, 2023 Posted September 6, 2023 I'm seeing the same issue on MacOS this morning. All Affinity apps affected. Quote
Komatös Posted September 6, 2023 Posted September 6, 2023 @zxjinn Please dowload and install the latest .NET Framework (4.8.1) from Microsoft. https://dotnet.microsoft.com/en-us/download/dotnet-framework/net481 Quote MAC mini M4 | MacOS Sequoia 15.2 | 16 GB RAM | 256 GB SSD AMD Ryzen 7 5700X | INTEL Arc A770 LE 16 GB | 32 GB DDR4 3200MHz | Windows 11 Pro 24H2 (26100.2605) Affinity Suite V 2.5.7 & Beta 2.6 (latest) Interested in a free (selfhosted) PDF Solution? Have a look at Stirling PDF Ferengi Acquisition Rule No. 49: “A deal is a deal is a deal.”
v_kyr Posted September 6, 2023 Posted September 6, 2023 16 minutes ago, Komatös said: @zxjinn Please dowload and install the latest .NET Framework (4.8.1) from Microsoft. https://dotnet.microsoft.com/en-us/download/dotnet-framework/net481 Additinally you can always (pre)check the installed .Net framework versions via downloading some handy utility tools from GitHub ... How to: Determine which .NET Framework versions are installed DotNetVersions https://github.com/jmalarcon/DotNetVersions/releases/download/v1.1.1/DotNetVersions.zip DotNetVersionLister ... etc. 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
v_kyr Posted September 6, 2023 Posted September 6, 2023 11 hours ago, tau said: I'm seeing the same issue on MacOS this morning. All Affinity apps affected. You should make an own thread for your MacOS related problems, as the OP here uses Windows. - Further for macOS, depending on the OS version you use, crosscheck the Metal hardware accelaration settings and try out also a run via OpenGL instead of Metal computing. 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
zxjinn Posted September 6, 2023 Author Posted September 6, 2023 Thanks v_kyr and komatos for your replies, I'll try to address them here. I deleted the %appdata%\Affinity folder while debugging, but after I launched one of the apps and it re-created the folder, but still behaved the same (after re-licensing). I still don't think it's the cause of the problems, since the issue was happening the same before and after the folder deletion. I do have a small Wacom tablet in a drawer nearby, but to my knowledge it hasn't been plugged into this computer. It's not an accessory that is used very often, had it for 5+ years and it's been used maybe twice in that time. This should have been mentioned in my original post, but I have uninstalled the apps and re-installed them before, I did that after the new driver didn't fix it This is another thing that should have been mentioned in the original post, but I already checked the .NET version I have installed and it reports 4.8.09037 Things I'll try, in this order, and report back: Install the .NET Framework v4.8.1, just to ensure that's correct and everything Uninstall all Affinity apps and re-install them Plug in the Wacom tablet and make sure that works. Perhaps it was plugged in by accident and quickly unplugged so it didn't have time to get all the drivers installed? I am just grasping at straws on that one Quote
zxjinn Posted September 6, 2023 Author Posted September 6, 2023 Alright, here's what I did Installed the .NET framework v4.8.1 from your link above. However the registry still says it's the same version, 4.8.09037, so maybe they round the final number up? 🙂 Uninstalled both Designer 2 and Photo 2 Deleted the %appdata%\Affinity folder Checked the C:\Program Files\Affinity folder, I was going to delete it but it was already gone Reinstalled just Designer 2, version 2.1.1 from the exe installer Launch Designer 2. Re-license Still didn't work Then, on to the Wacom Tablet debugging path Find the Wacom tablet dongle, it was still plugged into the old decommissioned computer so that makes me fairly confident it was never accidentally plugged in to this new computer, but I can't be 100% certain Let Windows install whatever drivers it thinks are correct Wacom didn't work with default Windows drivers, Designer 2 still didn't launch successfully Find latest drivers for my Wacom device (Intuos PT S, aka CTH-480) and install them This still didn't make my Wacom device work, and when the Wacom app came up it said those drivers were not compatible with my old device So I uninstalled the latest drivers Find the old drivers for my Wacom device, v6.3.46-2 and install them Reboot and now.. Designer 2 opens and I can create files and otherwise edit files that I couldn't before. I haven't put it through its paces yet, but at least this problem is resolved. I also noticed in the Settings > Performance > Renderer, that list is now populated with what I thought it should have been from the get-go (see attached). I don't know why it thinks it needed an un-used and un-loved tablet device drivers to work 🤷♂️. Perhaps it's related to the LTSC version of Windows that is more bare-bones than a standard install? Maybe Windows LTSC leaves some required bits out that Affinity needs? I don't know, I'm not complaining, I'm glad that it's functional now. Thanks for your eyes and comments on my issue. I hope this helps someone else in the future. Quote
v_kyr Posted September 6, 2023 Posted September 6, 2023 28 minutes ago, zxjinn said: I don't know why it thinks it needed an un-used and un-loved tablet device drivers to work Well if a tablet driver was once initially installed, the system and Affinity apps are probably looking also to make use of that then. - However the error logs/dumps indicated at least here, that some tablet related problem did occured. 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
zxjinn Posted September 6, 2023 Author Posted September 6, 2023 Agreed. That's especially apparent since the other computer I was testing on would never have had the tablet near it, and it worked just fine on my first try, despite being similar in a lot of ways. Thanks again for your help @v_kyr and @Komatös! v_kyr 1 Quote
Komatös Posted September 6, 2023 Posted September 6, 2023 5 minutes ago, zxjinn said: Agreed. That's especially apparent since the other computer I was testing on would never have had the tablet near it, and it worked just fine on my first try, despite being similar in a lot of ways. Thanks again for your help @v_kyr and @Komatös! You are welcome! Quote MAC mini M4 | MacOS Sequoia 15.2 | 16 GB RAM | 256 GB SSD AMD Ryzen 7 5700X | INTEL Arc A770 LE 16 GB | 32 GB DDR4 3200MHz | Windows 11 Pro 24H2 (26100.2605) Affinity Suite V 2.5.7 & Beta 2.6 (latest) Interested in a free (selfhosted) PDF Solution? Have a look at Stirling PDF Ferengi Acquisition Rule No. 49: “A deal is a deal is a deal.”
lucashaley Posted September 6, 2023 Posted September 6, 2023 I'm having this same issue. I'll try the same steps, see if it works. What a drag Quote
abdulnasor Posted November 3, 2023 Posted November 3, 2023 I have same issue, I can't create/open document. Solved after updating wacom driver: https://www.wacom.com/en-us/support/product-support/drivers My laptop is thinkpad x1 yoga 2nd (touch & pen support) 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.