HTML5 Blackscreen on Older Devices makes client moving to Phaser

Post reply

❤Follow Topic(4)

0 favourites

4 posts

From the Asset Store

Multiplayer (Server-Client)

$10 USD

Very simple code without excess options (15 events for server and 11 events for client)

paradine

- arcadesindo
- - Joined 30 Jan, 2014
  - 101 topics • 525 posts
- 1
- 13 Nov, 2023
- Quote
I'm not sure how many of the potential clients we met, are having a bad experience using Construct 3 for their game technology, they talked about general but unfixable problems like Blackscreen on Older Devices, lagging issues, and so on.

They're freaking out when knowing if we're using Construct 3 as our main engine and suggest using Phaser or Godot or any other HTML5 with more stable and real supporting all older devices.

The problem is really happening since long time ago, but it seems that there is nothing to do from our end as the Construct 3 users. Or maybe I just don't know how to fix it? How about you guys? Have you also met clients for the same reasons?
- Jase00
- - Joined 5 Jan, 2012
  - 108 topics • 1,033 posts
- 1
- 13 Nov, 2023
- Quote
Hmm, what sort of old devices do these issues happen on? Got any model names or android versions?
- arcadesindo
- - Joined 30 Jan, 2014
  - 101 topics • 525 posts
- 1
- 13 Nov, 2023
- Quote
most of them were devices made before 2020
Try Construct 3

Develop games in your browser. Powerful, performant & highly capable.
Try Now Construct 3 users don't see these ads
- Ashley Construct Team Founder
- Moderator
- - Joined 21 May, 2007
  - 669 topics • 30,350 posts
- 1
- 13 Nov, 2023
- Quote
Usually the biggest source of problems is buggy graphics drivers, which is not actually Construct's fault, and those will cause problems no matter which technology you use. Welcome to computer graphics - poor quality drivers have been a serious problem for decades and even sometimes ruin major game releases. The best approach is to install any available system software updates or driver updates on affected devices, but that does not always help, as sometimes the latest drivers are still broken.

If you can track down specific affected devices and report the issue to Google at crbug.com, you may be able to get a few specific cases fixed in Chrome, but it's hard work and you'll need detailed information about affected devices and access to them to test subsequent changes made.