Search Issue Tracker
Fixed in 5.3.2
Votes
33
Found in
5.2.0f3
Issue ID
728349
Regression
No
[Crash/Image Effects] Using Noise and Grain image effect crashes windows standalone builds on GPUs that do not support DX11
Reproduction steps:
1. Create a new project
2. Import Effects package from standard assets
3. Attach Noise and Grain script to the camera
4. Build to Windows
5. Run the build on GPU that DOES NOT support DX11
- The game will crash right after the splash screen
Notes:
1. Used ATI Radeon HD 4770 to test (QA Physical Lab QAWIN8)
2. The build plays fine when unchecking "Auto Graphics API for Windows" in the Player Settings and moving Direct3D 9 up the list
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
- GPU utilization increases by 20% on Meta Quest headsets when Render Graph is enabled on 6000.0.16f1 and higher
- Value on Slider (Int) control in UI Builder displays as default when saving UI Document
- Color mismatch in UI Builders Library panel when the Editors theme is set to Light Mode
- [Android ] "AndroidJNI.ToBooleanArray" returns a random non-zero value instead of "IntPtr.Zero" when the method argument is null
- Non-HDR color picker opens when selecting material color with HDR enabled
jaywinyeah
Jan 06, 2016 18:38
Unity QA, you can repro this issue with a D3D11 video card by forcing the application to run as D3D10 feature level. Example command line:
testApp.exe -force-feature-level-10-0
EpicIndustries
Nov 19, 2015 17:28
I'm seeing this too. Solution is to force direct x 9 but that's obviously not ideal. Would love to see a fix for this in the next patch
GeraldOBBI
Nov 02, 2015 18:47
Ditto to this, we're seeing it on several test platforms using Windows 7 32-bit and Geforce 8800GTS GPUs.
Seeing it with 'Depth of Field' image effects from the default image effects package.
Chris_TerraTech
Oct 27, 2015 16:18
Yeah, we have this too with the Depth of Field effect (Unity and Standard Assets version 5.2.0f3).
Unfortunately this is pushing back our fortnightly release schedule :(
Metkis
Oct 22, 2015 08:30
Thought for sure 5.2.2 would fix this issue, but I'm still having it unfortunately. Running Windows 10.
ShizumaruRiya
Oct 16, 2015 14:16
Same problem here, Game used DOF and crashed on my GTX260 that built by v5.2.1p4, but fine by v5.0.x.
novaVision
Oct 16, 2015 11:43
Same trouble on Win10 build with Bloom, DOF added to camera
GiTS_
Sep 28, 2015 11:51
Also had this issue when using the "Depth of Field" image effect from the standard assets package in windows standalone. (Not the deprecated one)