Zach Kinstner

Results 16 issues of Zach Kinstner

This will require investigation and some experience working with Unreal Engine. See [this forum discussion](https://forums.unrealengine.com/showthread.php?6935-VR-GUI-Menu-ideas) where developers are expressing interest for Unreal support.

enhancement

Please see the [**v2.0.0B (beta) release page**](https://github.com/aestheticinteractive/Hover-UI-Kit/releases/tag/v2.0.0B). This ticket is for discussion about the latest changes, including any bugs, issues, and questions that might come up. The [**project wiki**](https://github.com/aestheticinteractive/Hover-UI-Kit/wiki) provides...

announcement

Currently, only the Leap Motion input is supported. This implementation is hidden behind various [input interfaces](https://github.com/aestheticinteractive/Hovercast-VR-Menu/tree/master/Unity/Assets/Hovercast/Scripts/Input), however, which is the first step toward supporting multiple devices. The desired input type...

enhancement

Received via email: > Have you thought about integrating with something like OSVR? That seems like a nice attempt at some standardization in this space. Received via email: > We’d...

enhancement

From [this review video](https://www.youtube.com/watch?v=WKmbV6sSfW8) of @squakmix's Graffiti 3D, and the subsequent [Twitter discussion](https://twitter.com/JScottKuehnert/status/578664601157545985): > # Hovercast #VR didn't work too well... try select/release away from the edge :) https://www.youtube.com/watch?v=Phn3Ix-YxPA >...

enhancement
usability

[@belltyler](https://twitter.com/belltyler) wrote [on Twitter](https://twitter.com/belltyler/status/567412832254558208): > [@zachkinstner](https://twitter.com/zachkinstner) First off, amazing work on Hovercast VR. I think it's fantastic. Any chances you'll make a Three.js / Leap.js version next? :p

enhancement

@squakmix wrote: > After using the slider for color selection for a bit, I've noticed that its extremely difficult to release it on a particular value and other users I've...

enhancement
usability

This fix for issue #530 involves copying some logic from `Kinetic.SceneContext._stroke()` to `Kinetic.HitContext._stroke()`. The `HitContext` was not updating its transforms before drawing a line with `strokeScaleEnabled == false`. These changes...

A shape's hit area does not align with its visual position in the following scenario: - Use a `pixelRatio` not equal to one - Contain the shape within a group...

bug

Add a `CNAME` file and update DNS: https://help.github.com/articles/setting-up-a-custom-domain-with-pages

enhancement