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
- ScrollView speed is slower when entering Play mode
- UI Builder elements disappear and "Semantic - Unknown template name" error appears when changes to "Template" parameter are saved
- Renderers outside Light Probe hull use incorrect Ambient Probe values when "Renderer Light Probe Selection" is set to "Use Ambient Probe" and "Light Probes" on Mesh is set to "Blend Probes"
- ArgumentNullException error occurs when selecting a Camera in the Hierarchy with the Scene view open
- Clicking 'Open Editor Log' through the Console fails to open redirected Logs when relative Log files exist outside of the Project root
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.