Search Issue Tracker
Fixed
Fixed in 2.1.2
Votes
0
Found in [Package]
2.1.2
Issue ID
XRVOSB-74
Regression
No
VFX Graph effects start to flicker or disappear when the GameObjects are overlapping in the Scene and running on the VisionOS Player
How to reproduce:
1. Open the attached “IN-96604.zip” project
2. Build and Run
3. In the Player, observe the VFX effect going up from the projector that is tracking the moving “Car” GameObject
Expected result: Continuous playing of the VFX without issues
Actual result: Visible flickering is observed
Reproducible with: 2.0.4 (6000.0.42f1), 2.1.2 (6000.0.42f1, 6000.1.0b10)
Couldn’t test with: 1.3.11 (2022.3.60f1) - Compilation errors due to downgrading of package and usage of unsupported functions/methods for that version, 2.1.2 (6000.2.0a6) - VFX GameObjects not present in the Player
Reproducible on: Apple Vision Pro 2.3.1
Testing environment: macOS 15.3.1 (M3)
Notes:
- Not reproducible in the Editor and Standalone Player
- Using PolySpatial 2.0.4 the VFX column effect is no longer present in the Player, however the issue is observable with the projection effect in the same place in the Scene, reproduction video attached in the internal notes, showcasing the differences.
- Related Discussions Thread: [https://discussions.unity.com/t/vr-mode-flickering-problem-with-the-vfx-particles/1553226|https://discussions.unity.com/t/vr-mode-flickering-problem-with-the-vfx-particles/1553226|smart-link]
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
- Errors are logged when importing an asset at a path with Firebase
- Entering too big of a number in 2D Renderer Lightmode Tags freezes the Editor
- Crash on GUIManager::DoGUIEvent when focusing on the Game view window on a specific project
- Asset creation in the Project Browser is not always undone/inconsistent when the undo shortcut is pressed right after creating an asset
- JobTempAlloc memory leak warning is thrown when the Player is shut down
Resolution Note (fix version 2.1.2):
This will be fixed in Unity 6000.0.47f1/2022.3.62f1.