New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Android default browser bugs #44
Comments
Hi gunta, I absolutely agree that pixi.js needs to work on default android handsets. I know there is an issue with run pixi run that causes the textures to be oddly resized, fortunately I'm pretty sure this is a game specific issue (I plan on looking into the cause just in case) I have tested our later creations in the default android browser and they seem to run ok. If you could confirm for me that would be ace: http://www.theleisuresociety.co.uk/fightforeveryone/ thanks! |
Just tested the leisure society game on my Nexus S running Android 4.1.2 and it all works fine including sound. It didn't fill the screen but I don't think it was supposed to. |
Good to hear, thanks for testing @Harissa! |
I'm making an Android Test Farm right now and I have more than 20 android devices... As soon as I finish this project I'm going to test it ;) |
@gunta you legend 👍 |
I saw the issue you mentioned on RunPixieRun, but I was unable to reproduce it on any of the other examples or games. I suspect it has something to do with the game itself and not pixijs. If we encounter this issue again (or you get your test farm up) feel free to reopen this issue with new info. |
This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
Hi, this goes for Android in general, but I need to have a rendering engine that works on all the 2.x~ 4.x Android devices.
I was just trying Run pixi run on a Samsung Galaxy S3's default browser (the most popular handset yet) and it has serious rendering bugs that it makes the game unplayable.
What's do you think on this issue?
Thank you!
The text was updated successfully, but these errors were encountered: