Search Issue Tracker
Fixed
Votes
0
Found in
2019.4
2019.4.3f1
2020.1
Issue ID
1265284
Regression
No
Faraway objects can be seen through walls when DirectX11 and Feature Level 10.0 is used at runtime
How to reproduce:
1. Open the user's attached project "UWP_BugReport.zip"
2. In Build Settings, set the Platform to PC, Mac & Linux Standalone and the Target Platform to Windows
3. Build the project
4. Open Command Prompt and navigate to the folder with the newly built project in it
5. Launch the project by entering the following command in Command Prompt: "Tri6 Infinite.exe" -force-feature-level-10-0
Expected results: only the track that Main Camera is in can be seen (see "expected.png")
Actual results: walls of other tracks can be seen through the walls of the track that Main Camera is in (see "actual.png")
Reproducible with: 2019.4.7f1, 2020.1.0b16
Not reproducible with: 2020.1.0f1, 2020.1.1f1, 2020.2.0a20
Could not test with: 2018.4.26f1 due to errors and broken shaders
Notes:
- The issue was initially reported to appear when the project is built with UWP Support and deployed on an Xbox One devkit, as with DirectX11, a higher feature level cannot be used on Xbox
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Mono Windows Builds don't produce full log callstacks when generating logs
- AssetBundles fail to load when running in Built Players for Mobile Devices
- UI elements with text gets bigger and grey when Player window is moved to another screen with different resolution
- System name accepts multiline text but crops it on confirmation, duplicates input, and shrinks the field when empty
- UI element scale and position are wrong in project build when DRS is changed with HDR and Software Dynamic Resolution enabled
Add comment