Is this Unreal Engine 4 or something? DXR is known not to work with that at the moment, and it's not super high on anyone's priority list right now.
I believe it is, but the crash occurs even with raytracing disabled.
On Sat, Feb 26, 2022 at 12:53 PM Philip Rebohle @.***>
wrote:
Is this Unreal Engine 4 or something? DXR is known not to work with that
at the moment.—
Reply to this email directly, view it on GitHub
https://github.com/HansKristian-Work/vkd3d-proton/issues/1018#issuecomment-1052600078,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AACB45XEWJZSHFS7NRPOPWLU5E4WHANCNFSM5PMLIS6Q
.
You are receiving this because you authored the thread.Message ID:
@.***>
@ILOVEPIE Friendly ping pong. Do you still have this issue today with never vkd3d-proton versions?
I'll get back to you on that, have to reinstall it.
@Blisto91 this is still crashing as far as I can tell.
But it gives a different error message now.
@ILOVEPIE Can you verify that this works now? I just tested with Proton Experimental bleeding edge without issue
@Blisto91 I'll check after I get back from work.
It seems to work now, but I can't tell if the ray tracing is actually working or not.
Comparing fps is usually a good indicator
Comparing fps is usually a good indicator
The GPU does show 99% utilization, so I assume it is.
The engine pops up a window with the error:
in proton experimental and 7.0, the unofficial GE fork of proton actually experiences a null dereference error instead.