Hi all,
today I tried to launch the Citadel XV,... but unfortunately i ran into a problem.
I just see the splash screen and then,.... black. I poked around for some hours and came to the following conclusion:
After looking into the start process with a debugger I saw first, that the AURA integration tents to freeze the hole process until Unity decides to kill it.
Ok, so disable the In-Game Lighting effects in Amoury Crate --> ok we're getting future now, but it still refused to start,.... strange.
Good, back to the debugger aaaand,.... huh. The process tried to call the D3D10Wrap.dll and hangs there until the heat death of the universe. Maybe a problem with the renderer? Foreced to start with DX11 and DX12 calls,.... it still wants this specific dll. Try to start it with Vulkan --> App doesn't know Vulkan, so it doesn't start at all. OpenGL --> same as Vulkan.
And here my knowledge is ending. Maybe someone can make up something out of this. It seems like the Citadel process is waiting of smth. and ones it's getting whatever it wants it would continue, but it don't get that "thing". Following are the last 3 lines out of the debugger, that seems to holding up the startup process. Happy guessing / suggesting 🙂
[aurasdk][AuraToken::InitMutex] Global\AuraSdkTokenMutex ERROR_ALREADY_EXISTS[aurasdk][AuraToken::requireToken] In.[aurasdk][RogAuraService::SetProfile] In.[aurasdk][RogAuraService::SetProfile] Out.
[aurasdk][AuraToken::switchToken] In.[aurasdk][AuraToken::switchToken] !m_IsAuraServiceProcess[aurasdk][guidToken::CheckPriority] In.[aurasdk][guidToken::CheckPriority] out.[aurasdk][AuraToken::switchToken] Out.
[aurasdk][AuraToken::requireToken] Out.ModLoad: 00007ffc`35b80000 00007ffc`3613a000 C:\WINDOWS\SYSTEM32\D3D10Warp.dll
