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

Support for engine files #27

Open
NorthBlue333 opened this issue Dec 5, 2023 · 9 comments
Open

Support for engine files #27

NorthBlue333 opened this issue Dec 5, 2023 · 9 comments
Labels
triage reasoning about a feature (new or change)

Comments

@NorthBlue333
Copy link

NorthBlue333 commented Dec 5, 2023

Hello!
We tried the extension which seems great, but we do a lot of work directly in the engine.
Would it be possible to support the engine plugins and source paths? As a note, we use a custom installation for the engine. It could be possible to customize this path in the options maybe?

image

I can provide more info if needed.

Thank you for your time!

@fdefelici
Copy link
Owner

fdefelici commented Dec 6, 2023

Hi @NorthBlue333,

when working on the Engine are you using the standard workflow https://docs.unrealengine.com/5.3/en-US/building-unreal-engine-from-source/ to setup Visual Studio?

@fdefelici fdefelici added the triage reasoning about a feature (new or change) label Dec 6, 2023
@NorthBlue333
Copy link
Author

NorthBlue333 commented Dec 7, 2023

Hi,

I did not setup our engine, but it seems the workflow is (a bit) custom.
We do not have a root folder containing the Engine folder and the game projects. Each game project contains a .sln file, and we use these projects to work on the engine.

> Root
>> Engine
>>> Source
>>> Plugins
>> Game1
>>> Source
>>> Plugins
>>> Game1.sln (<-- project opened)

Could it be the reason the extension is not working on the engine's paths? Setting UE5 as the startup project does not change anything.

Thanks for your time!

@fdefelici
Copy link
Owner

I was trying to understand your project organization and evaluate a possible enanchement, because currently FUnreal is implemented for Game Development project type only, and the Engine project is skipped on purpose.

About your project oraganization, if I understood well, you use standard UE Game Development projects which point the custom Engine. So when you open a game project solution on VisualStudio you always have one Engine project and one Game project something like this:
image

Did I get it right?

@NorthBlue333
Copy link
Author

Yes that seems right!
Is there any reason the Engine is skipped? Performance maybe?

Thank you again for your time, it does not seem much but the extension would be a great improvment in our workflow.

@fdefelici
Copy link
Owner

Well, in first place the idea was just to support Game Development project. Futhermore in the past I saw some engine module not following the standard folder organization. And then, yes some perf hits could happen.

Anyway I could reason about this implementation.

Could you share your solution file (.sln)? And which engine version you are customizing?

@NorthBlue333
Copy link
Author

gameproject.txt

Sure, here it is.
We use Visual Studio 2022 and Unreal 5.2+ (we are actively updating the engine while we are not in production).

@fdefelici
Copy link
Owner

Thanks for the info.

Another question: currenlty in case you add a file to the Engine plugin/source, do you run UBT from the .uproject file related to the Game project, in order to make VS refresh? Like this:

image

@NorthBlue333
Copy link
Author

Yes, that's what we do!

@fdefelici
Copy link
Owner

OK. I'll try to do some in-depth analisys for the feasibilty of this feature.

Eventually, If I'll have other questions I'll back to you.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
triage reasoning about a feature (new or change)
Projects
None yet
Development

No branches or pull requests

2 participants