After the latest update to MCC for PC rolled out yesterday (5/12/2020) I was no longer able to load Reach maps.
To Reproduce
Steps to reproduce the behavior:
Start Assembly
Load a Reach map from the latest MCC version on PC (as of 8pm PST 5/12/2020)
See error
Expected behavior
The map loads
PC (please complete the following information):
OS: Windows 10
Additional context
It looks like the Reach maps were updated with a newer version that isn't in the Blamite/Formats/Engines.xml file. I'm not familiar at all with how this stuff works but I was able to work around the issue by adding a new entry to Engines.xml:
I then copied the Blamite/Formats/ReachMCC/ReachMCC_U1_StringIDs.xml and made ReachMCC_U2_StringIDs.xml with identical content. After rebuilding everything and running again, MCC Reach maps can load again without any exceptions. However I lack any real knowledge about these files so I have no idea if things will behave correctly with this workaround.
After the latest update to MCC for PC rolled out yesterday (5/12/2020) I was no longer able to load Reach maps.
To Reproduce Steps to reproduce the behavior:
Expected behavior The map loads
PC (please complete the following information):
Additional context It looks like the Reach maps were updated with a newer version that isn't in the Blamite/Formats/Engines.xml file. I'm not familiar at all with how this stuff works but I was able to work around the issue by adding a new entry to Engines.xml:
I then copied the Blamite/Formats/ReachMCC/ReachMCC_U1_StringIDs.xml and made ReachMCC_U2_StringIDs.xml with identical content. After rebuilding everything and running again, MCC Reach maps can load again without any exceptions. However I lack any real knowledge about these files so I have no idea if things will behave correctly with this workaround.