Level referenced by a level instance is still cooked even though a primary asset label marks it as "NeverCook"

Development Pipeline & Plugins
, ,
1

Hello,

We recently found that levels referenced by a level instance are still cooked even though we have a primary asset label that marks it as “NeverCook”. This appears to be caused by the void ALevelInstance::OnCookEvent logic which always add the level to be cooked.

I find it odd that primary asset label cook rules are being overwritten here. This gives us no final control over what levels are cooked as it’s easy for somebody to accidentally reference a level by mistake.

I wanted to ask, is this expected behaviour? If so, is there any way to have a final control mechanism to set this content to never cook?

Cheers

[Attachment Removed]

2

Steps to Reproduce

  1. Create a world partitioned level A.
  2. Create a level B.
  3. Reference level B inside level A via a level instance.
  4. Reference level A and B with a primary asset label with priority 2 to set them to always cook.
  5. Reference only level B with a primary asset label with priority 100 to set it to never cook.
  6. Observe that level B is cooked and available inside level A.
    [Attachment Removed]
3

Hello!

This is an expected behaviour, The NeverCook property will be ignored in the case of a hard reference as that would results in missing assets otherwise.

Martin

[Attachment Removed]