[quote]Maybe we can contribute to COLLADA blender exporter, so it can export to COLLADA 1.4 ?
[/quote]
i was looking into that yesterday:
the original author of this tool has stopped his support but there are some people to claim they are working on a 1.4 version but cvs doesn’t show any changes in 1.4 direction
but i don’t speak python so i won’t be able to contribute
It looks like SourceForge is working on the CVS problem. Their status webpage states
“Project CVS Service: Partial Outage In-Progress Last updated: 2006-03-13 Pacific”. https://sourceforge.net/docs/A04/
Did you have to flush your Java Web Start cache to get it to work?
I had a choice as to whether to support both 1.3 and 1.4 or just to migrate to 1.4 exclusively. I chose the latter because I figured people would stop using 1.3 pretty quickly and I did not want to have to continue to fix bugs in the 1.3 code.
Unfortunately, upgrading from 1.3 to 1.4 proved to be a bear for many of the vendors who support COLLADA including the Open Source guys. I myself regret my decision as my code was in a broken state for 2 months while I made the transition.
I also wish I had structured my code changes to support both as it would have enabled me to use Whoola COLLADA Converter to convert from 1.3 to 1.4. I had to upgrade many of my example files from 1.3 to 1.4 by hand. If you have the original files in another format besides COLLADA 1.3, Whoola COLLADA Converter might be able to convert them to 1.4 for you: http://earth.whoola.com:8080/space/collada/
[quote="<MagicSpark.org [ BlueSky ]>,post:20,topic:26413"]
Maybe we can contribute to COLLADA blender exporter, so it can export to COLLADA 1.4 ?
More seriously yes it would be good if we could import 1.3.1
[/quote]
I would love to see COLLADA support in Art of Illusion, one of the most popular Open Source Java projects on SourceForge: http://aoi.sourceforge.net/
i was looking into that yesterday:
the original author of this tool has stopped his support but there are some people to claim they are working on a 1.4 version but cvs doesn’t show any changes in 1.4 direction
but i don’t speak python so i won’t be able to contribute
[/quote]
I don’t speak Python either, so yes we just have to wait and see, but maybe we can just tell them there are many people interested ?
I would love to see COLLADA support in Art of Illusion, one of the most popular Open Source Java projects on SourceForge: http://aoi.sourceforge.net/
[/quote] Tell them !
I just wanted to load a COLLADA file with your fine loader, but it somehow doesn’t like my file.
This has been created in Maya 7.0 using ColladaMaya 0.86 and the .dae file itself looks superficially alright and seems to be in right version format:
but when trying to load it using XithColladaLoader it gives me:
Exception in thread "main" com.xith3d.loaders.ParsingErrorException
at com.whoola.core.media.xith.XithColladaLoader.load(Unknown Source)
at de.hh.gtgetest.HelloXith3D.<init>(HelloXith3D.java:60)
at de.hh.gtgetest.HelloXith3D.main(HelloXith3D.java:35)
Caused by: java.io.IOException
at com.whoola.core.text.xml.bind.JaxbCoder.parse(Unknown Source)
at com.whoola.core.media.collada.ColladaLoader.load(Unknown Source)
at com.whoola.core.media.collada.ColladaLoader.load(Unknown Source)
... 3 more
Caused by: javax.xml.bind.UnmarshalException: unexpected attribute "id"
- with linked exception:
[com.sun.msv.verifier.ValidityViolation: unexpected attribute "id"]
at org.collada._2005._11.colladaschema.impl.runtime.SAXUnmarshallerHandlerImpl.handleEvent(Unknown Source)
at org.collada._2005._11.colladaschema.impl.runtime.ErrorHandlerAdaptor.propagateEvent(Unknown Source)
at org.collada._2005._11.colladaschema.impl.runtime.ErrorHandlerAdaptor.error(Unknown Source)
at com.sun.msv.verifier.Verifier.onError(Verifier.java:371)DefaultValidationEventHandler: [ERROR]: unexpected attribute "id"
Location: line 269
at com.sun.msv.verifier.Verifier.onError(Verifier.java:363)
at com.sun.msv.verifier.Verifier.feedAttribute(Verifier.java:294)
at com.sun.msv.verifier.Verifier.startElement(Verifier.java:221)
at com.sun.msv.verifier.VerifierFilter.startElement(VerifierFilter.java:97)
at org.iso_relax.verifier.impl.ForkContentHandler.startElement(Unknown Source)
at org.collada._2005._11.colladaschema.impl.runtime.ValidatingUnmarshaller.startElement(Unknown Source)
at com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser.startElement(Unknown Source)
at com.sun.org.apache.xerces.internal.impl.XMLNSDocumentScannerImpl.scanStartElement(Unknown Source)
at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(Unknown Source)
at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown Source)
at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(Unknown Source)
at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(Unknown Source)
at com.sun.org.apache.xerces.internal.parsers.XMLParser.parse(Unknown Source)
at com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser.parse(Unknown Source)
at org.collada._2005._11.colladaschema.impl.runtime.UnmarshallerImpl.unmarshal(Unknown Source)
at javax.xml.bind.helpers.AbstractUnmarshallerImpl.unmarshal(AbstractUnmarshallerImpl.java:137)
at javax.xml.bind.helpers.AbstractUnmarshallerImpl.unmarshal(AbstractUnmarshallerImpl.java:105)
... 6 more
Caused by: com.sun.msv.verifier.ValidityViolation: unexpected attribute "id"
at com.sun.msv.verifier.Verifier.onError(Verifier.java:367)
... 23 more
I’ve checked the dae file and the mentioned line (269) contains the second source opening-tag of library-geometries/geometry/spline
I recognize that error. My importer is stricter than most exporters about conformity to the XML Schema since I am using JAXB. Please e-mail an example DAE file directly to david@croftsoft.com so I can verify.
OK, I received your example. The bad lines are the ones like this:
<control_vertices id=“curveShape1-lib-ControlVertex”>
In the XML Schema for COLLADA, no “id” attribute is defined for element “control_vertices”. If you manually delete the four or five instances in your example where these occur, the error goes away.
I see that you used ColladaMaya v0.86 to export the file. I also see that there is a new version out, v0.89. Please try with the new version of ColladaMaya and let me know if the “id” attribute problem goes away.
Once that is resolved or reported as a bug, I can then work with you to implement splines in the Whoola COLLADA Loader.
I took 0.90 of ColladaMaya (brand-new), which still outputs control_vertices elements with illegal id-attributes
erased the id-attributes off the elements as you suggested
now what I get is an exception (which might or might have not anything to do with above issue) :
Exception in thread "main" com.xith3d.loaders.ParsingErrorException
at com.whoola.core.media.xith.XithColladaLoader.load(Unknown Source)
at de.hh.gtgetest.HelloXith3D.<init>(HelloXith3D.java:60)
at de.hh.gtgetest.HelloXith3D.main(HelloXith3D.java:35)
Caused by: com.whoola.core.lang.NullArgumentException
at com.whoola.core.lang.NullArgumentException.check(Unknown Source)
at com.whoola.core.media.xith.XithColladaImporter.convertMeshType(Unknown Source)
at com.whoola.core.media.xith.XithColladaImporter.convertGeometryType(Unknown Source)
at com.whoola.core.media.xith.XithColladaImporter.convertInstanceGeometryType(Unknown Source)
at com.whoola.core.media.xith.XithColladaImporter.convertNodeType(Unknown Source)
at com.whoola.core.media.xith.XithColladaImporter.convertVisualSceneType(Unknown Source)
at com.whoola.core.media.xith.XithColladaImporter.convertInstanceWithExtra(Unknown Source)
at com.whoola.core.media.xith.XithColladaImporter.convertColladaSceneType(Unknown Source)
at com.whoola.core.media.xith.XithColladaImporter.convertColladaType(Unknown Source)
at com.whoola.core.media.xith.XithColladaImporter.importColladaType(Unknown Source)
at com.whoola.core.media.xith.XithColladaLoader.createScene(Unknown Source)
... 3 more
the regarding line (60) is where I do:
scene = colladaLoader.load("D:/Entwicklung/eclipse/workspace/GTGETest/resources/carCOLLADA.dae").getSceneGroup();
No, I got the same error, probably because splines aren’t implemented yet.
Now that you have confirmed that the problem still exists in v0.90, I am going to report the id bug to the COLLADA Maya exporter folks. I will then start working on the splines.
I’ve got a demo on the 25th. I’ll take a look at it sometime after then. If you need it sooner, let me know and we’ll work something out, maybe have you contribute the splines code.
[quote]…If you need it sooner, let me know…
[/quote]
nah, it’s alright. I still have some work to do for university so this might wait.
But I’d be happy to contribute anything valuable - could you be more precise?
In the spirit of an Open Source project, I wanted to offer you the oppurtunity to contribute the spline code. In truth, however, I’d rather reserve the joy of writing that code to myself. If I delay too long, however, feel free to dive in and scratch your own itch as needed.
Pleased to see the open source spirit isn’t the same for everyone… I’ve seen people saying “hey it’s open source if you want it, code it, nobody’s gonna do it for you…”. Just the opposite of what I was thinking…
oh kind thanks for this offer. I’ve already checked-out the xith-tk module and browsed the whoola-code. I see what I can do here if time permits. We keep in touch.