Failed to link shaders in Pokémon Colosseum

[Shady Guy Jose]

As of the latest update, I get this error:
   
Is this a regression or do I need to play around with settings/files?
Thanks in advance

[JosJuice]

Could you upload the bad_p_OGL_54.txt file so we can take a look at it?

[Shady Guy Jose]

(12-26-2021, 04:29 AM)JosJuice Wrote: Could you upload the bad_p_OGL_54.txt file so we can take a look at it?

  bad_p_OGL_54.txt (Size: 34.66 KB / Downloads: 47)
Here it is. There were hundreds of these in the folder, so there must be something horribly wrong going on

[JosJuice]

Hmm... Not quite sure what this is caused by. Can you test if it happens in a slightly older version, to see if it's a regression?

Also try disabling ubershaders if you have them enabled.

[Shady Guy Jose]

(12-26-2021, 05:55 AM)JosJuice Wrote: Hmm... Not quite sure what this is caused by. Can you test if it happens in a slightly older version, to see if it's a regression?

Also try disabling ubershaders if you have them enabled.

It started happening on Thursday, around the time 15676 was released (I can't pinpoint the exact build that broke it on my end). I've tested 4 games: Pokémon Colosseum and XD, which probably use the same engine, so I tested Sonic Adventure 2 and Megaman Network Transmission as well. All 4 threw similar errors like crazy. I'm afraid to uninstall and test older builds because of the scoped storage issue we've discussed at length, but I'll do it if need be. I think it's not broken right now because of an Oxygen OS update that included "optimizing third party app experience" in the changelog, so I may take the plunge if more testing is needed. Turning off Ubershaders (I had it on Hybrid) fixed it.

[JosJuice]

This is looking like it might be some kind of bug in the graphics driver. Unfortunately nobody on the development team has a device where this issue happens, so there isn't much we can do right now to investigate this further.

[Shady Guy Jose]

(12-28-2021, 05:26 AM)JosJuice Wrote: This is looking like it might be some kind of bug in the graphics driver. Unfortunately nobody on the development team has a device where this issue happens, so there isn't much we can do right now to investigate this further.

I understand. I can live without Ubershaders in the meantime, so it's a relatively minor issue for me, and thanks for the suggestion.

[Shady Guy Jose]

(12-28-2021, 05:26 AM)JosJuice Wrote: This is looking like it might be some kind of bug in the graphics driver. Unfortunately nobody on the development team has a device where this issue happens, so there isn't much we can do right now to investigate this further.

Hi! Are there any news on this? There's a game I've been wanting to replay (Megaman Network Transmission) that performs horribly on my phone (OnePlus 9 Pro, Android 12), and I'd like to see if OpenGL + Hybrid Ubershaders makes it run better (it used to be my go-to configuration for every game until I got this error, now I switch between OpenGL with specialized shaders and Vulkan with Hybrid Ubershaders). Thanks in advance

[JosJuice]

We've confirmed that it's a bug in the Adreno graphics drivers, but due to the complexity of trying to work around the bug, we currently don't have a solution.

For what it's worth: Hybrid ubershaders can't increase your overall framerate, it can only get rid of stutters.

[Shady Guy Jose]

(07-15-2022, 04:11 AM)JosJuice Wrote: We've confirmed that it's a bug in the Adreno graphics drivers, but due to the complexity of trying to work around the bug, we currently don't have a solution.

For what it's worth: Hybrid ubershaders can't increase your overall framerate, it can only get rid of stutters.

Yeah, I just wanted to try OpenGL without having it stutter, but I played around with it a bit and the slowdown is probably due to more than just shaders (I get about 30 FPS in a 60-FPS-locked game, so 50% speed), since it's slow, but mostly fluid (especially when running Vulkan with Hybrid Ubershaders). I also feel that performance dropped a bit as a whole since I updated to Android 12, but I always chalked that up to the new Color-OS-based Oxygen OS and its weird CPU-crippling options. Maybe it's the graphics drivers that got broken, then. Thank you for your help, I guess I'll just wait until they launch Oxygen OS 13 and hope it's solved by then.