Search Issue Tracker
Fixed in 5.3.3
Votes
10
Found in
5.3.0b1
Issue ID
733444
Regression
No
[DX9] Unity crashed in GfxDeviceD3D9::DrawBuffers due to HandleD3DDeviceLost when locking windows
To reproduce:
1. Open attached project
2. Run scene TestScene
3. Lock windows
4. Unlock windows
5. Crash in GfxDeviceD3D9::DrawBuffers (stack in editor logs)
From log:
andleD3DDeviceLost
HandleD3DDeviceLost: needs reset, doing it
FullResetD3DDevice
ResetD3DDevice
dev->Reset
D3D device reset failed [invalid call]
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Lightmaps are baked incorrectly for GameObjects when their Position is <=-2048 or >=2048 on any of the coordinates
- Sahder errors in Player when "Strict shader variant matching" is enabled and the rendering path is set to "Deferred"
- NullReferenceExceptions are being thrown when saving a ScriptableObject with an array of a type with a CustomPropertyDrawer that uses TrackPropertyValue
- Applied velocity is inconsistent when using Rigidbody AddForce() with ForceMode.VelocityChange
- Crash on AudioUtil_CUSTOM_HasAudioCallback when exiting Play Mode while the Inspector is displaying a GameObject with an empty script attached
Add comment