REVIEW 1 cited by
Visualising Game Engine Subsystem Coupling
Not yet reviewed by Pith; the record is open.
This paper has not been read by Pith yet. Machine review is queued; the pith claim, tier, and objections will appear here once it completes.
SPECIMEN: schema-true, not a live event
T0 review · schema-true
One-sentence machine reading of the paper's core claim.
pith:XXXXXXXX · record.json · timestamp
read the original abstract
Game engines support video game development by providing functionalities such as graphics rendering or input/output device management. However, their architectures are often overlooked, which hinders their integration and extension. In this paper, we use an approach for architecture recovery to create architectural models for 10 open-source game engines. We use these models to answer the following questions: Which subsystems more often couple with one another? Do game engines share subsystem coupling patterns? We observe that the Low-Level Renderer, Platform Independence Layer and Resource Manager are frequently coupled to the game engine Core. By identifying the most frequent coupling patterns, we describe an emergent game engine architecture and discuss how it can be used by practitioners to improve system understanding and maintainability.
Forward citations
Cited by 1 Pith paper
-
GameEngineBench: Evaluating Coding Agents on Real C++ Runtime Environments
On 110 scoped Unreal Engine C++ tasks from nine real game repos, the best coding-agent setup reaches only 55.5% pass@1 and 31 tasks remain unsolved by all twelve configurations.
Discussion (0). Continue with ORCID to comment.