3 ms·
The definition of "game engine" in the paper is subtly different to the one most players and game engine programmers would expect. The paper calls the set of ga
by YeGoblynQueenne 9y ago
The definition of "game engine" in the paper is subtly different to the one
most players and game engine programmers would expect. The paper calls the set
of game mechanics a "game engine". I think the players and programmers would
probably call that "mechanics" and refer to the actual code running the game
as an "engine".
For example, if I think of an AI that "learns a game engine from video" I
would expect to see an AI that can take as input video of, say, myself playing
XCOM2 and output the Unreal engine (or an engine with an interface
indistinguishable from it).
In other words, I'd expect to see an AI that goes from example game output to
an automaton that can reproduce that output _and any other output that the
original automaton could produce_.
Instead, from a quick read of the paper, I understand they learn to reproduce
a set of video frames that match the input- and then train a different AI to
actually simulate the physics (i.e. make sure the player doesn't fall through
walls etc).
While this is remarkable and I'm very glad to see a rule-based, greedy
approach that seems to work pretty damn well, I really don't think it does
what it says on the tin.
Still- this was published in IJCAI. So kudos to the authors for that.