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
- “+” button does nothing and has no functionality when clicked in Human Template "Bone Template" list
- Solid gray or black areas are present when using ShaderGraph with Custom Function nodes without manual reimport
- The Multiplayer Play mode tool doesn't see the list of Play Mode scenarios when using 6000.3.x
- Input field does not update when selecting the same input field after previous input was canceled
- No warning thrown when modifying array size while editing multiple objects
Add comment