12 comments

[ 0.21 ms ] story [ 31.9 ms ] thread
Looks interesting. Is there any online examples of it in use?
After some clicking, via their github page:

https://cdn.rawgit.com/areknawo/ThreeMap/a76571ba/example/in...

However, doesn't look too impressive to me :-( (Firefox)

Sorry for the inconvenience. I know that there are some issues with performance - antialiasing isn't fast enough (there are around 300k vertices in zoom 16 for example). I'll try to do better, as this is my first library too. Anyway, it is in early stages and working on, so expect updates in near future.
Probably I just suffer from a bug? https://imgur.com/a/KdRVofD looks like some textures were not loaded.
Well, there are no textures. It's just MeshToonMaterial with vertex colors. If you mean the disappearing roads then it's either antialias turned off or not active logarithmic depth buffer. The only bug that I see is the performance (22 fps is really bad). I'll try to fix these issues as fast as I can. If you know ThreeJS - maybe have advice for me? For performance, I'm already utilizing WebWorkers and as for antialiasing (if fixing performance bug won't allow normal solution) maybe I'll try some FXAA...
Maybe promote it once there are some working examples that are cool. Otherwise it is hard to get excited about just the idea of creating a library.
The example does nothing for me. Just a white page and errors in the browser console. That's not very compelling.
When I started (firefox) it was just a grey page with a frame rate graph in the top left. Turns out it started zoomed in way to far. Really cranking back on the scroll wheel revealed the map.
Except it's zoomed in so far you can't see anything unless you zoom out, and then zooming out too far breaks it (chrome 66). That's why screenshots and explanatory text are good to have. I like it, it just feels not-quite-finished.