p1 and p2 offscreen

[snoyface]

during testing with shui, p1 and p2 were not on screen, even with dot size at maximum. Also p3 was not seen, but we were only testing x axis.

[t3kt]

What x values were coming in for p1 and p2? We may need to adjust the rendering scale.

[JimAnkrom]

We were sending (and seemed to be receiving) data per spec tho... to be
clear.

On Sat, Mar 26, 2016 at 9:31 PM, Jonathan Macleod notifications@github.com
wrote:

during testing with shui, p1 and p2 were not on screen, even with dot size
at maximum. Also p3 was not seen, but we were only testing x axis.

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub
#4

[JimAnkrom]

For x... I think we were sending 0-360. Ok, so maybe that wasn't spec.

On Sat, Mar 26, 2016 at 9:50 PM, cosine zero arctanone@gmail.com wrote:

We were sending (and seemed to be receiving) data per spec tho... to be
clear.

On Sat, Mar 26, 2016 at 9:31 PM, Jonathan Macleod <
notifications@github.com> wrote:

during testing with shui, p1 and p2 were not on screen, even with dot
size at maximum. Also p3 was not seen, but we were only testing x axis.

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub
#4

[t3kt]

The spec says 0-1.
We can either scale it in sway or in the renderer. It doesn't really matter which.

[t3kt]

If we do decide to do it in the renderer, we should also update the test osc generator to match it.

[JimAnkrom]

No, no, the client software does all translations. The problem part is
converting the compass heading to be 0-1 within the installation space's
x-axis. .

No worries, will sort that out..

On Sat, Mar 26, 2016 at 10:34 PM, tekt notifications@github.com wrote:

If we do decide to do it in the renderer, we should also update the test
osc generator to match it.

—
You are receiving this because you commented.
Reply to this email directly or view it on GitHub
#4 (comment)