LevelSequence BindingReferences causing maps to be cooked

[Max.Chen]

Hello Geordie,

Soft references are still pulled in for cooking. So, you’ll need to clean up the soft references to the maps if you don’t want those maps cooked.

I did some tests on my end to confirm this and to confirm this also happens without Sequencer in the mix. The test I did without Sequencer was a variation of yours:

1. Create a map called MapDontCook
2. Create a blueprint with a soft object reference and assign the value to an actor in MapDontCook
3. Add that blueprint to MapDontCook
4. Create a map called DefaultMap, add that blueprint to it
5. Make DefaultMap the only map that is cooked (GameDefaultMap and list of maps to include in a packaged build)
6. Cook and notice that it the log indicates MapDontCook is being pulled in.

Also, I found this related forum post as well:

500×500 2.84 KB

I have a blueprint that has references to some data tables. I made it so that these are soft references instead of hard references and using the reference viewer’s ‘show soft references’ check I’ve made sure that these are in fact soft references, still they are treated as hard references and packed with said blueprint. One weird thing is that they are ‘white lines’ instead of the expected red ones as is the case for all soft references (right?) What does this specific line represent (both whi…

There is an option you can pass to the cooker: -SkipSoftReferences but that looks to be only for debugging purposes. I tried to run it with your test case, but it gave me a few errors so I don’t think it’s a viable option. There’s documentation about it here:

https://dev.epicgames.com/documentation/en\-us/unreal\-engine/cooking\-content\-in\-unreal\-engine