# \[Major\] v34.30 introduced a new editor validation error and when fixed it results in a cook validation error **URL:** \ **Category:** Issues and Bug Reporting\ **Tags:** open, fortnite-creative, unreal-editor-for-fortnite, fortnite\ **Created:** [April 8, 2025, 2:50pm UTC](https://forums.unrealengine.com/t/major-v34-30-introduced-a-new-editor-validation-error-and-when-fixed-it-results-in-a-cook-validation-error/2446730 "2025-04-08T14:50:14Z")\ **Posts on this page:** 8\ **Page:** 1
**Author:** ![Velocity\_Zero](https://d1ap1mz92jnks1.cloudfront.net/user_avatar/forums.unrealengine.com/velocity_zero/32/1036910_2.png) [@Velocity\_Zero](https://forums.unrealengine.com/u/Velocity_Zero)\ **Post date:** [April 8, 2025, 2:50pm UTC](https://forums.unrealengine.com/t/major-v34-30-introduced-a-new-editor-validation-error-and-when-fixed-it-results-in-a-cook-validation-error/2446730/1 "2025-04-08T14:50:14Z")
### Summary There’s a new validation error for project that use `GameFeatureData` and `Base Maps` to compose the final scene from multiple level assets: ```auto UEFNValidation: Error: [AssetLog] /vz_anomaly_1/after_3430/level_b_after_3430 : /vz_anomaly_1/after_3430/level_b_after_3430 Level has 0 Island Settings Devices. Levels should have exactly 1. Unique actors: (ValkyrieValidator_WorldLimits). (FortValidator_WorldPartitionActors) UEFNValidation: Error: /vz_anomaly_1/after_3430/level_b_after_3430 Level has 0 Island Settings Devices. Levels should have exactly 1. Unique actors: (ValkyrieValidator_WorldLimits) UEFNValidation: Error: [AssetLog] /vz_anomaly_1/after_3430/level_a_after_3430 : /vz_anomaly_1/after_3430/level_a_after_3430 Level has 0 Island Settings Devices. Levels should have exactly 1. Unique actors: (ValkyrieValidator_WorldLimits). (FortValidator_WorldPartitionActors) UEFNValidation: Error: /vz_anomaly_1/after_3430/level_a_after_3430 Level has 0 Island Settings Devices. Levels should have exactly 1. Unique actors: (ValkyrieValidator_WorldLimits) ``` The example project is called `vz_anomaly_1`. Here are screenshots of the pre-34.30 project setup. ![image](https://d3kjluh73b9h9o.cloudfront.net/original/4X/f/4/2/f42a187ba3ab7accf8481c1308dd864ed45c52ac.png) ![image](https://d3kjluh73b9h9o.cloudfront.net/original/4X/2/7/9/2792462fec0efdf1c56fa2db3bf74e540660c71a.png) As you can see, the main scene is the composition of `vz_anomaly_1`, `level_a_before_3430` and `level_b_before_3430`. Additionally you can see that all levels have an `IslandSettings0` actor. After 34.30 update the editor complains about those additional levels containing the mentioned actor and requires the project to have only a single `IslandSettings` actor. The project has been then update into such state as shown in the following screenshots: ![image](https://d3kjluh73b9h9o.cloudfront.net/original/4X/c/9/0/c90506104e5b56e44faca9e5b91a71c0fac1c44c.png) ![image](https://d3kjluh73b9h9o.cloudfront.net/original/4X/7/8/1/78193a34cd362d6900412f2b3eadd6761df0b8ae.png) In the update version the main scene is now composed of `vz_anomaly_1`, `level_a_after_3430` and `level_b_after_3430` and only `vz_anomaly_1` level contains the `IslandSettings0` actor. After initial project setup, the editor had a hiccup and complained that `level_a_after_3430` still required an `IslandSettings` actor in order to validate: ```auto UEFNValidation: Error: [AssetLog] /vz_anomaly_1/after_3430/level_a_after_3430 : /vz_anomaly_1/after_3430/level_a_after_3430 Level has 0 Island Settings Devices. Levels should have exactly 1. Unique actors: (ValkyrieValidator_WorldLimits). (FortValidator_WorldPartitionActors) UEFNValidation: Error: /vz_anomaly_1/after_3430/level_a_after_3430 Level has 0 Island Settings Devices. Levels should have exactly 1. Unique actors: (ValkyrieValidator_WorldLimits) ``` The validation passed in this strange state and I could try launching the session where we would be greeted with a cook validation error message: ```auto PlatformCook: Error: We hit an error while cooking this content PlatformCook: Error: errors.com.epicgames.content-service.cook_failure PlatformCook: Error: CookJobId:b754864d-3e18-4e9f-8746-fe5760a5e930 PlatformCook: Error: An error occurred while communicating with the game servers (failed to cook module 56e358d6-4e5d-414c-e43a-70ae96da7530 (artifact 41b07854-84da-470e-bd81-741fa0824971:pc) (cookJobId b754864d-3e18-4e9f-8746-fe5760a5e930) with error code errors.com.epicgames.cookplugin.assetvalidationerror). PlatformCook: Error: AssetCheck: Error: /56e358d6-4e5d-414c-e43a-70ae96da7530/after_3430/level_b_after_3430.level_b_after_3430 Level has 0 Island Settings Devices. Levels should have exactly 1. Unique actors: (ValkyrieValidator_WorldLimits) PlatformCook: Error: LogCook: Error: /56e358d6-4e5d-414c-e43a-70ae96da7530/after_3430/level_b_after_3430 failed validation PlatformCook: Error: AssetCheck: Error: /56e358d6-4e5d-414c-e43a-70ae96da7530/after_3430/level_b_after_3430.level_b_after_3430 Level has 0 Island Settings Devices. Levels should have exactly 1. Unique actors: (ValkyrieValidator_WorldLimits) PlatformCook: Error: LogCook: Error: /56e358d6-4e5d-414c-e43a-70ae96da7530/after_3430/level_b_after_3430 failed validation ``` Since at this point of time `level_b_after_3430` was the only level that didn’t contain the `IslandSettings` actor, the cook validation error did only mentioned that particular level. I deleted the entries in the `GameFeatureData` and re-created them again, which resolved the validation issue on the editor’s side and I could finally remove the `IslandSettings0` actor from `level_a_after_3430` as well (see the previous outliner image). When launching the session we will now hit the cook validation issue for both levels. ```auto PlatformCook: Error: We hit an error while cooking this content PlatformCook: Error: errors.com.epicgames.content-service.cook_failure PlatformCook: Error: CookJobId:375610d6-dc99-46b9-8cc6-f310b9bee6de PlatformCook: Error: An error occurred while communicating with the game servers (failed to cook module 56e358d6-4e5d-414c-e43a-70ae96da7530 (artifact a4bbb055-55d1-47c2-a0c3-09dd0432c24c:pc) (cookJobId 375610d6-dc99-46b9-8cc6-f310b9bee6de) with error code errors.com.epicgames.cookplugin.assetvalidationerror). PlatformCook: Error: AssetCheck: Error: /56e358d6-4e5d-414c-e43a-70ae96da7530/after_3430/level_a_after_3430.level_a_after_3430 Level has 0 Island Settings Devices. Levels should have exactly 1. Unique actors: (ValkyrieValidator_WorldLimits) PlatformCook: Error: LogCook: Error: /56e358d6-4e5d-414c-e43a-70ae96da7530/after_3430/level_a_after_3430 failed validation PlatformCook: Error: AssetCheck: Error: /56e358d6-4e5d-414c-e43a-70ae96da7530/after_3430/level_b_after_3430.level_b_after_3430 Level has 0 Island Settings Devices. Levels should have exactly 1. Unique actors: (ValkyrieValidator_WorldLimits) PlatformCook: Error: LogCook: Error: /56e358d6-4e5d-414c-e43a-70ae96da7530/after_3430/level_b_after_3430 failed validation PlatformCook: Error: AssetCheck: Error: /56e358d6-4e5d-414c-e43a-70ae96da7530/after_3430/level_a_after_3430.level_a_after_3430 Level has 0 Island Settings Devices. Levels should have exactly 1. Unique actors: (ValkyrieValidator_WorldLimits) PlatformCook: Error: LogCook: Error: /56e358d6-4e5d-414c-e43a-70ae96da7530/after_3430/level_a_after_3430 failed validation PlatformCook: Error: AssetCheck: Error: /56e358d6-4e5d-414c-e43a-70ae96da7530/after_3430/level_b_after_3430.level_b_after_3430 Level has 0 Island Settings Devices. Levels should have exactly 1. Unique actors: (ValkyrieValidator_WorldLimits) PlatformCook: Error: LogCook: Error: /56e358d6-4e5d-414c-e43a-70ae96da7530/after_3430/level_b_after_3430 failed validation ``` With this, the issue which I now have in my main project, was fully reproduced in an isolated project. I worked on my main project for many month and cannot launch it anymore after fixing the in-editor validation issue, due to an additional cook validation issue. If I try to upload a private version of this project, we will instantly hit similar validation problem like on the cook’s end. ```auto UEFNValidation: /vz_anomaly_1/after_3430/level_a_after_3430 Validating asset UEFNValidation: Error: [AssetLog] /vz_anomaly_1/after_3430/level_a_after_3430 : /vz_anomaly_1/after_3430/level_a_after_3430 Level has 0 Island Settings Devices. Levels should have exactly 1. Unique actors: (ValkyrieValidator_WorldLimits). (FortValidator_WorldPartitionActors) UEFNValidation: Error: /vz_anomaly_1/after_3430/level_a_after_3430 Level has 0 Island Settings Devices. Levels should have exactly 1. Unique actors: (ValkyrieValidator_WorldLimits) UEFNValidation: /vz_anomaly_1/after_3430/level_b_after_3430 Validating asset UEFNValidation: Error: [AssetLog] /vz_anomaly_1/after_3430/level_b_after_3430 : /vz_anomaly_1/after_3430/level_b_after_3430 Level has 0 Island Settings Devices. Levels should have exactly 1. Unique actors: (ValkyrieValidator_WorldLimits). (FortValidator_WorldPartitionActors) UEFNValidation: Error: /vz_anomaly_1/after_3430/level_b_after_3430 Level has 0 Island Settings Devices. Levels should have exactly 1. Unique actors: (ValkyrieValidator_WorldLimits) ``` Don’t get me wrong, the new / first error message is actually correct and it seems like it does addresses my previous issue report [FORT-871013](https://forums.unrealengine.com/t/false-positive-error-warning-there-can-only-be-one-instance-of-actor-type-fortminigamesettingsbuilding-in-a-map/2383213). The problem is that the cook (server-side) seems not to have an updated validation rule set. The cook seems to behave as it was validating on PRE-34.30 rules which force each level to have an `IslandSettings` actor. Either way, the two errors bite each other. If you fix one, it will raise the other issue and vice versa. To further clarify, I am personally fine with having a single `IslandSettings` actor in my project, but I still need the ability to compose multiple levels via `GameFeatureData` in order to work on things like environment or the landscape individually. This is a very critical workflow. ### Please select what you are reporting on: Unreal Editor for Fortnite ### What Type of Bug are you experiencing? Other ### Steps to Reproduce Shown in the previous images as well as described in the summery. Additionally you can try the isolated project ` verse:/velocity_zero@fortnite.com/vz_anomaly_1/` (module: `56e358d6-4e5d-414c-e43a-70ae96da7530`). ### Expected Result - when composed sub-levels contain an additional `IslandSettings` actor, there should be an error (already the case) - the `Default Map` should contain only a single `IslandSettings` actor in all composed levels (already the case) - the cook should not require each level to have an additional `IslandSettings` actor (this is like PRE-34.30 validation state) ### Observed Result Either we run into a validation error on the editor’s side or when fixed we run into cook validation failure (server side). The cook should permit the project that contains multiple levels using `Base Maps` array in `FortGameFeatureData` and which has exactly 1 `IslandSettings` actor! ### Platform(s) UEFN ### Additional Notes As noted before, this issue persists in my main project and prevents me from launching a session. ---
**Author:** ![Bug-Reporter](https://d1ap1mz92jnks1.cloudfront.net/user_avatar/forums.unrealengine.com/bug-reporter/32/997076_2.png) [@Bug-Reporter](https://forums.unrealengine.com/u/Bug-Reporter)\ **Post date:** [April 8, 2025, 2:58pm UTC](https://forums.unrealengine.com/t/major-v34-30-introduced-a-new-editor-validation-error-and-when-fixed-it-results-in-a-cook-validation-error/2446730/3 "2025-04-08T14:58:15Z")
FORT-887061 has been created and its status is ‘Unconfirmed’. This is now in a queue to be reproduced and confirmed. ---
**Author:** ![Flak](https://d1ap1mz92jnks1.cloudfront.net/user_avatar/forums.unrealengine.com/flak/32/769441_2.png) [@Flak](https://forums.unrealengine.com/u/Flak)\ **Post date:** [April 8, 2025, 3:31pm UTC](https://forums.unrealengine.com/t/major-v34-30-introduced-a-new-editor-validation-error-and-when-fixed-it-results-in-a-cook-validation-error/2446730/4 "2025-04-08T15:31:56Z")
We’re checking into this! ---
**Author:** ![Jamie\_Dale](https://d1ap1mz92jnks1.cloudfront.net/user_avatar/forums.unrealengine.com/jamie_dale/32/1165413_2.png) [@Jamie\_Dale](https://forums.unrealengine.com/u/Jamie_Dale)\ **Post date:** [April 8, 2025, 4:01pm UTC](https://forums.unrealengine.com/t/major-v34-30-introduced-a-new-editor-validation-error-and-when-fixed-it-results-in-a-cook-validation-error/2446730/5 "2025-04-08T16:01:45Z")
I just want to make sure I’m understanding your example correctly, as it seems you have the following: - Default Map: vz\_anomaly\_1 - Map Data: - Map[0]: vz\_anomaly\_1 - Base Map: level\_a\_after\_3430 - Base Map: level\_b\_after\_3430 - Map[1]: level\_a\_after\_3430 - Base Map: level\_b\_after\_3430 - Map[2]: level\_b\_after\_3430 The way the validation works is the “Default Map” and any “Map” entries in the “Map Data” array are considered “primary” maps for validation, and these are the maps we start to count from, including any specified base maps in their counts. The validation is getting confused here because “level\_a\_after\_3430” and “level\_b\_after\_3430” are declared as both a “primary” map _and_ a base map. If you deleted entries 1 and 2 from the “Map Data” array then the validation should pass. Is there a reason you have it configured like this? ---
**Author:** ![Velocity\_Zero](https://d1ap1mz92jnks1.cloudfront.net/user_avatar/forums.unrealengine.com/velocity_zero/32/1036910_2.png) [@Velocity\_Zero](https://forums.unrealengine.com/u/Velocity_Zero)\ **Post date:** [April 8, 2025, 4:14pm UTC](https://forums.unrealengine.com/t/major-v34-30-introduced-a-new-editor-validation-error-and-when-fixed-it-results-in-a-cook-validation-error/2446730/6 "2025-04-08T16:14:13Z")
> [@Jamie\_Dale](#): > > Is there a reason you have it configured like this? I do have `Map[1]` and `Map[2]` in order to be able to load into those maps in a session to visually inspect them during development. The thing is, in the past those “primary” maps did not required the `IslandSettings` actor and could run without it. That’s the behavior I wish we could get again. In my opinion only the `Default Map` should be required to contain the actor for published islands while the other maps should validate without that actor. * * * I’ll try removing the other entries in my main project and see if I can finally enter the session. ---
**Author:** ![Velocity\_Zero](https://d1ap1mz92jnks1.cloudfront.net/user_avatar/forums.unrealengine.com/velocity_zero/32/1036910_2.png) [@Velocity\_Zero](https://forums.unrealengine.com/u/Velocity_Zero)\ **Post date:** [April 8, 2025, 4:29pm UTC](https://forums.unrealengine.com/t/major-v34-30-introduced-a-new-editor-validation-error-and-when-fixed-it-results-in-a-cook-validation-error/2446730/7 "2025-04-08T16:29:44Z")
I can confirm that I can finally launch into a session in my main project after removing the additional primary maps. It’s not a huge deal breaker, but it would require manual rewrite of `GameFeatureData` in order to inspect other levels individually. At least I can continue working on my project. 🎉 * * * If you try to load into a non-default level while it’s not being added in `Map Data`, the editor will show a pop-up message where the user can pick if the level should become the default level or added to `Map Data`. ---
**Author:** ![Bug-Reporter](https://d1ap1mz92jnks1.cloudfront.net/user_avatar/forums.unrealengine.com/bug-reporter/32/997076_2.png) [@Bug-Reporter](https://forums.unrealengine.com/u/Bug-Reporter)\ **Post date:** [April 14, 2025, 8:45pm UTC](https://forums.unrealengine.com/t/major-v34-30-introduced-a-new-editor-validation-error-and-when-fixed-it-results-in-a-cook-validation-error/2446730/8 "2025-04-14T20:45:46Z")
FORT-887058’s status has changed to ‘Ready for QA’. A member of the QA department is investigating the issue. ---
**Author:** ![system](https://d3kjluh73b9h9o.cloudfront.net/original/4X/7/1/3/713c9d3f58553f0de89543d76a8a3a2779dc9fa4.png) [@system](https://forums.unrealengine.com/u/system)\ **Post date:** [October 5, 2025, 2:50pm UTC](https://forums.unrealengine.com/t/major-v34-30-introduced-a-new-editor-validation-error-and-when-fixed-it-results-in-a-cook-validation-error/2446730/9 "2025-10-05T14:50:17Z")
This topic was automatically closed after 180 days. New replies are no longer allowed.