Search Issue Tracker
Won't Fix
Votes
1
Found in [Package]
4.10.0, 7.0.0
Issue ID
1172875
Regression
No
Changing VFX graph capacity to a high number results in Unity running slow, unrelated panels/windows artifacts, crash
How to reproduce:
1. Open attached project "VFXDisappear.zip" and scene "SampleScene" (a visual effect in the scene must be present)
2. In Hierarchy window, open "New VFX" Visual Effect
3. In Visual Effect window, change capacity to 9999999 and press enter (might need to change between 0 and 99999999 a few times)
4. Observe the Editor
Expected result: the Editor runs normally
Actual result: the Editor start to run slow, visually corrupting unrelated programs and crashing after some time
Reproducible with: 2018.4.5f1(4.10.0), 2019.1.13f1(5.16.1), 2019.2.0f1(6.9.1), 2019.3.0a11(7.0.0)
Could not test with: 2017.4 (HDRP was not yet implemented)
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
- Error “Shader error in 'YSCloudCover': call to 'tex3D' is ambiguous at Assets/YSCloudCoverText.shader(606) (on d3d11)“ is present when compiling tex3D shader with DXC
- Placeholder asset is not loaded with Advertisement Legacy sample when using the latest version of the package
- Addressables content build fails but the Player build is successful when building a development build
- Out-of-bounds memory access with multiple CanvasRenderers under a Canvas when using Mesh API
- Inspector tries to access file after it was deleted when the file was locked in Inspector window
Resolution Note:
we don't want to implement a hard limit (same with most areas in Unity, you can always stall/crash the editor if you push the hardware).
A visual cue will be provided with the upcoming error feedback to give users more info within the graph itself.