Hi have recently created a game called Protocon the game uses parallax scrolling in front layer and back aswell.
The problem i think consists because of system webview versions. I have tried on my wife's Galaxy Note 3 which has Android System Webview 51.0.2704.81 the game works atleast graphic wise correctly.
I use a Asus Zenfone 2 which has Android System Webview 52.0.2743.41. I have tried everything even exported with XDK Crosswalk ectc. nothing made it work on phone correctly. Any known solution ?

tried the page using Webview browser shell and ToT system webview and did not see any issue (used Nexus 5x). cc'ing some people who knows graphics. Do the logs show any errors?

that device has intel atom cpu, but powervr gpu.. so, what about devices with other GPUs?

QA: maybe can check other devices with adreno and mali gpu?

Assigning to dneelamegam@ for now, dneelamegam@ feel free to assign to someone else to do testing as per comment #3.

Bo, what other devices do you think should be tested?

any recent nexus device + international version of samsung galaxy s6 or s7

dneelamegam@ could you test with one of the devices Bo suggested?

 gsennton@, 

1. I tried to download the apps from play store "Protocon" dont find the apps.

2. http://www.eamusavirlik.com/cyber/ptx/index.html, this link is getting  (File not found (404 error))

Yeah, that link doesn't work for me either.
funworxgames@gmail.com, could you provide a link to the app on the Play Store please?

Sorry i was on holiday. I have checked the code and behaviours again. It seems like since the new update of android system webview does not render correctly outside screen resolution. Sometimes in order to achive certain tiled texture effect i need to make the texture bigger then (active camera field) screen resolution. I have tried to lower the tiled texture exactly to the resolution of active camera field and now it works. Seems like overscan till outside given camera creates this problem. But this is not the case on previous android system webview versions. Anyway found a solution like that now it works. Thank you all for the help and interest. I truly appreciate it.

Thank you for providing more feedback. Adding "Needs-Review" label for tracking.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

Ok, so we could just close this as Won't Fix, unless we should investigate the potential regression described in comment #10, Bo/Toby, any thoughts?

I think it can be xlosed as fixed since we know what causes the bug. So thank you all for the help & support you all are wonderfull.

Can you keep a broken version of the game alive somewhere?

Finding a workaround in your game doesn't really say much whether there was a bug, and if the bug is in your game, in webview, or in the gpu driver.

Sure i will upload the broken edition tomorrow evebing up again and post a link.

Hello funworxgames@gmail.com, any news on a broken version of the game? Thanks!

Issue has not been modified or commented on in the last 365 days, please re-open or file a new bug if this is still an issue.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot