Hm. Alright, after a couple days I came back to this to try it again following those steps and I did exactly the steps you described. But three things happened that I’m sure are not right.
- When the binary builder runs, it doesn’t frame the command prompt window inside of the binary builder like the picture at the top. It just closes it and the command prompt comes up and begins running through it.
- At the end the command prompt closed suddenly, but i managed to make out it saying warning with some red text by it.
- Still no LocalBuilds folder.
At this point I’m assuming it’s the engine version I downloaded. There was a customized version that I wanted to use that has some cool toon shading options in the material editor. Not sure why it doesn’t want to compile this, and I can’t even see what happened at the end of the automation tool command prompt to see what failed if anything. There was a size bump somewhere as it went down 11gb. Which seems about right for an engine build. But it’s not in the engine folder of localbuilds like its supposed to be.
Edit: I just downloaded the normal 4.16.3 release code and tried to do the steps. Still no Local builds folder and the above steps happened again, although I can’t confirm the warning this time because it disappeared too fast. I really don’t know what I might be doing wrong here. Can you point me in the right direction here @ryanjon2040 ?