fails on latest chrome for mac

anyone from faithlife able to look into this? anyone else with chrome for mac able to confirm? Thanks

I've never seen this, and am not able to reproduce running the latest update of chrome. The experimental display uses webGL and i wonder if there is an issue with your GPU or some hardware configuration on your computer.

Could you provide the info at this link chrome://gpu

And then just to verify could you verify that the spinning cube on this site is functional https://get.webgl.org/ (it generally tests browser compatibility which yours should be but just wanted to be sure).

Does it exhibit the same problem on Safari or Edge?

Thanks,

Seth Copeland

Thanks, John. We're looking into it. Our research indicates your graphics card (AMD Radeon HD 6000M series) has a possible issue with Chrome 52 and above. We will look into possible workarounds on our end. Unfortunately, we don't have any machines with this graphics card so we might ask you to verify our workaround.

In the meantime, you might try launching Chrome with the following command line argument and let us know if that changes anything:

--disable-features=WebGLImageChromium

We greatly appreciate your help in identifying this issue since we are unable to reproduce it on our available hardware.

Wasn't entirely sure how to do that but I tried this in the terminal:

open -n ./Google\ Chrome.app --args --disable-features=WebGLImageChromium

It didn't help... I'd be very pleased to try any fixes. Thanks

Sorry for the confusion. It is a command line argument that needs to be passed to the application when starting it. I apologize that I'm not more familiar with OS X, but you might have to launch it from the terminal window in order to pass the argument.

Hi John, we've deployed a workaround which might fix the issue (not being able to reproduce it on our end, we can't guarantee its success), but the workaround has to be enabled explicitly. Could you do the following:

1. Open app.logos.com to a blank layout (close all panels if any are open).
2. Open the developer tools to the "Console" tab and wait until it seems that page activity has settled down.
3. Paste window.sinaiXCompatibility = { canvasHasAlpha: true } in the console and press enter. You should see something similar to this:
4. Open a resource panel. The console log should include a message containing 'Enabling "canvasHasAlpha" workaround' if everything has been done correctly so far.
5. Hopefully it renders correctly. If it doesn't, please let us know, and we will look into other potential workarounds.

Note: this workaround currently only lasts as long as the browser tab is open--if you close/reload the tab, you will have to apply the workaround again. If the workaround is successful, we can make it a permanent option.

Thanks - I tried it but get this error:

[.Offscreen-For-WebGL-0x7ffb5485f000]RENDER WARNING: there is no texture bound to the unit 0

Hi John, thanks for trying out the fix, and I'm sorry to hear it's still not working. The render warnings are a known issue, although that does not rule out the possibility of them being connected to this issue. If I could ask a favor which would help us narrow down what is going on, could you (1) visit https://threejs.org/examples/?q=texture#webgl_materials_texture_tga and post a screenshot, and (2) test the page in the latest version of Chrome Canary to see if the issue persists?

I'm thinking it can't be my graphics card because all these things work in firefox.

Thanks for continuing to help us develop a solution.

The problem is a combination of your graphics card and Chrome. The bug is detailed and discussed at length in various other places online including the Chromium developer mailing list and their online bug tracking system.

I'm disappointed that our workaround didn't help. We are continuing to try and track down some hardware to reproduce your issue in order to develop a better workaround. In the meantime, I recommend using Firefox or another browser that works. [:(]