[X3D-Ecosystem] X_ITE vs X3DOM - Missing Texture

[vmarchetti at kshell.com]

Aaron


X3DOM support physical based rendering through the PhysicalMaterial https://doc.x3dom.org/developer/x3dom/nodeTypes/PhysicalMaterial.html node. That was the implementation that spurred the Consortium to add PBR to the standard.

Vince


> On Mar 11, 2025, at 10:19 PM, Bergstrom, Aaron <aaron.bergstrom at und.edu> wrote:
> 
> Vince,
> 
> Thanks for getting back to me.
> 
> I just took a look at the X3DOM documentation, and it looks like it doesn't support X3D 4.0, which I'm sure everyone else here probably knows. I'm still playing a bit of catch up, I guess.
> 
> According to the X3DOM documentation, the Material node does not contain any texture fields.
> https://doc.x3dom.org/developer/x3dom/nodeTypes/Material.html
> 
> I stored the texture in the diffuseTexture field of the Material node, and not the 'texture' field of the Appearance node.
> 
> I'm re-evaluating the process for exporting for X3DOM.
> 
> Thanks,
> 
> Aaron
> 
> -----Original Message-----
> From: X3D-Ecosystem <x3d-ecosystem-bounces at web3d.org> On Behalf Of Vincent Marchetti via X3D-Ecosystem
> Sent: Tuesday, March 11, 2025 5:19 PM
> To: X3D Ecosystem public discussion <x3d-ecosystem at web3d.org>
> Cc: Vincent Marchetti <vmarchetti at kshell.com>
> Subject: Re: [X3D-Ecosystem] X_ITE vs X3DOM - Missing Texture
> 
> Aaron
> 
> I believe that X3DOM does not traverse the "backup" urls that are included in the TextureImage url field. 
> I see from the x3d file at https://vr.csgrid.org/x3dom/swordtest.x3d that you have supplied 3 urls.
> I could not determine from your bug description which image files would be accessible in your scenarios.
> 
> A test could be to rearrange your url field in the x3d file ImageTexture node so that the https:// protocol url is first, and ensure that the image file is accessible even under CORS restrictions -- use https://cors-test.codehappy.dev/ to check this.
> 
> Vince
> 
> 
>> On Mar 11, 2025, at 4:31 PM, Bergstrom, Aaron via X3D-Ecosystem <x3d-ecosystem at web3d.org> wrote:
>> 
>> Can anyone give me feedback on why my texture does not appear in X3DOM?
>> 
>> I’ve exported the same 3D sword model from Maya using RawKee, and put them both online.
>> 
>> The straight up X3D model can be viewed here using X_ITE:
>> https://vr.csgrid.org/x_ite/x_ite.html
>> 
>> The version of the X3D that is embedded in HTML using X3DOM can be viewed here:
>> https://vr.csgrid.org/x3dom/swordtest.html
>> 
>> A version that uses an inline node using X3DOM can be found here:
>> https://vr.csgrid.org/x3dom/swordtest2.html
>> 
>> The ‘Inline’ node in ‘swordtest2.html’ points to the same ‘swordtest.x3d’ file that the ‘x_ite.html’ file points to.
>> 
>> The X3D part of the code is identical as far as I can tell, but while the ImageTexture is displayed as expected using X_ITE, it is missing from the model when using X3DOM 1.8.3.
>> 
>> Can anyone tell me why the texture is missing?
>> 
>> A bit more info…
>> 
>> I get the same results whether using Chrome, Firefox, or Edge.
>> 
>> The content found on x3dom.org works just fine.
>> 
>> I tried using “https://www.x3dom.org/download/x3dom.js” and “https://www.x3dom.org/download/x3dom.css” instead of local versions of those packages, and the texture is still missing.
>> 
>> The textures are missing whether I open the HTML file to my browser from my local file system, or whether I open the HTML file from a URL.
>> 
>> And the PNG file is viewable if I visit its URL directly.
>> 
>> Any feedback is welcome.
>> 
>> Thanks,
>> 
>> Aaron
>> -- 
>> X3D-Ecosystem mailing list
>> X3D-Ecosystem at web3d.org
>> http://web3d.org/mailman/listinfo/x3d-ecosystem_web3d.org
> 
> 
> -- 
> X3D-Ecosystem mailing list
> X3D-Ecosystem at web3d.org
> http://web3d.org/mailman/listinfo/x3d-ecosystem_web3d.org

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://web3d.org/pipermail/x3d-ecosystem_web3d.org/attachments/20250312/299ce88c/attachment.html>