DLC Support still not working

Development Platform & Builds
, , , ,
1

Hi everyone,

I was hoping that the 4.15 release would have fix the “Couldn’t update resources” error when trying to package a DLC but the error is still here. Before, there was a workaround by changing the engine source code → AnswerHub topic. But since the 4.14 the code has been changed (probably in order to fix the issue, without being really tested I guess since the issue is still here).
I’m maybe just doing it wrong though. But I can’t find any proper documentation of the DLC feature so yeah… :smiley: rock&roll.

Please find the log of the package process with the error here.

Even with this error, the .pak file is still generated in the folder \Plugins\MYPLUGINSaved\StagedBuilds\WindowsNoEditor\Themis\Content\Paks. However my .pak doesn’t seem to be loaded at runtime if I place it next to the main game .pak.

Would be glad to give more infos about this issue.

Any help ? :slight_smile:
Best regards.

Step to reproduce:

  1. Using the binary version of 4.15 : Create a new C++ project (Basic code) with StarterContent
  2. Open the project launcher
  3. Create a new profile named “FULLGAME”
  4. Do you wish to build ? Enabled
  5. Build configuration: “Shipping”
  6. How would you like to cook the content ? By the book
  7. Tick only WindowsNoEditor
  8. Cooked map : Tick all 3 maps (Advanced_Lightning, Minimal_Default, StarterMap)
  9. In Release/DLC/Patching settings tick Create a release version of the game for distribution
  10. Name of the new release to create: “1.0”
  11. In advanced settings: Tick Store all content in a single file (UnrealPak)
  12. Set Cooker build configuration to “Shipping”
  13. How would you like to package the build ? Set to “Package and store locally”
  14. Tick Is this build for distribution to the public
  15. How would you like to deploy the build ? “Do not deploy”
  16. Go back to the ProjectLauncher
  17. Launch the “FULLGAME” profile and wait for the process to finish
  18. Create a new blank plugin from the PluginBrowser named “testplugin”
  19. Restart the editor (and build the .dll)
  20. Open the project launcher
  21. Create a new profile named “DLCTEST”
  22. Do you wish to build ? Enabled
  23. Build configuration: “Shipping”
  24. How would you like to cook the content ? By the book
  25. Tick only WindowsNoEditor
  26. In Release/DLC/Patching settings: Release version this is based on: “1.0”
  27. Tick Build DLC
  28. Name of the DLC to build: “testplugin”
  29. In Advanced Settings: Tick Store all content in a single file (UnrealPack)
  30. Cooker build configuration: Shipping
  31. How would you like to package the build ? Set to “Package and store locally”
  32. Tick Is this build for distribution to the public
  33. How would you like to deploy the build ? “Do not deploy”
  34. Go back to the ProjectLauncher
  35. Launch the “DLCTEST” profile and wait for the process to finish

The error should happens here.
My log following theses steps here.

Hope this helps.

2

Hey NymKappa,

Would you mind running me through your process so that I can reproduce this issue on my end? What steps are you following when you are seeing this issue?

Thanks!

3

Hi Sean. I’ve updated my original question. Please find a step by step there. Best regards.

4

Thanks for the steps.

I’ve reproduced the issue, and the behavior seems like a bug to me, so I’ve entered a ticket which you can track using the link below:

Thank you for your report.

Have a great day

5

Thank you. Also, if the DLC system is actually supported in UE4, it would be great to get an entry in the documentation at this chapter

Best regards.

6

I am also experiencing, this issue on version 4.14 of the engine, custom compiled.

7

Any new updates on this? I just ran into the exact same issue and checked UE-42880, which is not updated so far.

Is this method using a source built engine still the only workaround to build DLCs…? :frowning:

8

As I said, the code has been changed since this post so it’s not applicable anymore. Maybe you can try to get into the new code and try to check where the error is raising.

9

You might solve this by not using Package and store locally.
Try changing DLC build step’s How would you like to package the build ? to Do not package.

10

see this it is helped