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?
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?
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:
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.
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.
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:
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.
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.