Just found this as looking for optimisation information. Have been using insights but learning how to interpret the information. This video very helpful even though it released November. I Just had to look, I actually have Toms course on Udemy. Got it back in 2018! Looks like I did not get far into it 😞I think I will revisit as I am sure there will be plenty of useful information in there.
27:00 in regards to doing a distance to every frame, wouldn't that itself add a significant amount of overhead, especially in regards to games with LOTS of interactable objects? Perhaps some kind of significance pooling system that manages all actors in a level automatically would cut down on performance even more. Or maybe a large clientside sphere trace done on the player that updates props as they enter/leave the sphere, it'd be expensive, but surely cheaper than having ALL your props line trace to your player.
You don't line-trace to your player, you use size squared to figure out how distant that object it. It does add overhead indeed, but it's not that bad (I did share the same concern beforehand btw). You can use "stat SignificanceManager" to see how much time you spend on computing significance. The gains you can get from tuning down irrelevant Actors should greatly outway the cost of doing the distance squared check. You can get smarter about it, for example handle the significance per room if you have a more linear game and avoid calculating per-object significance within the same room.
it depend , if you want to do a game like pokemon, I say 1 month, but if you want to make a real game without any fucking bugs, probably it will take several years
