Re:A closer look at frame times: why FPS can mislead
by vertex-four on Saturday June 27, 2020 @03:34AM
(#23660149)
Unreal’s C++ code (specifically, anything deriving from UObject) is garbage collected as well.
Re:A closer look at frame times: why FPS can mislead
by rowanG077 on Saturday June 27, 2020 @09:51AM
(#23661839)
Really? Why is that in the times of smart pointers? You can just malloc a pointer and it gets cleaned up automatically by unity if it's no longer used?
Re:A closer look at frame times: why FPS can mislead
by vertex-four on Sunday June 28, 2020 @07:02AM
(#23667993)
Because you want garbage collection to happen at specific, well-defined times (i.e. in the slack between frames), in a separate thread - not in the middle of rendering a frame on the main thread when you happen to drop something out of scope.
Re:A closer look at frame times: why FPS can mislead
by rowanG077 on Tuesday June 30, 2020 @06:35AM
(#23688676)
Still I can't imagine GC is the best solution for this. You can easily make a memory allocation strategy that hands out shared_pointers or something like it that get cleaned up at will defined times instead of when it goes out of scope for a user.
I know .NET's GC is supposed to be pretty good, but Unity is still using the Mono implementation, right?
I can barely stand C++, but I'll put up with it to avoid long GC pauses or dynamic typing. (JS)