Windows 11 ARM, Crash after Splashscreen <Module>.Raster.Hardware<Raster::DefaultImplementation>.GetHardwarePossible()

[User9375]

Hi,

my Affinity programs (2.5.3) cannot get past the splashscreen on Windows 11 (ARM). I tried both the msi as well as the msix. From the logs I suspect it has something to do with hardware acceleration. How can I disable it if I cannot get to the settings menu because the program crashed just before lauching?

 

Spoiler

Anwendung: Designer.exe
Frameworkversion: v4.0.30319
Beschreibung: Der Prozess wurde aufgrund einer unbehandelten Ausnahme beendet.
Ausnahmeinformationen: System.Runtime.InteropServices.SEHException
   bei <Module>.Raster.Hardware<Raster::DefaultImplementation>.GetHardwarePossible()
   bei Serif.Interop.Persona.Settings.PerformanceSettings.get_CanUseHardwareAcceleration()
   bei Serif.Interop.Persona.Settings.PerformanceSettings.get_UseHardwareAcceleration()
   bei Serif.Interop.Persona.Services.InteropService.Initialise()
   bei Serif.Interop.Persona.Application.OnServicesInitialised(Serif.Interop.Persona.Services.IServiceProvider)
   bei Serif.Affinity.Application+<OnServicesInitialised>d__100.MoveNext()
   bei System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
   bei System.Windows.Threading.ExceptionWrapper.InternalRealCall(System.Delegate, System.Object, Int32)
   bei System.Windows.Threading.ExceptionWrapper.TryCatchWhen(System.Object, System.Delegate, System.Object, Int32, System.Delegate)
   bei System.Windows.Threading.DispatcherOperation.InvokeImpl()
   bei MS.Internal.CulturePreservingExecutionContext.CallbackWrapper(System.Object)
   bei System.Threading.ExecutionContext.RunInternal(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
   bei System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
   bei System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object)
   bei MS.Internal.CulturePreservingExecutionContext.Run(MS.Internal.CulturePreservingExecutionContext, System.Threading.ContextCallback, System.Object)
   bei System.Windows.Threading.DispatcherOperation.Invoke()
   bei System.Windows.Threading.Dispatcher.ProcessQueue()
   bei System.Windows.Threading.Dispatcher.WndProcHook(IntPtr, Int32, IntPtr, IntPtr, Boolean ByRef)
   bei MS.Win32.HwndWrapper.WndProc(IntPtr, Int32, IntPtr, IntPtr, Boolean ByRef)
   bei MS.Win32.HwndSubclass.DispatcherCallbackOperation(System.Object)
   bei System.Windows.Threading.ExceptionWrapper.InternalRealCall(System.Delegate, System.Object, Int32)
   bei System.Windows.Threading.ExceptionWrapper.TryCatchWhen(System.Object, System.Delegate, System.Object, Int32, System.Delegate)
   bei System.Windows.Threading.Dispatcher.LegacyInvokeImpl(System.Windows.Threading.DispatcherPriority, System.TimeSpan, System.Delegate, System.Object, Int32)
   bei MS.Win32.HwndSubclass.SubclassWndProc(IntPtr, Int32, IntPtr, IntPtr)
   bei MS.Win32.UnsafeNativeMethods.DispatchMessage(System.Windows.Interop.MSG ByRef)
   bei System.Windows.Threading.Dispatcher.PushFrameImpl(System.Windows.Threading.DispatcherFrame)
   bei System.Windows.Application.RunDispatcher(System.Object)
   bei System.Windows.Application.RunInternal(System.Windows.Window)
   bei Designer.Application.Main(System.String[])

 

 

Edited July 30, 2024 by User9375

[Ron P.]

Welcome to the forums @User9375 

Try doing a Control Run up.

1. Press and HOLD the CTL key.
2. Launch the App still holding down the CTL key
3. When the Clear User Defaults window appears, check the box to the left of Disable Hardware Acceleration
4. The app should continue to launch after pressing the Clear button in the bottom-right.

See if they will launch normally. If not post back.

 

 

[User9375]

21 hours ago, Ron P. said:

Welcome to the forums @User9375 

Try doing a Control Run up.

1. Press and HOLD the CTL key.
2. Launch the App still holding down the CTL key
3. When the Clear User Defaults window appears, check the box to the left of Disable Hardware Acceleration
4. The app should continue to launch after pressing the Clear button in the bottom-right.

See if they will launch normally. If not post back.

 

 

Thanks, the dialog popped up and I could disable the hardware acceleration. Unfortunately, I still get a crash after the splashscreen. But this time, the error log is different. Any ideas?

Spoiler

Anwendung: Photo.exe
Frameworkversion: v4.0.30319
Beschreibung: Der Prozess wurde aufgrund einer unbehandelten Ausnahme beendet.
Ausnahmeinformationen: System.Runtime.InteropServices.SEHException
   bei <Module>.PersonaController.InitPersona(PersonaController*, Kernel.StringT<Kernel::TEncUtf8>*, Int32, Int32, Kernel.StringT<Kernel::TEncUtf8>*, Kernel.StringT<Kernel::TEncUtf8>*, Kernel.StringT<Kernel::TEncUtf8>*, Kernel.StringT<Kernel::TEncUtf8>*, Kernel.StringT<Kernel::TEncUtf8>*, Int32, Int32, Double, Boolean, Boolean, Boolean, Boolean, Boolean, Boolean, Boolean, Boolean, Boolean, Boolean, Kernel.Counted<Kernel::LockFileCreator>*, Kernel.Counted<MigrationPlatformData const >*, Boolean, Boolean, Boolean, Boolean)
   bei Serif.Interop.Persona.Services.InteropService.Initialise()
   bei Serif.Interop.Persona.Application.OnServicesInitialised(Serif.Interop.Persona.Services.IServiceProvider)
   bei Serif.Affinity.Application+<OnServicesInitialised>d__100.MoveNext()
   bei System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
   bei System.Windows.Threading.ExceptionWrapper.InternalRealCall(System.Delegate, System.Object, Int32)
   bei System.Windows.Threading.ExceptionWrapper.TryCatchWhen(System.Object, System.Delegate, System.Object, Int32, System.Delegate)
   bei System.Windows.Threading.DispatcherOperation.InvokeImpl()
   bei MS.Internal.CulturePreservingExecutionContext.CallbackWrapper(System.Object)
   bei System.Threading.ExecutionContext.RunInternal(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
   bei System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
   bei System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object)
   bei MS.Internal.CulturePreservingExecutionContext.Run(MS.Internal.CulturePreservingExecutionContext, System.Threading.ContextCallback, System.Object)
   bei System.Windows.Threading.DispatcherOperation.Invoke()
   bei System.Windows.Threading.Dispatcher.ProcessQueue()
   bei System.Windows.Threading.Dispatcher.WndProcHook(IntPtr, Int32, IntPtr, IntPtr, Boolean ByRef)
   bei MS.Win32.HwndWrapper.WndProc(IntPtr, Int32, IntPtr, IntPtr, Boolean ByRef)
   bei MS.Win32.HwndSubclass.DispatcherCallbackOperation(System.Object)
   bei System.Windows.Threading.ExceptionWrapper.InternalRealCall(System.Delegate, System.Object, Int32)
   bei System.Windows.Threading.ExceptionWrapper.TryCatchWhen(System.Object, System.Delegate, System.Object, Int32, System.Delegate)
   bei System.Windows.Threading.Dispatcher.LegacyInvokeImpl(System.Windows.Threading.DispatcherPriority, System.TimeSpan, System.Delegate, System.Object, Int32)
   bei MS.Win32.HwndSubclass.SubclassWndProc(IntPtr, Int32, IntPtr, IntPtr)
   bei MS.Win32.UnsafeNativeMethods.DispatchMessage(System.Windows.Interop.MSG ByRef)
   bei System.Windows.Threading.Dispatcher.PushFrameImpl(System.Windows.Threading.DispatcherFrame)
   bei System.Windows.Application.RunDispatcher(System.Object)
   bei System.Windows.Application.RunInternal(System.Windows.Window)
   bei Photo.Application.Main(System.String[])

 

 

Edited July 31, 2024 by User9375

[Ron P.]

The only other possibility may be updating your GPU drivers.

 

[User9375]

Thanks, but I'm running Affinity inside Parallels Pro on my MacBook Pro M3. So I guess despite DirectX 11.1 emulation is fully supported, Affinity is not compatible.

[Ron P.]

3 hours ago, User9375 said:

Thanks, but I'm running Affinity inside Parallels Pro on my MacBook Pro M3. So I guess despite DirectX 11.1 emulation is fully supported, Affinity is not compatible.

Ok, well don't know anything about Mac, someone, like Serif will have to provide further help.. Sorry..

[walt.farrell]

3 hours ago, User9375 said:

So I guess despite DirectX 11.1 emulation is fully supported, Affinity is not compatible.

DirectX 11 is certainly not enough for Hardware Acceleration (OpenCL) as that requires 12. 

But I would expect the application to run, just with that option disabled. 

Are you getting Crash reports? 

Or, if not, the Windows Event Logs might show something: 

 

There's also a log.txt file that should have useful info. 

It would be in %userprofile%\.affinity\designer\2.0 for an MSIX install or in %appdata%\affinity\designer\2.0 for an MSI/EXE install.

[User9375]

Yes, please see my previous post. Inside the spoilers, I posted the contents of the Window Log Events.

From what I can read, the crash comes either from 

<Module>.Raster.Hardware<Raster::DefaultImplementation>.GetHardwarePossible()

if hardware acceleration is enabled or from

PersonaController.InitPersona

when hardware acceleration is not enabled.

I guess we can only find out if someone from the dev team would try to start Affinity in Parallels Pro from any capable Mac device.

From the log.txt:

[2024-08-01T00:13:10.744+0200] Affinity Photo 2
[2024-08-01T00:13:10.744+0200] IsSandboxed: Yes
[2024-08-01T00:13:10.744+0200] AppDataPathForCurrentUser: C:\Users\admin\.affinity\Photo\2.0
[2024-08-01T00:13:10.744+0200] AppDataPathForCurrentUserPersisted: C:\Users\admin\.affinity\Photo\2.0
[2024-08-01T00:13:10.744+0200] AppDataPathForAllUsers: C:\ProgramData\Affinity\Photo\2.0 (Store)
[2024-08-01T00:13:10.744+0200] CommonDataPathForCurrentUser: C:\Users\admin\AppData\Local\Publishers\844sdzfcmm7k0\Affinity\Common\2.0 (Store)
[2024-08-01T00:13:10.744+0200] CommonDataPathForCurrentUserPersisted: C:\Users\admin\.affinity\Common\2.0
[2024-08-01T00:13:10.744+0200] CommonDataPathForCurrentUserPersistedBuildInvariant: C:\Users\admin\.affinity\Common\2.0
[2024-08-01T00:13:10.745+0200] CommonDataPathForAllUsers: C:\ProgramData\Affinity\Common\2.0 (Store)
[2024-08-01T00:13:10.745+0200] TempPathForCurrentUser: C:\Users\admin\.affinity\Photo\2.0\temp
[2024-08-01T00:13:11.139+0200] Looking for WebView2 installation
[2024-08-01T00:13:11.140+0200] 	Found WebView2 version 126.0.2592.113
[DXCore] Found 2 adapters
Parallels Display Adapter (WDDM)
	Version: 20.18.1941.54985
	IsHardware: Yes
	Supports D3D12 Feature Level 12.0: No
	HardwareID: PCI\VEN_5404C42&DEV_0000&SUBSYS_00000000&REV_00
	LUID: 0x66FD
Microsoft Basic Render Driver
	Version: 10.0.22621.3672
	IsHardware: No
	Supports D3D12 Feature Level 12.0: Yes
	HardwareID: PCI\VEN_1414&DEV_008C&SUBSYS_00000000&REV_00
	LUID: 0x6842
[DXGI] Enumerating adapters
Parallels Display Adapter (WDDM)
	HardwareID: PCI\VEN_5404C42&DEV_0000&SUBSYS_00000000&REV_00
	LUID: 0x66FD
Microsoft Basic Render Driver
	HardwareID: PCI\VEN_1414&DEV_008C&SUBSYS_00000000&REV_00
	LUID: 0x6842
[OpenCL] Found 1 platforms:
Name: OpenCLOn12
	Vendor: Microsoft
	Version: OpenCL 3.0 D3D12 Implementation
[OpenCL] Found 1 devices for platform OpenCLOn12:
Parallels Display Adapter (WDDM)
	Vendor: Microsoft
	Version: OpenCL 3.0 D3D12 Implementation

Edited August 1, 2024 by User9375

[walt.farrell]

10 hours ago, User9375 said:

Inside the spoilers, I posted the contents of the Window Log Events.

That is not as complete as the Windows Event Viewer would provide, though. And probably not as good as a Crash Report, if you're getting them. Thanks for that much, though.

And thanks for the log. Didn't help me, but the Serif staff may get something from it.

[NathanC]

Hi @User9375,

Can you send us a few more recent crash reports as well as the full log.txt file? Also, just to confirm are you using the ARM64 builds on this parallels machine?

Thanks 🙂

[User9375]

Thanks. Here are all files from the Photo folder. If you need more, please contact me.

Photo.zip

[NathanC]

Thanks, it doesn't look like the app is even getting as far as generating a standard crash report or even creating the reports folder so that does limit me a bit. I've checked your PerformancePreferences.xml and <UseHardwareAcceleration2> field is set to 'False' so I think we can rule out it being H/A related for now, but it still could be renderer related.

Could you confirm for me if you're running the x64 or the ARM64 version of the apps? Just need to be certain.

Could you also provide a copy of the Windows System and Application Event viewer logs? FAQ on saving these below.

Thanks

[User9375]

Yes I tried the ARM versions of Affinity. I tried the version from the Microsoft Store, as well as the MSIX and MSI. No luck.

Affinity crashes Application Errors.evtx

[NathanC]

Thanks, I've since confirmed that the ARM64 versions of the apps (Be it via the Microsoft store or the Affinity Store, MSIX or MSI/EXE) will trigger an app crash on startup when using a Parallels VM on a Silicon Mac, this is logged internally with the developers.

I would suggest removing all existing Affinity apps and then install Photo via the MSI/EXE (x64) installer and then see how it goes. If that works repeat the same for Designer and Publisher. Link to the direct download page is below.

https://store.serif.com/en-gb/update/windows/photo/2/

[User9375]

Thanks, unfortunately, the x64 Version also crashes instantly after the splashscreen. Disabling hardware acceleration does not help. So I'm waiting for a bug fix from Affinity and/or Parallels. Thank you in advance.

[walt.farrell]

On 8/1/2024 at 10:49 AM, NathanC said:

I've since confirmed that the ARM64 versions of the apps (Be it via the Microsoft store or the Affinity Store, MSIX or MSI/EXE) will trigger an app crash on startup when using a Parallels VM on a Silicon Mac, this is logged internally with the developers.

FYI, and FWIW, the Windows ARM-64 MSIX Affinity applications run for me in a Parallels VM on my M2 Macbook, though the ARM-64 MSI/EXE versions crash before the Splash screen is displayed.

[User9375]

I just found out if you do not have the OpenCL™, OpenGL® und Vulkan® Compatibility Pack from the Microsoft Store installed, Affinity does not crash.

I find this really strange since the official compatibility pack from Microsoft should enhance the stability of graphic intense software.

Quote

This compatibility pack allows more of your favorite OpenCL™, OpenGL®, and Vulkan® apps to run on a Windows 10 or Windows 11 PC that doesn't have these hardware drivers installed by default. If a DirectX 12 driver is installed, supported apps will run with hardware acceleration for better performance. This package supports apps that use OpenCL version 3.0 and earlier, OpenGL version 3.3 and earlier, and Vulkan version 1.2 and earlier. OpenGL apps using versions up to 4.6 may work as well.