“Unhandled exception: UnauthorizedAccessException: Access to the path ‘F:_\UntitledCoopGame\plugins\AdvancedSessions\Binaries\Win64\UnrealEditor.modules’ is denied.”
I was able to locate this file in the directory above, but don’t seem to have any program capable of opening files of type “MODULES File”. Pretty much at a loss with what to do here, so any assistance would be greatly appreciated.
Three things I would check with this that can cause it
Ensure you’re not running into a file lock due to VS or UE Editor still being open when you’re trying to update the modules.
Make sure you don’t have the files on a read-only drive or something of that nature.
Ensure that the plugin files were built with the same version of UE that you’re trying to use it with. (Incompatibility on version can cause this error)
Much appreciated for the response! Unfortunately, neither appeared to be the issue, so I went ahead and nuked my plugins folder. I got a lot less errors after recompiling, but this is what’s being produced as of now:
I’ve made some progress, but still no luck in actually fixing my inability to compile C++ code. The following appears to be pointing at missing source files (which exist in other directories). I’ve attached a screenshot of the errors in VS2022 as well as the error output log in a .txt file:
I was able to resolve MSB4019. The issue appeared to be that $(EngineDir) wasn’t being explicitly defined in the ScriptGeneratorUbtPlugin.ubtplugin.csproj file:
I also tried to remove my Binaries, Intermediate, and Saved files in my project workspace to see if that would help, but it only ended up removing my entire UE5 and Games directories.
(Or one similiar) - The ‘VisualStudioTools’ is referenced in your build and is either not installed, not
part of your current build, or it’s incorrectly referenced. If you go into your Build.cs and you see "VisualStudioTools" in there, remove it unless you explicitly need it. That should clear the issue unless you’re intentionally putting it in there.
Thank you so much! I opened my build file and saw that line was missing, added it, and recompiled. No more errors are being produced. Instead, I’m getting a LOT of warnings now:
You’re most welcome. The warnings it’s listing may not cause any issues. But, I’d google each one and look at the things they can cause individually and how to resolve them. Those are fairly common. There should be a ton of info out there on them.