[SOLVED] Firefox black screen on mobile/tablet

Hi everyone,

I know this has been discussed in topics over a year ago, but I’m still running into the same problem today:
The problem occurs with Firefox on some mobile devices. After my game loads, it just shows a black screen. I can recreate this problem on desktop when I turn on the Responsive Design Mode, choose another Device Setting, and refresh the page. Is this a Firefox problem or a Playcanvas problem?

https://playcanv.as/b/d6c247f2

Is this something you can reproduce on a new PlayCanvas project as well?
Can you please try and turn off the antialiasing, if that is enabled.
also, what is your FF version and what is your desktop platform and also mobile device?

Firefox version is 133 on all devices, desktop, mobile and tablet.
The platform is Windows 11 on desktop and Android 14 on mobile and tablet.

With “turn off the antialiasing” i think you mean this in about:config?


I turned this off and refreshed the page, but it’s still black.

I’ll try to recreate the problem in a new project.

I created a new project and this has exactly the same problem. I even tried to open other public projects on the Playcanvas website and this one has the same problem:

These do work:

See the antialiasing setting in Editor’s Settings dialog, Rendering part. Try to disable this please.

1 Like

Ah, that’s it! It works. Thank you so much!

I’ll try to workaround this issue in the engine … we have a workaround for this currently, but it seems something has changed and it no longer triggers.

For now I’ll keep it turned off. But when there will be a fix I’d like to know it.

1 Like

please keep an eye on this issue: Application cannot start in Windows Firefox when antialiasing is enabled, or transparent canvas disabled · Issue #5856 · playcanvas/engine · GitHub

I looked at your original link, and that uses engine 1.67 or something … that wont receive a fix.
We have a workaround in 1.75.1, which is the current version of the engine used by the Editor. If you used this, it should work.

Yeah that link is quite old but I’m using downloaded builds with the 1.75.1 version and it has the same problem. Also, when I create a new blank project, it has the same problem.

1 Like

I tried to reproduce the issue and no success yet. I tried your example from the previous post as well as my simple project with AA enabled on these devices, and all works as expected:

  • Windows 10, Firefox 132 & 133
  • Windows 11, Firefox 132 & 133
  • MacOS 15.1.1, Firefox 133
  • Android 15, Google Pixel 8 Pro, Firefox 133.0.2

That’s strange… I immediately get this problem when I run the “testing” example from my previous post with the Responsive Design Mode enabled. It’s on Windows 11 with Firefox 133.

Have you tried the responsive view in Firefox (ctrl+shift+i, mobile icon in the top right of dev console)? I can repro those warnings on Win11 Firefox 133. They don’t show up unless you go to responsive view.

Do you reproduce the black screen? Warnings are Firefox performace warnings that can be enabled using flags as well, those are not related.
(I’m away from my Windows machine today). I have not tried the specific debug setting … I missed that bit from the initial post. If the black screen only happens in this mode, but not otherwise, that’s not too bad.

Ah, sorry, didn’t pay attention. No black screen here, just warnings:

1 Like

I guess it does not matter that it doesn’t work in the responsive mode, but it also doesn’t work on Firefox on some mobile devices. Which is the thing that bothers me. It has the same error there.
I’m using a Samsung galaxy A34 with the newest Firefox (133). With AA turned on, it does not work there. With AA turned off, it works.

The responsive mode was just to show you that I am able to replicate the problem on Firefox 133 on Windows 11 aswell.

Okay… I tried turning the phone off and on again. The “testing” example works now, but my own project does not (With AA turned on).

Is your project using the latest engine, or still 164 or something like that @Timo

I published it on 26 november 2024, and I never changed the engine version. So it must be 1.75.1 or something.

I will try to create a build to test this with my own project.