FlatWorldGeneratorOptions assert

Partner Rank: 2

Partner Team Reporting:

Polymaps

Verification builds:

Whichever build CR is using

Summary:

Chris Dauchot suggested making a bug report as CR is failing our content for an assert relating to FlatWorldGeneratorOptions. The CR fail report is as follows:

 

[BLOCKING] - Upon downloading the map, at the Importing Content step, I get the following assert: Assertion failed: If we fail to parse the json, we must end up with empty FlatWorldGeneratorOptions for them to be properly set on save Condition is false: !mFlatworldGeneratorOptions Function: LevelData::getTagData in D:\a_work\2\s\handheld\src\common\world\level\storage\LevelData.cpp @ 461 Hopefully this is an easy fix. 

 

Impact:

Many partners are being met with fail reports for our content, while being completely unable to reproduce this on any of the builds partners use.

Repro Steps:

1. Import the world with whatever build CR is using with asserts enabled I suppose?

Observed Results:

Assertion failed: If we fail to parse the json, we must end up with empty FlatWorldGeneratorOptions for them to be properly set on save Condition is false: !mFlatworldGeneratorOptions Function: LevelData::getTagData in D:\a_work\2\s\handheld\src\common\world\level\storage\LevelData.cpp @ 461

Expected Results:

There should be no assert so that CR won't fail our worlds and they should be immediately made aware to ignore this assert so partners can get their worlds reviewed again.

Screenshots/Videos attached: Yes/No

Yes

Regression Builds:

N/A

Notes:

Again, no partners are able to reproduce this assert, so it is likely a problem with CR's build.