Almar Klein
Almar Klein
While working on large shaders as in #628, it would help to have WGSL syntax highlighting. Right now the shaders are strings, which makes this hard. * Fix via an...
Relates to https://github.com/pygfx/wgpu-py/issues/391 Using the async versions of the wgpu methods would possibly result in better performance, but also make pyscript support easier/possible (see https://github.com/pygfx/wgpu-py/issues/407). I think we already do...
The wheel event object has properties like `button` and `buttons`, but they are always zero and the empty tuple, respectively. The reason is that the wgpu event dict does not...
During the work in (https://github.com/pygfx/gfxmorph) we realized two issues: * It would be nice if the uploading of data could be more precise, rather than uploading the full range from...
### Intro Right now, the `Scene` object is really just a `Group`. Although the `gfx.show()` function does behave differently depending on whether a `Scene` is given or a `Group`. We...
Specific use-cases, perhaps using custom shaders, may require buffers or textures to have additional usage flags, see e.g. #567. There is `resource._wgpu_usage`, which is a private flag intended for internal...
IIRC @panxinmiao proposed this earlier. Then we can create stuff like [this](https://threejs.org/examples/?q=dynamic#webgl_materials_cubemap_dynamic). ---- * [x] cube camera * [ ] PMREM generation utility
The basis for text rendering are laid in #305. This issue lists the tasks that we left for later, as well as possible improvements. ### Done * The basis was...
### Todo * [x] Decide on a coordinate system * [ ] Document it * [ ] Document that our coordinates are unit-free, see [this comment in this issue](https://github.com/pygfx/pygfx/issues/460#issuecomment-1642604075) for...
### Overview of issues There are currently a few issues related to how we currently deal with viewports and overlays. * It currently prevents using the values in the depth...