Search Issue Tracker
By Design
Votes
4
Found in
5.6.0f3
Issue ID
905454
Regression
Yes
Unity Crash while loading GfxPluginVRWorks64.dll into Editor
To reproduce:
1. Download attached project
2. Open project
Actual result: Editor crashes before load while using VRWork Asset.
Expected result: Editor should load and not crash.
Reproduced in: 5.6.0f3. 5.6.0p4, 2017.0b4;
Not reproduced in: 5.5.3f1
Notes:
-2017 results in a silent crash(no bug reporter, no stack trace)
-
catox
Aug 02, 2017 10:37
unity2017.1.0f3 with the newest VRWorks SDK works fine.
But it seems two demos of Nvidia still use the older sdk, so the crash happend.
And I also find that it could be opened on a pc with GTX 1050, and always crash on a pc without GTX graphics card. -
efpkop
May 10, 2017 18:30
I ran into this as I first tried to import NVidia Viking Village. I thought it had to do with the items that were being imported, so I incrementally imported items (taking the top level folders step-wise from the import tree structure). I was able to import just fine most of the items. However,when I tried to import 'Lighting' and 'Materials' at the same time, the importer crashed. Is there something in one of these folders that is contributing to this crash?
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- [Android] The warning "Internal: JobTempAlloc has allocations that are more than the maximum lifespan of 4 frames old - this is not allowed and likely a leak" is displayed when ShaderVariantCollection.WarmUp is called
- RectangleContainsScreenPoint returns false for some points even when the points are in the rectangle
- [iOS] Stacked camera does not render when using post effects
- TextField cannot be edited in an extended Editor window when double-clicking it
- [VisionOS] visionos build do not add plugin or frameworks
Resolution Note (2017.1.0f3):
Nvidia's VRWorks is an external plugin that we have no control over and the crashes happen in their dlls. We have communicated the issue to their team but it is out of our hands to fix.