Greg Tatum
Greg Tatum
I ended up using the straight modules with some glue. I really like the idea of offloading the internals of how these things work to modules. It was fairly painless...
Yes! Until I rename this project (again) tonight.
If anyone wants a work around: * Clone the repo * Comment out the assertion * Run `cargo run --bin twiggy -- top path/to/file.wasm` I don't know if the results...
This is still on my list to look at, I only had time today to look at some smaller PRs.
I would love to write custom shaders that looked like this: ``` // main.glsl precision mediump float; #pragma glslify: import(glam/fragment) #pragma glslify: applyLighting = require('glam/lighting/simple') #pragma glslify: getAlbedo = require('glam/albedo')...
Just refactored flat materials. This will be how the user-facing shaders will be structured. I'm thinking on the documentation page you can copy/paste a working shader and customize from there....
@eu9ene Is this bug actionable? Should we close without more specific things to focus on?
I think this is still valid. I'm guessing our task will fail in Taskcluster if and when it comes up. We only need to fix it when a dataset triggers...
This is specific to the JW300 dataset. I'm not sure how applicable this specific fix still is.
Actually, re-reading this issue, I could see where it would be legit. We could analyze datasets and provide a taskcluster warning, maybe in "analyze-" tasks.