<div dir="ltr">valancy:<div>shape 1: m projective textures</div><div>Its possible and likely for terrain or drone mappnig you would have dozens of images and perhaps one terrain grid, and so when rendering a pixel on the terrain, you would go through a list of projectors until you get a hit, or there might be a way to prioritize several hits, for example the PTM ray hit that's most normal to the surface.</div><div>-Doug</div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Wed, Jan 29, 2020 at 4:59 PM GPU Group <<a href="mailto:gpugroup@gmail.com">gpugroup@gmail.com</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 dir="ltr"><div>Andreas - I like your Viewpiont-re-use ideas, if necessary split viewpoint</div>Viewpoint :: Camera<div>Projector :: Camera</div><div>And yes - same orientation methods as Viewpoint would make sense.</div><div>Holger what did you do?</div><div><br></div><div>I think because it's slow/busy shader code you wouldn't want it to apply universally - you'd want to pair it explicitly with whatever shapes are going to get it.</div><div>Projector maybe implies the wrong thing. It's not like you are shooting rays from the projector and seeing what geom it htis. It should be the other way I think for sanity and efficiency - when you have geometry that's getting PTM then you run a special shader and give it the relative pose of the projector and (ortho or perspective) and construct a ray from your shape surface pixel back toward the projectors image plane - through the perspective center / focal point if perspective, or perpendicular to the image plane if ortho.</div><div>The image plane is an infinite plane. And when your ray hits that plane you get an xy on the plane, and you see if its inside the image. If not, its a miss, else it's a hit, and you do a smapler2D on the image and do your modulate or replace or whatever.</div><div>Holger what did you do?</div><div>-Doug</div><div><br></div><div><br></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Wed, Jan 29, 2020 at 3:57 PM Andreas Plesch <<a href="mailto:andreasplesch@gmail.com" target="_blank">andreasplesch@gmail.com</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">Hi Michalis,<br>
<br>
I took the opportunity to look at<br>
<a href="https://www.web3d.org/specifications/X3Dv4Draft/ISO-IEC19775-1v4-WD1/Part01/components/ProjectiveTextureMapping.html" rel="noreferrer" target="_blank">https://www.web3d.org/specifications/X3Dv4Draft/ISO-IEC19775-1v4-WD1/Part01/components/ProjectiveTextureMapping.html</a><br>
and some of the history.<br>
<br>
My main thought was why not reuse the existing, abstract viewpoint<br>
nodes to define the projector characteristics. The projector node<br>
fields just reiterate the viewpoint node fields, for the most part.<br>
But probably there are enough differences since viewpoint mixes camera<br>
and navigation options.<br>
<br>
Why not follow viewpoint and use orientation as a rotation instead of<br>
direction and upVector ? Seems more consistent and simpler.<br>
<br>
The definition of the coordinate system for location/direction seems<br>
to be missing. It is probably implied that it is the local coordinate<br>
system.<br>
<br>
Overall, it feels strange to have a global projector to affect all<br>
appearances by default but perhaps that is the most common scenario.<br>
The term Texture Mapping rather implies that it is a way to compute<br>
texture coordinates for a given texture, similar to<br>
TextureCoordinateGenerator, and on a similar level:<br>
ProjectiveTextureGenerator. DEF/USE would allow applying it to<br>
multiple Appearances easily.<br>
<br>
-Andreas<br>
<br>
On Mon, Jan 27, 2020 at 6:18 PM Michalis Kamburelis<br>
<<a href="mailto:michalis.kambi@gmail.com" target="_blank">michalis.kambi@gmail.com</a>> wrote:<br>
><br>
> Andreas Plesch <<a href="mailto:andreasplesch@gmail.com" target="_blank">andreasplesch@gmail.com</a>> wrote:<br>
> ><br>
> > x3dom has an extra explorationMode field which restricts mouse function in examine/turntable mode.<br>
> > zoom, pan, rotate values restrict to only these.<br>
> > -zoom, -pan, -rotate disable these.<br>
> > The field tends to be quite useful.<br>
> ><br>
> > I think x-ite implemented Projective Texture Mapping.<br>
><br>
> Good news we have an implementation of PTM.<br>
><br>
> I had some questions about how the Projective Texture Mapping in X3D<br>
> v4 applies the texture -- what happens if the shape already has a<br>
> ImageTexture, what happens if shape already has MultiTexture etc. I<br>
> listed them on "TODO: Address how the projective texturing in spec<br>
> affects existing textures" in<br>
> <a href="https://github.com/michaliskambi/x3d-tests/wiki/Clarify-%22Projective-texturing%22-component#todo-address-how-the-projective-texturing-in-spec-affects-existing-textures" rel="noreferrer" target="_blank">https://github.com/michaliskambi/x3d-tests/wiki/Clarify-%22Projective-texturing%22-component#todo-address-how-the-projective-texturing-in-spec-affects-existing-textures</a><br>
> . I'll test how X_ITE answered these questions.<br>
><br>
> Regards,<br>
> Michalis<br>
><br>
> ><br>
> > ---on the phone---<br>
> ><br>
> > On Mon, Jan 27, 2020, 3:00 PM <<a href="mailto:x3d-public-request@web3d.org" target="_blank">x3d-public-request@web3d.org</a>> wrote:<br>
> >><br>
> >> Send x3d-public mailing list submissions to<br>
> >> <a href="mailto:x3d-public@web3d.org" target="_blank">x3d-public@web3d.org</a><br>
> >><br>
> >> To subscribe or unsubscribe via the World Wide Web, visit<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>
> >> or, via email, send a message with subject or body 'help' to<br>
> >> <a href="mailto:x3d-public-request@web3d.org" target="_blank">x3d-public-request@web3d.org</a><br>
> >><br>
> >> You can reach the person managing the list at<br>
> >> <a href="mailto:x3d-public-owner@web3d.org" target="_blank">x3d-public-owner@web3d.org</a><br>
> >><br>
> >> When replying, please edit your Subject line so it is more specific<br>
> >> than "Re: Contents of x3d-public digest..."<br>
> >><br>
> >><br>
> >> Today's Topics:<br>
> >><br>
> >> 1. Re: x3d v4 proposed changes > 2 opensource criteria > any<br>
> >> that are short (GPU Group)<br>
> >><br>
> >><br>
> >> ----------------------------------------------------------------------<br>
> >><br>
> >> Message: 1<br>
> >> Date: Mon, 27 Jan 2020 12:18:39 -0700<br>
> >> From: GPU Group <<a href="mailto:gpugroup@gmail.com" target="_blank">gpugroup@gmail.com</a>><br>
> >> To: X3D Graphics public mailing list <<a href="mailto:x3d-public@web3d.org" target="_blank">x3d-public@web3d.org</a>><br>
> >> Subject: Re: [x3d-public] x3d v4 proposed changes > 2 opensource<br>
> >> criteria > any that are short<br>
> >> Message-ID:<br>
> >> <<a href="mailto:CAM2ogRfqXoH1duy9iGvX9BEmLFCpiLbYYO_HwMuR7HbYXkRvmg@mail.gmail.com" target="_blank">CAM2ogRfqXoH1duy9iGvX9BEmLFCpiLbYYO_HwMuR7HbYXkRvmg@mail.gmail.com</a>><br>
> >> Content-Type: text/plain; charset="utf-8"<br>
> >><br>
> >> INVENTORY<br>
> >> FREEWRL<br>
> >> * X3Dv4 Implementations<br>
> >> <a href="https://www.web3d.org/x3dv4-implementations" rel="noreferrer" target="_blank">https://www.web3d.org/x3dv4-implementations</a><br>
> >> 1) 43 Projective Texture Mapping<br>
> >> x freewrl does not implement, document is mistaken<br>
> >> 2) 23.4.4 NavigationInfo > TURNTABLE<br>
> >> * freewrl implemented<br>
> >> (other freewrl navmodes and related not in v3.3:<br>
> >> DIST - explicit control over distance to pivot point for examine, turntable<br>
> >> - touchpads don't need RMB<br>
> >> SHIFT - turns off sensors<br>
> >> HOVER - isOver mode (useful for touch pad - allows triggering of isOver<br>
> >> only)<br>
> >> PEDAL - can drag 'floating cursor' in steps<br>
> >> SPHERICAL - like FLY: YAWPITCH except rotations constrained to viewpoint<br>
> >> local axes)<br>
> >> subsets of FLY: YAWZ, XY, YAWPTICH,ROLL)<br>
> >> 3) GeoSpatial > GeoOrigin - freewrl still allows in v3.3, never deprecated<br>
> >> in freewrl<br>
> >> 4) The rest freewrl has not implemented<br>
> >> /FREEWRL<br>
> >> Does this table miss anything?<br>
> >> /INVENTORY<br>
> >> -Doug Sanden<br>
> >> PS who's doing projective texture mapping? Should start with that?<br>
> >><br>
> >><br>
> >> On Mon, Jan 27, 2020 at 11:59 AM GPU Group <<a href="mailto:gpugroup@gmail.com" target="_blank">gpugroup@gmail.com</a>> wrote:<br>
> >><br>
> >> > INVENTORY<br>
> >> > FREEWRL<br>
> >> > * X3Dv4 Implementations<br>
> >> > <a href="https://www.web3d.org/x3dv4-implementations" rel="noreferrer" target="_blank">https://www.web3d.org/x3dv4-implementations</a><br>
> >> > 1) 43 Projective Texture Mapping<br>
> >> > x freewrl does not implement, document is mistaken<br>
> >> > 2) 23.4.4 NavigationInfo > TURNTABLE<br>
> >> > * freewrl implemented<br>
> >> > (other freewrl navmodes and related not in v3.3:<br>
> >> > DIST - explicit control over distance to pivot point for examine,<br>
> >> > turntable - touchpads don't need RMB<br>
> >> > SHIFT - turns off sensors<br>
> >> > HOVER - isOver mode (useful for touch pad - allows triggering of isOver<br>
> >> > only)<br>
> >> > PEDAL - can drag 'floating cursor' in steps<br>
> >> > SPHERICAL - like FLY: YAWPITCH except rotations constrained to viewpoint<br>
> >> > local axes)<br>
> >> > subsets of FLY: YAWZ, XY, YAWPTICH,ROLL)<br>
> >> > 3) GeoSpatial > GeoOrigin - freewrl still allows in v3.3, never deprecated<br>
> >> > in freewrl<br>
> >> > 4) The rest freewrl has not implemented<br>
> >> > /FREEWRL<br>
> >> > Does this table miss anything?<br>
> >> > /INVENTORY<br>
> >> ><br>
> >> ><br>
> >> > On Mon, Jan 27, 2020 at 11:14 AM Don Brutzman <<a href="mailto:brutzman@nps.edu" target="_blank">brutzman@nps.edu</a>> wrote:<br>
> >> ><br>
> >> >> Thanks for writing Doug.<br>
> >> >><br>
> >> >> On 1/27/2020 6:01 AM, GPU Group wrote:<br>
> >> >> > A rule of <a href="http://web3d.org" rel="noreferrer" target="_blank">web3d.org</a> <<a href="http://web3d.org" rel="noreferrer" target="_blank">http://web3d.org</a>> is that changes to the spec<br>
> >> >> need a least 2 opensource implementations.<br>
> >> >><br>
> >> >> * Web3D Standards Adoption Process<br>
> >> >> <a href="https://www.web3d.org/standards/adoption-process" rel="noreferrer" target="_blank">https://www.web3d.org/standards/adoption-process</a><br>
> >> >><br>
> >> >> 5.c. "Identify at least two independent and interoperable implementations<br>
> >> >> (at least one should be open source)"<br>
> >> >><br>
> >> >> > Q. are there any proposed changes that do not yet have 2 opensource<br>
> >> >> implementations?<br>
> >> >><br>
> >> >> Yes, plenty. We have not taken a recent inventory of features yet, but<br>
> >> >> will be tracking that at<br>
> >> >><br>
> >> >> * X3Dv4 Implementations<br>
> >> >> <a href="https://www.web3d.org/x3dv4-implementations" rel="noreferrer" target="_blank">https://www.web3d.org/x3dv4-implementations</a><br>
> >> >><br>
> >> >> Our prominent open-source implementations for X3Dv3.3 include FreeWrl,<br>
> >> >> X_ITE, X3DOM, Castle Game Engine. Soon Xj3D will be back on the table as<br>
> >> >> well. There are also non-rendering X3Dv4 implementations for Java,<br>
> >> >> JavaScript, Python, conversions and validation. Not sure about Titania but<br>
> >> >> presumably yes. X3D-Editv4 is on the horizon. Interestingly everything on<br>
> >> >> this list is open source.<br>
> >> >><br>
> >> >> Hoping that FreeWrl developers are keen to keep their record-setting X3D<br>
> >> >> support accomplishments continuing! 8)<br>
> >> >><br>
> >> >> All feedback welcome, appreciate your many efforts.<br>
> >> >><br>
> >> >> > Thanks,<br>
> >> >> > Doug Sanden<br>
> >> >> > -freewrl<br>
> >> >><br>
> >> >> all the best, Don<br>
> >> >> --<br>
> >> >> Don Brutzman Naval Postgraduate School, Code USW/Br<br>
> >> >> <a href="mailto:brutzman@nps.edu" target="_blank">brutzman@nps.edu</a><br>
> >> >> Watkins 270, MOVES Institute, Monterey CA 93943-5000 USA<br>
> >> >> +1.831.656.2149<br>
> >> >> X3D graphics, virtual worlds, navy robotics<br>
> >> >> <a href="http://faculty.nps.edu/brutzman" rel="noreferrer" target="_blank">http://faculty.nps.edu/brutzman</a><br>
> >> >><br>
> >> ><br>
> >> -------------- next part --------------<br>
> >> An HTML attachment was scrubbed...<br>
> >> URL: <<a href="http://web3d.org/pipermail/x3d-public_web3d.org/attachments/20200127/53a57192/attachment-0001.html" rel="noreferrer" target="_blank">http://web3d.org/pipermail/x3d-public_web3d.org/attachments/20200127/53a57192/attachment-0001.html</a>><br>
> >><br>
> >> ------------------------------<br>
> >><br>
> >> Subject: Digest Footer<br>
> >><br>
> >> _______________________________________________<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>
> >><br>
> >><br>
> >> ------------------------------<br>
> >><br>
> >> End of x3d-public Digest, Vol 130, Issue 49<br>
> >> *******************************************<br>
> ><br>
> > _______________________________________________<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>
<br>
<br>
<br>
-- <br>
Andreas Plesch<br>
Waltham, MA 02453<br>
<br>
_______________________________________________<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>
</blockquote></div>