Vasco Asturiano

@benjaminlim00 the fact that some characters look fine but others don't, makes me think whether your typeface may be missing support for some characters. If there was something wrong with...

@AldoS thanks for the report. This error is originating at the most recent version of Three (`0.139.0`). Seems like there's a fix in flight for it that should be merged...

@AldoS even if you add a top level dependency of `three`, the app could still be using a different version deeper down in your dependency tree. If you use `yarn`,...

@Marcioshub are you still experiencing any issues with React 17? I've tried with 17 and it behaves fine, I'm not able to reproduce your error. In fact, the examples are...

@furkancelik in that example a grid size of `[50,50]` would lead to 50x50 = `2500` tiles. 1M tiles seems well beyond what would be achievable with these tile objects (each...

@Claeb101 please see: https://github.com/vasturiano/react-globe.gl/issues/1 https://github.com/vasturiano/react-globe.gl/issues/15

@nobu-sh thanks for your suggestion. There is a way to do this already. Attached to each of your data points is an attribute called `__threeObj`. This attribute is a reference...

@steven3092 could you please provide more detail into what error do you get? If also helps if you can make a simple reproducible example on https://codesandbox.io/

@jan-wilhelm thanks for your suggestion. I actually switched the arcs blending mode from additive to normal. That is a more suitable blending, and specially for light backgrounds makes a big...

@benjaminlim00 I'd suggest trying to isolate the functionality that's causing the performance degradation. You have two layers on your globe, try with just each layer independently to narrow it down....