EvergineTeam / Feedback

Feedback, feature requests, and bug reports for Evergine.
https://evergine.com
14 stars 1 forks source link

Issue with WPF #120

Open aka-blackboots opened 2 years ago

aka-blackboots commented 2 years ago

When I'm trying to create WPF project, I'm referring Automotive Demo for it. I was able to add WPF basic components. When I added Evergine packages it is giving me a error as

"GetScenesToCompileTask" task was not given a value for the required parameter "ContentDir"

While adding packages do I need to make any configuration changes?

aka-blackboots commented 2 years ago

Project file, profile name or content folder can not be resolved from Evergine.Targets.Targets

emepetres commented 2 years ago

Hi @aka-blackboots , thanks for your report.

We have currently a rather hidden requirement for WPF projects that the Evergine folder has to be named the same as the parent folder., that could be the origin of your issue. We want to change the WPF samples to reflect that.

To solve this, you can set the the Evergine project name property at your main WPF project csproj:

<EvergineProjectName>[The Evergine project name]</EvergineProjectName>

BTW the evergine project is the one that has the scenes on it. The name is the same as the project's folder.

Hope that it helps!

sageikosa commented 1 year ago

Still true in 2022.9.28.6. Adding the suggested property to csproj file does resolve the issue, so it's not catastrophic, just a little jarring if you are trying to roll your own WPF application, as it is is not one of the provided profiles from the launcher.

KonradZaremba commented 1 year ago

Hi, unfortunately, I have been stuck in the same spot and the solution doesn't work. I also couldn't find any info about content compilation in the docs. Kind investigated it up to this point :D

edit: I have managed to force the compilation of assets by setting up EvergineAssetContent to location but it doesn't load assets on startup.

JuandreG commented 1 year ago

This seems to still be an issue. When creating a Evergine project then trying to reuse that project across multiple UWP projects I get the same error.

The original UWP project that is created with the Evergine project works, probably because the name is the same. But whenever that name changes this error occurs.

But my goal is to be able to use the Evergine project across multiple UWP projects.

RayLiu516 commented 7 months ago

After tracking the build log, we found a solution.

You will need to add the follwing project setting in your project file (*.csproj): <EvergineProjectFilePath>[The Evergine project path]</EvergineProjectFilePath>

The project file path can be relative or absolute. And must point to the .weproj file.

Like: '../3DModel/3DModel.weproj' or 'c:\xxx\xxx\source\repos\3DModel\3DModel.weproj'.

Hope this helps.