Module Export Broken

[Nemesismmx]

When Module is marked as ready only, exported xml has broken links.
Elements are put into <Reference> element, but links are still pointing to elements as in editable version. For example instead of reference.encounters.id-0001 it says encounter.id-0001

[Moon Wizard]

I just pushed a new Windows build that fixes this issue; the Mac build should be up by tomorrow.

Regards,
JPG

[Tyrannosaurus VeX]

I don't think this is the same error, especially since I updated today.

I exported a module with images from Unity, then loaded another table and loaded that module ... this is the error I was getting when trying to load those images.



EDIT: Out of six images, only 3 work. I don't know why only those three either.

[Zacchaeus]

Make sure that the images are in RGB and not CMYK format.

[Tyrannosaurus VeX]

Make sure that the images are in RGB and not CMYK format.

All RGB 72px/inch 8 bits/channel.

EDIT: Don't know why ... tried re-exporting. But it works now.

Didn't do anything differently, just exported a 2nd time.

[Trenloe]

Is it just the ones with -- in the filename that fail?

[Tyrannosaurus VeX]

Is it just the ones with -- in the filename that fail?

No, they all had a double dash in them. Just some worked ... I re-exported, now it works.

Something went wrong during the first export. Not sure what.

[pindercarl]

Make sure that the images are in RGB and not CMYK format.

It's always a good idea to use RGB vs. CMYK images, as there are ~25% smaller, support for CMYK images was added in the February 27 build.

[Tyrannosaurus VeX]

Ok, I finally got the module to export correctly and open correctly in Unity ... but when I open the module in Classic, the images are blank grey squares.

At first, I thought it was because of the LOS stuff I added, but there were images that I didn't even touch in Unity ... what is going on here? Anyone know?

[Trenloe]

I'm not aware of FGU -> FG Classic compatibility. You can go FG Classic -> FG Unity but not vice versa.