I downloaded valley of the ancient but it cannot be opened with UE 5.1.0.
It says some plugins are built in 5.0.0.
I tried to rebuilt it with visual studio project. But there were some errors that “AddPatchTool.h” cannot be found.
It seems they belong to MeshModelingToolsetExp experimental plugin.
How can I fix it?
Or is there any valley of the ancient build for UE 5.1.0
Did you ever figure this out?
I’m having a similar issue, where the current Valley of the Ancients project does not load for me. It says it wants these “plugins”:
And fails to open:
Plugin ‘InstanceLevelCollision’ failed to load because module ‘InstanceLevelCollision’ could not be loaded. There may be an operating system error or the module may not be properly set up.
But AFAIK, these aren’t plugins that have ever been available in UE5 EA2 or UE5 Preview from Epic store, so must one do a build from GitHub to access Valley of the Ancients? Yeesh.
Fixed it!
But what a weird solution.
I see that in the downloaded Valley of the Ancient, a Plugins directory is included, which contains:
So… that must be what it’s looking for, but not finding.
I take them, and move them to the Plugins directory of UE_5.0\Engine\Plugins
try to reopen, and… nothing.
So, dismayed, I put them right back where I found them in the original ValleyOfTheAncient plugins directory, and for kicks try once more to reopen and now it works for some reason.
weird.
It happens to me too, and I can’t make it work.
As I have read in this reddit post, we are not the only ones. I hope Epic fix this soon. I’m having the exact same problem the OP has.
After using that zip file in that reddit thread, generate the visual studio project (right-click ValleyoftheAncient.uproject).
Then reopen the project, confirm rebuild modules.
After a while UE5 Preview 2 should start loading the project.
I installed the project again on the disk where the UE5 program is located and everything worked!!!
I understand you’re having trouble opening the Valley of the Ancient project with Unreal Engine 5.1.0. This is a common issue when trying to open projects created with older versions of the engine in newer versions. Let’s break down the problem and explore some potential solutions:
Version compatibility:
Valley of the Ancient was originally built for UE 5.0.0, which explains the plugin version mismatch you’re encountering.
Plugin issues:
The error you’re seeing related to “AddPatchTool.h” and the MeshModelingToolsetExp experimental plugin suggests that there might be incompatibilities with these experimental features between versions.
Rebuilding attempt:
It’s good that you tried rebuilding the project, but it seems this didn’t resolve all the issues.
Here are some potential solutions you can try:
Note: Always verify the authenticity and compatibility of any unofficial ports or modifications.
As of my last update, there isn’t an official Valley of the Ancient build specifically for UE 5.1.0. However, it’s worth checking the Unreal Engine marketplace or forums for any recent updates.
Disable experimental plugins:
Try disabling the MeshModelingToolsetExp plugin and any other experimental plugins in the project. You can do this by editing the .uproject file and setting these plugins to “Enabled”: false.
Migrate content:
Create a new blank project in UE 5.1.0 and try migrating the content from the Valley of the Ancient project into it. This might help bypass some of the version-specific issues.
Use UE 5.0.0:
If possible, consider using UE 5.0.0 to open the project as it was originally intended. This would avoid compatibility issues altogether.
Check for community solutions:
The Unreal Engine community is quite active. Check forums and community sites to see if others have found workarounds for this specific issue.
Rebuild from source:
If you’re comfortable with it, you could try rebuilding the engine from source with the necessary modifications to include the missing experimental features.
Remember, working with experimental features and migrating between engine versions can be tricky. It’s always a good idea to back up your project before making any significant changes.
If you decide to try any of these solutions, I’d be happy to provide more detailed guidance on the steps involved. Let me know which approach you’d like to pursue, or if you need any clarification on the options presented.