When packaging in UE5 in SHIPPING configuration, the packaged project still shows the print strings and has the console command

Development Platform & Builds Debugging, Optimization, & Profiling
, , , , ,
1

Further details:

  • The building configuration is set to Shipping on the new quick menu for packaging.
  • The building configuration in project settings is also set to Shipping.
  • I’m using the latest (currently) UE5 version (5.0.2).
  • I’ve restarted the engine multiple times to make sure this isn’t a fluke.
  • In DefaultGame.ini I’ve found BuildConfiguration=PPBC_Shipping so I’m guessing the engine recognizes I’ve set it to shipping

I think this is a bug in the engine too but I don’t know any workarounds.
Thanks in advance

3 Likes
2

Workaround found:

  • Using Console Command disableallscreenmessages when the game loads to lose all print strings (I’ve set it on a branch on an enum if the build version isn’t a playtest/cheat enabled).
  • Unbinding the shortcut to “Open Console Command Box” at Editor Preferences/Keyboard Shortcuts (search by or scroll down to category System-wide).
  • EDIT: to disable the debugging controls you also need to follow this link:
    [SOLVED] How to unbind Semicolon and Apostrophe from debug controls in PIE?

This is not an exact solution!
As far as I understand when packaging for shipping the build is more performant than packaging for development/debugging.

I have not checked if other computers/ projects have this bug too but if so then it is worth opening a bug report if you (random internet stranger) have this bug too.

1 Like
3

Update:
updating the engine messed up my solution.

I’ve checked on multiple computers and the bug persists.
I have submitted a bug report from the engine, let’s hope it helps.
Until then we can only package on “Development” configuration on 5.0.2 and 2.0.3

1 Like
4

update update the sequel

It’s all due to the engine not packaging on a Shipping build.
Additional problem is that the savegame file is in a local folder and every time the project is updated (say, on Steam), the players’ progress will be overwritten.

My solution/ workaround for that is this but this requires building the engine from source (which I’m doing rn and it doesn’t go very well for me right now lol).

This is all due to this bug in the engine.

I also submitted a bug report but I didn’t get any response :confused:

2 Likes
5

I have this problem too. Still no update?

1 Like
6

Hey,

Sorry for the delay.

AFAIK the problem is with specific engine versions. Currently I’m using the normal (aka not from source, downloaded from the epic store) 5.1.1 version and it doesn’t have this bug.

My solution for you is to:

  1. Either use my workaround here if it’s a simple non important project that you will not be updating.

(the reason for that is that my workaround doesn’t include a way to move the save file location, as with packaging settings that aren’t shipping it will put the save file in the same file as the project that will be overwritten when updated on a platform like Steam).

  1. Or to update to a different, more stable version of the engine. You could also download and build the engine from source and if the bug persists, just edit the enum that has the packaging version (development, shipping, etc…) to have shipping enabled.

In my case, migrating to the source version fixed it immediately. I’m guessing someone else noticed the bug and hotfixed it into the source build before the official update came out.

Just out of curiosity, what engine version are you using?

Goodluck with your project and LMK if I helped you!

7

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.