I wonder if these types of negative performance encounters were happening in WL builds prior to Sandbox 2.0/Unreal 4.72.
What happens if you just leave Wild Life window active in empty showroom idle but don't use sandbox editor mode?
How many objects items, characters etc were you adding to a map etc, FisherVillage or happens in Showroom too?
These past few builds I've seen odd issues I wasn't having before: All textures blurring after half an hour of play on FisherVillage sandboxing a small Beach House/Cave Hideout map and for the first time ever while in Wild Life I had BSOD after playing with automation events, I wish I had more helpful info to provide to Steve in case these are worth investigating or if it's just us.
Would Wild Life benefit from having some sort of in-game Bug Reporter that zips up current scene/map, details, logs, screenshot and a text input box for the player to give a short description of the issue and a submit button that Steve could use to investigate in case these aren't flukes. Such in-game bug reporters are in other titles around F95 and Steam Early Access games.
I have 32GB of DDR4, 3070 Ti, I want to conduct tests on old & newest build to see if my WL has this supposed RAM overflow.
Of course keeping in mind this game is not final, fully optimized and new problems are common in all work in progress games.
Would Wild Life moving to Unreal 5 escalate these issues or improve some such given it's supposed newer/better tech...?
Questions for those who are more technically knowledgeable and well conversed around such I suppose we won't know until then.