Issue metadata
Sign in to add a comment
|
Textures applied to meshes Randomly or Repeatedly
Reported by
pnalchaj...@outlyertech.com,
Mar 13 2018
|
||||||||||||||||||||||
Issue descriptionSteps to reproduce the problem: 1. Navigate to https://cdnadsp.advrtas.com/ads/disjointed/index-300x250.html on Chrome for Desktop 2. Navigate to the above link on Chrome for Android 3. Note the correct character textures (desktop) are being replaced by the butterfly (Android) What is the expected behavior? We expect all characters to load in their assigned locations. What went wrong? Chrome for Android seems to be pulling the butterfly asset and using it instead of the character portraits. Did this work before? Yes prior to 65.0.3325.109 Chrome version: 65.0.3325.109 Channel: n/a OS Version: 7.1.1 Flash Version:
,
Mar 13 2018
After testing, we found a workaround. The problem arises when we draw to a 2d canvas a non power-of-two image and use that image as a texture for a mesh. When we reuse the canvas to draw a different image, the textures for all meshes that used the same temporary canvas change to some other random texture we drew to the same temporary canvas. It almost seems like the meshes use a pointer to the canvas vs. the image created on the canvas. To fix this we create a new canvas for every image we want to render. We destroy the canvas after the image is made into a texture. The issue I see with this workaround is the amount of creation and destruction of a canvas that occurs when we have many textures. Plus, this is not the desired behavior as compared with other browsers and standards.
,
Mar 14 2018
,
Mar 14 2018
Tested the issue in Android Steps Followed: 1. Launch Chrome. 2. Navigated to https://cdnadsp.advrtas.com/ads/disjointed/index-300x250.html 3. Observed the butterfly asset. Chrome versions tested: 65.0.3325.109(Stable), 67.0.3369.0(Canary) OS: Android 7.0.0, 8.1.0 Android Devices: Samsung J7, Pixel 2 XL Observing the same behavior since M58. @pnalchajian: Could you please help us with a screencast with the exact problem? Thanks!!
,
Apr 19 2018
Closing this issue as there is no response from the reporter. Please update your Chrome to #65.0.3325.109 and feel free to file a new issue if the issue is still observed. Thanks! |
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by pnalchaj...@outlyertech.com
, Mar 13 2018