Yet another "Shroud of the Apocrea" crash

Keine Antworten
Cydalone

Hello,
I'd waited eagerly to play the "Shroud of the Apocrea" missions, but each time the game crashes within dozens of seconds.
I'm playing the stand-alone version of Spiral Knights (i.e. neither on a browser nor on Steam) on Win10, 8GB of RAM, Intel Core i5, NVIDIA GeFOrce GTX 1050,... with the included Java Virtual Machine for 32-bits.
So I followed several guides to upgrade the JRE to 64-bits, in vain. I did not even have the luxury to try various "extra.txt" tweaks. Here are some samples of the various crashes I still have:
[barely loaded the splash screen]
2021/05/01 07:45:26:873 WARNING K$a.b: Failed to bind clip [key=com.threerings.openal.l@2fca16c2:sound/feedback/chat_open.ogg, errno=40961]
[black screen then crash]
2021/05/01 08:33:37:455 INFO K$a.b: Resetting video due to like issue with startup count.
2021/05/01 08:33:38:514 INFO ControllerEnvironment.log: Failed to initialize device HIDI2C Device because of: java.io.IOException: Failed to acquire device (8007001e)
[freeze on login screen]
2021/05/01 08:35:48:437 INFOS m.a: Failed to find proxy settings in Windows registry [error=java.lang.UnsatisfiedLinkError: C:\Users\Cydalone\AppData\Roaming\Spiral Knights\jRegistryKey.dll: Can't load IA 32-bit .dll on a AMD 64-bit platform]
I could login only once, but then the game crashed when I tried to open the "missions" panel. Today I cannot even reproduce that step.

And here are the warnings I still have when playing on the 32-bits JRE:
2021/04/30 22:51:44:775 WARNING DefaultControllerEnvironment.getControllers: Found unknown Windows version: Windows NT (unknown)
2021/04/30 22:51:44:775 WARNING DefaultControllerEnvironment.getControllers: Attempting to use default windows plug-in.
2021/04/30 22:51:45:384 INFO ControllerEnvironment.log: Failed to initialize device HIDI2C Device because of: java.io.IOException: Failed to acquire device (8007001e)

Please, Grey Havens, can you consider upgrading the JRE you include in your package? because proposing a mission -already difficult per se- that systematically crashes your default setup is... awkward.
Thanks!