lwc: SF migration of bugs to Trac was quite a while ago, so I think it was expected that all account migrations / mergers would be done by now. I think either Rootfather or _sev could probably help you since I think wjp is inactive / retired.

Ganellon: Have updated the bug. I can't replicate this, so would suspect you may have corrupted or incomplete datafiles. Please check the bug for a full list of required datafiles and md5sums to allow you to check these.

I would suggest filing a bug at bugs.scummvm.org as per rule 3a: viewtopic.php?f=1&t=17

Ganellon: Thanks. Please standby...

Ganellon: Could you test with the latest nightly build and update the bug with the bitmap resourceId? ... I had forgotten that I don't have a copy of GNAP... yet as it is now on order from the usual suspects

OK. For any other developers, the bug is https://bugs.scummvm.org/ticket/11740 ... Will see if I can replicate with my copy.

https://github.com/scummvm/scummvm/commit/f898546f71c2c06ace4dfbde5ea13342bc2a93b1 As I said, test with the next nightly build which will include this and the error message will now list the resource id ... add that and other required data i.e. version of GNAP, Operating System etc. to a new bug and...

Ganellon: I also can't find this listed as a bug against GNAP in the tracker. Please file a bug for this at: https://bugs.scummvm.org/

Ganellon: I will commit a change shortly to the GNAP engine which should improve that error output to indicate which bitmap resource id is failing. Please test with the next nightly build and see if you can replicate and get the resource id causing the issue.

VinnieL: What platform are you running ScummVM on? i.e. is this Win32, OSX, Linux, Android or iOS autoupdate ... There shouldn't be daily updates, unless you are on some kind of testing / nightly build?

Those two tools were added to scummvm-tools, but are not really intended / ready for end-user usage i.e. compression of resources. They really should have been in scummvm/devtools i.e. developer tools as they were mainly for developers to use in looking at the contents of Mohawk archives and testing...

If you wonder about the overlay, compare resources #2034 and #2036 in the CHANNELWOOD.DAT Mohawk archive file of Myst ME.

Hmm... I might be wrong here. I'm not sure my notes covered the original Windows 3.1 version of the datafiles... so not sure if something is lurking

I did the initial work on this for the Mohawk Myst engine. I did a quick check of my notes. Myst ME has no additional slides in it's datafiles compared to the older Windows 3.1 / WIN16 version based on Mohawk. The main changes are the addition of the Help System slides, upgrading of image resources ...

Interesting. Always nice to see a new port, though I think quite restricted in terms of which engines will run due to the platform limitations of the ESP-32.