Hey James,
Memreport is a tool that runs a bunch of console commands and groups their output together.
This makes it very hard to parse and use it’s output in a machine readable way.
As such we don’t have any visualization tools available and I would not recommend memreport as a primary tool to get memory usage going forward. Memory Insights is our primary tooling for this use-case and is actively developed and maintained.
Memory Insights right now provides mostly a per allocation view, or a per category (with LLM enabled) view of the memory usage, but we’re in the process of improving the instrumentation so individual allocations can be better associated with individual assets, too.
As for memreport, it’s not maintained as one single tool, instead each of the individual commands is owned by their respective teams. Many of those commands are legacy and not actively maintained itself.
There is a -csv parameter that will be forwarded to each of the commands run by memreport, but it is not handled by all commands.
Some of them will format their output in a csv compatible way if that option is given, but only some.
There’s also the option of creating a [MemReportCsvCommands] section in your Engine.ini to specify a list of commands that should each be written to their own .csv by memreport. That section is not present by default, but you could create it with the commands from the regular list that actually support csv output to get something more usable and machine readable (but still no nice visualization).
There is also the MemReportHelper command in UAT, which tries to extract some of the csv outputs from the combined memreport into individual csv. It was written for an internal project and is likely not maintained either (plus memreport can generate separate csvs by itself).
Hopefully this clears things up a bit, overall memreport can be useful for getting lots of low level information, but it’s not intended as a replacement for something like Unity’s memory profiler, the equivalent tools here would be the Asset Audit in the Editor or Memory Insights with asset tags at runtime.
Kind Regards,
Sebastian