Add marketplace content to newer engine version even if not compatible

I have an asset pack I bought a while back that I want to add to my new 4.15 project. The problem is that the author of the asset pack clearly no longer maintains it, and it’s compatibility has not been upgraded past 4.12. This wouldn’t be a problem (since it’s just art, it’s most likely 100% compatible already), but the Epic Launcher won’t let me add the pack because of the compatibility.

There should be a way to force add a marketplace item to a project regardless of version compatibility, with a warning that says that something may not work and it’s the user’s responsibility to fix any problems since the author hasn’t upgraded the compatibility.

I’m going to just download it and manually add it in File Explorer, but this would be a good feature for the Launcher to have.

1 Like

Hi Fragfest2012,

Have you tried the following steps:

  1. Click Add to project on the vault item of choice.
  2. Select Show all projects on the “Select the Project to Add the Asset to”
  3. Select the incompatible project. This should show the warning “Asset not compatible with version X.X, please select closest alternative version” with a control for selecting a version.
  4. Select the closest alternative version from the select version dropdown.
  5. Click “Add to Project”
3 Likes

I cannot believe I didn’t see that checkbox…Thanks!

1 Like

thanks dude helped

Is there any way to do the same for a PLUGIN? I purchased the plugin and built the whole project’s logic around it, but as it is not updated for newer versions of UE, I stuck with the old version of UE. I am pretty sure it will work in newer versions if I can somehow force UE to accept the unsupported plugin. Any ideas anyone?