Page 1 of 1

Scripting - DynamicLoadObject vs UT ram usage

Posted: 29 Oct 2020, 10:56
by jammer64
Quick question for coders with best insight into engine - are dynamically loaded objects of any help with working around fixed 2GB memory limit?

Re: Scripting - DynamicLoadObject vs UT ram usage

Posted: 29 Oct 2020, 17:45
by yrex
Well, you can use it to load assets when needed (as opposed to when the map starts).

You can also free some memory by calling ConsoleCommand("OBJ GARBAGE")

Re: Scripting - DynamicLoadObject vs UT ram usage

Posted: 29 Oct 2020, 21:26
by jammer64
So engine's garbage collector doesn't handle it automatically when asset is, for example, not in use for longer time? Does 'obj garbage' introduce any noticeable slowdowns or stuttering (like regular flush does).

Re: Scripting - DynamicLoadObject vs UT ram usage

Posted: 30 Oct 2020, 15:51
by yrex
I think (not sure) that garbage collection only happens when a map loads.

And yes, it probably will introduce some lag.