111–120 of 271 posts
Does anybody know if the Blender project is involved / working towards this in any capacity?
Earlier quoted context omitted.
Then it sounds like AI.
Stable Diffusion isn't a familiar term outside a very niche audience. Probably over 50% of the earth's population is familiar with checking 'USD' exchange rates.
This is pretty neat to see Apple involved in a standard. They don't like to back everything that comes along. What is very interesting though, is that Meta isn't involved. Maybe because they're backing another horse, namely OpenXR [0]. [0] https://www.khronos.org/openxr/
Why have they created yet another alliance, isn't Khronos group which standardizes similar things(APIs, 3d model standards such as GlTF etc) enough?
Unity and Epic seem like two glaringly omissions from this.
Seen Autodesk here, which might - or might not - mean that the standard is also applicable for 3D engineering artifacts. However I see no explicit mention of this in the article by the link. Can this standard be well used for, say, designing a model for a 3D printer?
I suspect, but have no evidence, that it's the Maya side of AutoDesk
Does anybody know if the Blender project is involved / working towards this in any capacity?
Odd to see Nvidia and Apple working together on anything
I'm more wondering where AMD is in this. "Open" isn't very open without all the major GPU players involved.
https://www.amd.com/en/technologies/radeon-prorender ("A Pixar® USD™ Hydra™ render delegate...")
Earlier quoted context omitted.
Can I open an OpenUSD file in a text editor and read it?
The ASCII (plain-text, .usda file extension version) absolutely. For large scenes/models, the normal .usd binary/compressed version is often used for efficiency reasons (and proper round-tripping of float values for xforms, etc), but you can convert between the two with the 'usdcat' util and the python/c++ apis for debugging.
Why do so many (all?) textual data serialization formats represent floats in base-10 scientific notation, anyway?
If we wanted floats that are 1. human-editable but 2. bijective with IEEE754, wouldn't floating-point hexadecimal (and "e" notation representing a base-2 exponent) be a better idea?
Earlier quoted context omitted.
I'm more wondering where AMD is in this. "Open" isn't very open without all the major GPU players involved.
AMD isn't directly involved with the alliance, but they have embraced USD: https://www.amd.com/en/technologies/radeon-prorender ("A Pixar® USD™ Hydra™ render delegate...") https://gpuopen.com/learn/amd-usd-hydra-blender