gl-vis / gl-plot3d

A common interface for setting up 3D plots

gl-vis

A modular visualization system for JavaScript.

gl-plot3d's Issues

Aspect ratio for axes

Should have some option to preserve the aspect ratio of the axes.

`mouse-wheel` (and the buggy `to-px` dependency) is abandoned, please replace

mouse-wheel has not been touched in 3 to 4 years, and to-px in 7 months, and this critical module loading bug has sat untouched since January: mikolalysenko/to-px#6

@archmoj Since it looks like it was added in c7f8316 could you please review this, and change to a different library for that mouse wheel dependency?

zoomMin zoomMax possibly switched

I was looking at the code here:

gl-plot3d/scene.js

Line 120 in 0ae1280

zoomMin: options.camera.zoomMax || 0.1,

and was wondering if it was meant to be

zoomMin: options.camera.zoomMin || 0.1, 

(and vice versa on the following line)

Canvas scaling skwed

Using the following code:

var createScene = require('gl-plot3d');
var scene = createScene({'canvas': document.getElementById('mycanvas')});

I expect the canvas to maintain it's height and width defined in html. This was the case in v1.0.0. However, when I try 1.0.1, adding the scene to the canvas results in a change in placement and dimension of the canvas.

Switch camera from free movement to turntable by default

iPhone/iPad flickering

Related #11

Some frames get lost while panning in iPad/iPhone. That is not happening if context has preserveDrawingBuffer: true, therefore frame gets rendered before marked as dirty.
Similar issue was in dy/pan-zoom@2cfc238.

Hardware + chrome-dependent washed out colors

If I visit this page: https://rreusser.github.io/plotly-mock-viewer/#gl3d_bunny

On a computer with these specs:
OS X El Capitan
Version 10.11.6
MacBook Pro (Retina, 13-inch, Early 2015)
Processor 2.7 GHz Intel Core i5
Memory 8 GB 1867 MHz DDR3
Graphics Intel Iris Graphics 6100 1536 MB

With Chrome 62.0.3202.94

I see this:

With Chrome <= 59, I see this:

If I change scene.js#L706 to this:

gl.clearColor(0,0,0,0.0000001)

I see this:

I'm aware of this happening on other webgl software products and at least a couple computers using it. It seems like new Chrome has some sort of hardware-dependent bug.