Flycast: Grandia II graphical bugs (Android)

Created on 31 Aug 2018  路  17Comments  路  Source: libretro/flycast

On the reicast Android Retroarch core:
screenshot_20180830-214937
screenshot_20180830-214900
screenshot_20180830-214822

android bugs graphics bugs

All 17 comments

May be fixed by PR #239

Sadly no the same bugs are still present, may be related to this similar issue too:
https://github.com/libretro/reicast-emulator/issues/218

BTW these bugs are not present in your reicast fh branch.

@blackman91
Could you please retry using the latest build?

Using Reicast 0.1 bb23007 on Android the same bugs are still there.

The same happens on Jojo's Bizarre Adventure on Android:
https://i.redd.it/69wlgf0aqml11.jpg

Is this a Mali GPU, something similar has happened before with the RetroArch XMB menu flickering black?

Nope my gpu is Adreno 506

What device and OS version?

I have same issue on my Samsung Galaxy S8. RetroArch 1.7.5 and reicast build a2d26a5. That build fixed games like PSO not rendering, but still have black boxes in Grandia like the OP. As well as cutscenes showing black and only has audio, but I believe that's is a separate reported issue.

Motog5 plus Android 7

Hopefully #295 will fix this. Please report.

@flyinghead what's the easiest way to pull in these code changes? I used core updater in RetroArch, but it still shows 1.7.5 - Reicast 0.1 a2d26a5, which was from when I updated to fix PSO glitches.

You'll have to be patient as the buildbot has been having some issues lately

Latest core is much closer to rendering properly... Instead of black boxes, they are now highlighted green while being legible so at least it's playable! Couple sample images linked below.

https://ibb.co/n0Aste
https://ibb.co/mK2GKK

Issue doesn't seem to be present with latest fh/mymaster standalone, so maybe something specific to the libretro core?

Edit: Seems it may have been related to a save state from before the fix. I loaded from in game save and confirmed its all showing up normally now.

It renders now properly on my device on Android 7 using latest core:
screenshot_20180930-221530
screenshot_20180930-221435

It seems this is fixed now, flyinghead you do great work.

Was this page helpful?
0 / 5 - 0 ratings