[x3d-public] RawKee - PhysicalMaterial Implementation

[Bergstrom, Aaron]

All,

If the process outlined on this web page matches up with the PhysicalMaterial node, then I don't see much of a problem grabbing this data and prepping it for X3D export.
https://www.soft8soft.com/docs/manual/en/maya/GLTF-Materials.html

Aaron

From: x3d-public <x3d-public-bounces at web3d.org> On Behalf Of Bergstrom, Aaron via x3d-public
Sent: Tuesday, January 21, 2025 1:42 PM
To: Extensible 3D (X3D) Graphics public discussion <x3d-public at web3d.org>
Cc: Bergstrom, Aaron <aaron.bergstrom at und.edu>
Subject: [x3d-public] RawKee - PhysicalMaterial Implementation

Michalis and I chatted a bit this morning (my time) about extracting shader info from Maya.

I will probably implement three mechanisms for getting shader info from RawKee Python:

  1.  Interpreted glTF Shaders
The more I thought about I, the more I think that it's highly likely that Maya already supports a PhysicalMaterial style shader because of it's support for glTF. If that's the case, I'll dig up the info and interpret such shaders in a manner appropriate for X3D export. However, if by chance this is not the case, I will write custom Maya ShaderEngine and Shader Nodes corresponding to an X3D Appearance node with "blending", and PhysicalMaterial node. If I end up having to do this, I might need some math help from the community in order to implement the "compute" functions of these two custom Maya nodes. Though I don't see this being a lot of work (in the grand scheme of things) either way.
  2.  Traditional Way
Aka - the way I previously implemented it for the RawKee C++ version, which is mostly just building an appearance using a standard phong/lambert/materials and a stack of MultiTexture/MultiTextureTransform/MultiTextureCoordinate nodes. Call it VRML97-style with an X3D MultiTexture upgrade and a bit of 2008 Aaron's understanding of Normal/Bump Maps.
  3.  GLSL Shaders
Maya's ShaderFX GUI allows ShaderFX nodes constructed by Maya content developers/artists to be exported out as GLSL code. I'll just need to do some I/O trickery to properly capture and format this code at export. This would likely take the most work since packaged shaders are implemented differently by different X3D viewers, and thus, be the lowest priority.

Aaron
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://web3d.org/pipermail/x3d-public_web3d.org/attachments/20250121/c5b2a1ef/attachment.html>