Fred Emmott

Fred Emmott

@fredemmott.com

Freelance VR software engineer

45 followers17 following56 posts

Lots of in depth advice about how to make sure you can scale, but here’s an easy one for day one: your primary key starts at 1024, not zero, not one. The only thing that knows this is your “new <T>” flow

Fred Emmott reposted

We are pleased to announce the release of the Best Practices Validation Layer. It addresses a critical need in XR development: catching suboptimal API usage patterns that can lead to inconsistent behavior across different OpenXR runtimes. Learn more: www.khronos.org/blog/new-ope... #OpenXR #XR

Fred Emmott reposted

Funding: if your mid/large business uses Dear ImGui - and maybe you are approaching end of year budget/planning etc. - please consider reaching out (PM/email) so I can help you help Dear ImGui !

2/3. More than half of the headsets on the Steam Hardware Survey are Quest-series headsets that have support for hand tracking, but it requires developer mode or third-party software.

3/3. Meta could bring hand tracking support to > 50% of PCVR headsets overnight by removing an arbitrary restriction - this would substantially change the cost/benefit of hand tracking for game developers.

Fred Emmott reposted

Slightly snowed under with the spatial entities announcement, OpenXR 1.1.49 also includes the new render models extension which provides access to 3D models of the controllers currently held by the user.

[1/5] PCVR journalists: when covering a headset software/firmware update, run the OpenXR Conformance Test Suite. If it fails, the headset/software/firmware *DOES NOT* support OpenXR and users should expect problems. The CTS is freely available on GitHub.

View full thread

[5/5] This is clearly bad for developers and users - and it hurts the ecosystem as a whole; your readers/viewers deserve to know what they’re buying; don’t mislead them by saying headsets support OpenXR when they don’t.

It's frustrating as a developer when I investigate crashes and see they're caused by a runtime bug that could easily have been detected before release. It's frustrating for users when I have to tell them to hope for a fix from their manufacturer.

[1/5] PCVR journalists: when covering a headset software/firmware update, run the OpenXR Conformance Test Suite. If it fails, the headset/software/firmware *DOES NOT* support OpenXR and users should expect problems. The CTS is freely available on GitHub.

View full thread

[3/5] Some manufacturers routinely test their releases, and they should be celebrated for this: conformant runtimes make the whole ecosystem stronger and reduce locking. I’ve unfortunately also seen a mix of:

[4/5] - some vendors seem to stick with an old version of the test suite - some vendors only seem to test their initial release, or only major milestone releases - some seem unlikely to have passed any version, and only been spot-tested on a few games

[1/5] PCVR journalists: when covering a headset software/firmware update, run the OpenXR Conformance Test Suite. If it fails, the headset/software/firmware *DOES NOT* support OpenXR and users should expect problems. The CTS is freely available on GitHub.

[2/5] You can ask manufacturers what version of the CTS you should use - this should either be the latest version, or any other version published by Khronos that’s at most 180 days old.

Fred Emmott reposted

You are up to date.