[webvr] WebVR 1.0: can resetPose() be considered cheap?

Jan Wrobel wrr at mixedbit.org
Thu Sep 29 02:01:24 UTC 2016


I need a difference not an absolute position to handle
collisions. Absolute position is not easy to work with
if an app does not allow to move through objects.

On Fri, Sep 9, 2016 at 3:39 PM, Sean McBeth <sean.mcbeth at gmail.com> wrote:
> And why do you need this?
>
>
> On Sep 9, 2016 9:33 AM, "Jan Wrobel" <wrr at mixedbit.org> wrote:
>>
>> I was thinking of doing something like this:
>>
>> handleFrame() {
>>   var pose =  display.getPose();
>>   // ... do something with the pose
>>   display.resetPose(); // so getPose() during the next frame returns a
>> difference from this frame not an absolute value.
>> }
>>
>>
>>
>> On Fri, Sep 9, 2016 at 3:22 PM, Sean McBeth <sean.mcbeth at gmail.com> wrote:
>> > I don't understand what you are trying to do here. Reset pose every
>> > frame
>> > would show essentially a fixed position and orientation. It's basically
>> > "zero sensor", though I understand it's a little more involved than
>> > that.
>> >
>> > In the general case, you shouldn't need to call reset pose. It's a
>> > calibration tool.
>> >
>> >
>> > On Sep 9, 2016 9:14 AM, "Jan Wrobel" <wrr at mixedbit.org> wrote:
>> >
>> > Hi,
>> >
>> > In WebVR 1.0 API will it be a good practice to call resetPose() each
>> > frame if an application is interested in a position difference between
>> > frames? Or should resetPose() be considered expensive and it is better
>> > to calculate such difference manually?
>> >
>> > Thank you,
>> > Jan Wrobel
>> > _______________________________________________
>> > web-vr-discuss mailing list
>> > web-vr-discuss at mozilla.org
>> > https://mail.mozilla.org/listinfo/web-vr-discuss
>> >
>> >


More information about the web-vr-discuss mailing list