Marcin Ignac
Marcin Ignac
Base on this code I assume quality = ``` this.quality = ( settings.quality / 100 ) || .8; ```
As the application grows so is the number of components that create regl commands and relaying on `regl.stats` and `reglCommand.stats` is not enough. Some issues: 1. Currently there is no...
For saturation 100 quite often I get RGB results with one of the components slightly below zero: ```javascript hsluv.hsluvToRgb([171, 100, 55]) //[-3.261485526095953e-13, 0.5825533896631454, 0.5048262083306216] ``` I've noticed that while working...
Currently emitting invalid state transition emits error `nanostate.emit: invalid transition ${this.state} -> ${eventName}`. Do you have any ideas on how to handle those errors? E.g. ```javascript var machine = nanostate('cash',...
Can't make any rg.* node work with `pixelFormat: ctx.PixelFormat.RGBA32F`. I get empty texture. `ctx.PixelFormat.RGBA16F` works fine. Tried both Linear and Nearest filtering. Not needed (i can change older r.g. node...
As per https://developer.mozilla.org/en-US/docs/Web/API/WebGLRenderingContext/texImage2D Should we warn in pex-context or rely on browser to fail? Is creates issue here https://github.com/pex-gl/pex-renderer/blob/v4/loaders/glTF.js#L1234
Caused by `const NAMESPACE = "\x1b[31mpex-context\x1b[39m";` Chrome  Safari  Firefox 
Used here https://github.com/pex-gl/pex-context/blob/master/examples/shadows.js#L283
Is available in WebGL 2 Example usage renderbufferStorageMultisample + blitframebuffer: https://stackoverflow.com/a/55976760/1527470
To make this transition manageable i propose following steps - [x] update this repo to ESM - [x] port VAO (#85) from [85-vao-temp](https://github.com/pex-gl/pex-context/tree/85-vao-temp) branch - [ ] decide on UBO...