Hi there.
Have you tried making a apitrace? Or is it just an assumption that it won't work? I would be surprised if it allowed the dxvk files but not the apitrace ones
Hi there. Have you tried making a apitrace? Or is it just an assumption that it won't work? I would be surprised if it allowed the dxvk files but not the apitrace ones
Not 100% sure but game is being launched on windows and it works with default and if i do as it says to do for apitrace(so place its dlls in Binaries instead of DXVK) then i would be dumping state of D3D9 native renderer which works, and isn't apitrace of dxvk what im supposed to dump?
No in most cases that is fine as we just replay it with dxvk locally where it should hopefully reproduce then
No in most cases that is fine as we just replay it with dxvk locally where it should hopefully reproduce then
Okay managed to do a dump, is 7z compression okay?
If yes will upload it to gdrive soon
That is fine yes
The trace replays fine. No crashes with it.
Could be driver issue?
It dies after spawning cursor for me..
Could be anything, if the log is anything to go by we literally die during device creation, which is pretty much outside of our control at that point.
It's also extremely annoying to work with games that have literally been shut down already, so I'd honestly just suggest sticking to 2.4.1 if that works for you, I don't really see a good way for us to figure this out remotely.
I haven't been able to reproduce this in game either. I've started the same game version on Windows with both my Intel b580 and AMD rdna2 iGPU using dxvk 2.5.3. Also tried same driver version on AMD
I haven't been able to reproduce this in game either. I've started the same game version on Windows with both my Intel b580 and AMD rdna2 iGPU using dxvk 2.5.3. Also tried same driver version on AMD
Didn't amd branch-out polaris from rdna driver?
I also tried older driver 24.3.1 and it also fails.
From replaying using qapitrace i get something like this:
Probably last resort of rulling amd driver bug would be trying to run on linux/mesa but it ain't that easy so far.
I was messing around renderdoc and some d3dretrace cmd had some " a Vulkan feature bufferDeviceAddressCaptureReplay is not available"
@Kiciuk Could you as a test give this build a spin? https://github.com/doitsujin/dxvk/actions/runs/12750843593 It is the 2.5.3 release but made with a different compiler.
Just use the d3d9.dll as you would with a regular release and ignore the extra files.
@Kiciuk Friendly ping
@Kiciuk Friendly ping
Replay on both x32 and x64 qapitrace(windows) with replaced dlls still gives same 0xc00000005 exception.
I tried to replay it on linux(wine) with rules to use dll from binary folder and it was replaying, albeit i have no idea how to get HUD to show like on one from SS above.
@Kiciuk Could you give it another go with 2.6?
@Kiciuk Now 2.6.1 if you can try
@Kiciuk Now 2.6.1 if you can try
Still crashes on both Vega and Polaris with same error.
Weird thing is log on vega ends on enumeration of VK_EXT_extended_dynamic_state3 right before unsupported VK_EXT_fragment_shader_interlock
while polaris ends on VK_EXT_non_seamless_cube_map
Maybe it fails somewhere during extension enumeration?
Soon i will be switching to RDNA4(RX 9070XT) so i guess i will probably close issue.
d3d9.dllx1 2025-01
Old TERA Online client(UE3/UDK) crashes on launch after it spawn window and initialize cursor.
It appears to work with DXVK 2.4
Game is being launched with launcher and runs some kind of custom anti-cheat(afterburner doesn't show anything) so i have no idea how to attach RenderDoc or Apitrace so i cannot provide dumps.
In log files i also attached log from working 2.4 version it differs a bit it looks like.
System information
Log files
TERA_d3d9.log
TERA_d3d9 _dxvk_2_4.log