Im pretty sure its the MobileAdvert action "Configure" that is not working. At first i tried using that to configure and then use the event "On Configure Complete" but it did not work. The only way i got it to work is deleting all actions and events about configuration and just inputing all the data on the properties of the MobileAdvert object

That would make sense since the Mobile Advert properties are incomplete in my game and it is apparently not showing for EU players. Is your game only for Android?

If that is the case, then what do we do if we want to use the same project for both Android and iOS? It's not feasible to keep two identical projects with the only difference being Mobile Advert and ad ids set up for each platform.

And if this is the issue with the plugin not showing the dialog consent, then hopefully this is a bug and not intentional so it can be corrected.

I'd also still like to know how it determines when the dialog is shown and if we can show it to everyone. I am assuming other countries will follow suit and we'll have to do it for everyone, so might as well.

I'm hoping Nepeo can confirm the above and let me know about the other questions.

Hi Nepeo, I have a few questions about this plugin I hope you can answer...

How does the Consent SDK determine if a user is an EU resident? Is it geo-location or something else? I haven't been able to find an answer in their support docs.

Also, what is required to show the consent dialog automatically? Here's my set-up on the loader layout. I am told it is not working for EU users. What am I missing?

I left the App ID out of the advert properties settings in left column because the game is built for iOS and Android. Hence why I am configuring in the events. But is the App ID required in the plugin settings for this to automatically show?

Also, is it possible to show the consent dialog to everyone? How can I do that?

Well, since webgl2 is off for android devices, if built with r111. This is another error you are having.

Thanks for testing sizcoz

And fredriksthlm I built the game with r111. WebGL is enabled in Advanced, but it should WebGL v1, correct?

Before, on my Nexus 10, the game would only show a black screen, but now it at least loads, then the start screen shows with banner ad and Google Play Games logs in, but then after you hit start to play, it slows down quickly and just freezes. But the banner ads refresh.

I have no clue. The Nexus 10 just might not be able to hack it anymore.

I just built my app with r111 yesterday. I'm not getting a black screen anymore, but the game freezes right after the start screen. So something is still broken and not working properly. Anyone with affected device mind testing with this game?

https://play.google.com/store/apps/details?id=com.kenyonb.runnybutt

Let me know if it works or if it is stuck after start.

construct.net/forum/construct-3/general-discussion-7/force-webgl1-135173/page-4

It should be working now in R111

The game I linked above was built with r111, and it starts to show on my older device, but freezes. So it no longer has the white or black screen, but it freezes once gameplay starts after the start screen.

I haven't tried enabling advanced features and disabling webgl yet though.

hey folks in the EU, would you mind trying this game to see if the Consent Dialog box appears?

https://play.google.com/store/apps/details?id=com.kenyonb.runnybutt

Just make sure it is version 1.5

It was built wit C3 r111 and I changed my number of ad providers from Default to Select Providers (only using 8). I am assuming this should work, but you never know.

Also, a screen capture would be neat to see how the dialog looks in game. Thanks in advance!

You know what, i just tried it myself and it is not working, my stuff becomes transparent using WebGL it seems the Beta did not fix anything. I will have to keep disabling WebGl alltogether for the time being.

Thanks. I'll have to try that and see how it performs on low-end and high-end devices and see if it is worth turning it off.

I also thought I read it only turns it off for C2 projects in the latest r111 release notes?

KENYONB Yes i did choose the custom list of Ad Providers in AdMob settings and selected only 12.

sachos345 awesome! thanks for confirming.

C3 Beta 110 just released and that disables WebGL 2 for the time being that should fix any withe screen or transparent sprites problem, it was a bug with GPU drivers. I bypased it in my small apps by just disabling WebGL in the Project properties but i understand that is not a good solution for bigger apps.

Anyone from EU could try my app to see if the consent dialog is showing?

https://play.google.com/store/apps/details?id=com.sachosdev.dig

From what i understand it should automatically show up since using the new version of the Mobile Advert Plugin right? Or do you actually need to put the action "Show consent dialog" On Start of Layout?

In the About screen i added the option to show it again whenever you want maybe you could try that.

I tested the most recent beta and this did not solve the white screen for me. ANother app shows a black screen. so not sure this is a webgl issue... ?

C3 Beta 110 just released and that disables WebGL 2 for the time being that should fix any withe screen or transparent sprites problem, it was a bug with GPU drivers. I bypased it in my small apps by just disabling WebGL in the Project properties but i understand that is not a good solution for bigger apps.

Anyone from EU could try my app to see if the consent dialog is showing?

https://play.google.com/store/apps/details?id=com.sachosdev.dig

From what i understand it should automatically show up since using the new version of the Mobile Advert Plugin right? Or do you actually need to put the action "Show consent dialog" On Start of Layout?

In the About screen i added the option to show it again whenever you want maybe you could try that.

awesome. I'm going to give the new beta a try and see if it fixes the white screen.

as for the user consent dialog, did you reduce your number of ad providers to 12 or less in AdMob? or did you leave it at default?

> thanks for testing. I also get the same results on my very old Nexus 10. What Android device are you using?

A Moto C+ Pulse Max - about 6 months old.

Thank you. This might help me figure out what is causing the issue.