8th December 2010, 05:45 PM | #1 |
Member
Expert member
Join Date: Jan 2006
Location: PA
Posts: 82
|
Collada Dae
.dae format is working beautifully thank you!
|
11th January 2011, 05:34 PM | #2 |
Senior Member
Professional user
Join Date: Feb 2004
Location: Portland, OR
Posts: 604
|
Re: Collada Dae
A question I don't think has been properly answered anywhere here...
What format specifically is the exported file? I have heard in some circles that Collada 1.4.1 or newer is an important factor in whether the file works with current software. Merrie, for what destination program did you export a Collada file from AC3D? And what was the indicator of "success"? Was it just the file "looking right" or was there access to some imbedded data that worked in the destination program?
__________________
Flight Sim Project Contributor My Gaming Rig: i5 2500K Quad-Core CPU at 3.3GHz MSI P67A-C43 mobo 4GB of PC12800 DDR3 memory Windows 7 1GB Galaxy GeForce GTX550 Ti video card GeForce 270.61 drivers (4/2011) Cougar joystick/throttle combo CH Pedals |
16th January 2011, 05:15 PM | #3 |
Member
Expert member
Join Date: Jun 2006
Posts: 51
|
Re: Collada Dae
I miss the grouping in the Collada export. An exported file from AC3D is flat without any parent-child relationship in DAZ Studio and all the object centers appear to be at 0/0/0.
In the Collada file every object is listed in "visual_scene" without a local translation one after the other. What it should look like (at least for DAZ Studio) is that there is one or more node in visual_scene which would be the WORLD node. Inside all top-level groups are mentioned in "nodes". It would just be a representation of what you see in the hierarchy view in AC3D. Every node in the "visual_scene" hierarchy can have its own translation, rotation and scale. I think it should make the exporter even simpler as it reflects what we see in the .ac format. If somebody really needs all objects to be on the same level he can ungroup just before exporting. |
29th January 2011, 03:07 AM | #4 |
Member
Expert member
Join Date: Jun 2006
Posts: 51
|
Re: Collada Dae
Nobody else has an issue with the flat structure (missing hierarchy through groups) in the DAE exporter? Am I really the only one who needs a preserved structure?
|
29th January 2011, 04:45 PM | #5 |
Senior Member
Professional user
Join Date: Feb 2004
Location: Portland, OR
Posts: 604
|
Re: Collada Dae
I don't even know what issues I have with it yet. I can't even get a straight answer as to which VERSION of Collada AC3D exports. This is significant, as 1.4 and 1.4.1 formatted files have had different results when exporting to various game engines.
As the bill of goods I've been sold relative to Collada is that it's a seamless import of 3D shapes and animation programming (for 3D programs that actually support animation), I'd imagine the part heirarchy would be an important element of that. So, if I understand you properly, I'd say that'd be a concern of mine as well. Right now, I'm doing experiments that consist of 3D modeling and texture assignment in AC3D, exporting to Blender 2.5 (in both Collada and .3ds), adding animation in Blender and export as Collada to two target game engines. It's been slow going, as both target game engines have their own (slow) development issues, which complicate the scenario a lot.
__________________
Flight Sim Project Contributor My Gaming Rig: i5 2500K Quad-Core CPU at 3.3GHz MSI P67A-C43 mobo 4GB of PC12800 DDR3 memory Windows 7 1GB Galaxy GeForce GTX550 Ti video card GeForce 270.61 drivers (4/2011) Cougar joystick/throttle combo CH Pedals |
31st January 2011, 08:50 PM | #6 |
Junior Member
Member
Join Date: Dec 2007
Posts: 12
|
Re: Collada Dae
So, when do we get to import Collada files?
|
Tags |
collada, dae |
|
|