Search Issue Tracker
Fixed in 2019.3.X
Fixed in 2019.2.X
Votes
0
Found in
2019.2.0a9
2019.2.0b4
Issue ID
1159110
Regression
Yes
Crash on (nvoptix) optixQueryFunctionTable when opening project or lighting tab
Create a new project.
Close the editor.
Open the project with -force-vulkan.
=> Crashes the editor with the following stack trace:
0x00007FF922706BF7 (nvoptix) optixQueryFunctionTable
0x00007FF92269AC74 (nvoptix) optixQueryFunctionTable
0x00007FF798EC40E6 (Unity) optix::PostprocessingStageObj::destroy
0x00007FF798EBDDD4 (Unity) OptixDLDenoiser::DenoiserContext::DestroyContext
0x00007FF798EBB491 (Unity) OptixDLDenoiser::DenoiserContext::~DenoiserContext
0x00007FF798EBD641 (Unity) OptixDLDenoiser::DLDenoiserAvailable
On D3D11, opening the lighting settings or baking the lighting may trigger this crash if Optix is improperly supported.
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- There is no way to adjust the HDR Paper White value of the Unity Editor's interface, making it difficult/uncomfortable for some developers to work on very dark/bright scenes in HDR
- Animator window has a dropdown button that throws “MissingReferenceException” error on a new project when the previous project had a GameObject with an animation
- Animator State name overflows outside the visual box when the State has a long name
- UI Document file remains marked as Dirty after Undoing made changes
- Switching between UI Documents with different Canvas sizes marks the UXML file as dirty
Add comment