[x3d-public] X3D Working Group call for Feb 7 2020

[GPU Group]

> 1. Current 'standard' navigation methods, how do implementations differ?
> 2. Current extensions, for example the TURNTABLE. Can they be put in spec?
in freewrl, hit the ? button, then mouse over the menu bar to see the names
of the menu buttons
- anything you see that you like you can put in the spec - no patents and
I'm a member of web3d.org
> 3. What methods are usable for environments not mouse-driven , for
example haptic devices; and mobile touchscreens,
>
A. touch screen
I had freewrl running as an Android app, and worked up a desktop
configuration to emulate that touchscreen style.
There are a few things about touch screens:
1) no mouse over / isOver
-- for that I put a HOVER mode button, that emulates a desktop mode of
mouse xy motion with no buttons pressed
2) your finger might obscure the screen where you are trying to touch
-- for that I made a PEDAL button that allows you to offset an in-scene
cursor from your touch position
3) no RMB right mouse button to drag to adjust EXAMINE distance
-- for that I made an explicit DIST button, so a touch drag (in Y
direction) will adjust DIST for EXAMINE, TURNTABLE (and I think EXPLORE is
in EXAMINE mode (you click the EXPLORE button 2x to put it into recenter
mode)).
4) if a Sensor node is filling up your screen and you want to navigate away
without touching the sensor, you need a way to temporarily turn off
sensors. in desktop I think the standard is to press the SHIFT hey on the
keyboard. For mobile - like Android- you might not have a keyboard handy
without it taking up half your screen, so  in freewrl I put a SHIFT button
on  the menu so a touch would toggle it.
So in general, any RMB, mouse-up drag, keyboard reliance should be reworked
for touch-screen.

B. headset
I also did a 'cardboard' stereo on Android with freewrl, using just the
orientation sensor on the device, to change the avatar look angle. (but no
position sensor). If someone sends me more sophisticated headsets, I'll see
what I can get working.

C. space mouse
Something I didn't try: 3D positioning device / space mouse / 3dconnexion
sometimes used for CAD. I haven't thought of how that would work.

-Doug Sanden


On Tue, Feb 4, 2020 at 4:01 PM Christoph Valentin <christoph.valentin at gmx.at>
wrote:

> May I suggest a few ideas, although I don't know whether they're new,
> although I will not be able to contribute to their realization?
>
> 1) One should be able to implement custom navigation methods, e.g. by
> scripting
>
> 2) one should be able to introduce a navigation method (or methods) as an
> integral part(s) of an avatar
>
> 3) what is an avatar: an avatar consists of one or more dynamic models
> that represent a virtual identity
>
> 4) a dynamic model is a model that can be loaded or unloaded on demand
> during the lifetime of a multiuser session
>
> 5) one virtual identity can be related to one or more real identities
> (users). In the latter case the virtual identity is called a "crew"
>
> Kind regards
> Christoph
>
>
>
>
> --
> Diese Nachricht wurde von meinem Android Mobiltelefon mit GMX Mail
> gesendet.
> Am 04.02.20, 15:55 schrieb KShell Email <vmarchetti at kshell.com>:
>>
>> I propose a review of X3D navigation methods for the Feb 7 2020 X3D
>> Working Group call. 11:00 AM EST, 8 AM PST, 16:00 UTC
>>
>> On Zoom: https://zoom.us/j/148206572
>>
>> Preliminary outline
>>
>> 1. Current 'standard' navigation methods, how do implementations differ?
>> 2. Current extensions, for example the TURNTABLE. Can they be put in
>> spec?
>> 3. What methods are usable for environments not mouse-driven , for
>> example haptic devices; and mobile touchscreens,
>>
>>
>> All suggestions welcome
>>
>> Vince Marchetti
>>
>>
>>
>>
>>
>> _______________________________________________
>> x3d-public mailing list
>> x3d-public at web3d.org
>> http://web3d.org/mailman/listinfo/x3d-public_web3d.org
>>
> _______________________________________________
> x3d-public mailing list
> x3d-public at web3d.org
> http://web3d.org/mailman/listinfo/x3d-public_web3d.org
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://web3d.org/pipermail/x3d-public_web3d.org/attachments/20200204/19ca7078/attachment.html>