🤖 AI Summary
This study addresses the effective integration of generative tools into early-stage graphical asset creation in game development. Through a mixed-methods empirical study with 16 professional game designers and developers—including Likert-scale surveys, in-depth interviews, and statistical testing (p < .001)—we systematically identify key adoption requirements: strong user preference for tool intervention during conceptual design, demand for editable output formats and native IDE/engine integration, and a prevalent “quantity-first, refinement-later” workflow (mean quality tolerance: 0.17). Integration compatibility (mean rating: 3.5/5) and lack of universal data formats emerge as primary deployment bottlenecks. Based on these findings, we propose the first empirically grounded design guideline for generative graphics tools—specifying functional, interoperability, and workflow-aware principles. This work provides both theoretical foundations and actionable implementation pathways for the trustworthy integration of AIGC into industrial game development pipelines.
📝 Abstract
Graphical assets play an important role in the design and development of games. There is potential in the use of generative tools, to aid in creating graphical assets, thus improving game design and development pipelines. However, there is little research to address how the generative methods can fit into the wider pipeline. We conducted a user study with 16 game designers and developers to examine their preferences regarding generative tools for graphical assets. The findings highlight that early design stage is preferred by all participants (mean values above 0.67 and p<.001 for early stages). Designers and developers prefer to use such tools for creating large amounts of variations at the cost of quality as they can improve the quality of the artefacts once they generate a suitable asset (mean value 0.17 where 1 is high quality, p<.001). They also strongly (mean value .78, p<.001) raised the need for better integration of such tools in existing design and development environments and the need for the outputs to be in common data formats, to be manipulatable and integrate smoothly into existing environments (mean 3.5 out of 5, p = .004). The study also highlights the requirement for further emphasis on the needs of the users to incorporate these tools effectively in existing pipelines. Informed by these results, we provide a set of guidelines for creating tools that meet the expectations and needs of game designers and developers.