Issues
- 3
Virtual Camera
#674 opened by crunchwrap89 - 8
Converting coordinates (Vector3 to latlngAltitude)
#887 opened by ashkalor - 4
Error after update Three dependency: export 'sRGBEncoding' (imported as 'c') was not found in 'three'
#1036 opened by GKersten - 3
Export types in package.json
#837 opened by Krassnig - 7
- 3
Usage with React Three fiber
#880 opened by ashkalor - 3
google.maps has no exported member named WebGLOverlayView . Did you mean OverlayView
#872 opened by markokitanoski1 - 2
Access to renderer
#861 opened by alexlemons - 2
Manipulate tiles
#789 opened by crunchwrap89 - 1
Request documentation
#788 opened by crunchwrap89 - 2
Render with WebGPURenderer
#860 opened by crunchwrap89 - 3
Implement floating anchors
#619 opened by usefulthink - 2
- 1
Anti-aliasing: Enable Access to Renderer
#209 opened by YosanAI - 14
Objects noticeably jitter / anchor issue
#189 opened by MadOPcode - 1
Default lighting
#22 opened by jpoehnelt - 2
Add support for raycasting
#20 opened by jpoehnelt - 2
- 0
Improve coordinate handling and documentation
#618 opened by usefulthink - 1
polyline over 3d object
#529 opened by dognk - 1
- 2
- 5
Combining with google.maps.Polygon
#94 opened by kevinsimper - 3
Example of box staying the same size regardless of zoom like original Marker
#110 opened by kevinsimper - 1
- 4
Enable casting Shadows
#185 opened by YosanAI - 2
Unable to extend ThreeJSOverlayView
#219 opened by YosanAI - 2
Rendering on demand
#242 opened by YosanAI - 6
- 2
- 3
@googlemaps/js-three accept a reference to three module rather than importing it directly?
#45 opened by mprevdelta - 1
Coordinate Transformer Breaking Changes
#354 opened by jpoehnelt - 4
@googlemaps/js-three latLngToVector3 inconsistent on different hemispheres
#51 opened by shannonhobby - 1
z-up vs y-up
#23 opened by jpoehnelt - 1
- 0
The automated release is failing 🚨
#2 opened by github-actions