<html><body><html><head><meta name="viewport" content="width=device-width" /><meta http-equiv="Content-Type" content="text/vnd.ui.insecure+html;charset=utf-8" /></head><body style="overflow-wrap:break-word; word-break: break-word;"><div class="mail_android_message" style="line-height: 1; padding: 0.5em">>>>>>I don't think X3D defines any force feedback nodes. Maybe it should?<br>
<br>
Hmmmmmm. I am not sure. <br>
<br>
I think X3D in any encoding is a standard for decades- if not centuries.<br>
<br>
Having dependencies to VR hardware - which is changing fast and innovatively - could be a challenge.<br>
<br>
I mean, some concept like "touching the scenery" is a virtual skill (very abstract) which might be realized by different real skills- a mouse, a VR control or anything else in future. Thus the TouchSensor specifies perfectly a virtual skill and it's up to the Browser, which real skill must be used to invoke the virtual skill.<br>
<br>
In some way the HMD and the VR controller would be seen as a resource of the X3D Player and the integration with different HMDs and VR Controllers would be up to the X3D Player, independent from the x3d standard.<br>
<br>
Now, when we talk about force feed back, then we have another active element. I call it "the cockpit". This is Independent from the X3D Player.<br>
<br>
We need something in the scene that represents the state of the cockpit (position, orientation, velocity, angular velocity, acceleration) .<br>
<br>
The "virtual cockpit" (which should be provided by the Vendor of the "real cockpit") could use the Network Sensor to communicate with the "real cockpit".<br>
<br>
Just my $0.02<br>
<br>
<br>
<br>
-- <br>
Diese Nachricht wurde von meinem Android Mobiltelefon mit GMX Mail gesendet.</div><div class="mail_android_quote" style="line-height: 1; padding: 0.3em">Am 23.01.19, 00:19, GPU Group <gpugroup@gmail.com> schrieb:<blockquote class="gmail_quote" style="margin: 0.8ex 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<div dir="ltr"><div>Christoph,</div><div>"NavigationInfo", "Viewpoint", "ProxiSensor", "TouchSensor", "PlaneSensor" <br /></div>- navigationInfo<div>in-scene definition might be OK, but the browser might have some settings for different effects for flying or walking<br /><div>- viewpoint OK</div><div>ProximitySensor - likely OK - its where your viewpoint is?</div><div>TouchSensor - in scene OK, and the browser would have various ways to define a ray from the viewpoint - a data glove or other method of steering/dragging a ray, for example a hand-held game thumbstick (I have one) that you can push a button to shoot a ray from the center of the right (or left) eye, and when you take your finger off it is like a single click etc or dataglove equivalent.</div><div>PlaneSensor - similar to touch</div><div>Yes I think all those scene file nodes would be OK. Your browser may need some options for different ways to fly / walk forward (without you moving much), and some mechanisms to aim a ray and 'click' for touch / planesensors.</div><div>I don't think X3D defines any force feedback nodes. Maybe it should?</div><div>-Doug</div><div><br /></div><div><br /></div><div><br /></div><div><br /></div></div></div><br /><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Tue, Jan 22, 2019 at 2:21 PM Christoph Valentin <<a href="mailto:christoph.valentin@gmx.at">christoph.valentin@gmx.at</a>> wrote:<br /></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div><div style="word-break:break-word"><div class="gmail-m_530807069937712937mail_android_message" style="line-height:1;padding:0.5em">Hi Doug.<br />
<br />
That sounds good. So have I got it correctly?<br />
<br />
I need not expect major changes to my content. At least basic navigation and interactivity is ensured by existing X3D nodes like "NavigationInfo", "Viewpoint", "ProxiSensor", "TouchSensor", "PlaneSensor" and so on.<br />
<br />
Just when I needed some special things like Force Feed back in a car race or "riding a locomotive", then I would have to expect some Scripting or Prototyping.<br />
<br />
True?<br />
<br />
Thanks<br />
Christoph<br />
-- <br />
Diese Nachricht wurde von meinem Android Mobiltelefon mit GMX Mail gesendet.</div><div class="gmail-m_530807069937712937mail_android_quote" style="line-height:1;padding:0.3em">Am 22.01.19, 21:56, GPU Group <<a href="mailto:gpugroup@gmail.com" target="_blank">gpugroup@gmail.com</a>> schrieb:<blockquote class="gmail_quote" style="margin:0.8ex 0pt 0pt 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<div dir="ltr">"..VR equipment.."<div>Do you mean HMDs / head mounted displays? And 'data gloves' etc to go with it?</div><div>I think it's not hard - the hard part is ... buying the HMD with real money. Hard currency. Then fiddling for a few weeks.</div><div>Someone had freewrl running with an HMD a decade ago, but didn't leave the code.</div><div>I've had freewrl running on an android phone with so-called cardboard HMD - uses the IMU inertial measuring unit for orientation, and 2 magnifying lenses.</div><div>I was planning to do HMDs/AR this year but so far no action.. </div><div>Someone else was working on a Unity game engine x3d display, and my guess is that Unity can use HMDs. </div><div>-Doug</div><div><br /></div><div><br /></div></div><br /><div class="gmail_quote"><div dir="ltr" class="gmail-m_530807069937712937gmail_attr">On Tue, Jan 22, 2019 at 1:11 PM Christoph Valentin <<a href="mailto:christoph.valentin@gmx.at" target="_blank">christoph.valentin@gmx.at</a>> wrote:<br /></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div><div class="gmail-m_530807069937712937gmail-m_1881856007079569007mail_android_message" style="line-height:1;padding:0.5em">Hi all. <br />
<br />
Thanks for all hints received so far.<br />
<br />
However my main question was about VR.<br />
<br />
Are there any plans or is it already possible to use X3D Players with VR equipment?<br />
<br />
Does it make a difference whether I use "native" X3D Players (Contact, Instant Player, Castle Game Engine, ......) or "WebGL based" X3D Players.<br />
<br />
I will myself face this question actually earliest in 2020 I admit, but I thought having some answers on X3D-public could also help other People.<br />
<br />
KR<br />
Christoph<br />
-- <br />
Diese Nachricht wurde von meinem Android Mobiltelefon mit GMX Mail gesendet.</div><div style="word-break:break-word"><div class="gmail-m_530807069937712937gmail-m_1881856007079569007mail_android_quote" style="line-height:1;padding:0.3em">Am 19.01.19, 03:36, Christoph Valentin <<a href="mailto:christoph.valentin@gmx.at" target="_blank">christoph.valentin@gmx.at</a>> schrieb:<blockquote class="gmail_quote" style="margin:0.8ex 0pt 0pt 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<div style="font-family:Verdana;font-size:12px"><div>Hi all,</div>
<div> </div>
<div>When I will be finished with my application (alpha release "not before 2020"), then I will have a nice little Visual Basic Application for .NET/Windows integrated with an X3D Scene played on BS Contact, made multiuser capable by BS Collaborate.</div>
<div> </div>
<div>Besides some licensing questions (will my users like to pay for BS Contact? will at least one of my users be willing to buy and run BS Collaborate) I will have some other questions:</div>
<div> </div>
<div>What about VR?</div>
<div> </div>
<div>Will it be possible to go downstairs to the VR Cafe and tell the people: here's a nice collaborative application, where everybody can bring his/her own content. Can we play it on your hardware?</div>
<div> </div>
<div>Will I need to rebase to another X3D Player? Instant Player? Free Wrl? X3DOM? X_ITE? Castle Game Engine? ...?</div>
<div> </div>
<div>Any hint welcome.</div>
<div> </div>
<div>Thanks in advance</div>
<div>Christoph</div></div></blockquote></div></div></div>
_______________________________________________<br />
x3d-public mailing list<br />
<a href="mailto:x3d-public@web3d.org" target="_blank">x3d-public@web3d.org</a><br />
<a href="http://web3d.org/mailman/listinfo/x3d-public_web3d.org" rel="noreferrer" target="_blank">http://web3d.org/mailman/listinfo/x3d-public_web3d.org</a><br />
</blockquote></div>
_______________________________________________
x3d-public mailing list
<a href="mailto:x3d-public@web3d.org" target="_blank">x3d-public@web3d.org</a>
<a href="http://web3d.org/mailman/listinfo/x3d-public_web3d.org" target="_blank">http://web3d.org/mailman/listinfo/x3d-public_web3d.org</a>
</blockquote></div></div></div>
</blockquote></div>
_______________________________________________
x3d-public mailing list
x3d-public@web3d.org
http://web3d.org/mailman/listinfo/x3d-public_web3d.org
</blockquote></div></body></html></body></html>