Packaged Game crashes after shortly

it seems to crash probably on winmain where it is just starting up the project.

Could it be an external problem? Like your graphics card switching power modes and maybe killing the project in it’s startup phase?

Could you try running it with your power config set to performance?

Also try looking in the “Call Stack” and “Output” tabs in visual studio during the exceptions to see if more info can be found there

1 Like

I checked my power config and it’s on high performance. the output log seem to give similar log in “crash” folder

Did you try add the “Player Start” object to the level “Make_Her_Laugh_1”?
It’s still mentioning that it can’t find the spawn location.

Can you upload a list of objects in the outliner of that level?
It should have at least 1 object of type “PlayerStart” in it.

1 Like

inside my main menu widget graph I set on start button hit to load up level Make_Her_Laugh_1 but my main game is called Make_Her_Laugh_2 and I deleted Make_Her_Laugh_1 long time ago. so that fixed the issue of game not reading player start in the world and also the correct level/map loading. I placed my character BP in the Make_Her_Laugh_2 world with possess 0 to assign the instance variables. so that fixed the tried to access the index 0 of get all actors of class function by length 0. now the game crashes still but I believe only because of these two warnings by searching in packaged game log:

FKControlRig referencing RigVM /Script/ControlRig.Default__FKControlRig:VM which is not part of root set

FKControlRig referencing RigHierarchy /Script/ControlRig.Default__FKControlRig:DynamicHierarchy which is not part of root set

it’s directing to my skeletal mesh animation with FKRig in three level sequences. so it’s simply failing to put the rig animation together?! all three play through fine in editor and standalone however

Try maybe adding the rig directory to the package by force and see if that changes anything

But now that we are focusing on the control rig only I see on many forums that it is an issue when packing ue5 games. Might be able to narrow down the error with time.

Could be just a bug in the control rig that might be fixed in the next update.

1 Like

Seems someone using controlrig with animgraph was able to get it fixed by adding a dependency to his build file.

Grasping a bit at straws at the moment but it could be worth a try, especially since it’s a cut-scene where it crashes right?

1 Like

yeah it’s a simple level sequence with FKRig animated skeletal mesh inside but it causes crash. I made a Control Rig out of the skeletal mesh and simply compiled the default graph inside it. assigned it to the Control Rig class of the FKControlRig inside level sequence and also to interaction rig and packaged the game but still didn’t work and gives same log

I’ll try to pick the rig folder along with the Control Rig I made to see if it works

Seems control rig in sequencer is cursed :stuck_out_tongue:
Probably just a bug that will be sorted out in future updates.

Some people were able to get around crashes with this combination by baking the control rig animation:

Here is a tutorial how to bake control rig animations. It’s worth a try at this point

1 Like

I can’t believe it! wow thank you so much I fixed the FKRig issue with this. so basically you can bake an animation in level sequence and simply replace the animation with the baked one and include it in additional assets in packaging settings and it’ll work perfectly well! I’m so happy man thank you I knew after one super rough week I can fix them haha

1 Like

Good to hear the project isn’t sunk due to a bug. That would be the worse type of outcome.
Must’ve been tough to have the project hang on such a weird problem.

Buy yourself a beer or burger, treat yourself to something good and try to de-stress if you can.

Congratulations !

1 Like