Open a new file, drop a camera comp, leave viewer open, then a null geo comp leave viewr open, drag null1 onto cam1, select “Lookat” as the parameter reference. then hang and eventual Vulcan Device Crash error popup if TdrDelay is low, if its high it just hangs for ever it seems.
If the viewers of those two COMPs are not visible when the drop > Lookat reference occurs all is well and I can then turn them back on and proceed just fine.
Yeah I can confirm I’m getting these TdrDelay / Vulkan Crash issues regularly enough, just while touch is running, seemingly for no apparent reason. I’m probably going to downgrade back a couple of official versions to develop with moving ahead! keep us in the loop
An update from my issues, i don’t see this on my desktop 3080, only on my older MSI max-q 2080 laptop, but after downgrading nvidia driver to 512.95 i at least don’t see this particular crash as described in my initial post, but haven’t switched back to the newest build to know for sure if the issue is less prevalent in general on the laptop.
Thanks, can you also tell me the exact model of your laptop? I’m curious if it has an integrated Intel or AMD GPU as well. Trying to get a machine to reproduce this.
Hello friends, did you happen to find a resolution to this issue? I have the same GPU and I am experiencing this vulcan device crash when trying to link chop data to parameters of other operators.