My colleague Tom has been making great progress on getting the triggers functional. Here’s a teaser video:
You can see we’re exposing both a binary on/off input (used to do the red/green switch on the overlay) and the analog input (see the bar at the bottom of the video). The analog one is a little noisy but still probably useful for certain situations, so we’ll pass it on to content developers and see what they come up with.
We’re aiming to have an updated ZapBox app release for the end of the year, which will feature:
- Trigger support (first version ready to go)
- Improved lens calibration (mainly complete, needs some UI tweaks)
- Improved map building (mainly complete, small UI tweaks left)
- More content in launch menu, and a way for us to update that menu outside of app updates (some extra content ready to go, UI updates still needed)
- Pointcode performance and tracking improvements (in progress)
- Android fixes for some more devices (in progress)
So still much to do, but wanted to provide a small progress update at least.
@steve - the triggers and controllers in general are just cardboard, so need to be seen by the device to be reported through to content developers. For the inputs to work, the app will need to see both the “diamond” at the top with the codes on, and also the “collar” that moves up and down when the trigger is pressed. Our early testing is quite positive about the range of controller angles where the trigger still functions, so it’s a real relief that the trigger design that we did a year ago is actually workable on the software side