Skip to content
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

Fix bug preventing map from rendering on Chrome on Windows 10 #2942

Closed
calvinmetcalf opened this issue Aug 4, 2016 · 13 comments
Closed

Fix bug preventing map from rendering on Chrome on Windows 10 #2942

calvinmetcalf opened this issue Aug 4, 2016 · 13 comments

Comments

@calvinmetcalf
Copy link

Some of my co workers have been having issues viewing any webgl maps in chrome on windows
This is up to date chrome and windows 10, the map is blank white but opening up dev tools seems to suggest that stuff is loading as panning the whiteness causes more network traffic. Microsoft Edge does work.

2016-08-04

@mourner
Copy link
Member

mourner commented Aug 16, 2016

Could you share what http://webglreport.com/ or https://www.browserleaks.com/webgl says on those machines?

@calvinmetcalf
Copy link
Author

pinging my coworker @ismyrnow who was the one who was experiencing this though he's on vacation this week so we might not get the report for a week or so

@wangtun
Copy link

wangtun commented Aug 19, 2016

@calvinmetcalf you could try set the pitch a value which is not zero! @mourner this issue may be the issue #2178 , it is closed. but the problem is still existing in some computer with version 0.20.0

@lucaswoj lucaswoj changed the title Isses with chrome on windows 10 Fix bug preventing map from rendering on Chrome on Windows 10 Aug 19, 2016
@anandthakker
Copy link
Contributor

We've got a client reporting this in Firefox and Chrome on Windows. I am asking him for the webglreport @mourner asked for and for any console errors, and to see if Edge works for him.

@anandthakker
Copy link
Contributor

Here's his webglreport:

gltesttab1

Also

@TippyTipster
Copy link

Ran into this error as well with a couple computers at the workplace. Setting the pitch to anything other than 0 made the map render for them though.

@ilyatrunov
Copy link

The "pitch other than 0" trick is working.
I have a Win 7 machine (NVIDIA 210, latest drivers). IE 11 was rendering Mapbox GL, Chrome and FF was not.
Set the pitch to 1, рender was ok. But if I switch pitch back to 0 - the map disappears.

@jd327
Copy link

jd327 commented Oct 31, 2016

@ilyatrunov same thing, one of my customers applied pitch and it worked. Otherwise, just does not load.

@ilyatrunov
Copy link

Yes, but now the map is pitched a little bit. I'm going to investigate a
little further

On Mon, Oct 31, 2016 at 8:25 PM, Ivan Akimov notifications@github.com
wrote:

@ilyatrunov https://github.com/ilyatrunov same thing, one of my
customers applied pitch and it worked. Otherwise, just does not load.


You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
#2942 (comment),
or mute the thread
https://github.com/notifications/unsubscribe-auth/AQnd1rLvuDhPif97hCZao3nxl2SWOv2Eks5q5jKTgaJpZM4JctLU
.

@TippyTipster
Copy link

You are able to set the pitch to very small increments (such as .1) and it's quite negligible (no one I applied the pitch to at that level even noticed), until this issue is fixed.

@tgecho
Copy link

tgecho commented Dec 6, 2016

This pitch hack/workaround appears to fix a few cases I've encountered, but it has the side effect of triggering a bit of z-fighting: #3320

@mourner
Copy link
Member

mourner commented Dec 6, 2016

This should have been fixed by #3740.

@mourner mourner closed this as completed Dec 6, 2016
@jd327
Copy link

jd327 commented Jan 18, 2017

One of my clients has just shared a screenshot where the map does not load only on Win 10 + latest Chrome. Could there be something else behind this? (Using v0.29.0)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

9 participants