Search Issue Tracker
Fixed in 2020.2.X
Votes
0
Found in
2018.1
2018.2
2018.3
2018.4
2019.1
2019.2
2019.3
2019.3.0b12
2020.1
Issue ID
1204993
Regression
No
[GPU PLM] VRAM not released following a GPU PLM bake
Repro:
1.Download the attached repro project. Open using the Editor version above.
2. Ensure that we have enough texel density in Lighting Settings to require a juicy GPU bake
3. Ensure Progressive GPU is selected as lightmapper backend
4. Hit generate
Note:
Using a tool like GPU-Z it should be possible to see how much VRAM is being used by Unity during the bake. This is likely to be quite high as I have artificially pumped up the texel usage in my test project. If you've got the time, let the bake finish. Observe that once the bake has finished, Unity doe not release the VRAM used during the bake.
Expected:
Once the bake has finished, the amount of VRAM used by Unity should return to somewhere around what Unity was using before the bake was started. The amount used does not just include the additional VRAM required by the lightmaps now added to the Scene. Seems somewhere more in line with the buffers assigned by our OpenCL kernels. This will be a lot on real-world Scenes. Especially considering we frequently run out of memory. Not a lot will be left for Windows and I have observed really poor Windows performance following GPULM.
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- var VisionOSEDRHeadromm has a comma instead of a dot when building with Metal Rendering App Mode and local OS localization is set to German
- IAP Catalog remove product “x” and add product “+” buttons are not consistent with other remove and add buttons in the Editor
- Performance issues in Play Mode when quickly hovering the mouse cursor over Hierarchy GameObjects
- Frame Debugger displays incorrect output when FidelityFX Super Resolution or Spatial-Temporal Upscaler is used with Temporal Anti-aliasing or Subpixel Morphological Anti-aliasing
- The layout system is failing to correctly calculate or apply the height of the Japanese fallback font when the primary English font's metrics are used
Add comment