Menu
▾
▴
x3dom-users — List for posting questions, ideas, etc. on X3DOM.
You can subscribe to this list here.
| 2011 |
Jan
|
Feb
|
Mar
|
Apr
(8) |
May
(9) |
Jun
(23) |
Jul
(9) |
Aug
(29) |
Sep
(5) |
Oct
(24) |
Nov
(31) |
Dec
(19) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2012 |
Jan
(18) |
Feb
(17) |
Mar
(43) |
Apr
(38) |
May
(21) |
Jun
(51) |
Jul
(27) |
Aug
(12) |
Sep
(24) |
Oct
(19) |
Nov
(45) |
Dec
(21) |
| 2013 |
Jan
(59) |
Feb
(64) |
Mar
(63) |
Apr
(59) |
May
(74) |
Jun
(28) |
Jul
(28) |
Aug
(19) |
Sep
(26) |
Oct
(65) |
Nov
(24) |
Dec
(23) |
| 2014 |
Jan
(62) |
Feb
(34) |
Mar
(18) |
Apr
(24) |
May
(18) |
Jun
(21) |
Jul
(53) |
Aug
(22) |
Sep
(31) |
Oct
(22) |
Nov
(23) |
Dec
(30) |
| 2015 |
Jan
(29) |
Feb
(62) |
Mar
(58) |
Apr
(68) |
May
(53) |
Jun
(17) |
Jul
(17) |
Aug
(35) |
Sep
(88) |
Oct
(17) |
Nov
(71) |
Dec
(55) |
| 2016 |
Jan
(76) |
Feb
(105) |
Mar
(69) |
Apr
(31) |
May
(24) |
Jun
(26) |
Jul
(23) |
Aug
(42) |
Sep
(17) |
Oct
(31) |
Nov
(17) |
Dec
(10) |
| 2017 |
Jan
(13) |
Feb
(42) |
Mar
(19) |
Apr
(20) |
May
(90) |
Jun
(23) |
Jul
(38) |
Aug
(38) |
Sep
(8) |
Oct
|
Nov
(16) |
Dec
(11) |
| 2018 |
Jan
(3) |
Feb
(1) |
Mar
(38) |
Apr
(19) |
May
(117) |
Jun
(12) |
Jul
(27) |
Aug
(41) |
Sep
(8) |
Oct
(3) |
Nov
(2) |
Dec
(1) |
| 2019 |
Jan
(3) |
Feb
(16) |
Mar
(57) |
Apr
(13) |
May
(33) |
Jun
(11) |
Jul
(14) |
Aug
(2) |
Sep
(22) |
Oct
(6) |
Nov
(29) |
Dec
(11) |
| 2020 |
Jan
(43) |
Feb
(4) |
Mar
(2) |
Apr
(9) |
May
(63) |
Jun
(22) |
Jul
(30) |
Aug
(8) |
Sep
(14) |
Oct
(28) |
Nov
(10) |
Dec
(17) |
| 2021 |
Jan
(25) |
Feb
(6) |
Mar
(1) |
Apr
(3) |
May
(2) |
Jun
(32) |
Jul
(13) |
Aug
|
Sep
(32) |
Oct
|
Nov
(11) |
Dec
(38) |
| 2022 |
Jan
(26) |
Feb
(4) |
Mar
|
Apr
(18) |
May
(21) |
Jun
(22) |
Jul
(7) |
Aug
|
Sep
|
Oct
(3) |
Nov
(9) |
Dec
|
| 2023 |
Jan
(35) |
Feb
(63) |
Mar
(2) |
Apr
(19) |
May
(5) |
Jun
(9) |
Jul
|
Aug
(11) |
Sep
(19) |
Oct
(9) |
Nov
(4) |
Dec
|
| 2024 |
Jan
(4) |
Feb
(6) |
Mar
|
Apr
(5) |
May
(3) |
Jun
(1) |
Jul
(7) |
Aug
(6) |
Sep
(5) |
Oct
(4) |
Nov
|
Dec
(9) |
| 2025 |
Jan
(29) |
Feb
(4) |
Mar
(1) |
Apr
|
May
(10) |
Jun
(10) |
Jul
(15) |
Aug
(9) |
Sep
|
Oct
|
Nov
|
Dec
(2) |
|
From: John C. <yot...@gm...> - 2025-12-07 03:06:41
|
Thanks for excellent points, Don. I hope to have some excellent examples based on Aaron's .ply gaussian splats soon, but one problem seems to be that there's no explicit color names in those examples, except for opacity (I am currently only handling coordinates, and they don't look right). If anyone wants to map these properties to PointSets or PointProperties, that would be great! I do see from: Anatomy of a PLY file | Blurry Blog <https://www.useblurry.com/blog/anatomy-of-a-ply-file> that f_dc_0 ... f_dc_2, opacity map to RGBA, so I'll be moving to decode those colors. I have code which is set up for X,Y,Z and RGB which currently reads nx, ny, nz (normals? not documented on link). Any additional mapping to PointSets and PointProperties are welcome, I think that point normals were discussed some time ago on the list. This work will be done in my X3DJSONLD depot, because that's where my PLY to JSON (and DOM) code currently is. I'm developing a binary .ply reader, mostly for point sets. Other binary .ply examples are welcome. property float x property float y property float z property float nx property float ny property float nz property float f_dc_0 property float f_dc_1 property float f_dc_2 property float opacity property float scale_0 property float scale_1 property float scale_2 property float rot_0 property float rot_1 property float rot_2 property float rot_3 On Fri, Dec 5, 2025 at 6:19 PM Don Brutzman <don...@gm...> wrote: > Thanks for looking at this example, which was one of three that needed a > little updating. > > - X3D Example Archives: Basic, Points > - This directory demonstrates point-based rendering using PointSet and > PointProperties. Such techniques are an important option for rendering > scans and point clouds. > - https://www.web3d.org/x3d/content/examples/Basic/Points/ > > It is not clear that PointProperties is well supported by many browsers. > > Nevertheless PointProperties does have excellent support, as the following > composite-screenshot image showing 9 separate players demonstrates. > > - X3D Example Archives: Basic, Points, Archimedes Point Properties > - PointSet rendering of 3D scan with color applied per vertex, > renderable with PointProperties settings > - > https://www.web3d.org/x3d/content/examples/Basic/Points/ArchimedesPointPropertiesIndex.html > > > - ArchimedesPointProperties X3d Players Comparison > - > https://www.web3d.org/x3d/content/examples/Basic/Points/ArchimedesPointPropertiesX3dPlayersComparison.png > > Author Vince Marchetti also provided the following interesting example, > which emulates a spherical shape for points as sprites, using a 2D image > showing a simple rendered sphere. Cool hack! > > - X3D Example Archives: Basic, Points, Basic Point Sprites > - PointProperties test case emulating spherical point sprites by > displaying colored images of spheres. This model is suitable for X3Dv4 > implementation comparisons and conformance. > - > https://www.web3d.org/x3d/content/examples/Basic/Points/BasicPointSpritesIndex.html > > It is easy to think of a few more examples that might be added... > especially perhaps showing PointProperties effect present versus > missing, side by side. Contributions welcome. > > all the best, Don > -- > X3D Graphics, Maritime Robotics, Distributed Simulation > Relative Motion Consulting https://RelativeMotion.info > > > On Thu, Dec 4, 2025 at 8:46 PM John Carlson via x3d-public < > x3d...@we...> wrote: > >> It must be full moon, because this message popped up when I was looking >> for PointProperties. I wonder if this was ever solved? >> >> See attached console log: >> >> [image: image.png] >> >> On Fri, Nov 22, 2019 at 4:44 PM James Saunders <ja...@sa...> >> wrote: >> >>> HI John, >>> >>> Thanks for looking. >>> >>> One reason why the reason why the HTML file you have built does not work >>> is because it is failing to load d3-x3d: >>> In the html file header: >>> <script src="../../../dist/d3-x3d.js"></script> >>> Needs swapping for: >>> <script src=" >>> https://raw.githack.com/jamesleesaunders/d3-x3d/master/dist/d3-x3d.js >>> "></script> >>> >>> It also needs D3. >>> >>> Thanks anyway. All the best, >>> >>> Jim >>> >>> On Fri, Nov 22, 2019 at 4:54 AM <yot...@gm...> wrote: >>> >>>> I copied the DOM document from “Elements” into foo4.html and got the >>>> following: >>>> >>>> >>>> >>>> Uncaught TypeError: Cannot read property 'chart' of undefined >>>> >>>> >>>> >>>> I don’t know why the original code doesn’t show the same error, but >>>> here’s foo4.html attached. >>>> >>>> >>>> >>>> John >>>> >>>> >>>> >>>> Sent from Mail <https://go.microsoft.com/fwlink/?LinkId=550986> for >>>> Windows 10 >>>> >>>> >>>> >>>> *From: *yot...@gm... >>>> *Sent: *Thursday, November 21, 2019 10:39 PM >>>> *To: *James Saunders <ja...@sa...>; X3D Graphics public >>>> mailing list <x3d...@we...>; x3dom users mailing list >>>> <x3d...@li...> >>>> *Subject: *RE: [x3dom-users] PointProperties in X_ITE >>>> >>>> >>>> >>>> Your response is null???? >>>> >>>> >>>> >>>> See console. >>>> >>>> >>>> >>>> John >>>> >>>> >>>> >>>> Sent from Mail <https://go.microsoft.com/fwlink/?LinkId=550986> for >>>> Windows 10 >>>> >>>> >>>> >>>> *From: *James Saunders <ja...@sa...> >>>> *Sent: *Thursday, November 21, 2019 5:00 PM >>>> *To: *X3D Graphics public mailing list <x3d...@we...>; x3dom >>>> users mailing list <x3d...@li...> >>>> *Subject: *[x3dom-users] PointProperties in X_ITE >>>> >>>> >>>> >>>> Hi All, >>>> >>>> >>>> >>>> I appreciate the PointProperties node is a new proposal in v4 and at he >>>> moment it has not yet been implemented in x3dom. However I see this is >>>> implemented in x_ite ( >>>> http://create3000.de/users-guide/components/shape/pointproperties/). >>>> >>>> >>>> >>>> I am trying to use PointProperties to get larger particles on the >>>> following chart: >>>> >>>> >>>> https://raw.githack.com/jamesleesaunders/d3-x3d/ScatterPlot/examples/X_ITE/chart/ParticlePlot.html >>>> >>>> >>>> >>>> <Shape class="particles"> >>>> >>>> <Appearance> >>>> >>>> <PointProperties colorMode="POINT_COLOR" pointSizeMinValue="1" >>>> pointSizeMaxValue="5" pointSizeScaleFactor="100"></PointProperties> >>>> >>>> </Appearance> >>>> >>>> <PointSet> >>>> >>>> <Coordinate point="4.444444444444445 22.22222222222222 >>>> 17.77777777777778 ...."></coordinate> >>>> >>>> <Color color="0.8431 0.1882 0.1529 ...."></color> >>>> >>>> </PointSet> >>>> >>>> </Shape> >>>> >>>> >>>> >>>> But the points still only come out as single pixels? >>>> >>>> What am I doing wrong? >>>> >>>> I want to make the particles (points) larger. >>>> >>>> >>>> >>>> I can see PointProperties working here: >>>> >>>> >>>> https://www.web3d.org/x3d/content/examples/Basic/Points/ArchimedesPointPropertiesIndex.html >>>> >>>> >>>> >>>> Jim >>>> >>>> >>>> >>>> >>>> >>>> >>>> >>> _______________________________________________ >> x3d-public mailing list >> x3d...@we... >> http://web3d.org/mailman/listinfo/x3d-public_web3d.org >> > |
|
From: John C. <yot...@gm...> - 2025-12-05 04:46:01
|
It must be full moon, because this message popped up when I was looking for PointProperties. I wonder if this was ever solved? See attached console log: [image: image.png] On Fri, Nov 22, 2019 at 4:44 PM James Saunders <ja...@sa...> wrote: > HI John, > > Thanks for looking. > > One reason why the reason why the HTML file you have built does not work > is because it is failing to load d3-x3d: > In the html file header: > <script src="../../../dist/d3-x3d.js"></script> > Needs swapping for: > <script src=" > https://raw.githack.com/jamesleesaunders/d3-x3d/master/dist/d3-x3d.js > "></script> > > It also needs D3. > > Thanks anyway. All the best, > > Jim > > On Fri, Nov 22, 2019 at 4:54 AM <yot...@gm...> wrote: > >> I copied the DOM document from “Elements” into foo4.html and got the >> following: >> >> >> >> Uncaught TypeError: Cannot read property 'chart' of undefined >> >> >> >> I don’t know why the original code doesn’t show the same error, but >> here’s foo4.html attached. >> >> >> >> John >> >> >> >> Sent from Mail <https://go.microsoft.com/fwlink/?LinkId=550986> for >> Windows 10 >> >> >> >> *From: *yot...@gm... >> *Sent: *Thursday, November 21, 2019 10:39 PM >> *To: *James Saunders <ja...@sa...>; X3D Graphics public >> mailing list <x3d...@we...>; x3dom users mailing list >> <x3d...@li...> >> *Subject: *RE: [x3dom-users] PointProperties in X_ITE >> >> >> >> Your response is null???? >> >> >> >> See console. >> >> >> >> John >> >> >> >> Sent from Mail <https://go.microsoft.com/fwlink/?LinkId=550986> for >> Windows 10 >> >> >> >> *From: *James Saunders <ja...@sa...> >> *Sent: *Thursday, November 21, 2019 5:00 PM >> *To: *X3D Graphics public mailing list <x3d...@we...>; x3dom >> users mailing list <x3d...@li...> >> *Subject: *[x3dom-users] PointProperties in X_ITE >> >> >> >> Hi All, >> >> >> >> I appreciate the PointProperties node is a new proposal in v4 and at he >> moment it has not yet been implemented in x3dom. However I see this is >> implemented in x_ite ( >> http://create3000.de/users-guide/components/shape/pointproperties/). >> >> >> >> I am trying to use PointProperties to get larger particles on the >> following chart: >> >> >> https://raw.githack.com/jamesleesaunders/d3-x3d/ScatterPlot/examples/X_ITE/chart/ParticlePlot.html >> >> >> >> <Shape class="particles"> >> >> <Appearance> >> >> <PointProperties colorMode="POINT_COLOR" pointSizeMinValue="1" >> pointSizeMaxValue="5" pointSizeScaleFactor="100"></PointProperties> >> >> </Appearance> >> >> <PointSet> >> >> <Coordinate point="4.444444444444445 22.22222222222222 >> 17.77777777777778 ...."></coordinate> >> >> <Color color="0.8431 0.1882 0.1529 ...."></color> >> >> </PointSet> >> >> </Shape> >> >> >> >> But the points still only come out as single pixels? >> >> What am I doing wrong? >> >> I want to make the particles (points) larger. >> >> >> >> I can see PointProperties working here: >> >> >> https://www.web3d.org/x3d/content/examples/Basic/Points/ArchimedesPointPropertiesIndex.html >> >> >> >> Jim >> >> >> >> >> >> >> > |
|
From: Andreas P. <and...@gm...> - 2025-08-30 14:20:07
|
No need to check. My fork does not have additional work on Multitexture or MultitextureTransform. I think custom shaders can use multiple textures. It may be possible to add better support based on glTF texture support but not a priority. Andreas Plesch Waltham, MA 02453 On Fri, Aug 29, 2025, 11:20 PM John Carlson <yot...@gm...> wrote: > This is probably a question for Andreas Plesch. I know glTF is at least > partially supported. > > > Also see that I am cc’ing the X3DOM users mailing list. There’s a > developer list too. I guess they are still on sourceforge. > > Heres Andreas’ GitHub branch: > > https://github.com/andreasplesch/x3dom > > You can get to x3dom/x3dom from there. > > If you set the right x3d element attributes, you can see unimplemented > node, I think MultiTextureTransform.js would fit here? > https://github.com/andreasplesch/x3dom/tree/master/src/nodes/Texturing > > Maybe one of other .js files implements it? Download source and do a > folder search? > > UTSL! > > John > > On Fri, Aug 29, 2025 at 9:49 PM Bergstrom, Aaron via X3D-Ecosystem < > x3d...@we...> wrote: > >> How does X3DOM support MultiTextureTransform nodes? >> >> -- >> X3D-Ecosystem mailing list >> X3D...@we... >> http://web3d.org/mailman/listinfo/x3d-ecosystem_web3d.org >> > |
|
From: John C. <yot...@gm...> - 2025-08-30 03:29:44
|
You can also try Andreas’ X3DOM distribution, here: https://andreasplesch.github.io/x3dom/dist/ At least I think that’s it! Good Luck! Ultimately, we have to pull up our sleeves. If you ever get interested in Multi-user X_ITE and maybe Sunrize (I haven’t tried Sunrize yet), let’s do it! Or just try for an Unity or Unreal X3D plugin! But surely Castle Game Engine is better than anything C++? John On Fri, Aug 29, 2025 at 10:19 PM John Carlson <yot...@gm...> wrote: > This is probably a question for Andreas Plesch. I know glTF is at least > partially supported. > > > Also see that I am cc’ing the X3DOM users mailing list. There’s a > developer list too. I guess they are still on sourceforge. > > Heres Andreas’ GitHub branch: > > https://github.com/andreasplesch/x3dom > > You can get to x3dom/x3dom from there. > > If you set the right x3d element attributes, you can see unimplemented > node, I think MultiTextureTransform.js would fit here? > https://github.com/andreasplesch/x3dom/tree/master/src/nodes/Texturing > > Maybe one of other .js files implements it? Download source and do a > folder search? > > UTSL! > > John > > On Fri, Aug 29, 2025 at 9:49 PM Bergstrom, Aaron via X3D-Ecosystem < > x3d...@we...> wrote: > >> How does X3DOM support MultiTextureTransform nodes? >> >> -- >> X3D-Ecosystem mailing list >> X3D...@we... >> http://web3d.org/mailman/listinfo/x3d-ecosystem_web3d.org >> > |
|
From: John C. <yot...@gm...> - 2025-08-30 03:20:09
|
This is probably a question for Andreas Plesch. I know glTF is at least partially supported. Also see that I am cc’ing the X3DOM users mailing list. There’s a developer list too. I guess they are still on sourceforge. Heres Andreas’ GitHub branch: https://github.com/andreasplesch/x3dom You can get to x3dom/x3dom from there. If you set the right x3d element attributes, you can see unimplemented node, I think MultiTextureTransform.js would fit here? https://github.com/andreasplesch/x3dom/tree/master/src/nodes/Texturing Maybe one of other .js files implements it? Download source and do a folder search? UTSL! John On Fri, Aug 29, 2025 at 9:49 PM Bergstrom, Aaron via X3D-Ecosystem < x3d...@we...> wrote: > How does X3DOM support MultiTextureTransform nodes? > > -- > X3D-Ecosystem mailing list > X3D...@we... > http://web3d.org/mailman/listinfo/x3d-ecosystem_web3d.org > |
|
From: Andreas P. <and...@gm...> - 2025-08-08 05:47:13
|
On Thu, Aug 7, 2025 at 11:42 PM John Carlson <yot...@gm...> wrote: > Okay. I tried setting the magnfiicationFilter to FASTEST, then > NEAREST_PIXEL (for each .x3d file), and the latter had the best results, > but there's still some things to be desired. > These options are just instructions how the browser should fill in color between pixels when the texture is small. FASTEST could still mean different things to different browsers.but I think now usually means linear interpolation between vertices which on GPUs may be faster than the logic required by NEAREST. > Since <Environment> was not included in .json, iI switched to using .x3d. > X_ITE had no issues, but I'm guessing other validation tools will have > issues, I'm not sure. > Yes, Environment is a non-standard x3dom extension, a bit like browser settings. > > These two still have significant differences between X3DOM and X_ITE. I > haven't tested other browsers. > > > - indexedfaceset_pixeltexture_plus.x3d > - indexedfaceset_pixeltexture_whole.x3d > > > I see it. Not sure what is going on. https://www.web3d.org/x3d/content/examples/ConformanceNist/Geometry/IndexedFaceSet/empty_textureIndexIndex.html has similar differences with a jpg texture. It probably should not appear just green. are you saying put a magnficationFIlter as FASTEST for one, and > NEAREST_PIXEL on the other to make them match? > No, these are just the settings for the 'DEFAULT' field value. Matching values would be required for matching results, just like what you did. Andreas Thanks, > > John > > On Thu, Aug 7, 2025 at 9:05 PM Andreas Plesch <and...@gm...> > wrote: > >> Hi John, >> >> after some attempts, I could get the pixeltexture examples to load in >> both viewers. >> >> The difference is due to the 'DEFAULT' value of magnificationFilter in >> TextureProperties: >> https://www.web3d.org/documents/specifications/19775-1/V4.0/Part01/components/texturing.html#TextureProperties >> >> x3dom has the webgl default (I think 'FASTEST') and x_ite probably has >> "NEAREST_PIXEL" which was probably the traditional default. >> >> For a more specific prescription of desired rendering an author has to >> explicitly set magnificationFilter to a value other than 'DEFAULT'. >> >> Cheers, -Andreas >> >> PS: for better color correspondence, switch off gamma correction in x3dom >> with >> >> https://doc.x3dom.org/tutorials/lighting/gamma/index.html >> >> eg., >> >> <Environment id="gamma" gammaCorrectionDefault="none"></Environment> >> >> Cheers, -Andreas >> >> On Thu, Aug 7, 2025 at 9:16 PM John Carlson <yot...@gm...> wrote: >> >>> It occurred to me that you can pick up data files here: >>> https://coderextreme.net/X3DJSONLD/src/main/data/ >>> >>> Mouse over a link to get the filename, I think. >>> >>> I know it’s clunky. >>> >>> Thanks, >>> >>> John >>> >>> On Thu, Aug 7, 2025 at 7:59 PM John Carlson <yot...@gm...> wrote: >>> >>>> Please look at these examples on >>>> https://coderextreme.net/X3DJSONLD/src/main/html/main_viewer.html under >>>> NavigationInfo type menu at right. There’s a difference between X3DOM and >>>> X_ITE, but I don’t know which is correct yet. If needed, I can track down >>>> the .x3d files. They’re in this folder which is huge: >>>> https://github.com/coderextreme/X3DJSONLD/tree/master/src/main/data >>>> >>>> - >>>> - indexedfaceset_pixeltexture_entire.json >>>> - indexedfaceset_pixeltexture_part.json >>>> - indexedfaceset_pixeltexture_plus.json >>>> - indexedfaceset_pixeltexture_whole.json >>>> >>>> >>>> Thanks, >>>> >>>> John >>>> >>>> P.S.: if all else fails, I will attach them. >>>> >>> >> >> -- >> Andreas Plesch >> Waltham, MA 02453 >> > -- Andreas Plesch Waltham, MA 02453 |
|
From: John C. <yot...@gm...> - 2025-08-08 03:42:58
|
Okay. I tried setting the magnfiicationFilter to FASTEST, then NEAREST_PIXEL (for each .x3d file), and the latter had the best results, but there's still some things to be desired. Since <Environment> was not included in .json, iI switched to using .x3d. X_ITE had no issues, but I'm guessing other validation tools will have issues, I'm not sure. ' These two still have significant differences between X3DOM and X_ITE. I haven't tested other browsers. - indexedfaceset_pixeltexture_plus.x3d - indexedfaceset_pixeltexture_whole.x3d are you saying put a magnficationFIlter as FASTEST for one, and NEAREST_PIXEL on the other to make them match? Thanks, John On Thu, Aug 7, 2025 at 9:05 PM Andreas Plesch <and...@gm...> wrote: > Hi John, > > after some attempts, I could get the pixeltexture examples to load in both > viewers. > > The difference is due to the 'DEFAULT' value of magnificationFilter in > TextureProperties: > https://www.web3d.org/documents/specifications/19775-1/V4.0/Part01/components/texturing.html#TextureProperties > > x3dom has the webgl default (I think 'FASTEST') and x_ite probably has > "NEAREST_PIXEL" which was probably the traditional default. > > For a more specific prescription of desired rendering an author has to > explicitly set magnificationFilter to a value other than 'DEFAULT'. > > Cheers, -Andreas > > PS: for better color correspondence, switch off gamma correction in x3dom > with > > https://doc.x3dom.org/tutorials/lighting/gamma/index.html > > eg., > > <Environment id="gamma" gammaCorrectionDefault="none"></Environment> > > Cheers, -Andreas > > On Thu, Aug 7, 2025 at 9:16 PM John Carlson <yot...@gm...> wrote: > >> It occurred to me that you can pick up data files here: >> https://coderextreme.net/X3DJSONLD/src/main/data/ >> >> Mouse over a link to get the filename, I think. >> >> I know it’s clunky. >> >> Thanks, >> >> John >> >> On Thu, Aug 7, 2025 at 7:59 PM John Carlson <yot...@gm...> wrote: >> >>> Please look at these examples on >>> https://coderextreme.net/X3DJSONLD/src/main/html/main_viewer.html under >>> NavigationInfo type menu at right. There’s a difference between X3DOM and >>> X_ITE, but I don’t know which is correct yet. If needed, I can track down >>> the .x3d files. They’re in this folder which is huge: >>> https://github.com/coderextreme/X3DJSONLD/tree/master/src/main/data >>> >>> - >>> - indexedfaceset_pixeltexture_entire.json >>> - indexedfaceset_pixeltexture_part.json >>> - indexedfaceset_pixeltexture_plus.json >>> - indexedfaceset_pixeltexture_whole.json >>> >>> >>> Thanks, >>> >>> John >>> >>> P.S.: if all else fails, I will attach them. >>> >> > > -- > Andreas Plesch > Waltham, MA 02453 > |
|
From: John C. <yot...@gm...> - 2025-08-08 02:58:47
|
Oh, cool, I wasn’t aware one could set gamma correction with an Environment element. Good info! Is this a cross-browser feature yet? These are examples from the archives, I’ve just had them stashed for early testing, probably in 2017. I don’t know if any authors are in the files yet. I guess it’s time to separate myself from kinematics and get back to normal stuff. On Thu, Aug 7, 2025 at 9:05 PM Andreas Plesch <and...@gm...> wrote: > Hi John, > > after some attempts, I could get the pixeltexture examples to load in both > viewers. > > The difference is due to the 'DEFAULT' value of magnificationFilter in > TextureProperties: > https://www.web3d.org/documents/specifications/19775-1/V4.0/Part01/components/texturing.html#TextureProperties > > x3dom has the webgl default (I think 'FASTEST') and x_ite probably has > "NEAREST_PIXEL" which was probably the traditional default. > > For a more specific prescription of desired rendering an author has to > explicitly set magnificationFilter to a value other than 'DEFAULT'. > > Cheers, -Andreas > > PS: for better color correspondence, switch off gamma correction in x3dom > with > > https://doc.x3dom.org/tutorials/lighting/gamma/index.html > > eg., > > <Environment id="gamma" gammaCorrectionDefault="none"></Environment> > > Cheers, -Andreas > > On Thu, Aug 7, 2025 at 9:16 PM John Carlson <yot...@gm...> wrote: > >> It occurred to me that you can pick up data files here: >> https://coderextreme.net/X3DJSONLD/src/main/data/ >> >> Mouse over a link to get the filename, I think. >> >> I know it’s clunky. >> >> Thanks, >> >> John >> >> On Thu, Aug 7, 2025 at 7:59 PM John Carlson <yot...@gm...> wrote: >> >>> Please look at these examples on >>> https://coderextreme.net/X3DJSONLD/src/main/html/main_viewer.html under >>> NavigationInfo type menu at right. There’s a difference between X3DOM and >>> X_ITE, but I don’t know which is correct yet. If needed, I can track down >>> the .x3d files. They’re in this folder which is huge: >>> https://github.com/coderextreme/X3DJSONLD/tree/master/src/main/data >>> >>> - >>> - indexedfaceset_pixeltexture_entire.json >>> - indexedfaceset_pixeltexture_part.json >>> - indexedfaceset_pixeltexture_plus.json >>> - indexedfaceset_pixeltexture_whole.json >>> >>> >>> Thanks, >>> >>> John >>> >>> P.S.: if all else fails, I will attach them. >>> >> > > -- > Andreas Plesch > Waltham, MA 02453 > |
|
From: Andreas P. <and...@gm...> - 2025-08-08 02:05:47
|
Hi John, after some attempts, I could get the pixeltexture examples to load in both viewers. The difference is due to the 'DEFAULT' value of magnificationFilter in TextureProperties: https://www.web3d.org/documents/specifications/19775-1/V4.0/Part01/components/texturing.html#TextureProperties x3dom has the webgl default (I think 'FASTEST') and x_ite probably has "NEAREST_PIXEL" which was probably the traditional default. For a more specific prescription of desired rendering an author has to explicitly set magnificationFilter to a value other than 'DEFAULT'. Cheers, -Andreas PS: for better color correspondence, switch off gamma correction in x3dom with https://doc.x3dom.org/tutorials/lighting/gamma/index.html eg., <Environment id="gamma" gammaCorrectionDefault="none"></Environment> Cheers, -Andreas On Thu, Aug 7, 2025 at 9:16 PM John Carlson <yot...@gm...> wrote: > It occurred to me that you can pick up data files here: > https://coderextreme.net/X3DJSONLD/src/main/data/ > > Mouse over a link to get the filename, I think. > > I know it’s clunky. > > Thanks, > > John > > On Thu, Aug 7, 2025 at 7:59 PM John Carlson <yot...@gm...> wrote: > >> Please look at these examples on >> https://coderextreme.net/X3DJSONLD/src/main/html/main_viewer.html under >> NavigationInfo type menu at right. There’s a difference between X3DOM and >> X_ITE, but I don’t know which is correct yet. If needed, I can track down >> the .x3d files. They’re in this folder which is huge: >> https://github.com/coderextreme/X3DJSONLD/tree/master/src/main/data >> >> - >> - indexedfaceset_pixeltexture_entire.json >> - indexedfaceset_pixeltexture_part.json >> - indexedfaceset_pixeltexture_plus.json >> - indexedfaceset_pixeltexture_whole.json >> >> >> Thanks, >> >> John >> >> P.S.: if all else fails, I will attach them. >> > -- Andreas Plesch Waltham, MA 02453 |
|
From: John C. <yot...@gm...> - 2025-08-08 01:17:04
|
It occurred to me that you can pick up data files here: https://coderextreme.net/X3DJSONLD/src/main/data/ Mouse over a link to get the filename, I think. I know it’s clunky. Thanks, John On Thu, Aug 7, 2025 at 7:59 PM John Carlson <yot...@gm...> wrote: > Please look at these examples on > https://coderextreme.net/X3DJSONLD/src/main/html/main_viewer.html under > NavigationInfo type menu at right. There’s a difference between X3DOM and > X_ITE, but I don’t know which is correct yet. If needed, I can track down > the .x3d files. They’re in this folder which is huge: > https://github.com/coderextreme/X3DJSONLD/tree/master/src/main/data > > - > - indexedfaceset_pixeltexture_entire.json > - indexedfaceset_pixeltexture_part.json > - indexedfaceset_pixeltexture_plus.json > - indexedfaceset_pixeltexture_whole.json > > > Thanks, > > John > > P.S.: if all else fails, I will attach them. > |
|
From: John C. <yot...@gm...> - 2025-08-08 00:59:50
|
Please look at these examples on https://coderextreme.net/X3DJSONLD/src/main/html/main_viewer.html under NavigationInfo type menu at right. There’s a difference between X3DOM and X_ITE, but I don’t know which is correct yet. If needed, I can track down the .x3d files. They’re in this folder which is huge: https://github.com/coderextreme/X3DJSONLD/tree/master/src/main/data - - indexedfaceset_pixeltexture_entire.json - indexedfaceset_pixeltexture_part.json - indexedfaceset_pixeltexture_plus.json - indexedfaceset_pixeltexture_whole.json Thanks, John P.S.: if all else fails, I will attach them. |
|
From: John C. <yot...@gm...> - 2025-07-25 05:08:07
|
My examples work okay for the most part, understanding that I added an extra point to the spine. I tested the jsdelivr and x3dom.org “production” versions. I also only tested on my phone so far. Thanks for your work on this area, Andreas, maybe eventually I’ll have a pp3.x3d and pp3.json eventually where scripting is working in both X_ITE and X3DOM. On Thu, Jul 24, 2025 at 10:07 PM John Carlson <yot...@gm...> wrote: > I’ll probably test extrusions sometime tonight, the examples I have are > qq3 and pp3 (pp3 is more comprehensive, at this site: Be sure to select > X3DOM version for comparison. > > https://coderextreme.net/X3DJSONLD/src/main/html/main_viewer.html > > I plan to work on a phone version, there are caching issues and some > models cause a refresh, unfortunately, on iPhone. I believe the Mac > version can work appropriately. > > John > > On Thu, Jul 24, 2025 at 9:58 PM Andreas Plesch <and...@gm...> > wrote: > >> A new x3dom-dev version was released with Extrusion fixes, available at >> https://cdn.jsdelivr.net/gh/x3dom/x3dom-dev/dist/x3dom-full.js >> <https://cdn.jsdelivr.net/gh/x3dom/x3dom-dev/dist/x3dom.js> et al. >> >> jsdelivr also supports versioned links, by commit SHA hash. >> https://github.com/x3dom/x3dom-dev/commits/main/ lists all commits to >> the repository along with their SHA. For example, this latest version is >> also available at this fixed URL: >> >> >> https://cdn.jsdelivr.net/gh/x3dom/x3dom-dev@19a788e003f12f66d5ba2b16fab8614762ed6f42/dist/x3dom-full.js >> >> Have fun with x3dom ! >> >> -Andreas >> >> On Thu, Jul 10, 2025 at 1:14 AM Andreas Plesch <and...@gm...> >> wrote: >> >>> Please note that the download link for the dev version of x3dom has >>> migrated from x3dom.org/download/dev (not updated) to >>> >>> https://cdn.jsdelivr.net/gh/x3dom/x3dom-dev/dist/x3dom.js (preferred) >>> or >>> https://x3dom.github.io/x3dom-dev/dist/x3dom.js >>> >>> which is >>> automatically updated at >>> https://github.com/x3dom/x3dom-dev >>> for every merged PR at >>> https://github.com/x3dom/x3dom >>> >>> Have fun with x3dom ! >>> >>> Andreas >>> >> >> >> -- >> Andreas Plesch >> Waltham, MA 02453 >> _______________________________________________ >> X3dom-users mailing list >> X3d...@li... >> https://lists.sourceforge.net/lists/listinfo/x3dom-users >> > |
|
From: John C. <yot...@gm...> - 2025-07-25 03:07:55
|
I’ll probably test extrusions sometime tonight, the examples I have are qq3 and pp3 (pp3 is more comprehensive, at this site: Be sure to select X3DOM version for comparison. https://coderextreme.net/X3DJSONLD/src/main/html/main_viewer.html I plan to work on a phone version, there are caching issues and some models cause a refresh, unfortunately, on iPhone. John On Thu, Jul 24, 2025 at 9:58 PM Andreas Plesch <and...@gm...> wrote: > A new x3dom-dev version was released with Extrusion fixes, available at > https://cdn.jsdelivr.net/gh/x3dom/x3dom-dev/dist/x3dom-full.js > <https://cdn.jsdelivr.net/gh/x3dom/x3dom-dev/dist/x3dom.js> et al. > > jsdelivr also supports versioned links, by commit SHA hash. > https://github.com/x3dom/x3dom-dev/commits/main/ lists all commits to the > repository along with their SHA. For example, this latest version is also > available at this fixed URL: > > > https://cdn.jsdelivr.net/gh/x3dom/x3dom-dev@19a788e003f12f66d5ba2b16fab8614762ed6f42/dist/x3dom-full.js > > Have fun with x3dom ! > > -Andreas > > On Thu, Jul 10, 2025 at 1:14 AM Andreas Plesch <and...@gm...> > wrote: > >> Please note that the download link for the dev version of x3dom has >> migrated from x3dom.org/download/dev (not updated) to >> >> https://cdn.jsdelivr.net/gh/x3dom/x3dom-dev/dist/x3dom.js (preferred) >> or >> https://x3dom.github.io/x3dom-dev/dist/x3dom.js >> >> which is >> automatically updated at >> https://github.com/x3dom/x3dom-dev >> for every merged PR at >> https://github.com/x3dom/x3dom >> >> Have fun with x3dom ! >> >> Andreas >> > > > -- > Andreas Plesch > Waltham, MA 02453 > _______________________________________________ > X3dom-users mailing list > X3d...@li... > https://lists.sourceforge.net/lists/listinfo/x3dom-users > |
|
From: Andreas P. <and...@gm...> - 2025-07-25 02:57:43
|
A new x3dom-dev version was released with Extrusion fixes, available at https://cdn.jsdelivr.net/gh/x3dom/x3dom-dev/dist/x3dom-full.js <https://cdn.jsdelivr.net/gh/x3dom/x3dom-dev/dist/x3dom.js> et al. jsdelivr also supports versioned links, by commit SHA hash. https://github.com/x3dom/x3dom-dev/commits/main/ lists all commits to the repository along with their SHA. For example, this latest version is also available at this fixed URL: https://cdn.jsdelivr.net/gh/x3dom/x3dom-dev@19a788e003f12f66d5ba2b16fab8614762ed6f42/dist/x3dom-full.js Have fun with x3dom ! -Andreas On Thu, Jul 10, 2025 at 1:14 AM Andreas Plesch <and...@gm...> wrote: > Please note that the download link for the dev version of x3dom has > migrated from x3dom.org/download/dev (not updated) to > > https://cdn.jsdelivr.net/gh/x3dom/x3dom-dev/dist/x3dom.js (preferred) > or > https://x3dom.github.io/x3dom-dev/dist/x3dom.js > > which is > automatically updated at > https://github.com/x3dom/x3dom-dev > for every merged PR at > https://github.com/x3dom/x3dom > > Have fun with x3dom ! > > Andreas > -- Andreas Plesch Waltham, MA 02453 |
|
From: John C. <yot...@gm...> - 2025-07-17 23:11:30
|
If someone wants to upgrade to X3DOM, great! https://github.com/coderextreme/X3DJSONLD/blob/master/src/main/data/x3dconnectorProto.x3d |
|
From: John C. <yot...@gm...> - 2025-07-15 14:02:09
|
What are various X3DOM production links? I've got a pulldown to change X3DOM versions on my main_viewer.html. Currently, everything is development. Might as well provide all of them! Thanks, John On Sun, Jul 13, 2025 at 1:22 PM Don Brutzman via x3d-public < x3d...@we...> wrote: > Andreas writes on 10 JUL 2025: > >> I have deployed a new dev version. >> Please note that the download link for the dev version of x3dom has >> migrated from x3dom.org/download/dev (not updated) to >> https://cdn.jsdelivr.net/gh/x3dom/x3dom-dev/dist/x3dom.js (preferred) >> or >> https://x3dom.github.io/x3dom-dev/dist/x3dom.js >> which is >> automatically updated through >> https://github.com/x3dom/x3dom-dev >> for every merged PR at >> https://github.com/x3dom/x3dom >> The netlify link is obsolete. > > >> Andreas > > > Thanks for the alert. I am hoping to get the address and invocation > correct in our X3D Example Archives scenes by updating the conversion > stylesheet. > > - X3D Example Archives > - https://www.web3d.org/x3d/content/examples/X3dResources.html#Examples > - > https://sourceforge.net/p/x3d/code/HEAD/tree/www.web3d.org/x3d/stylesheets/X3dToX3domX_ITE.xslt > > The X3dToX3domX_ITE.xslt stylesheet produces the following header in these > examples: > > - X3D Example Archives: X3D4WA, X3D for Web Authors, Chapter 01 > Technical Overview, Hello World > - > https://www.web3d.org/x3d/content/examples/X3dForWebAuthors/Chapter01TechnicalOverview/HelloWorldIndex.html > - > https://www.web3d.org/x3d/content/examples/X3dForWebAuthors/Chapter01TechnicalOverview/HelloWorldX3dom.xhtml > > <!DOCTYPE html> > > <!-- =================================================================== > --> > > <!-- embedded X3D scene appears after html/head/script and style entries > --> > > <!-- =================================================================== > --> > > <html xmlns="http://www.w3.org/1999/xhtml"> > > <head> > > <title>Hello World!, HelloWorld.x3d (X3DOM)</title> > > <meta http-equiv="X-UA-Compatible" content="chrome=1,IE=edge"/> > > <meta http-equiv="Content-Type" content="text/html;charset=utf-8"/> > > <meta name="generator" > > content="https://www.web3d.org/x3d/stylesheets/X3dToX3domX_ITE.xslt"/> > > <script type="text/javascript" src=" > https://ajax.googleapis.com/ajax/libs/jquery/3.2.1/jquery.min.js"> > </script> > > <!-- Numbered X3DOM release versions: https://www.x3dom.org/download --> > > <!-- Developer X3DOM release version: https://www.x3dom.org/download/dev > --> > > <link rel="stylesheet" > > type="text/css" > > href="https://x3dom.org/download/dev/x3dom.css"/> > > <script type="text/javascript" > > src="https://x3dom.org/download/dev/x3dom-full.js"/> > > > Questions please, before I start a major rebuild: > > 1. *x3dom.js or x3dom-full.js ? (both look to be available)* > 2. *Same treatment for x3dom.css or is it no longer used?* > 3. *What is up-to-date guidance whenText node is included?* I have > > > - "X3DOM Text Example > The following scenes demonstrate the use of the text and fontsyle > nodes. You can also use web fonts, however on windows there is a glitch. > You have to use and display the font in your document before you can use > them in X3DOM." > - https://x3dom.org/x3dom/example/x3dom_text.html > > <meta name="warning" > > content="Webfonts must be loaded prior to using Text node in X3D scene... > see https://x3dom.org/x3dom/example/x3dom_text.html"/> > > <!-- X3DOM needs Web Fonts when an X3D Text node is included --> > > <!-- adapted from https://x3dom.org/x3dom/example/x3dom_text.html and > https://web.mit.edu/jmorzins/www/fonts.html --> > > <style type="text/css"> > > /* > ============================================================================= > */ > > @font-face { > > font-family: 'SERIF'; /* default original */ > > font-style: normal; > > font-weight: 700; > > src: local('Roman'), url('Roman.ttf') format('truetype'); > > } > > @font-face { > > font-family: 'SERIF'; /* default alternate */ > > font-style: normal; > > font-weight: 700; > > src: local('Times New Roman'), local('TimesNewRoman'), url('Times New > Roman.ttf') format('truetype'); > > } > > /* > ============================================================================= > */ > > @font-face { > > font-family: 'SANS'; /* default original */ > > font-style: normal; > > font-weight: 400; > > src: local('Arial'), url('Arial.ttf') format('truetype'); > > } > > @font-face { > > font-family: 'SANS'; /* default alternate */ > > font-style: normal; > > font-weight: 400; > > src: local('Helvetica'), url('Helvetica.ttf') format('truetype'); > > } > > /* > ============================================================================= > */ > > @font-face { > > font-family: 'TYPEWRITER'; /* default original */ > > font-style: normal; > > font-weight: 900; > > src: local('Courier'), url('Courier.ttf') format('truetype'); > > } > > @font-face { > > font-family: 'TYPEWRITER'; /* default alternate */ > > font-style: normal; > > font-weight: 900; > > src: local('Courier New'), url('Courier New.ttf') format('truetype'); > > } > > /* > ============================================================================= > */ > > </style> > > <style type="text/css" media="screen, print"> > > .webfont { font-size:200%; font-family:'TYPEWRITER'; color:green;} /* > Conversion TODO font families: SANS SERIF TYPEWRITER */ > > </style> > > and > > *4. Is the following still the best up-to-date list of supported nodes?* > > https://andreasplesch.github.io/x3dom/dist/doc/author/nodes.html > > P.S. node wish list: IndexedTriangleFanSet, Script > > Thanks in advance for all improvements to these invocations, and thanks as > ever for ongoing progress with X3DOM! > > all the best, Don > _______________________________________________ > x3d-public mailing list > x3d...@we... > http://web3d.org/mailman/listinfo/x3d-public_web3d.org > |
|
From: Andreas P. <and...@gm...> - 2025-07-14 03:45:39
|
Answers below. On Sun, Jul 13, 2025 at 2:21 PM Don Brutzman <don...@gm...> wrote: > Andreas writes on 10 JUL 2025: > >> I have deployed a new dev version. >> Please note that the download link for the dev version of x3dom has >> migrated from x3dom.org/download/dev (not updated) to >> https://cdn.jsdelivr.net/gh/x3dom/x3dom-dev/dist/x3dom.js (preferred) >> or >> https://x3dom.github.io/x3dom-dev/dist/x3dom.js >> which is >> automatically updated through >> https://github.com/x3dom/x3dom-dev >> for every merged PR at >> https://github.com/x3dom/x3dom >> The netlify link is obsolete. > > >> Andreas > > > Thanks for the alert. I am hoping to get the address and invocation > correct in our X3D Example Archives scenes by updating the conversion > stylesheet. > > - X3D Example Archives > - https://www.web3d.org/x3d/content/examples/X3dResources.html#Examples > - > https://sourceforge.net/p/x3d/code/HEAD/tree/www.web3d.org/x3d/stylesheets/X3dToX3domX_ITE.xslt > > The X3dToX3domX_ITE.xslt stylesheet produces the following header in these > examples: > > - X3D Example Archives: X3D4WA, X3D for Web Authors, Chapter 01 > Technical Overview, Hello World > - > https://www.web3d.org/x3d/content/examples/X3dForWebAuthors/Chapter01TechnicalOverview/HelloWorldIndex.html > - > https://www.web3d.org/x3d/content/examples/X3dForWebAuthors/Chapter01TechnicalOverview/HelloWorldX3dom.xhtml > > <!DOCTYPE html> > > <!-- =================================================================== > --> > > <!-- embedded X3D scene appears after html/head/script and style entries > --> > > <!-- =================================================================== > --> > > <html xmlns="http://www.w3.org/1999/xhtml"> > > <head> > > <title>Hello World!, HelloWorld.x3d (X3DOM)</title> > > <meta http-equiv="X-UA-Compatible" content="chrome=1,IE=edge"/> > > <meta http-equiv="Content-Type" content="text/html;charset=utf-8"/> > > <meta name="generator" > > content="https://www.web3d.org/x3d/stylesheets/X3dToX3domX_ITE.xslt"/> > > <script type="text/javascript" src=" > https://ajax.googleapis.com/ajax/libs/jquery/3.2.1/jquery.min.js"> > </script> > > <!-- Numbered X3DOM release versions: https://www.x3dom.org/download --> > > <!-- Developer X3DOM release version: https://www.x3dom.org/download/dev > --> > > <link rel="stylesheet" > > type="text/css" > > href="https://x3dom.org/download/dev/x3dom.css"/> > > <script type="text/javascript" > > src="https://x3dom.org/download/dev/x3dom-full.js"/> > > > Questions please, before I start a major rebuild: > > 1. *x3dom.js or x3dom-full.js ? (both look to be available)* > > x3dom-full.js > > 1. *Same treatment for x3dom.css or is it no longer used?* > > Yes, same treatment. It is still used. > > 1. *What is up-to-date guidance whenText node is included?* I have > > > - "X3DOM Text Example > The following scenes demonstrate the use of the text and fontsyle > nodes. You can also use web fonts, however on windows there is a glitch. > You have to use and display the font in your document before you can use > them in X3DOM." > - https://x3dom.org/x3dom/example/x3dom_text.html > > <meta name="warning" > > content="Webfonts must be loaded prior to using Text node in X3D scene... > see https://x3dom.org/x3dom/example/x3dom_text.html"/> > > <!-- X3DOM needs Web Fonts when an X3D Text node is included --> > > <!-- adapted from https://x3dom.org/x3dom/example/x3dom_text.html and > https://web.mit.edu/jmorzins/www/fonts.html --> > > <style type="text/css"> > > /* > ============================================================================= > */ > > @font-face { > > font-family: 'SERIF'; /* default original */ > > font-style: normal; > > font-weight: 700; > > src: local('Roman'), url('Roman.ttf') format('truetype'); > > } > > @font-face { > > font-family: 'SERIF'; /* default alternate */ > > font-style: normal; > > font-weight: 700; > > src: local('Times New Roman'), local('TimesNewRoman'), url('Times New > Roman.ttf') format('truetype'); > > } > > /* > ============================================================================= > */ > > @font-face { > > font-family: 'SANS'; /* default original */ > > font-style: normal; > > font-weight: 400; > > src: local('Arial'), url('Arial.ttf') format('truetype'); > > } > > @font-face { > > font-family: 'SANS'; /* default alternate */ > > font-style: normal; > > font-weight: 400; > > src: local('Helvetica'), url('Helvetica.ttf') format('truetype'); > > } > > /* > ============================================================================= > */ > > @font-face { > > font-family: 'TYPEWRITER'; /* default original */ > > font-style: normal; > > font-weight: 900; > > src: local('Courier'), url('Courier.ttf') format('truetype'); > > } > > @font-face { > > font-family: 'TYPEWRITER'; /* default alternate */ > > font-style: normal; > > font-weight: 900; > > src: local('Courier New'), url('Courier New.ttf') format('truetype'); > > } > > /* > ============================================================================= > */ > > </style> > > <style type="text/css" media="screen, print"> > > .webfont { font-size:200%; font-family:'TYPEWRITER'; color:green;} /* > Conversion TODO font families: SANS SERIF TYPEWRITER */ > > </style> > > I think this guidance still applies for custom font families if a FontLibrary node is not used. FontLibrary font loading does not require this css. Also, all basic X3D font families do not require css. https://github.com/x3dom/x3dom/blob/master/test/functional/fonts.html has examples. > and > > *4. Is the following still the best up-to-date list of supported nodes?* > > https://andreasplesch.github.io/x3dom/dist/doc/author/nodes.html > > P.S. node wish list: IndexedTriangleFanSet, Script > > https://x3dom.github.io/x3dom-dev/dist/doc would be the best source for up to date documentation on supported nodes with dev releases as it is built and deployed along with the library. Thanks in advance for all improvements to these invocations, and thanks as > ever for ongoing progress with X3DOM! > > all the best, Don > All the best, Andreas -- Andreas Plesch Waltham, MA 02453 |
|
From: Andreas P. <and...@gm...> - 2025-07-10 05:15:01
|
Please note that the download link for the dev version of x3dom has migrated from x3dom.org/download/dev (not updated) to https://cdn.jsdelivr.net/gh/x3dom/x3dom-dev/dist/x3dom.js (preferred) or https://x3dom.github.io/x3dom-dev/dist/x3dom.js which is automatically updated at https://github.com/x3dom/x3dom-dev for every merged PR at https://github.com/x3dom/x3dom Have fun with x3dom ! Andreas |
|
From: John C. <yot...@gm...> - 2025-07-06 22:58:46
|
Apologies, the link behind the text was wrong. I confirmed that Y-axis extrusions works. Here’s the full file: https://github.com/coderextreme/X3DJSONLD/blob/master/src/main/data/pp3.json I will make changes, and hopefully I won’t run into trouble. I realize this example has Scripts, AFAIK, and won’t interact properly in X3DOM. That wasn’t why I created another example so the issue could be focused on. There’s no need to work on this version, please apply any work to x3dom. (Full text) { "X3D": { "encoding":"UTF-8", "@profile":"Immersive", "@version":"4.0", "@xsd:noNamespaceSchemaLocation":" https://www.web3d.org/specifications/x3d-4.0.xsd", "JSON schema":" https://www.web3d.org/specifications/x3d-4.0-JSONSchema.autogenerated.json", "head": { "meta": [ { "@name":"title", "@content":"pp3.x3d" }, { "@name":"creator", "@content":"John Carlson" }, { "@name":"translator", "@content":"John Carlson" }, { "@name":"created", "@content":"5 May 2015" }, { "@name":"modified", "@content":"23 Dec 2022" }, { "@name":"description", "@content":"A process pipeline between three spheres (try typing on spheres and blue" }, { "@name":"identifier", "@content":"https://coderextreme.net/x3d/pp3.x3d" }, { "@name":"generator", "@content":"manual" }, { "@name":"translated", "@content":"26 June 2025" }, { "@name":"generator", "@content":"X3dToJson.xslt, https://www.web3d.org/x3d/stylesheets/X3dToJson.html" }, { "@name":"reference", "@content":"X3D JSON encoding: https://www.web3d.org/wiki/index.php/X3D_JSON_Encoding" } ] }, "Scene": { "-children":[ { "ProtoDeclare": { "@name":"Process", "ProtoBody": { "-children":[ { "Group": { "-children":[ { "#comment":"left" }, { "Transform": { "@scale":[0.5,0.5,0.5], "-children":[ { "Shape": { "-appearance": { "Appearance": { "-material": { "Material": { "@diffuseColor":[0.7,1,0], "@transparency":0.5 } } } }, "-geometry": { "Extrusion": { "@creaseAngle":0.785, "@crossSection":[1,0,0.92,-0.38,0.71,-0.71,0.38,-0.92,0,-1,-0.38,-0.92,-0.71,-0.71,-0.92,-0.38,-1,0,-0.92,0.38,-0.71,0.71,-0.38,0.92,0,1,0.38,0.92,0.71,0.71,0.92,0.38,1,0], "@spine":[-2.5,0,0,-1.5,0,0] } } } }, { "#comment":"<Transform translation=\"-2.5 0 0\"> <Shape> <Text DEF=\"LeftString\" string='\"l\"'/> </Shape> </Transform> <StringSensor DEF=\"LeftSensor\" enabled=\"false\"/> <TouchSensor DEF=\"LeftTouch\" enabled=\"true\"/>" } ] } }, { "#comment":"right" }, { "Transform": { "@scale":[0.5,0.5,0.5], "-children":[ { "Shape": { "-appearance": { "Appearance": { "-material": { "Material": { "@diffuseColor":[0,0.7,1], "@transparency":0.5 } } } }, "-geometry": { "Extrusion": { "@creaseAngle":0.785, "@crossSection":[1,0,0.92,-0.38,0.71,-0.71,0.38,-0.92,0,-1,-0.38,-0.92,-0.71,-0.71,-0.92,-0.38,-1,0,-0.92,0.38,-0.71,0.71,-0.38,0.92,0,1,0.38,0.92,0.71,0.71,0.92,0.38,1,0], "@spine":[1.5,0,0,2.5,0,0] } } } }, { "Transform": { "@translation":[2,0,0], "-children":[ { "Shape": { "-appearance": { "Appearance": { "-material": { "Material": { "@DEF":"MaterialLightBlue", "@diffuseColor":[1,1,1] } } } }, "-geometry": { "Text": { "@DEF":"RightString", "@string":["r"] } } } } ] } }, { "StringSensor": { "@DEF":"RightSensor", "@enabled":false } }, { "TouchSensor": { "@description":"touch to activate", "@DEF":"RightTouch" } } ] } }, { "#comment":"up" }, { "Transform": { "@scale":[0.5,0.5,0.5], "-children":[ { "Shape": { "-appearance": { "Appearance": { "-material": { "Material": { "@diffuseColor":[0,0.7,1], "@transparency":0.5 } } } }, "-geometry": { "Extrusion": { "@creaseAngle":0.785, "@crossSection":[1,0,0.92,-0.38,0.71,-0.71,0.38,-0.92,0,-1,-0.38,-0.92,-0.71,-0.71,-0.92,-0.38,-1,0,-0.92,0.38,-0.71,0.71,-0.38,0.92,0,1,0.38,0.92,0.71,0.71,0.92,0.38,1,0], "@spine":[0,1.5,0,0,2.5,0] } } } }, { "Transform": { "@translation":[-0.5,2,0], "-children":[ { "Shape": { "-appearance": { "Appearance": { "-material": { "Material": { "@USE":"MaterialLightBlue" } } } }, "-geometry": { "Text": { "@DEF":"UpString", "@string":["u"] } } } } ] } }, { "StringSensor": { "@DEF":"UpSensor", "@enabled":false } }, { "TouchSensor": { "@description":"touch to activate", "@DEF":"UpTouch" } } ] } }, { "#comment":"down" }, { "Transform": { "@scale":[0.5,0.5,0.5], "-children":[ { "Shape": { "-appearance": { "Appearance": { "-material": { "Material": { "@diffuseColor":[0.7,1,0], "@transparency":0.5 } } } }, "-geometry": { "Extrusion": { "@creaseAngle":0.785, "@crossSection":[1,0,0.92,-0.38,0.71,-0.71,0.38,-0.92,0,-1,-0.38,-0.92,-0.71,-0.71,-0.92,-0.38,-1,0,-0.92,0.38,-0.71,0.71,-0.38,0.92,0,1,0.38,0.92,0.71,0.71,0.92,0.38,1,0], "@spine":[0,-2.5,0,0,-1.5,0] } } } }, { "#comment":"<Transform translation=\"-0.5 -2.5 0\"> <Shape> <Text DEF=\"DownString\" string='\"d\"'/> </Shape> </Transform> <StringSensor DEF=\"DownSensor\" enabled=\"false\"/> <TouchSensor description='touch to activate' DEF=\"DownTouch\" enabled=\"true\"/>" } ] } }, { "#comment":"center" }, { "Transform": { "-children":[ { "Shape": { "-appearance": { "Appearance": { "-material": { "Material": { "@diffuseColor":[1,0,0.7] } } } }, "-geometry": { "Sphere": { } } } }, { "Transform": { "@scale":[0.5,0.5,0.5], "@translation":[-0.5,0,1], "-children":[ { "Shape": { "-appearance": { "Appearance": { "-material": { "Material": { "@USE":"MaterialLightBlue" } } } }, "-geometry": { "Text": { "@DEF":"CenterString" } } } } ] } }, { "StringSensor": { "@DEF":"CenterSensor", "@enabled":false } }, { "TouchSensor": { "@description":"touch to activate", "@DEF":"CenterTouch" } } ] } } ] } }, { "Script": { "@DEF":"RightSingleToMultiString", "field": [ { "@name":"set_rightstring", "@accessType":"inputOnly", "@type":"SFString" }, { "@name":"rightlines", "@accessType":"outputOnly", "@type":"MFString" } ], "#sourceCode":[ "", "ecmascript:", "", "function initialize() {", "\trightlines = new MFString(\"\");", "}", "", "function set_rightstring(rightstr) {", "\trightlines = new MFString(rightstr);", "}", "" ] } }, { "Script": { "@DEF":"UpSingleToMultiString", "field": [ { "@name":"set_upstring", "@accessType":"inputOnly", "@type":"SFString" }, { "@name":"uplines", "@accessType":"outputOnly", "@type":"MFString" } ], "#sourceCode":[ "", "ecmascript:", "", "function initialize() {", "\tuplines = new MFString(\"\");", "}", "", "function set_upstring(upstr) {", "\tuplines = new MFString(upstr);", "}", "" ] } }, { "Script": { "@DEF":"CenterSingleToMultiString", "field": [ { "@name":"set_centerstring", "@accessType":"inputOnly", "@type":"SFString" }, { "@name":"centerlines", "@accessType":"outputOnly", "@type":"MFString" } ], "#sourceCode":[ "", "ecmascript:", "", "function initialize() {", "\tcenterlines = new MFString(\"\");", "}", "", "function set_centerstring(centerstr) {", "\tcenterlines = new MFString(centerstr);", "}", "" ] } }, { "ROUTE": { "@fromField":"enteredText", "@fromNode":"CenterSensor", "@toField":"set_centerstring", "@toNode":"CenterSingleToMultiString" } }, { "ROUTE": { "@fromField":"centerlines", "@fromNode":"CenterSingleToMultiString", "@toField":"set_string", "@toNode":"CenterString" } }, { "ROUTE": { "@fromField":"isOver", "@fromNode":"CenterTouch", "@toField":"set_enabled", "@toNode":"CenterSensor" } }, { "ROUTE": { "@fromField":"enteredText", "@fromNode":"RightSensor", "@toField":"set_rightstring", "@toNode":"RightSingleToMultiString" } }, { "ROUTE": { "@fromField":"rightlines", "@fromNode":"RightSingleToMultiString", "@toField":"set_string", "@toNode":"RightString" } }, { "ROUTE": { "@fromField":"isOver", "@fromNode":"RightTouch", "@toField":"set_enabled", "@toNode":"RightSensor" } }, { "ROUTE": { "@fromField":"enteredText", "@fromNode":"UpSensor", "@toField":"set_upstring", "@toNode":"UpSingleToMultiString" } }, { "ROUTE": { "@fromField":"uplines", "@fromNode":"UpSingleToMultiString", "@toField":"set_string", "@toNode":"UpString" } }, { "ROUTE": { "@fromField":"isOver", "@fromNode":"UpTouch", "@toField":"set_enabled", "@toNode":"UpSensor" } } ] } } }, { "NavigationInfo": { } }, { "Viewpoint": { "@description":"Process pipes", "@orientation":[1,0,0,-0.4], "@position":[0,5,12] } }, { "Transform": { "@translation":[0,-2.5,0], "-children":[ { "ProtoInstance": { "@name":"Process" } } ] } }, { "Transform": { "-children":[ { "ProtoInstance": { "@name":"Process" } } ] } }, { "Transform": { "@translation":[0,2.5,0], "-children":[ { "ProtoInstance": { "@name":"Process" } } ] } } ] } } } |
|
From: John C. <yot...@gm...> - 2025-07-06 04:51:29
|
It seems like X3DOM doesn’t do extrusion properly, at least according to successful renderings in other browsers. This is a long term issue, mentioned several times. This is one reason I don’t use X3DOM on a more regular basis. So I tried converting my extrusion to PLY, and things are even worse. I need: 1) a way to render extrusions properly in X3DOM. 2) a way to tessellate X3D XML/JSON Extrusions to PLY. I will put this on a feature request. John |
|
From: John C. <yot...@gm...> - 2025-07-03 07:18:16
|
I am adding tessellattion to my project, particularly converting X3D JSON
to PLY.
Here's a picture of a sphere in X3DOM (rubk.json or rubik.x3d converted to
PLY, then back to XML or JSON for viewing in X3DOM):
[image: image.png]
So this might be the source of the split in my flowers code? which takes a
Sphere, and manipulates the surface by offsetting the points of the surface
with a shader.
Here's my current Gemini Pro 2.5 tessellation code (perhaps derived from
Three.js or X3DOM? I haven't looked):
function tessellateSphere(node, options) { /* ... (Unchanged) ... */
const r = node['@radius'] ? parseFloat(node['@radius']) : 1;
const sub = options.subdivisions || 24; const verts=[], faces=[];
for (let j=0;j<=sub;j++){let
aj=j*Math.PI/sub,sj=Math.sin(aj),cj=Math.cos(aj); for(let
i=0;i<=sub;i++){let ai=i*2*Math.PI/sub,si=Math.sin(ai),ci=Math.cos(ai);
verts.push([r*si*sj,r*cj,r*ci*sj]);}}
for(let j=0;j<sub;j++){for(let i=0;i<sub;i++){let
p1=j*(sub+1)+i,p2=p1+1,p3=(j+1)*(sub+1)+i,p4=p3+1; faces.push([p1,p2,p4]);
faces.push([p1,p4,p3]);}}
return { vertices: verts, faces: faces };
}
Any better tessellation welcome!
I'm going to ask Claude for better code.
John
|
42 messages has been excluded from this view by a project administrator.
