Understanding how builds work..

Development Programming & Scripting C++
1

First, I apologize if this question ended up in the incorrect forum. I am trying to understand builds. At one point in my life, I could have sworn that

  1. yellow warnings in the output log are simply warnings, meaning, the game will build *regardless *if the systems telling me that there is a problem
  2. red errors in the output log is stating, “Fool, fix this ■■■■ cause I’m not building a ■■■■ thing until you do.”

Is this philosophy correct?

2

Follow that closely and you will setup vs to work for you.
https://docs.unrealengine.com/en-US/…tup/index.html

3

@gamepainters I apologize, but I think I’m having a hard time following the typos.

Follow the [link] closely and this will work? Is that what you’re saying?

I’m not having c++/visual studio issues, I am having build issues within the editor:

File > Package Project > Windows > Windows 64 (choose my folder, then Cook)

4

What are the issues you are having when packaging?

5

I wish there was a way to color-code the output log… The yellow warnings is because i am missing materials or a material is broken or animations are missing. These things, I am actively cleaning.

Its the red errors that we have had issues with for over 6 months:

None of the guys on our team know what a UAT Helpers is… we THINK its “unreal animation tool” But even if thats true, we dont understand the error.

6

You have a stack overflow somehow. This is what happens when a function calls itself recursively in an infinite loop. Unfortuantely it appears you don’t have debug symbols installed so the log isn’t telling you what function it actually is.

UAT is Unreal Automation Tool - it’s part of the build system. Before doing anything, install the debug symbols from the launcher. Also, at the bottom you can see that it spat out another log file somewhere else, be sure to check that one too.

7

I apologize, but I think I’m having a hard time following the typos.

Follow the [link] closely and this will work? Is that what you’re saying?

I’m not having c++/visual studio issues, I am having build issues within the editor:

File > Package Project > Windows > Windows 64 (choose my folder, then Cook)
[/QUOTE]

Sorry i thought you had problems with vs compiling. I remembered the setting to turn off or ignore the errors < that is what i was thinking when reading your post.

In vs if you right click UATHelper then you can go to where it is defined or referenced at in code. It will show you everywhere it being used.

8

@ Thank you, I will look into this immediately. I will learn about how to install debug symbols because this is new education for me. Thank you also for teaching me about the definition of UAT and we will check that other log as well.

@gamepainters Thank you

9

You can also try packaging from an Editor launched from Visual Studio in debug mode. This might let you step through and see what asset is causing the issue . (Although many times the package commands are launched as separate processes and this wont work ) .

10

This is a small tutorial as to how to install the Debugging Symbols:

tutorial_installing_DebugSymbols.png
tutorial_installing_DebugSymbols.png1536×619 81.2 KB

11

@ Attached is my output log related to UAT Helper

@OptimisticMonkey** @**gamepaintersthank you for making time to offer to help. Do you guys take on Freelance work? @ No disrespect to you, I extend the same question, however, it appears that you have a great job right now :smiley:

12

Also, I didn’t get a direct answer to my initial question. I am 20 year veteran artist, but I didn’t get into heavy in-engine work until this year. I haven’t had to.

I am not trying to be annoying, but it is my goal to not only obtain a working build, but also to receive proper education:

  1. yellow warnings in the output log are simply warnings, meaning, the game will build *regardless *if the systems telling me that there is a problem. <— This is the biggest question that I need answered. We are a small studio and we need to mind our budget. We know we have warnings, however, if we can ignore them and instead, focus on fixing errors that will allow us to build, we can begin solving problems.

We need to be able to focus and prioritize the this now, today.

  1. red errors in the output log is stating, “fix these issues because I am to building until you do.”

Is this philosophy correct?

13

A warning is always there for a reason. They are not errors and won’t prevent you from packaging but I don’t personally recommend you to just ignore all the warnings. Read them and decide for yourself if there is anything to fix.

For errors, yeah you will always want to fix those - don’t matter what.

14

@_brunocoimbra Right, well, I’m not stating that theyll never get fixed, we just need to prioritize what the immediate needs are that are preventing the build to happen.

Thank you for answering the philosophical question. Do you do contract work?

Now to the output log!

This is still an open topic. I will re-attach the output log to this reply if someone is still available to help.

15

Looking at the log, it’s difficult to say. Jamsh is right in that you have some object which is referencing some object which is referencing the original object (A -> B -> A till Infinity). As for WHAT object is causing that, I’m not sure. The problem with the amount of warnings in your stuff is that can pollute objects down stream, the build tries to hobble along - but it’s not 100% guaranteed that warnings won’t screw you later in a build.

Your options are to either have a programmer attach to the debugger and catch the stack overflow, start fixing warnings and pray one of them fixes the error, or start disabling content bit by bit till you find what is triggering things (start with a really simple scene and package that, then a bit more, etc).

16

@ExtraLifeMatt Thank you for your time Matt! We will look into this immediately!

17

@_brunocoimbra @ExtraLifeMatt @OptimisticMonkey @gamepainters Thank you all for your help! We figured out our issue. Inside the project settings, we didnt have our maps setup in the Cook List! It sucks that it took us like 6 months to figure this out, but at least we solved it on Dec 1. I forgot to say thank you. :smiley:

I hope this helps someone else out in the future!