Disabling plugins forbids dlc packaging

Development Pipeline & Plugins Plugins
, , , ,
1

Hey,

I’m trying to package some dlc that contains only content (a few static meshes, nothing else), so i unchecked pretty much everything in the profile launcher (no build, no include…)

Here is the configuration i use:

85048-dlcconf.png
85048-dlcconf.png1117×968 84.8 KB

When trying to package i get the following leapmotion error:

LogPackageName:Error:
DoesPackageExist: DoesPackageExist
FAILED:
‘/LeapMotionController/LM_PassthroughMaterial.LM_PassthroughMaterial’
is not a standard unreal filename or a
long path name. Reason: Path does not
start with a valid root. Path must
begin with: ‘/Engine/’, ‘/Game/’,
‘/Paper2D/’, ‘/TempAutosave/’,
‘/Config/’, ‘/Script/’, or ‘/Temp/’

When unchecking the paper 2D plugin (in Edit/Plugins/2D) i get the same error with paper 2D but the error disappears when i paper 2D is enabled.

But with the leap motion controller plugin (edit/plugins/input devices), it doesn’t matter whether it is enabled or not, i get the error any way. As a result, i currently can’t package the dlc.

It used to work until 4.11 preview 6 (i didn’t try to package the dlc with p7 and p8). I am now using the stable 4.11.

I don’t own the leap motion controller, so obviously there is no LMC plugged in.

I enclose the full log file.

Thanks for any help.

[link text][2]

2

Hi ,

Would it be possible to get the full file path to where the file mentioned in the error is located? Also, is this something that you are able to reproduce in a new project/DLC that is not related to your current project?

3

Hi ,

Thanks for answering !

I couldn’t reproduce the problem in a new project (i bumped into another problem when trying to build a brand new third person project with shipping conf). I’ll try again tonight but i must go to work right now.

In the meantime here are some info that might help.

My project is installed on a different drive (H:) from the engine drive (native C:).

The engine is installed here:

C:\Program Files\Unreal Engine\4.11

and my project here:

H:\unreal_projects\yag

Here are a few bizarre things i noticed in case it helps:

  • There is no LeapMotionController dir anywhere in the engine plugin dir but i found a LeapMotion dir:

C:\Program Files\Unreal Engine\4.11\Engine\Plugins\Runtime\LeapMotion

  • Just above the error i sent you there is this message in the logs:

LogCook:Display: Invalidating cooked content because Engine:Core.System:Paths:…/…/…/Engine/Content ini setting was out of date

That could be related to the fact that the engine and the project are on different drives.

I couldn’t find a variable containing this path in my project config files.

Hope this helps !

Thanks

4

Problem solved. Strange one.

The culprit was the release version of my custom launch profile, aka AssetRegistry.bin.

After deleting it and rebuilding a new release version, everything worked fine.

The old one had been built with the early 4.11 previews and never since.

How a leap motion controller plugin sneaked in will remain a mystery. Well, those were previews so anything goes :slight_smile:

Cheers

5

Hi ,

I’m glad to hear that you were able to get past this particular issue. You were not the only person who ran into some trouble with the Leap Motion plugin when upgrading to 4.11, but as far as I can tell you were the only one with this particular issue. Please let us know if you start seeing this happen again.