Bjorn
Bjorn
From chat: we should add degree of freedom restriction. There's SixDOF joint, but a simpler approach might be the `allowedDofs` param of `MotionProperties::SetMassProperties` (world space only though). Example API might...
Ok pretty much all of the ideas here have been implemented, so I'm going to close this.
None of the other :setPose methods take a Mat4 either. There's also `Mat4:getPose` which can work around this pretty easily. So maybe this isn't really needed, although it's kinda convenient...
Hey, thanks for the thoughts. I think the assessment about the use cases is accurate. LÖVR aims to be: - Easy to use for beginners to sketch things out without...
This probably won't be merged soon because #737 brought up more questions about vectors that need to be resolved.
Another slightly more simplified/concrete stab at this: - Add an "HDR mode". It's a simplified boolean that indicates whether the backbuffer is using HDR10 (technically PQ10). When active: - Backbuffer...
It seems like HDR metadata is required for this stuff. It mostly consists of metadata about the color space (primaries, white point), plus some data about the range of light...
Other considerations after thinking about it more: - Are `pread`/`pwrite` portable enough for us? Also the windows support with IO completion ports or w/e. - It's possible to do this...
Args on .read/.write get too messy/inconsistent. I think this should be implemented as `File` objects. This isn't immediately planned though.
File object was added in #721