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
- Enabling “Editor Extension Authoring” in UI Builder doesn’t dirty the document and saving with shortcut doesn’t persist the state
- WebRequest.Create() function fails with "URI prefix is not recognized" errors when the project is built for Linux Standalone or Windows Dedicated Server
- “GUIStyle” and “NullReferenceException” errors thrown in the Console when opening Object Field during script compilation
- Reflections are visible on objects without Recursive Rendering when viewed through transparent parts of another object with Recursive Rendering and Alpha Clipping enabled
- Visual artifacts appear when using "clip" method in custom shader and running on GLES
Add comment