Noeri Huisman

> > ``` > > > > ``` > > Should probably consolidate all in controllers in gripSpace? From a consistency pov I agree, it's weird that _only_ the `oculus-touch-controls`...

Under the hood the `hand-controls` uses these individual components, which you can check to see which one is actually active. For example: ```JS if(handControlsEl.components('vive-controls').controllerPresent) { // Do something only for...

> Does “Vive-controls” mean just the wand? or does it trigger for index controllers as well? It shouldn't trigger for the index controllers, but it does currently trigger for all...

@wyzwon While I would still like to avoid additional logic for specific controllers, it might indeed be the easiest way forward for the time being. It would definitely help anyone...

@dmarcos While setting `texture.colorSpace` manually works, you could consider calling `rendererSystem.applyColorCorrection(texture)` from your component instead. That way the component will work correctly with older versions (

Things have changed with regards to colour management in both three.js and A-Frame recently, so it might be a good idea to try and get things working on master. Also...

There are a couple of issues at play simultaneously, some of which _do_ depend on `colorManagement: true` (or at least they should). The second point you listed about the material...

> Is it possible to move OBJLoader.js / MTLLoader.js to AFRAME tree and fix that? Making custom changes to three.js leads to more maintenance, and can create incompatibilities with libraries...

> Please can you help and point me to correct manual how to substitute specific node module for all for libraries which reference it in project? With the way A-Frame...

Hard to tell without knowing your full setup, but in general you don't want to explicitly refer to `super-three`. The error is correct in the sense that neither three nor...