![]() ![]() We do also contact personally companies with which we eared that there was issue with our valid COLLADA file to see what can be done. The issues that were unveiled at that Plug Fest were fixed and released in Crosswalk 3.1 – only two month later. We tested our plugin with the next gen 3dsMax and Maya plugins (not implemented by FS btw), with SketchUp, Cinema4D, Daz, Poser, etc. We did participate to the Intel Plug Fest and we had great success of interoperability with the companies that were present. ![]() But we’re not sitting there and waiting for that Conformance Tests to come out. With that test, to be able to be considered COLLADA Conformant, applications will have to support more then the 3dsMax subset. To help solve this complex situation, we do put a lot of hope in the COLLADA Conformance Test that Khronos is developing project into which we’re participating. You can run the coherency test and COLLADA schema validation on your own file by using the COLLADA Refinery if you want: If you encounter issues please do send them our way, we do care and fix those issues. We validate our file against the COLLADA schema and we also run the Coherency Test so, you can be insured that when you export a COLLADA file from XSI, it’s valid. We support every arbitrary transform stack at import.Īdditionally, we do make sure that the COLLADA files exported from XSI are valid. A thorough importer implementer would detect if a given transform stack is compatible with his application and if it isn’t, he would evaluate and bake the transform into his own transform stack. So, that’s what we do, we express our transform stack, which is different from the 3dsMax one, in COLLADA, and it’s completely valid. One cannot expect all applications to standardize on a give transformation stack so that’s why COLLADA itself allows for very arbitrary transform stack representation to enable every application to represent their transform stack in a lossless fashion. Even if XSI has a very simple and documented transform stack, it’s not the same as the 3dsMax one and problem can occur with implementations that supports only the 3dsMax flavour of COLLADA. This is especially true with transform stacks. As a result, they support only a subset of what’s totally legal in COLLADA and worst than that, they often make assumption that elements in the file (id, names, hierarchy, etc.) will be exactly as 3dsMax does export them and if they don’t, the import fails. They coded it based strictly on COLLADA file exported form 3dsMax. What happen in those cases, and it’s always the same story, is that the implementers of those application specific COLLADA importers often did not code their importer by looking at the COLLADA spec. We cannot agree more with you that it’s a very unfortunate situation. We are aware that some applications does have problems importing XSI generated COLLADA files. ![]() When I import it in Papervision : the mesh is not correctly animated (deformations are “strange”). There are no other transformation apply to the cylinder. PS : I use Softimage XSI7 & Crosswalk 3.0, it’s a simple cynlinder with only two bones that rotate in Forward Kinematics. Is there anybody that have a workaround to make XSI’s bones working with Papervision/Collada ? Also, XSI export only “ID” Tags, whereas 3ds max export also “name” and “type” properties. It’s not the fault of Papervision : the same cynlinder animated in Forward Kinematic with 3ds max works perfectly with Papervision.Īs I’m not a software ingeneer, I can not say exactly what is wrong with Softimage’s Collada ? With XSI’s Collada every transformation is “ungroup” with each 3 axis (posx,posy,posz…), whereas 3ds max’s Collada group (pos, rot, scale). When object are animated (bones) Softimage’s Collada produce bad results (mesh animations are wrong !). I’m trying to use XSI to create 3D animations for PaperVision (a Flash 3D Engine that reads Collada). ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |