Joe Pea
Joe Pea
This fixes some issue with newer three.js, where three.js manages to overwrite `THREE.InstancedMesh` with its own one (didn't happen before I updated from r108 to r121). It is probably better...
see: https://github.com/mrdoob/three.js/commit/764bc3dbbc57b696277b77e648be3857ca3e4b25
It works fine if I start with `wireframe` true, ```js private boxMat = new MeshLambertMaterial({ wireframe: true, }) ``` but I can not change it later: ```js this.boxMat.wireframe = false...
After updating from 107 to 111, I'm getting an error: ``` Uncaught (in promise) TypeError: Cannot read property 'setXYZ' of undefined ``` happening at https://github.com/pailhead/three-instanced-mesh/blob/master/index.js#L186 I don't have a small...
I tried adding a `map` property when making my texture, and this causes the models to become invisible. Should it work? Or are textures not supported yet?
Suppose my InstancedMesh has 10 instances, but I only want to render the first 8 of them for a frame. Can I do that?
I have instanced objects spread around, along with individual non-instanced transparent boxes, and you can see that at certain angles the instanced objects are not visible or they are:  section of the README?
Hello, is it possible for the web pages to access Electron or Atom APIs?
I have a config file like this: .eslintrc.js ```js module.exports = { root: true, parser: '@typescript-eslint/parser', parserOptions: { ecmaVersion: 2018, sourceType: 'module', }, env: { browser: true, node: true, es2017:...