# Crash in packaged game in UE5.3

**URL:** <https://discourse.kitware.com/t/crash-in-packaged-game-in-ue5-3/1279>\
**Category:** Pulse Physiology Engine\
**Created:** [April 19, 2024, 7:39am UTC](https://discourse.kitware.com/t/crash-in-packaged-game-in-ue5-3/1279 "2024-04-19T07:39:49Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![Varun\_Madhu](https://discourse.kitware.com/user_avatar/discourse.kitware.com/varun_madhu/32/922_2.png) [@Varun\_Madhu](https://discourse.kitware.com/u/Varun_Madhu)\
**Post date:** [April 19, 2024, 7:39am UTC](https://discourse.kitware.com/t/crash-in-packaged-game-in-ue5-3/1279/1 "2024-04-19T07:39:49Z")

</div>

Hi,  
I am using the pulse physiology engine plugin in UE5.3. The app runs properly in PIE but when running a packaged game, there is a crash. We are running the simulation on a different thread.

 ![pulse_crash](https://discourse.kitware.com/uploads/default/original/1X/9ee2b100f84589939a070a5055eb8ed5fbf120b9.png)

---

<div class="post-metadata">

**Author:** ![abray](https://discourse.kitware.com/user_avatar/discourse.kitware.com/abray/32/12_2.png) [@abray](https://discourse.kitware.com/u/abray)\
**Post date:** [April 19, 2024, 7:19pm UTC](https://discourse.kitware.com/t/crash-in-packaged-game-in-ue5-3/1279/2 "2024-04-19T19:19:03Z")

</div>

I believe this is due to how our build references and tells unreal to load our dll

Can you take a look at and apply these changes in your copy and see if they help on your system

[https://gitlab.kitware.com/physiology/unreal/-/commit/5289b4a66e4868a803f7fd80c12393d07c59043c](https://gitlab.kitware.com/physiology/unreal/-/commit/5289b4a66e4868a803f7fd80c12393d07c59043c)

---

<div class="post-metadata">

**Author:** ![abray](https://discourse.kitware.com/user_avatar/discourse.kitware.com/abray/32/12_2.png) [@abray](https://discourse.kitware.com/u/abray)\
**Post date:** [April 20, 2024, 12:00am UTC](https://discourse.kitware.com/t/crash-in-packaged-game-in-ue5-3/1279/3 "2024-04-20T00:00:55Z")

</div>

Can you also double check when you pulled the plugin?  
I did upload an update to the [plugin in Janurary](https://data.kitware.com/api/v1/item/65972adf9c30d6f4e17c9f03/download) that might also fix this issue