Search Issue Tracker
Fixed
Fixed in 0.6.3-exp.0
Votes
0
Found in [Package]
0.4.3-exp.0
Issue ID
AVPB-55
Regression
No
visionOS - PolySpatial Volume To World shader incorrect if Volume Camera Output Dimensions are not 1,1,1
How to reproduce:
1. Open the attached “visionOSTemplate-0.4.3_WorldPosition.zip” Project
2. Build the project for visionOS
3. Run the build in the Simulator
4. Switch between “Object space position” and “World space position”
5. Observe the changed Mesh Colors
6. In the Editor change the “Output Dimensions” on the “Volume Camera” to [1, 1, 1]
7. Build and run in the Simulator again
8. Observe the Mesh Colors
Expected result: Mesh Colors change depending on “object/world space positions” used
Actual result: Mesh Colors do not change
Reproducible with: 0.4.3 (2022.3.11f1)
Reproduced on: macOS 13.5 (M1)
Not reproduced on: No other environment tested
Notes:
- Testing was not done by CQA due to not having visionOS
- The user noted that the Shader Graph “WorldPositionDebug” shows more information regarding the issue
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- 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
- Graphics State Collection warm-up does not work when using with Addressables Shaders
- "Baked Shadow Radius" field is visible but inactive when when the Shadow Type is set to "Hard Shadows" under the Light Component
Add comment