[x3d-public] X3DOM vs X_ITE? Browser bake-off, round 1

[Andreas Plesch]

On Thu, Aug 7, 2025 at 11:42 PM John Carlson <yottzumm at gmail.com> 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 <andreasplesch at gmail.com>
> 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 <yottzumm at gmail.com> 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 <yottzumm at gmail.com> 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
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://web3d.org/pipermail/x3d-public_web3d.org/attachments/20250808/5e3ad470/attachment.html>