News for hackers. Stuff that matters.
Re:Filament: Physically-based rendering engine by naikrovek on Friday August 03, 2018 @10:18PM (#17685038)
I don't need 3ds Max to support glTF as an editor format, I just need it to support the format at least as well as it supports minimal OBJ, which is the lowest common denominator of 3D file formats.

GlTF is a runtime transfer format and that's mostly how I'm going to use it. Others at my employer need to do VR work, and sometimes that requires the geometry to make a trip through something like 3ds Max. It would be nice if Autodesk acknowledged the existence and utility of glTF. People want to move away from FBX so Autodesk are unlikely to provide glTF support until it is demanded of them by a large enough portion of their audience.

Once I am done with this Creo View stuff I will look at writing a 3ds Max import plugin myself. It would definitely get used by my employer.

Re:Filament: Physically-based rendering engine by florabuzzword on Friday August 03, 2018 @11:33PM (#17685238)
I am a 3ds Max user, excited about gITF, and would be interested in contributing to an importer. Is your Creo View project by any chance open-source? Would your Max importer be open-source?
Re:Filament: Physically-based rendering engine by naikrovek on Saturday August 04, 2018 @10:23PM (#17689376)
No, but I bet someone could create a Creo View converter if they have access to PTC partner downloads. Specifically, the Creo View Files Tools that includes command-line tools to convert Creo View files to their ASCII representations.

Writing an importer for those ASCII files is easy, and when you have the binary and ASCII versions of the same files side-by-side, working out the binary file format is made much easier.

I haven't even begun work on a 3ds Max importer.