This is still an issue today. The problem does not appear to have anything to do with machine specs. It’s not a problem of just needing to wait for it to brute force out.
My PC completed memory calculations successfully 16 times for our current work in progress, each time it took roughly 15 secs to complete the calculation. It’s really obvious when it’s running because all the algorithm seems to do is subdivide your map’s playable area, teleport your avatar across this area and average the memory usage from each location. So when things are running correctly it’s super obvious to any casual observer.
Once you get into the state where memory calculations don’t run, which I am in now, the avatar remains stationary and progress sits at 0% until the session times out. The calculation doesn’t even get off the ground, the avatar transform never changes a single time.
We need more details about this process written to the editor log so that we can self-diagnose. If the issue is being caused by some bad asset then we need some visibility into the operations being performed on level assets and the results of those operations.
Is there any way to escalate this issue or have the team look at our map so that they can reproduce it?
I gave this a try but it didn’t make any difference in my ability to complete memory calculation.