The map archive supplied in #123 reproduces a separate AAS 1.08 settings-parser mismatch.
Evidence
- attachment:
airdefense1.zip, SHA-256 CED6E9D92E67D8FF71E1F2E93B68D7F6DD7C961D7E759E90E3AA243408AED187
- each generated
.aas32, .aas48, .aas96, .aas128, and .aas250 file includes generateAllFaces = 0
- the openQ4 AAS writer itself emits that setting
idAASSettings::FromParser currently recognizes generateTacticalFeatures but not generateAllFaces, producing three warnings per AAS file (generateAllFaces, =, and 0)generateAllFaces is also not initialized in the settings constructor, and the writer hardcodes both AAS 1.08 flags instead of round-tripping their values
The warnings do not cause #123's save restore failure, but the producer/consumer mismatch is an engine bug and should be fixed with a parser/writer contract test and a load check against the supplied files.
The map archive supplied in #123 reproduces a separate AAS 1.08 settings-parser mismatch.
Evidence
airdefense1.zip, SHA-256CED6E9D92E67D8FF71E1F2E93B68D7F6DD7C961D7E759E90E3AA243408AED187.aas32,.aas48,.aas96,.aas128, and.aas250file includesgenerateAllFaces = 0idAASSettings::FromParsercurrently recognizesgenerateTacticalFeaturesbut notgenerateAllFaces, producing three warnings per AAS file (generateAllFaces,=, and0)generateAllFacesis also not initialized in the settings constructor, and the writer hardcodes both AAS 1.08 flags instead of round-tripping their valuesThe warnings do not cause #123's save restore failure, but the producer/consumer mismatch is an engine bug and should be fixed with a parser/writer contract test and a load check against the supplied files.