A Few Problems That Occur in Packaged Game but Not in Editor Play

Hello.

I apologise if this supposed to belong to Packaging and Developtment section, but since the problems I have are NOT happening in editor play but in packaged ones, I decided to went with the Bug Reports. Now let me start.

The “Fighting Game Template” I am working on is growing steadily, yet so does it’s problems. Though I am not sure they are something I can fix myself or not. I just decided to post after days of trying to figure out things.

Now first of let me start with the structs.

Blueprint Structs are working completely fine in editor, yet they are completely disregarded in packaged game. There is no way to use them. I need them to keep a few bool variables, well, look good and tidy, yet they are currently not functioning at all.

—|—

There is also a massive problem regarding the variables of a parent, and a child using its parent’s variables. Lets have we got a Parent Variable, named “Float”. And it’s on default settings, which is “0”. Now, if you change this variable’s value in a CHILD blueprint, and lets say, make it “50”, its all nice in editor. Yet Packaged Game doesn’t care and it uses the parent’s default value. I think setting the variable’s value at the beginplay instead of the blueprint fixes this, but its clumbersome.

Also the tooltips in parent’s variables do not show up in childs. Small bug, or even if it isn’t, you can’t edit the tooltips of parent variables in child blueprints. Looks odd.

—|—

Event Tick also seems to have a large problem if it belongs to a Child Actor. My Character BP have 4 total child actors right now. When I put a tick event on each of them. They work nice in “editor play”. I get spammed with Print Strings all around. Problem starts when I try it in “Package Game”. Child Actors work fine (if you exclude the problems above) generally, yet the Event Tick just… doesn’t tick. And it seems a bit of random. Sometimes only one of them ticks, mostly none. I got the feeling that Event Tick just doesn’t know if it should tick or not if there are other child actors… Or something.

It is hard for me test this one. I could not produce this on a clean project. Though on my project Tick Event on Child Actors only work if the parents got no variables in packaged game… like, odd.

—|—

I -REALLY- need help on these problems. Since I will be making this a Marketplace Template for people to use after buying, I really dont want people to make a hunting crowd with pitchforks and thorches once they press that “Launch” button. :frowning:

I can share the template with a staff aswell. It’s just a 40MB zip file.

Thank you for your time and reading.

Hello ,

In order to assist you further, could you please tell us what you’re packaging to? Which version of the engine are you working out of? Which version of the engine did you start in for this project? Since you’re willing to upload this project, please do so and feel free to provide the link either here (where the public can obtain it) or through a private message on the forums.

Thanks!

Hello Miss .

I really appreciate that you are willing to help. I will try my best to explain how to reproduce these problems on my project once I can send it to you (or someone else if you prefer).

Though I need to know, how can I send it via private message? I tried " " and it lighted up, so I believe this is you, right? And lastly, where shall I put it? To a etc?

Also regarding your questions, I package for Windows 32/64. The packaging do not fail, neither the launcher. Though as I said, the structs are still not used, child actor event ticks are not firing, and child actors that are using parent variables with their own values are ignored as parent values are used. And all is normal as best at editor play or stand alone. :slight_smile:

And I have this… project started at 4.7. And Atm I am using 4.8.3. I also want to note that, all the child actors are created at 4.8.3. My whole template got a head at 4.8. So there wasn’t much of a “Large Project Migration” thingy going on before.

Thanks once again!

You can write a PM to me, ’ ’ on the forums and provide a link to your or your Drive so that I can download it. Make sure it’s shared too.

Looking forward to seeing your project, please provide as much information as possible so that I can look into the issues that you’re seeing.

Thanks! :slight_smile:

Hello once again Miss . I have sent the link to you via forums. It should be there shortly!

Now here is the deep explanation on what is going on.

First of all, struct problem;

This image is from “Attack Level 1” Graph of “Ability System Ken”. This Light Punch occurs once you press Q. Simply play in Editor and press the button, you will see a small punch happening visually too!

Now as you see from the red box, this event checks for a Struct value and demands it to be true in order to continue executing animation etc. So here is the problem. This struct is by default set to true on all of its booleans so editor play got no problems. Yet Packaged game does not care about it. So the branch returns false, and we get only the Print String.

Here is the work around:

In same Blueprint and in its Event Graph, I set the values to true at beginplay, despite the fact that they are already true by default. This is the only way to make it work. Just plug it in and you will see it all works. ^^

WARNING: Launching the game is kind of bugged aswell. It does not care about the things you have changed if you launched the game before. So please close the editor after saving, and open it again to Launch. You will see all working now. ^^

Second problem: Tick Event.

If you check the second picture once again, you will see there is also a Tick Event that suppose to tick in Packaged Game, but it only does so in Editor Play.

The only work around is making a tick event in Player Blueprint, that this child actor is added. Then Create a custom event in the child actor which is connected to the tick event in Player BP. Clumbersome at best. :slight_smile:

Last problem: Parent Default Value Usage in Packaged Game

This image is taken from the Collision_System_Ken Blueprint. As you see its a simple print string spamage. In Editor you will see the correct numbers spammed on the screen, 59 and 500 which are changed in default values.

But in Packaged game, you will see the numbers spammed as 0, which are default values in parents. The Child Actor also uses these values so the collision system does not work properly, but no need to test that part. Numbers tell enough. :slight_smile:

Note: In all images, you can see the asset browser, simply follow the folders and you will get to those blueprints easily. Also Parent Blueprints are stored in ThirdPersonBP → Blueprints → CharacterSystem → Base_Components. :slight_smile:

Thank you for your time!

Hey,

Did you provide me the full project including all of the materials? The reason I ask is because your project will not package. It’s also having trouble with the fact that there are spaces in some of the files. You cannot have spaces in any of the file names or any special characters within the project naming conventions otherwise, it’ll cause numerous problems with packing and deployment.

It looks like there are a lot of issues with your ‘inputactions’, and some are building successfully but have warnings in them, that could be causing the trouble you’re seeing:

MainFrameActions: Packaging (Windows (64-bit)): UE4Editor-Cmd: [2015.08.13-15.54.10:110][  0]LogInit:Display: LogBlueprint:Warning: [compiler Input_System_Ken] Warning Input Axis Event references unknown Axis 'Jump Player 1' for  InputAxis Jump Player 1 
MainFrameActions: Packaging (Windows (64-bit)): UE4Editor-Cmd: [2015.08.13-15.54.10:111][  0]LogInit:Display: LogBlueprint:Warning: [compiler Input_System_Ken] Warning Input Axis Event references unknown Axis 'Jump Player 2' for  InputAxis Jump Player 2 
MainFrameActions: Packaging (Windows (64-bit)): UE4Editor-Cmd: [2015.08.13-15.54.10:111][  0]LogInit:Display: LogBlueprint:Warning: [compiler Input_System_Ken] Warning InputAction Event references unknown Action 'Heavy Kick Player 2' for  InputAction Heavy Kick Player 2 
MainFrameActions: Packaging (Windows (64-bit)): UE4Editor-Cmd: [2015.08.13-15.54.10:111][  0]LogInit:Display: LogBlueprint:Warning: [compiler Input_System_Ken] Warning InputAction Event references unknown Action 'Medium Kick Player 2' for  InputAction Medium Kick Player 2 
MainFrameActions: Packaging (Windows (64-bit)): UE4Editor-Cmd: [2015.08.13-15.54.10:112][  0]LogInit:Display: LogBlueprint:Warning: [compiler Input_System_Ken] Warning InputAction Event references unknown Action 'Light Kick Player 2' for  InputAction Light Kick Player 2 
MainFrameActions: Packaging (Windows (64-bit)): UE4Editor-Cmd: [2015.08.13-15.54.10:112][  0]LogInit:Display: LogBlueprint:Warning: [compiler Input_System_Ken] Warning InputAction Event references unknown Action 'Heavy Punch Player 2' for  InputAction Heavy Punch Player 2 
MainFrameActions: Packaging (Windows (64-bit)): UE4Editor-Cmd: [2015.08.13-15.54.10:112][  0]LogInit:Display: LogBlueprint:Warning: [compiler Input_System_Ken] Warning InputAction Event references unknown Action 'Heavy Punch Player 1' for  InputAction Heavy Punch Player 1 
MainFrameActions: Packaging (Windows (64-bit)): UE4Editor-Cmd: [2015.08.13-15.54.10:113][  0]LogInit:Display: LogBlueprint:Warning: [compiler Input_System_Ken] Warning InputAction Event references unknown Action 'Medium Punch Player 2' for  InputAction Medium Punch Player 2 
MainFrameActions: Packaging (Windows (64-bit)): UE4Editor-Cmd: [2015.08.13-15.54.10:113][  0]LogInit:Display: LogBlueprint:Warning: [compiler Input_System_Ken] Warning InputAction Event references unknown Action 'Light Punch Player 2' for  InputAction Light Punch Player 2 
MainFrameActions: Packaging (Windows (64-bit)): UE4Editor-Cmd: [2015.08.13-15.54.10:113][  0]LogInit:Display: LogBlueprint:Warning: [compiler Input_System_Ken] Warning InputAction Event references unknown Action 'Heavy Kick Player 1' for  InputAction Heavy Kick Player 1 
MainFrameActions: Packaging (Windows (64-bit)): UE4Editor-Cmd: [2015.08.13-15.54.10:114][  0]LogInit:Display: LogBlueprint:Warning: [compiler Input_System_Ken] Warning InputAction Event references unknown Action 'Medium Kick Player 1' for  InputAction Medium Kick Player 1 
MainFrameActions: Packaging (Windows (64-bit)): UE4Editor-Cmd: [2015.08.13-15.54.10:115][  0]LogInit:Display: LogBlueprint:Warning: [compiler Input_System_Ken] Warning InputAction Event references unknown Action 'Light Kick Player 1' for  InputAction Light Kick Player 1 
MainFrameActions: Packaging (Windows (64-bit)): UE4Editor-Cmd: [2015.08.13-15.54.10:115][  0]LogInit:Display: LogBlueprint:Warning: [compiler Input_System_Ken] Warning InputAction Event references unknown Action 'Medium Punch Player 1' for  InputAction Medium Punch Player 1 
MainFrameActions: Packaging (Windows (64-bit)): UE4Editor-Cmd: [2015.08.13-15.54.10:115][  0]LogInit:Display: LogBlueprint:Warning: [compiler Input_System_Ken] Warning InputAction Event references unknown Action 'Light Punch Player 1' for  InputAction Light Punch Player 1 
MainFrameActions: Packaging (Windows (64-bit)): UE4Editor-Cmd: [2015.08.13-15.54.10:115][  0]LogInit:Display: LogBlueprint:Warning: [compiler Input_System_Ken] Warning Input Axis Event references unknown Axis 'Movement Player 2' for  InputAxis Movement Player 2 
MainFrameActions: Packaging (Windows (64-bit)): UE4Editor-Cmd: [2015.08.13-15.54.10:115][  0]LogInit:Display: LogBlueprint:Warning: [compiler Input_System_Ken] Warning Input Axis Event references unknown Axis 'Movement Player 1' for  InputAxis Movement Player 1 
MainFrameActions: Packaging (Windows (64-bit)): UE4Editor-Cmd: [2015.08.13-15.54.10:116][  0]LogInit:Display: LogBlueprint:Warning: [compiler Input_System_Ken] Warning [0020.37] Compile of Input_System_Ken successful, but with 16 Warning(s) [in 95 ms]
MainFrameActions: Packaging (Windows (64-bit)): UE4Editor-Cmd: [2015.08.13-15.54.10:116][  0]LogInit:Display: LogBlueprint:Warning: [compiler Input_System_Ken] Warning [0020.38] Compile of Input_System_Ken successful, but with 17 Warning(s) [in 7 ms]
MainFrameActions: Packaging (Windows (64-bit)): UE4Editor-Cmd: [2015.08.13-15.54.10:117][  0]LogInit:Display: LogBlueprint:Warning: [compiler Movement_System_Ken] Warning Input Axis Event references unknown Axis 'Movement Player 2' for  InputAxis Movement Player 2 
MainFrameActions: Packaging (Windows (64-bit)): UE4Editor-Cmd: [2015.08.13-15.54.10:117][  0]LogInit:Display: LogBlueprint:Warning: [compiler Movement_System_Ken] Warning Input Axis Event references unknown Axis 'Movement Player 1' for  InputAxis Movement Player 1 
MainFrameActions: Packaging (Windows (64-bit)): UE4Editor-Cmd: [2015.08.13-15.54.10:117][  0]LogInit:Display: LogBlueprint:Warning: [compiler Movement_System_Ken] Warning [0020.54] Compile of Movement_System_Ken successful, but with 2 Warning(s) [in 105 ms]
MainFrameActions: Packaging (Windows (64-bit)): UE4Editor-Cmd: [2015.08.13-15.54.10:118][  0]LogInit:Display: LogBlueprint:Warning: [compiler Movement_System_Ken] Warning [0020.54] Compile of Movement_System_Ken successful, but with 3 Warning(s) [in 7 ms]
MainFrameActions: Packaging (Windows (64-bit)): UE4Editor-Cmd: [2015.08.13-15.54.10:119][  0]LogInit:Display: LogBlueprint:Warning: [compiler Input_System_Ryu] Warning Input Axis Event references unknown Axis 'Jump Player 1' for  InputAxis Jump Player 1 
MainFrameActions: Packaging (Windows (64-bit)): UE4Editor-Cmd: [2015.08.13-15.54.10:120][  0]LogInit:Display: LogBlueprint:Warning: [compiler Input_System_Ryu] Warning Input Axis Event references unknown Axis 'Jump Player 2' for  InputAxis Jump Player 2 
MainFrameActions: Packaging (Windows (64-bit)): UE4Editor-Cmd: [2015.08.13-15.54.10:120][  0]LogInit:Display: LogBlueprint:Warning: [compiler Input_System_Ryu] Warning InputAction Event references unknown Action 'Heavy Kick Player 2' for  InputAction Heavy Kick Player 2 
MainFrameActions: Packaging (Windows (64-bit)): UE4Editor-Cmd: [2015.08.13-15.54.10:121][  0]LogInit:Display: LogBlueprint:Warning: [compiler Input_System_Ryu] Warning InputAction Event references unknown Action 'Medium Kick Player 2' for  InputAction Medium Kick Player 2 
MainFrameActions: Packaging (Windows (64-bit)): UE4Editor-Cmd: [2015.08.13-15.54.10:121][  0]LogInit:Display: LogBlueprint:Warning: [compiler Input_System_Ryu] Warning InputAction Event references unknown Action 'Light Kick Player 2' for  InputAction Light Kick Player 2 
MainFrameActions: Packaging (Windows (64-bit)): UE4Editor-Cmd: [2015.08.13-15.54.10:121][  0]LogInit:Display: LogBlueprint:Warning: [compiler Input_System_Ryu] Warning InputAction Event references unknown Action 'Heavy Punch Player 2' for  InputAction Heavy Punch Player 2 
MainFrameActions: Packaging (Windows (64-bit)): UE4Editor-Cmd: [2015.08.13-15.54.10:122][  0]LogInit:Display: LogBlueprint:Warning: [compiler Input_System_Ryu] Warning InputAction Event references unknown Action 'Heavy Punch Player 1' for  InputAction Heavy Punch Player 1 
MainFrameActions: Packaging (Windows (64-bit)): UE4Editor-Cmd: [2015.08.13-15.54.10:122][  0]LogInit:Display: LogBlueprint:Warning: [compiler Input_System_Ryu] Warning InputAction Event references unknown Action 'Medium Punch Player 2' for  InputAction Medium Punch Player 2 
MainFrameActions: Packaging (Windows (64-bit)): UE4Editor-Cmd: [2015.08.13-15.54.10:122][  0]LogInit:Display: LogBlueprint:Warning: [compiler Input_System_Ryu] Warning InputAction Event references unknown Action 'Light Punch Player 2' for  InputAction Light Punch Player 2 
MainFrameActions: Packaging (Windows (64-bit)): UE4Editor-Cmd: [2015.08.13-15.54.10:123][  0]LogInit:Display: LogBlueprint:Warning: [compiler Input_System_Ryu] Warning InputAction Event references unknown Action 'Heavy Kick Player 1' for  InputAction Heavy Kick Player 1 
MainFrameActions: Packaging (Windows (64-bit)): UE4Editor-Cmd: [2015.08.13-15.54.10:124][  0]LogInit:Display: LogBlueprint:Warning: [compiler Input_System_Ryu] Warning InputAction Event references unknown Action 'Medium Kick Player 1' for  InputAction Medium Kick Player 1 
MainFrameActions: Packaging (Windows (64-bit)): UE4Editor-Cmd: [2015.08.13-15.54.10:124][  0]LogInit:Display: LogBlueprint:Warning: [compiler Input_System_Ryu] Warning InputAction Event references unknown Action 'Light Kick Player 1' for  InputAction Light Kick Player 1 
MainFrameActions: Packaging (Windows (64-bit)): UE4Editor-Cmd: [2015.08.13-15.54.10:124][  0]LogInit:Display: LogBlueprint:Warning: [compiler Input_System_Ryu] Warning InputAction Event references unknown Action 'Medium Punch Player 1' for  InputAction Medium Punch Player 1 
MainFrameActions: Packaging (Windows (64-bit)): UE4Editor-Cmd: [2015.08.13-15.54.10:124][  0]LogInit:Display: LogBlueprint:Warning: [compiler Input_System_Ryu] Warning InputAction Event references unknown Action 'Light Punch Player 1' for  InputAction Light Punch Player 1 
MainFrameActions: Packaging (Windows (64-bit)): UE4Editor-Cmd: [2015.08.13-15.54.10:124][  0]LogInit:Display: LogBlueprint:Warning: [compiler Input_System_Ryu] Warning Input Axis Event references unknown Axis 'Movement Player 2' for  InputAxis Movement Player 2 
MainFrameActions: Packaging (Windows (64-bit)): UE4Editor-Cmd: [2015.08.13-15.54.10:125][  0]LogInit:Display: LogBlueprint:Warning: [compiler Input_System_Ryu] Warning Input Axis Event references unknown Axis 'Movement Player 1' for  InputAxis Movement Player 1 
MainFrameActions: Packaging (Windows (64-bit)): UE4Editor-Cmd: [2015.08.13-15.54.10:125][  0]LogInit:Display: LogBlueprint:Warning: [compiler Input_System_Ryu] Warning [0022.03] Compile of Input_System_Ryu successful, but with 16 Warning(s) [in 102 ms]
MainFrameActions: Packaging (Windows (64-bit)): UE4Editor-Cmd: [2015.08.13-15.54.10:125][  0]LogInit:Display: LogBlueprint:Warning: [compiler Input_System_Ryu] Warning [0022.04] Compile of Input_System_Ryu successful, but with 17 Warning(s) [in 8 ms]
MainFrameActions: Packaging (Windows (64-bit)): UE4Editor-Cmd: [2015.08.13-15.54.10:125][  0]LogInit:Display: LogBlueprint:Warning: [compiler Movement_System_Ryu] Warning Input Axis Event references unknown Axis 'Movement Player 2' for  InputAxis Movement Player 2 
MainFrameActions: Packaging (Windows (64-bit)): UE4Editor-Cmd: [2015.08.13-15.54.10:125][  0]LogInit:Display: LogBlueprint:Warning: [compiler Movement_System_Ryu] Warning Input Axis Event references unknown Axis 'Movement Player 1' for  InputAxis Movement Player 1 
MainFrameActions: Packaging (Windows (64-bit)): UE4Editor-Cmd: [2015.08.13-15.54.10:126][  0]LogInit:Display: LogBlueprint:Warning: [compiler Movement_System_Ryu] Warning [0022.21] Compile of Movement_System_Ryu successful, but with 2 Warning(s) [in 112 ms]
MainFrameActions: Packaging (Windows (64-bit)): UE4Editor-Cmd: [2015.08.13-15.54.10:126][  0]LogInit:Display: LogBlueprint:Warning: [compiler Movement_System_Ryu] Warning [0022.21] Compile of Movement_System_Ryu successful, but with 3 Warning(s) [in 8 ms]
MainFrameActions: Packaging (Windows (64-bit)): UE4Editor-Cmd: [2015.08.13-15.54.10:126][  0]LogInit:Display: LogBlueprint:Warning: [compiler Input_System_Ken] Warning [0033.11] Compile of Input_System_Ken successful, but with 16 Warning(s) [in 95 ms]
MainFrameActions: Packaging (Windows (64-bit)): UE4Editor-Cmd: [2015.08.13-15.54.10:127][  0]LogInit:Display: LogBlueprint:Warning: [compiler Input_System_Ken] Warning [0033.12] Compile of Input_System_Ken successful, but with 17 Warning(s) [in 8 ms]

With that being said, could you please upload your full .txt file from your packaging process and let me look over it for any errors?

Thanks!

Hello again Miss . I tried to produce the warnings you have but I could not. Though what I realised that, while I was adding “_” instead of spaces on those input commants, my compiler was having same warnings in editor, stating I should change them.

So I updated all inputs to have "" instead of spaces and all the warnings gone. I packaged and launched, both had no warnings (some engine ones that I dont understand exlucded ^^). Unfortunately this didn’t clear out any problems I am having right now. :frowning:

Anyhow, here are the text files you requested.

[link text][1]
[link text][2]

Also at the first parts of the you will see regarding how some blueprints are not inherited by their parents. Thats not true though. I think there is a problem with the engine-begin compiler. All children blueprints have their parents so casts dont fail at the other complies I do. ^^

Sent you the file links once again to you via inbox. =)

54041-fighting_game±+after+pressing+launch+button.log (718 KB)
[2]: 54042-fighting_game-+after+packaging+and+exiting.log (2.01 MB)

Something I want to add. Even when I was having those warnings you had, the inputs were working in packaged game.

Also I just downloaded what I linked to you, and I had no problems with packaging etc. So tested fully. :slight_smile:

You said that even though you were having the warnings I was having, the inputs were working, or weren’t working?

I was unable to package your project due to naming conventions in your project, which I changed but it still flagged it, which was strange. I also saw those errors which I posted - - which referenced the inputactions. Those warnings are of concern especially if the movements we’rent working properly.

Looking forward to hearing back from you for some clarification, thanks! :slight_smile:

Inputs were working Miss . As long as I set the Structs true in beginplay the guy punches kicks etc. But I no longer get those warnings as I changed the names so I cant test now.

I also sent you the second version with name fixes with a second private message. Inputs have no longer space and instead have “_”. So it -must- work. Incase it doesn’t, launching, please go to Input_System_Ryu, Input_System_Ken, Movement_System_Ken and Movement_System_Ryu and compile them. I didnt need them but eh… maybe you need it. >.<

As I said, I downloaded my own project, and packaged it fine. I have no idea why the inputs are still having the same problem though. As you see from the log files, I do not get such warnings.

UPDATE:

Miss , a friend of mine downloaded the project from the second private message I sent you, and he had no problems launching the game, or packaging. Give it one more try please, and delete anything related to old project. :slight_smile:

Hey,

Your friend is correct, it seems to be working better now. I did notice I could not throw any punches, or control the blue character. Was this intended, ?

Looking forward to hearing back, enjoy your weekend! :slight_smile:

I hope you get a better weekend than I do! Working in airport that is open 7/24 means no meaningful weekend for me. :slight_smile:

You can only control blue character if you have Numlock On. Its just a design mistake of mine to have both characters moving with arrow and num keys. Without Numlock blue character movement buttons move red character instead of blue. :slight_smile:

Though that is not really the problem, as I can fix it later. The reason you can’t punch or kick in packaged game yet you can do in editor play is explained in detail with pictures right above your Answer-Post with the warnings you showed me and it shows the temporary fix aswell!

In short, the reason you dont see punches and kicks is, there is a struct(named Act System Ken) check related to it’s certain variables being true, in order to continue play the animation etc. But despite the fact that the struct is all set to true on its booleans, packaged game does not care, keeping the default value “false” which causes no animation to play.

Also, in editor gameplay, you supposed to see the screen like this;

As you see, the Ability_System_Ken Child Actor ticks (its just a string spam) in editor, also Collision_System_Ken print spams the parent variable values it has changed in its properties.

Here is in the packaged game;

You see the Ability_System_Ken is not ticking in packaged game, also Collision_System_Ken is using its default parent values unlike the editor, so the values are all spammed as zero, which causes the system to not function.

Thanks for your time again. :slight_smile:

Hey,

So, I’ve had a developer look over this issue and what’s going on looks very similar to a bug we had in the editor recently which was UE-17464. This bug has been closed for 4.9. It’s suggested that you upgrade your 4.9 preview to preview 4 and create a copy of your project for 4.9 preview 4 and see whether or not the same issue occurs.

Thank you for your patience, looking forward to hearing back from you. :slight_smile:

I will check and let you know , I am glad to know at least this is known. :slight_smile: