• Which the release of FS2020 we see an explosition of activity on the forun and of course we are very happy to see this. But having all questions about FS2020 in one forum becomes a bit messy. So therefore we would like to ask you all to use the following guidelines when posting your questions:

    • Tag FS2020 specific questions with the MSFS2020 tag.
    • Questions about making 3D assets can be posted in the 3D asset design forum. Either post them in the subforum of the modelling tool you use or in the general forum if they are general.
    • Questions about aircraft design can be posted in the Aircraft design forum
    • Questions about airport design can be posted in the FS2020 airport design forum. Once airport development tools have been updated for FS2020 you can post tool speciifc questions in the subforums of those tools as well of course.
    • Questions about terrain design can be posted in the FS2020 terrain design forum.
    • Questions about SimConnect can be posted in the SimConnect forum.

    Any other question that is not specific to an aspect of development or tool can be posted in the General chat forum.

    By following these guidelines we make sure that the forums remain easy to read for everybody and also that the right people can find your post to answer it.

Error when importing a KMZ file

Messages
1
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(IFormatProvider 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
 

Attachments

Hi,

I also get the error here, I am going to look into it.
 
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.
 
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.
 
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.
 
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.
 
Last edited:
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.
 
Back
Top