Search Issue Tracker
Fixed in 5.3.6
Votes
0
Found in
5.4.0b14
Issue ID
786972
Regression
No
Crashes Editor or standalone while DX11 unloads Resouces when AMD's Raptr software is running
Steps to reproduce Editor crash:
1. Download and open project
2. Open Player settings
3. Change graphics API from DirectX11 to DirectX9
4. Crash window opens. See the attached log "Editor.log".
Steps to reproduce Standalone crash:
1. Open same project
2. Build for Windows and run it
3. Notice game crashes after a few seconds. See the attached log "output_log.txt".
Notes:
Changing graphics API from DX9 to DX11 doesn't crash.
Workaround:
Exit Raptr (AMD Gaming Evolved App) before launching Unity Editor or standalone build.
Reproduced with Unity: 5.2.4f1, 5.3.0f1, 5.3.4p2, 5.4.0b14 versions.
Reproduced with Raptr (AMD Gaming Evolved App) 2.11.000 version.
Not reproduced Standalone build crash with 5.2.4f1, because multi-display feature appeared in 5.3 version.
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- [macOS] Editor window is not restored to previous position when launching the Editor and mouse cursor is on a different screen
- [Usability] Warning message in an Adaptive Probe Volume Component is not informative enough when Realtime Global Illumination is enabled
- Inspector for Adaptive Probe Volumes is not repainted when toggling Realtime Global Illumination setting in the Lighting Window
- Surface Inputs are not rendering when using the custom BaseShaderGUI
- Reflection Problem custom Cubemap loses its reference when HDR is enabled and the platform is switched
Add comment