Error when importing a KMZ file

[kobbe]

When I import a KMZ file into MCX 1.2 I get the following error:

An error occured during importing the selected file

Message:
De indeling van de invoertekenreeks is onjuist.

StackTrace:
bij System.Number.StringToNumber(String str, NumberStyles options, NumberBuffer& number, NumberFormatInfo info, Boolean parseDecimal)
bij System.Number.ParseSingle(String value, NumberStyles options, NumberFormatInfo numfmt)
bij System.Single.Parse(String s, NumberStyles style, NumberFormatInfo info)
bij System.Convert.ToSingle(String value, IFormatProvider provider)
bij System.String.System.IConvertible.ToSingle(IFormat Provider provider)
bij System.Convert.ChangeType(Object value, Type conversionType, IFormatProvider provider)
bij COLLADA.Document.Array`1..ctor(Document doc, XmlNode arrayElement)
bij COLLADA.Document.Source..ctor(Document doc, XmlNode node)
bij COLLADA.Document.Mesh..ctor(Document doc, XmlNode node)
bij COLLADA.Document.Geometry..ctor(Document doc, XmlNode node)
bij COLLADA.Document..ctor(String name)
bij ASToFra.DAEReader.Read(String filename)
bij ASToFra.KMZReader.Read(String filename)
bij ASToFra.ObjectReader.read(String fileName)
bij ASToFra.MainWindow.bwImporter_DoWork(Object sender, DoWorkEventArgs e)

I've added the file to this message

[arno]

Hi,

I also get the error here, I am going to look into it.

[arno]

Hi,

The issue should be fixed in the next development release. The object had some infinite values in the COLLADA file and that gave trouble.

[Pyscen]

Hi,

The issue should be fixed in the next development release. The object had some infinite values in the COLLADA file and that gave trouble.

Arno,... does that mean version 1.21? Just asking?

Oh,... have you done anything about the naming errors mentioned before in the material editor, not that its a big "bug" or anything. I know your working on gpoly more at this time.

[arno]

Hi Doug,

It's in the 1.3 development release which is available at the normal address for the development releases. In the end this will become version 1.3.

The material editor bug is still on the todolist for 1.3. Since it is not a direct crash of the tool I did not try to fix it immediately.

[Pyscen]

Yes... I agreee its not a "crash bug",... no problem. :) I assume, then that the rewriting of the material editor/ mass editor is part of the 1.3 change also, since you had plans to combine the 2 at one point.

[arno]

Hi Doug,

Yes, I might have forgotten that in my post about the 1.3 changes. Improving the material editor GUI to make it easier to use (including mass texture editor and drawcall minimizer) is also planned for 1.3. That will include the bug with the material names you reported as well of course.