The Software Modeling Paradox in Videogames: An Empirical Evaluation of Unreal Blueprints vs. Unity Visual Scripting

Despite the fact that the leading video game engines include Model-Driven Development (MDD) principles, a paradox exists in the videogame industry: while Unreal Engine’s Blueprints (BP) enjoy wide-spread industrial adoption, Unity Visual Scripting (UVS) remains largely marginalized. To investigate the underlying causes of this phenomenon, we present a controlled empirical experiment with 31 participants. Using a mixed-methods approach, we compare both software models (BP and UVS) across quantitative performance metrics (Correctness and Efficiency) and qualitative assessments (Method Evaluation Model and focus group discussions). Results show that BP significantly outperforms UVS across all metrics. Qualitative analysis reveals that while BP provides a tailored abstraction layer and model-based debugging, UVS functions primarily as a visual wrapper for C#, inheriting the cognitive load of traditional coding without its efficiency. Additionally, the seamless bidirectional integration between Blueprint models and C++ code in Unreal mitigates the “loss of control” barrier to MDD adoption. Our results may not only inform the video game domain by identifying effective directions for key factors such as abstraction and debugging, but may also generalize to more traditional software domains where the “loss of control” adoption barrier can also emerge.