PDA

View Full Version : Module Export Results in Image Errors



LordEntrails
June 15th, 2025, 23:43
I've got a development campaign that has had several occurances where after a few exports to module images start to fail to export. The following error is given inthe console and logs;


[6/15/2025 3:29:10 PM] [ERROR] Graphic: Unable to load file (images/Installation Floor Plan 1.webp) (modules/FS_Ref_Hndbk.mod)
[6/15/2025 3:29:10 PM] [ERROR] Graphic: Unable to load file (images/Installation Floor Plan 2.webp) (modules/FS_Ref_Hndbk.mod)
[6/15/2025 3:29:10 PM] [ERROR] Graphic: Unable to load file (images/Installation Floor Plan 3.webp) (modules/FS_Ref_Hndbk.mod)
[6/15/2025 3:29:10 PM] [ERROR] Graphic: Unable to load file (images/Installation Floor Plan 4.webp) (modules/FS_Ref_Hndbk.mod)
[6/15/2025 3:29:10 PM] [ERROR] Graphic: Unable to load file (images/Lite Transport Deck Plan.webp) (modules/FS_Ref_Hndbk.mod)
[6/15/2025 3:29:10 PM] [ERROR] Graphic: Unable to load file (images/Sector Map-Nebulae.webp) (modules/FS_Ref_Hndbk.mod)



The images exist in the campaign/images folder, and have not been changed since last time the module was exported. They open in various image apps with no issues. In the past the resolution has been to delete and re-add the images. And often new images then have this issue but are resolved one at a time until eventually the export works. But since this is re-occurring I would like to find a permanent solution.
64600

So, why is FG failing to export these images and how do I fix it so that it works as intended?

Some supporting files that may be of interest.

Trenloe
June 16th, 2025, 04:32
Assuming the db.xml file is from the exported module - the <bitmap> entries have "@FS Referee's Handbook" at the end. I don't know what's adding that, but try removing it from the db.xml file with a find/replace.

LordEntrails
June 16th, 2025, 04:49
So the db.xml is from the development campaign, not the exported module. So, I believe the @ reference should be there. Right?

Trenloe
June 16th, 2025, 04:58
So, I believe the @ reference should be there. Right?
@ references are to a module. They should only be in a campaign if the campaign is referencing an image from a module of that name outside of the campaign. And, if it is, images from a module won't be exported. So, this is your problem - remove the @ references in your campaign db.xml file.

Moon Wizard
June 16th, 2025, 06:24
No. There should be no @ references within a module db.xml; unless they are pointing at another module. Similarly, for campaign db.xml; there should be no @ references unless pointing to module references.

Regards,
JPG

LordEntrails
June 16th, 2025, 15:16
Hmm, well given this is a development campaign not sure I could have referenced a module image. But I will delete and re-add and see if the issue re-occurs. Maybe somehow I had the module loaded into it's own development campaign. It's possible I made such a mistake.

Trenloe
June 16th, 2025, 15:20
Hmm, well given this is a development campaign not sure I could have referenced a module image.
I'm guessing you probably created the campaign images from the assets window, not actually importing the image files into your campaign.

LordEntrails
June 19th, 2025, 02:54
So the images not only had the @ reference, they also did not have the full path. It was "images/<image>@<module>" . I changed them all to "campaign/images/<image>" and all is working now. Thanks for the help.

Trenloe
June 19th, 2025, 16:40
So the images not only had the @ reference, they also did not have the full path. It was "images/<image>@<module>" .
This indicates they were directly referencing the module - so you more than likely created the image record via the FG assets window, not directly importing the image file into the campaign.

LordEntrails
June 19th, 2025, 17:05
Thanks. Probably late at night :)