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

FSX "file too small" error message

D

DGBarton

Messages
28
Country
unitedkingdom
Hi,


Can anyone please help with a problem loading a.dae file made with sketchup?

The error reads “Error importing the file: File is too small” and will not load. The file size is 26MB

Apart from the obvious and the file is indeed too small (I have tried various file sizes and all report same error) is there anything else that will cause this.

I am running Version 1.4.0.0 of MCX

Windows XP SP3

Direct X 9c


Regards

DGB
 

Attachments

  • file error.jpg
    file error.jpg
    185 KB · Views: 470
Hello DGB,...

I did ask you (in another thread) about another file before being to small,.. and sent you a message on where to send it (my email address)

I believe though if you can send the SketchUp file, that would be best, but before you do send it... what options (within SketchUp) are set before you are exporting it into a dae file?
 
Hi,

It seems this error is coming for the library I use to read the DAE files. I'll try to check the code of that library when I get home to see what is causing it. If you have an object for me to try that would be useful.
 
Hello DGB...

I was able to export into a dae file your RN_Jeep and import it into MCX 1.4 with no problems,... not getting a error of it being to small.

Make sure within the options, when you are exporting into a dae file that the Export options are set correctly (see pictures)

Screenshot (58).png
Screenshot (59).png
 
arno said:
Hi,

It seems this error is coming for the library I use to read the DAE files. I'll try to check the code of that library when I get home to see what is causing it. If you have an object for me to try that would be useful.
Click to expand...

Hi,

Here is the sketchup file I am referring to.

After an email from Pyscen, who has kindly been looking into this problem

for me he suggests sending in aythe original sketchup file I used..

This file, via a MCX version I was using at the time produced a working .bgl file for FSX.

I remember that version having a different materials editor that converted textures to size and format suitable for use in FSX

Regards

DGB
Pyscen said:
Hello DGB...

I was able to export into a dae file your RN_Jeep and import it into MCX 1.4 with no problems,... not getting a error of it being to small.

Make sure within the options, when you are exporting into a dae file that the Export options are set correctly (see pictures)

View attachment 33052 View attachment 33053
Click to expand...
Pyscen said:
Hello DGB...

I was able to export into a dae file your RN_Jeep and import it into MCX 1.4 with no problems,... not getting a error of it being to small.

Make sure within the options, when you are exporting into a dae file that the Export options are set correctly (see pictures)

View attachment 33052 View attachment 33053
Click to expand...


Hi,
Thanks for the info.
I have tried again following your suggestions but the same error report appears.
Looking at your screenshots your version of sketchup is different to mine but the export settings look to be the same
On my 32bit XP machine the latest version I can use is v2014 or sketchup8.
Any other suggestions welcome
Regards
DGB
 

Attachments

  • sketchup.jpg
    sketchup.jpg
    124.9 KB · Views: 443
Why not share the DAE file you use? Then I can check if I can reproduce the issue here.
 
Hi,

I have check the source code and the "file is too small" error is only thrown if a file is less than 8 bytes in length. So are you sure you did not try to import a 0 kB file by accident?
 
Hi,
Can I send you an email with the files attached?
They wont upload into thread direct
Regards
DGB
 
Hello DGB...

Zip up the dae file that is causing the error "file to small". You should be able to link it in the thread.

The reason: the SketchUp Import screen looks different is because mine is a later version. Unfortunately,.. your OS is XP,.. so I believe that the last version is SketchUp 2014, that is compatible to XP,... but it shouldn't matter concerning the error that your getting. Unless the 32-bit version library of MCX is not reading it correctly.

Arno,...

Is there a way to force MCX to use the 32-bit version library?
 
Last edited:
He says the file size is 26 MB - isn't that too large to attach to a message?
 
Hi,

I got the file via email, but I can read it fine in MCX here.

But I also did not test with 32 bit. I would have to compile MCX as 32 bit to test that.
 
Hi,


Thanks to you for testing the .dae file.

As it works for you the problem must be on my system.

I think I will have to uninstall and start again from scratch.

What additional files and (if possible) version numbers

must be installed for latest (or any)version of MCX to work on a 32bit XP system.

Will a 32bit XP system support all the additional files needed for MCX to run.

Also are older versions of MCX still available.

The last success I had was about 2 years ago with previous aversion I

Don’t know for sure what build no. it was

The thing I do notice is different is the materials editor menu. Is that a clue to the version I was using


Thanks again

DGB.
 
Hi,

For the latest MCX you need .NET 4.0 and Visual Studio 2015 runtime files. I think both of these are still available for XP as well.

The only old version of MCX is the 1.3 release, but that is really old :).

I'll try to test tonight with a 32 bit build and see if I get the file too small error there.
 
Hi,

I have made a bit of progress today.

After reinstalling NET4.0 and 2015 runtime files I can now

Import the.dae file into MCX version 1.3.0.0 with no errors.

However I cannot export to a FSX .bgl file.

The error messages are in enclosed screenshot

Regards

DGB
 

Attachments

  • Jeep-export errors log.jpg
    Jeep-export errors log.jpg
    581.9 KB · Views: 498
There are no error messages, only Information. It appears the BGL file was created successfully (last line). Did you look everywhere on your Desktop?
 
Hello,...

The Visual Studio 2015 runtime files are only needed in MCX 1.4 not v1.3,... so that wouldn't of made any differences. Concerning the NET 4.0 files,.. I can't remember exactly when those were needed,...

Tom, there are errors but its regarding the vertices limit reached,... looks like it parsed the internal errors and completed the model. Hard to read since the window clips the rest.

Did it save anything to the desktop?
 
Hi

The exporting did not produce anything at all anywhere

Is there a way of saving the events log and sending it in?

Here is a better representation of the error messages

Regards.
DGB
 

Attachments

  • Jeep-export errors log -2.JPG
    Jeep-export errors log -2.JPG
    273.7 KB · Views: 490
Hello...

No,... there isn't a way unless it's a critical error to send the log file. It seems that you need to remove some of vertices... is this the same jeep you sent me or have you done more to it since then?
 
Hi,

MCX 1.3 uses .NET 2.0 (and no Visual C++ requirement either).

Your object seems to be too complex to export to MDL. You need to use less polygons per material or simplify the object.
 
Hi,


Yes it is the same Jeep file that I sent before.

Can the .dae be edited to make it less complex but retain its appearance?

Also I now have access to a Windows v8.1 laptop.

What are the files I need to install to make MCX work on it?

Am I correct in thinking it will require NET4 and C++ 2015 (64bit version)


Regards

DGB
 
You must log in or register to reply here.
Back
Top