• 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 message on close

C

Coggie

Messages
10
Country
canada
Hi Arno

I've just installed ModelConverterX on my main PC and when closing the program I get the following error (see image).

I searched through the old posts and seen that Sidney Schwartz was getting an error message on close too, but there was no description or image to compare it to mine. And yes it only happens if I open an object or objects. If I open the program and then close it, no issues.

On an old PC running XP SP2 512mb Ram and an old ATI card I don't get the error message. My main PC runs Media Center, 2Gb ram and a Nvidia 7600GT card.

Scott
 

Attachments

  • MCX_Error.jpg
    MCX_Error.jpg
    35.1 KB · Views: 588
Coggie said:
Hi Arno

I've just installed ModelConverterX on my main PC and when closing the program I get the following error (see image).

I searched through the old posts and seen that Sidney Schwartz was getting an error message on close too, but there was no description or image to compare it to mine. And yes it only happens if I open an object or objects. If I open the program and then close it, no issues.

On an old PC running XP SP2 512mb Ram and an old ATI card I don't get the error message. My main PC runs Media Center, 2Gb ram and a Nvidia 7600GT card.

Scott
Click to expand...

Scott,...

Is this the latest development verison or v1.2?
 
Both versions Doug.

The program doesn't show any error while running and all seems to function as it should.
 
Hi,

Are you sure you have the latest Microsoft .NET Framework Version 2.0 Redistributable Package (x86) ?
 
Hi Scott,

I also have this problem when I run ModelConverterX at work. I still have not figure out what it is. The problem is that I do not have it on my development machine, so that makes it very hard to debug.

Like you already said, it does not affect the functioning of the tool.
 
Rob - Yes I have the latest .NET Framework V2 Redistributable Package.

Arno - So it's the same error message Sydney was/is getting then. Ok no problem.
 
arno said:
Hi Scott,

I also have this problem when I run ModelConverterX at work. I still have not figure out what it is. The problem is that I do not have it on my development machine, so that makes it very hard to debug.

Like you already said, it does not affect the functioning of the tool.
Click to expand...

I'm wondering if it is a firewall blocking access to certain areas of memory maybe? or memory in general?
 
I ran across this snippet:

try this to force the bug to happen while under program control

Code: 
   //set as many statics as you can to null;
   GC.Collect();
   GC.WaitForPendingFinalizers();
} //exit main

Dick
 
Thanks Dick, I'll give that a try.
 
Hi,

I tried to insert that piece of code now, but I still get exactly the same crash when I try it at work (and at home still no crash at all).
 
Hi,

At work I got a new video card in my PC (and updated drivers as well). The error message is gone since then. So it seems to be a combination of driver and videocard, which probably explains why I could not reproduce it at home.
 
You must log in or register to reply here.
Back
Top