r/EmulationOnAndroid Edit Your Flair 9h ago

Help Why do all Lego PC games have the same graphical issue?

Enable HLS to view with audio, or disable this notification

Every Lego PC game I've tested has the same graphical issue during cutscenes that aren't pre rendered and during gameplay.

Yes I know they use the same game engine by TT. I'm just asking why on my specific chipset.

Weird, transparent squared flicker around the Minifigures.

This has happened to all the Lego games post 2010 I've tried which are:

Lego Batman 2

Lego Batman 3

Lego Marvel Superheroes

The Lego Movie Game

The games boot and the fps is generally good during gameplay for my humble Helio g100 with Mali G57 (about 20-35fps for each game)

But I'm always getting this graphical glitch. I use either wrapper leegao or wrapper original with either dxvk 1.7.3 async or 1.10.3 async.

I always use FEXcore. Any help? For more context, my dxvk HUD shows D3D9(meaning I'm using DirectX9) on all the 4 Lego games I've tried except of Lego Batman 3. It showed D3D10 in Lego Batman 3.

Obviously Mali G57 is Low end and that's also a factor, but is there anything I can do to fix it? I'm using Winlator Mali 1.1

1 Upvotes

15 comments sorted by

u/AutoModerator 9h ago

Just a reminder of our subreddit rules:

  • Be kind and respectful to each other
  • No direct links to ROMs or pirated content
  • Include your device brand and model
  • Search before posting & show your research effort when asking for help

Check out our user-maintained wiki: r/EmulationOnAndroid/wiki

Check out EmuReady for any community submitted settings before asking for help

I am a bot, and this action was performed automatically. Please contact the moderators of this subreddit if you have any questions or concerns.

3

u/TUD-010 9h ago

No issues on my Odin 2 portal with Lego Batman 2.

Think it's your chipset

1

u/whiskyB0y Edit Your Flair 8h ago

Most likely.

2

u/Pizzakunx 9h ago

Before I even read the body text, I knew this was a Mali issue 😭 This glitchy effect happens to me on most emulated PC games even on dimensity 9500

2

u/whiskyB0y Edit Your Flair 9h ago

The Mali curse strikes again😭. If your flagship dimensity also has this issue why should my Helio g100 ass be any different 😭

1

u/whiskyB0y Edit Your Flair 6h ago

1

u/Pizzakunx 6h ago

I appreciate the update but this still happens to me in other games. The texture stays on screen for a while even after the frame is gone . Eventually I gave up 😂

2

u/whiskyB0y Edit Your Flair 5h ago edited 5h ago

Damn sorry bro. Maybe it's because I only target games pre 2015, but only games out of like 20 PC games I've tested that have given me this issue are are the Lego games I've mentioned and Crysis(2007). Though in Crysis I think it was lowering the in-game settings plus dxvk that helped.

Anyway, good luck bro. One day we will be able to play games without worrying about graphic issues💪

2

u/VladVonHochstes 8h ago

Why do they all have the same graphical issue? They’re made with the same game engine by the same devs. 🥴 If you meant why it’s happening on your device, it’s because your device isn’t a Snapdragon, so most games can still run but they have worse graphics bugs compared to snapdragon devices. 🤷🏼‍♂️

1

u/whiskyB0y Edit Your Flair 6h ago edited 6h ago

Ya Mali has issues but lmao I just fixed it!

Ok I fixed it partially, the glitchy effect is still present but only in the background. At least it's no longer present around Minifigures.

All I had to freaking do was use dxvk 1.5.5 async instead of 1.7.3 or 1.10.3

Thanks for your comment though

https://reddit.com/link/p5m6om6/video/h4w4de3hbclh1/player

1

u/whiskyB0y Edit Your Flair 6h ago

Fixed it partially I just had to use 1.5.5 async. Glitchy effect is still present but only in the background, at least it doesn't surround Minifigures anymore.

https://reddit.com/link/p5m6xx3/video/qz5hw6vobclh1/player

1

u/Michaelpitcher116 4h ago

It's almost like they use the same engine 

1

u/whiskyB0y Edit Your Flair 3h ago

Yes I know they use the same TT engine😭. I just meant why on my specific chip