Thank you for the precise report. We checked the MetaGrid Pro 1.7.7 production code and confirmed the mismatch you described.
The exporter writes scene macros without the primary/secondary markers that the importer expects. The importer consequently skips those macros while restoring the other scene settings.
We’ve added the correction to the planned MetaGrid Pro 1.7.8 update. This includes preserving both macro roles in new exports and designing compatibility handling for previously exported files, where the original macro roles may be ambiguous.
Your description gives us enough information to reproduce and test this in-house—there’s no need to send anything or repeat the test. Please keep your original exports intact.
Thanks again for catching this and documenting it so clearly.