# Using MVVM ( View Models ) in Blueprints for UMG Widgets.

**URL:** <https://forums.unrealengine.com/t/using-mvvm-view-models-in-blueprints-for-umg-widgets/2008379>\
**Category:** Blueprint\
**Tags:** unreal-engine\
**Created:** [September 6, 2024, 2:31pm UTC](https://forums.unrealengine.com/t/using-mvvm-view-models-in-blueprints-for-umg-widgets/2008379 "2024-09-06T14:31:49Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Core2kx](https://d3kjluh73b9h9o.cloudfront.net/original/4X/2/8/5/28502927f1d97ba1051b3b47ccfe17233bf41ef0.png) [@Core2kx](https://forums.unrealengine.com/u/Core2kx)\
**Post date:** [September 6, 2024, 2:31pm UTC](https://forums.unrealengine.com/t/using-mvvm-view-models-in-blueprints-for-umg-widgets/2008379/1 "2024-09-06T14:31:49Z")

</div>

I am working on a game where I wanted to incorporate the MVVM subsystem. I struggled quite a bit to get it work in Blueprints. The issue I was having was that the MVVM subsystem wasn’t being initialized in the Game Instance Blueprint before it was being called. I am not using any C++ in this project so I needed a solution.

My eventual work-around was this:

1. I created an event in the Game Instance BP which would setup all of the View Models and add them to the subsystem.

2. In the Game Mode BP I call the event inside the Game Instance BP.

This worked because the Game Mode BP is executed after the Game Instance BP so the MVVM subsystem is already initialized and ready to be used. I hope this helps anyone that is running in the same issue.

---

<div class="post-metadata">

**Author:** ![ImYourBeast](https://d1ap1mz92jnks1.cloudfront.net/user_avatar/forums.unrealengine.com/imyourbeast/32/1220194_2.png) [@ImYourBeast](https://forums.unrealengine.com/u/ImYourBeast)\
**Post date:** [November 22, 2026, 11:44am UTC](https://forums.unrealengine.com/t/using-mvvm-view-models-in-blueprints-for-umg-widgets/2008379/2 "2026-11-22T11:44:14Z")

</div>

Keep all viewmodel setup inside one GameInstance event that runs at startup, and let widgets only bind after that event has finished. A single startup gate in the GameInstance removes the ordering guesswork for a Blueprint only project. You can also try Blueprint Subsystems Bridge, it runs game instance startup logic in a Blueprint BP\_Initialize with no C++ needed: [https://www.fab.com/listings/ef648821-09e5-4813-b003-9d22379ecea6](https://www.fab.com/listings/ef648821-09e5-4813-b003-9d22379ecea6)
