Code 6 Issue
so I wanted to get into Satisfactory Modding but get punched in the Face when trying to Build FactoryGame for the first time. Pretty much followed the Docs to the tea.
heres the Log, its rlly short since it basically fails like 2 seconds into the build:
Solution:Jump to solution
default options from game dev and c++ desktop workload + additionally:
MSVC v143 - VS 2022 C++ x64/x86 build tools (v14.34-17.4)(Out of Support)
.NET 6.0 Runtime (Out of support)...
16 Replies
Note: the "exit code 6" message which appears in build logs is very vague - it indicates that building C++ failed for some other reason. If you'd like help with this error, make sure that you also share the rest of the build output as described here (or from the Alpakit Log tab if you're getting this at mod package time)
https://docs.ficsit.app/satisfactory-modding/latest/Development/BeginnersGuide/project_setup.html#_the_command_exited_with_code_6
-# Responding to
exitcode6moreinfoneeded triggered by @RovetownIm on WIndows 11, with the VS Setup from the SML Config provided by the Docs.
Fresh Clean VS 22 install, all steps done without issue.
Looks like you didn't integrate Wwise
It's complaining about missing definitions from Wwise
weird it did integrate to my knowledge. gonna do it again then...
it shows as integrated though inside wwise
redid the wwise integration, seems to have again worked
Same Error Message
Try generating project files again
The step about right clicking the .uproject file and generating visual studio files
Did that, same issue... ima just start over from the githubs .exe step and fully clean reinstall vs22 again
I don't think you need to restart everything
Try restarting the project setup, i.e. redownload the SML GitHub repo and go from there
k ill try that
Solution
default options from game dev and c++ desktop workload + additionally:
MSVC v143 - VS 2022 C++ x64/x86 build tools (v14.34-17.4)(Out of Support)
.NET 6.0 Runtime (Out of support)
.NET Framework 4.8.1 SDK
----------------------------------
Redid the Project and went from there. Reinstalled Wwise 2023.1.3.8471. Re-integrated Wwise and Generated Soundbanks for all platforms.
Then Generated Project Files. Opened the solution with VS22. Besides a warnign that can be ignored, opening was fine. I ignored the extra components notification. I set the build to Development Editor Win64. i selected the FactoryGame, made it my startup project. I then selected the FactoryGame again and selected Build.
seems something in the vs22 install had an issue - build now runs. my guess is that the config on the docs selects some additional components besides whats written in the manual install, which will result in build fails.
i confirmed this on my laptop which has a fresh win 11 install. did the same thing again there but with the config from the docs - same error as mentioned.
@Mircea sounds like the vsconfig needs to be updated
I need to say thank you to the participants and OP for this thread.
This successfully helped me diagnose my code 6 build issue (missing source files, it seems?).
I also had to re-download (via git) the SML project, integrate Wwize, Generate SoundBanks for All Platforms, and Generate VS Project files. Then set the build to Development Editor and set as the startup project (
Game/FactoryGame).
Building was successful, however the MSVC compiler was complaining about heap size (I kept building, and this worked too, eventually).
If anyone else is having issues with build failures relating to: C3859: virtual memory range for PCH exceeded or C1076: compiler limit: internal heap reached, check if you have your page file disabled or too small. I had page file disabled to save on disk space, causing the max heap size error. Enabling page file (I set it to system managed on my Windows OS-installed drive) or setting a larger page file can minimize or solve that issue. You can find more info on how to do this here: https://devblogs.microsoft.com/cppblog/precompiled-header-pch-issues-and-recommendations/
I hope my follow-up problem and solution helps someone and is helpful for this community. Again, thanks all for the help.
remember for the future that "code 6" shows up for nearly every failure to build, so the actual issue you had is C3859 and C1076
Sorry I should have been more explicit - I had the exact same issues as OP to the letter (his logs output were practically identical to mine).
My contribution refers to an issue that followed the failure to build as described by OP. My apologies.