• 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.

MCX error message

J

joel98

Messages
11
Country
switzerland
Hi everybody
I'm new in this forum and I'm from switzerland, so sry about my bad english.

A few days ago, I started with a terminal building in Google SketchUp. Yesterday I tried to convert it to a MDL file with the ModelConverterX. So I exported the project as a .dae-file and tried to import it into the MCX, but then there was the following error message:

An error occured during importing the selected file

Message:
Der Wert für ein unsigniertes Byte war zu groß oder zu klein.
-> the value was either too large or too small for an unsigned byte

StackTrace:
bei System.Convert.ToByte(Int32 value)
bei ASToFra.ObjectModel3D.ObjectModel.SetAlphaTextures()
bei ASToFra.ObjectReader.DAEReader.Read(String filename)
bei ASToFra.ObjectReader.AllObjectReader.Read(String fileName)
bei ASToFra.ModelConverterX.MainWindow.bwImporter_DoWork(Object sender, DoWorkEventArgs e)

Because it's my first time using the MCX and other SDK things I've no idea what I should do. :(

Thanks for answering
Joel
 
Hi Joel,

I think you have found a bug, I don't think you did anything wrong.

Are you using the development release or the stable version 1.3? If you are using 1.3 please try the development release first.

If both have the problem, can you send me the object and texture to fix the bug?
 
Hi Arno,
thanks for your fast answer.

arno said:
Are you using the development release or the stable version 1.3? If you are using 1.3 please try the development release first.
Click to expand...
I tried it with the development release and there occured the same error.
I'll send you ZIP with the sketchup- and the .dae-file and also the texture folder.
 
Ok, thanks. Then I'll try to reproduce the issue here.
 
Hi,

Thanks, I got the file.

The problem seems to be that SketchUp used a comma instead of a dot as decimal character in the DAE file. It is the first time I have seen this happen, I thought the DAE was always made with dots.

At the moment the COLLADA importer of ModelConverterX expects dots, that's why it goes wrong. I'll try to find out if this is a SketchUp bug or if I should make the importer code more flexible.
 
Hi Arno,
thanks for your help.

Is there any option to change this comma to a dot? Maybe reinstalling sketchup?
With other files everything was okay, it seems that just this particular file is invalid.

Thanks again
Joel
 
Hi,

It's probably easiest to change your regional settings in windows. The fs tools require the dot as decimal character as well. I think sketchup will export correctly as well after you change it.
 
Hi

I had the same idea and tried it already but it changed nothing. I'll try some other ideas and in the worst case I'd build a new terminal. :)

Thanks again for your great support
Joel
 
Hi,

Humm, you would expect that to work. Let me try to export your sketchup file here and see what I get.
 
Hi,

If I export the object here (using SketchUp 8.0, not yet the Trimble version) and with the decimal character set to dot, I get a COLLADA file that imports fine.

Which SketchUp version are you using?
 
Hi,

I'm using the trimble version. I'll try it with the other version and tell you the result.

Thanks
Joel

Edit: I tried it with the other version and it imports perfect!!! Thanks so much!! :)
 
Last edited:
You must log in or register to reply here.
Back
Top