Search Issue Tracker
By Design
Votes
0
Found in
2022.2.0a13
Issue ID
UUM-2877
Regression
No
Different behavior between UnityEditor and UTR observed when counting m_ResourceCreationThisFrameBytes
Steps to reproduce:
- Open Editor and run Tests/EditModeAndPlayModeTests/TextureStreaming project
- Observe GfxDeviceD3D11Base::FlushIfNeeded()
-> GetD3D11Context()->Flush() never actually gets called
-> so m_ResourceCreationThisFrameBytes never surpasses 1GB
- Now compare with running "perl utr.pl --suite=playmode --clean-library --testproject=Tests/EditModeAndPlayModeTests/TextureStreaming --debug"
- Again, observe GfxDeviceD3D11Base::FlushIfNeeded()
Expected result: same behavior, no actual manual flushing
Actual result: now we actually see the device getting flushed; running this way, m_ResourceCreationThisFrameBytes actually surpasses 1GB
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
- 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
Resolution Note:
UTR uses a different mode. It generates what is essentially a huge single frame. The flush is needed to avoid drivers crashing. As we cannot make UTR to actually tick frames, or EndBatchModeUpdates, we must do this or crash in the driver.