#15506 closed defect (fixed)
DGDS Rise of the Dragon: gfx defect (BE/MORPHOS)
| Reported by: | BeWorld2018 | Owned by: | dwatteau |
|---|---|---|---|
| Priority: | high | Component: | Engine: DGDS |
| Version: | Keywords: | ||
| Cc: | Game: | Rise of the Dragon |
Description
Scummvm (build 16-11-2024 master 2.10.0git)
Something wrong with gfx (check screenshoot), intro, menu etc...
(Only little menu with SKIP INTRO/PLAY INTRO working)
All mode: OpenGL (Software or OpenGL) or SDL Surface
Game: Rise of the Dragon DOS/English
MorphOS - PPC - BigEndian
Attachments (3)
Change History (10)
by , 4 days ago
| Attachment: | 2024-11-17_08h26_05.png added |
|---|
comment:1 by , 4 days ago
by , 4 days ago
| Attachment: | valgrind-rise-big-endian-ppc32.txt added |
|---|
Valgrind output when starting the game on big-endian ppc32 (current Git HEAD)
comment:2 by , 4 days ago
| Component: | --Unset-- → Engine: DGDS |
|---|---|
| Priority: | normal → high |
by , 4 days ago
| Attachment: | rise-big-endian-disabled-doVqtDecode.png added |
|---|
screen output when disabling _doVqtDecode() call inside _doVqtDecode() on big-endian. The non-VQT content appears fine, so the endianness issue may lie there?
comment:5 by , 2 days ago
| Owner: | set to |
|---|---|
| Resolution: | → fixed |
| Status: | new → closed |
@BeWorld2018: I've pushed a fix on both the main Git branch and branch-2-9. It now looks good to me on my big-endian PowerBook G4, feel free to reopen this issue if you still see some problem with this game on MorphOS, though.
Thank you very much for your report and test!
Thank you the time you take into testing the newly supported games on MorphOS.
@ScummDevs: I can reproduce this on my usual big-endian development environment. I don't know this engine, so I can't suggest much, but I see that if I remove the
_doVqtDecode()call insideImage::loadVQT(), most of the screen content becomes black (obviously), but what's left appears to be OK. So the endianness issue maybe lies in the VQT part? I'm attaching a screenshot of that.I'm also attaching a Valgrind log under big-endian ppc32.
If any developper wants to do some tests (I have GDB too there), you can ping me here on on Discord for some tests on my big-endian env. Or you can also use the environment described in <https://wiki.scummvm.org/index.php/HOWTO-Debug-Endian-Issues> for local big-endian debugging.