Guus Waals
Guus Waals
Shards like `Set`, `Update`, `Push`, etc. that take a table key are able to do complicated operations on elements inside sequences or tables. Some downsides of having this on these...
The shapes/operations defined by the shards (#455) need to be evaluated on the GPU, raymarching the result for now. - [ ] We should try use the existing shader translator...
Add shards to describe CSG shapes (and their properties) and operations. Shapes: - [ ] Cube - [ ] Size XYZ - [ ] Edge rounding - [ ] Sphere...
Retrieving input from VR devices: - HMD sensors - Hand sensors/buttons - Input represented as OpenXR Actions (an action is a state of a generic controller)
Try to set up a step that can catch leaks on graphics samples/tests
Verify audio works in VR and is positional
https://docs.fragcolor.xyz/contribute/code/getting-started/ The contribute docs don't contain much info about how to debug shards and what tools best to use. Clearly describe the process and tools for debugging on: - [...
Moving panels: - [ ] Drag panels around the viewer Sizing logic for panels: - [ ] Constant screen-size? - [ ] Resizable?
Currently, something like this does not work. ```clj [...] (ForEach (-> >> .my-seq)) .my-seq (Log "Sequence") ``` The type system can't figure out the type of my-seq and it's elements...
Some useful code can be extracted from the shader translator that might later be used for other scenarios