Status
None
Memory reporting runs automatically on every cook, so developers see a project’s memory against its limit as they work instead of only at publish.
The publish memory requirement now lives in the profiling tools, where it can also be run on demand, and any session launch or pushed change produces a new value. The memory thermometer is removed from running sessions, and the Game Performance report at the bottom of the editor flags a project that is over the limit. A per-asset digest shows which assets drive the total, and memory reads in real units - 300 MB in place of 100,000 units, with no change to the budget. It’s for developers at or near the limit who today find out only when a publish fails.
