- Rating
- 3
- Confidence
- 3
- Informativeness
- 3
- Presentation
- 3
- Soundness
- 3
Read review
Paper summary
Authors introduce GameCrafter, a hierarchical approach to generating playable 3D game worlds through a prompt via a VLM. The first stage is Specification-guided orchestration where the user inputs a prompt, optionally some reference images and assets, and the system extracts game specifications, artifact graphs and designs a workflow orchestrator. The second stage, named structure-aware asset synthesis, synthesises the environment by generating art plans, scene layouts etc.. It also creates or imports character meshes, cleans it up and performs important operations on them to check motion etc. Multi-gameplay world realization is the third step where GameCrafter sets up an UnrealEngine project and intergrates all necessary assets and checks gameplay and physics routines. Lastly, * Closed-loop quality control* reviews visual aspects and playtests the game. These steps results in playable and editable game world, 2 gameplay modes, 3 camera views and 5 modalities, such as RGB, depth etc.
The authors create a benchmark of 10 tasks, and compare there methods with three baselines. The evaluation and playtesting is also done by VLM. The final metrics contain Core Mechanics (M), Content Depth (D), Functional Visuals (V), and Art and Presentation (A). M has 6 checks, D, V and A has 4 checks each, with A having more atomic checks as well.
Critical strengths
The strengths are:
- Very easy to follow. No unnecessary mathematical jargon. Clearly states what the pipeline is and what it is supposed to do.
- Very good introduction and related works section.
- Results are qualitatively great. Editable small worlds are much better than Genie-type uneditable larger worlds as game designers can use them for quick prototyping.
- Multi-gameplay modes is the strongest contribution as this can be used to create a full game with exploration and boss fights etc.
Critical weaknesses
The weaknesses are:
- It is not clear if ALL of the metrics are judged via VLM
- No evaluations of playtesting in the main text.
- Needs ablations.
Questions for authors
- Playtesting via VLM is very risky, how do you evaluate the playtester itself?
- Are all evaluations done by a VLM?
- Can you measure the diversity of generated worlds?
- Can you ablate each stage, where necessary?