Amethyst Technical Preview (v1.0.3.0)

Amethyst v1.0.3.0 Technical Preview (RC 1)

Short Commit ID: 1cce2c4 (Amethyst)

In case you wanted to know what's changed since 0.9...
Better ask what's NOT been changed. But that'd be stupid
Anyway, there's a simple somewhat-of-a-changelog, here

Setup instructions are also available on discord
For help with, please hit 公彦赤屋先#5023 or #development

Pre-requisites (You need these to run the app):

• Install VCRedist 2022

Actually doing the thing:

• Download Amethyst-Release-XXXXXXX.zip
• Create a new folder, e.g. C:\Amethyst
• Extract the ZIP into that new folder.
  In the case of the example folder, you would end up with C:\Amethyst\Amethyst.exe
• Once Amethyst is launched, Click re-register SteamVR driver and follow the prompts.
• 

It's unsupported but please help me anyway!!!

My SteamVR gives me Error 203 and won't start no matter what I do.

You have the Amethyst and K2EX drivers enabled at the same time.
They use the same logging library and conflict with each other on startup, causing the entirety of the SteamVR backend to crash.
Close SteamVR, then either delete or edit %localappdata%\openvr\openvrpaths.vrpath
if your file says null in it after you edited it, go learn JSON, and WTF are you doing on GitHub????

I have some other unrelated issue.

Unless you're actually braindead, you may possibly have run into a bug,
reporting those is important to building a stable application for release.
See just below on how to report bugs.

Time for your move:

We're currently localizing (translating) Amethyst, crash handler and devices.
If you know (or someone, you know, knows?) more languages than English
(preferably intermediate), please consider committing to the project.
You can find the instructions, FAQ, and files here

You can register VR manifests and enable AutoStart with SteamVR inside Amethyst.

Changes:

• Light theme shouldn't now break the app! (Fixed calibration/offsets/device-settings/...)
• Both the server driver and the API have been rewritten to use Google Protocol Buffers.
  • Amethyst should react even faster (note: Kinect is still operating at 30Hz!)

    Reason: Protobuf is faster, and we don't need to HEX-encode everything

  • Decrease in badly formatted/parsed messages - less errors should happen
  • Higher config/version mismatch tolerance (sometimes helps in debugging)
• Amethyst now uses the native Win32 http client class for networking
• Settings are handled by cereal, this should hopefully fix often config breaks
• Filesystem handlers are operated by STL, this should decrease possible errors
• Various string changes and interface stability updates

What's with that RC?

Amethyst has entered its Release Candidate state.
This means devs are bored so much they randomy rewrite half of the app.
the next builds are only gonna become more and more stable and fixed,
and that their backend/interfacing code is finally robust enough (...maybe)

Due to pending API changes, this release may be one of the last PREVIEW ones.

Note: it doesn't mean that a stable is near, it means we're only preparing for it

Pending critical changes:

• Releases checked with K2VR Web API and updated with the installer
  • Internal-external automatic Amethyst app updater
• New, super-cute automatic calibration image w/ directions
• New User Experience w/ TeachingTips and app-state-aware flyouts

Reports:

• Record the issue (or at least describe it as well as you can)
• Send us the log files from %AppData%/Amethyst/logs