Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add Visual Studio 2022 Source Code Editor Support #161

Closed
Somersloop opened this issue Dec 28, 2022 · 2 comments
Closed

Add Visual Studio 2022 Source Code Editor Support #161

Somersloop opened this issue Dec 28, 2022 · 2 comments

Comments

@Somersloop
Copy link

Hey Guys,

I just finished going through your "Getting Started" Guide and set up my SatisfactoryModLoader project to start modding. As stated in the guide, i installed Visual Studio 2022 and created the simple mod from the guide. Everything went pretty smooth until i tried to derive a c++ class for a new hologram.
The Unreal Editor was not able to detect any c++ compiler and suggested to install Visual Studio 2019. Thus i was not able to create the c++ class from the Unreal Editor.

With some research i found some similar problem with a hint to the solution:
https://www.reddit.com/r/unrealengine/comments/t5awb7/wanting_to_start_a_new_project_after_updating_to/

Looking through the UE4 Engine plugins, i found the Visual Studio Source Code Access plugin and the fix in UE 5 master repository:
https://github.com/EpicGames/UnrealEngine/commit/b23fc15cac880cbb297b396571c01d2ff9c7a9f5

I applied the modifications to my local engine and recompiled the plugin and now i can select the Visual Studio 2022 as Source Code Editor in the Unreal Editor preferences and create c++ classes without any problems.

I recommend to add any hint about this problem on the Getting started guide or to use Visual Studio 2019 by default or to Update the SatisfactoryModLoader project with the changes to support Visual Studio 2022

@budak7273
Copy link
Member

It should support 2022 once the U8 and UE5 update comes through, so it's not worth fixing this in the mean time

@budak7273
Copy link
Member

We might have to re-add the section of the docs talking about installing the extension now that it doesn't fail to install on VS 2022 like the old one did

@mircearoata mircearoata closed this as not planned Won't fix, can't repro, duplicate, stale Jul 13, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Development

No branches or pull requests

3 participants