Error Generating Visual Studio Files With CMD Or PowerShell

When attempting to generate my VS files via CMD or PowerShell I receive the error "Targets with a unique build environment cannot be built with an installed engine.". I initially removed the "&" and used my build command in CMD, however using the "&" and PowerShell still results in the same error. My build command is "C:\Programs\Unreal Engine 5.3.2-CSS-66\Engine\Build\BatchFiles\Build.bat" -projectfiles -project="C:\Programs\Unreal Engine 5.3.2-CSS-66\FactoryGame.uproject" -game -rocket -progress. I have searched the docs for this error, but have not found anything detailing it. Could this be some kind of installation issue, or something different?
Solution:
Update: This morning I decided to simply nuke my Unreal Editor installation and start over. This time I left the default UE installation folder name alone and put the starter project files in a subfolder. After re-integrating Wwise with the start project again, I used the context menu to generate the VS files and it worked without any errors! Now, instead of the file path looking like "C:\Programs\Unreal Engine 5.3.2-CSS-66 (raw project files stored here without a subfolder)" it now looks...
Jump to solution
16 Replies
Rex
Rex3mo ago
Tried generating VS project files through the context menu? https://docs-dev.ficsit.app/satisfactory-modding/latest/Development/BeginnersGuide/project_setup.html#_generate_visual_studio_files If updating from an earlier project version, also see https://docs-dev.ficsit.app/satisfactory-modding/latest/Development/UpdatingFromSml37.html There's a specific procedure to follow if you want to keep both engine versions installed at the same time
AtomicFallout757
AtomicFallout757OP3mo ago
Yes, I tried that first but it failed. I am only updating a small mod and as such I didn't have anything worth keeping in my old Unreal Engine installation (aside from a few small files I backed up elsewhere) so I uninstalled it before installing the latest engine when I started.
Rex
Rex3mo ago
What did it fail on?
AtomicFallout757
AtomicFallout757OP3mo ago
Generating the files through the context menu. The context menu error is longer but displays the same text at the end "Targets with a unique build environment cannot be built with an installed engine." as it does when I try using CMD or PowerShell instead. I have the engine installed to a short file path, but could this be happening because I changed the installation folder name? I would think not, but I have ran into some programs that are sensitive to such changes.
Rex
Rex3mo ago
Not sure, but my engine is in C:\UE\5.3.2-CSS-66 I installed it there
AtomicFallout757
AtomicFallout757OP3mo ago
Hmm, sounds like it shouldn't be a problem then.
Rex
Rex3mo ago
Try redownloading the Starter Project
AtomicFallout757
AtomicFallout757OP3mo ago
Ok, I just finished downloading another copy of the latest starter project, replacing the old files and re-integrating Wwise into the project. Unfortunately it is still failing with the same error when using the context menu or CMD / PowerShell to generate the VS files.
Rex
Rex3mo ago
replacing the old files
What do you mean?
AtomicFallout757
AtomicFallout757OP3mo ago
Replacing / overwriting the old starter project files to get rid of them. Dragging and dropping the new files over the old files and clicking overwrite.
Rex
Rex3mo ago
That won't work, the problem can be in newly-created files...
AtomicFallout757
AtomicFallout757OP3mo ago
In the latest starter project? I can't use anything older to get the mod working on 1.0.
Rex
Rex3mo ago
Set up the starter project first, then once you can open the editor try adding your mod's files
AtomicFallout757
AtomicFallout757OP3mo ago
I can't use the editor because I haven't generated the VS files. I'm not able to do anything with my mod files yet because I don't have UE fully set up.
Mattigins
Mattigins3mo ago
For a sanity check, try putting the starter project in a different location rather than replacing the old. Also don't modify it at all (don't add your mod files) before you generate the project files.
Solution
AtomicFallout757
Update: This morning I decided to simply nuke my Unreal Editor installation and start over. This time I left the default UE installation folder name alone and put the starter project files in a subfolder. After re-integrating Wwise with the start project again, I used the context menu to generate the VS files and it worked without any errors! Now, instead of the file path looking like "C:\Programs\Unreal Engine 5.3.2-CSS-66 (raw project files stored here without a subfolder)" it now looks like "C:\Programs\Unreal Engine - CSS\SatisfactoryModLoader-master (project files stored in this subfolder)". Hopefully this helps someone else having the same issue. Thanks for the help and suggestions.
Want results from more Discord servers?
Add your server