• 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 Suspended Right After Launch

alexito_178

alexito_178

Messages
5
Country
puertorico
Hello!

MCX 1.4 is getting suspended every time I launch it; it's been going on for a while now (maybe a month?). I opened up the Task Manager and in less than three seconds, the app gets suspended. I managed to create a DMP File in case it was necessary, though it's too large to upload. Any help would be great! Thank y'all in advance
 
Hi,

Does the preview window show up normally or does the loading of that not finish?

You might want to try a clean installation of the 1.4 stable release as well.
 
arno said:
Hi,

Does the preview window show up normally or does the loading of that not finish?

You might want to try a clean installation of the 1.4 stable release as well.
Click to expand...
Hi, Arno!

I've deleted and reinstalled multiple times yet nothing seems to work. Absolutely nothing shows up. 1.3 does open up, but 1.4 is the one I need for P3D.

Is there maybe a hidden folder that I don't know about? If so, I could try and delete than one as well.
 
You could try to delete all configuration files. But it might also be an issue with the dotnet framework.
 
Yes, but it differs bit per version. 1.3 used version 2 if I remember correctly. 1.4 is version 3.5 or 4.0 (I can't remember) and 1.5 uses version 4.7.
 
arno said:
Yes, but it differs bit per version. 1.3 used version 2 if I remember correctly. 1.4 is version 3.5 or 4.0 (I can't remember) and 1.5 uses version 4.7.
Click to expand...
Downloaded 1.5 but even that won't open. I decided to try and see the dotnet framework version but it's all updated. I can't even install 4.7 or any one older if I wanted to.
 
Have you tried renaming the exe file? Do that and then try starting it by double clicking the exe file.
 
In that case removing the old configuration files will do the trick. The manual explains where they are located.
 
Arno, I assumed this was an OS restriction of some sort. Are you saying that MCX may not start at all if something is wrong with the configuration files?

I did a search for "configuration" and "cfg" in the 1.4 manual and nothing relevant was found. Could you tell me where that is?
 
Yes, sometimes it seems the configuration files get corrupt and then MCX won't start. This is not the first thread where it happens.

The information is in section 2.3 of the manual. But it might be I added it after the 1.4 stable release. Just for the record, the configuration files can be found in this folder:

Code: 
C:\Users\{username}\AppData\Local\SceneryDesign.org
 
I just now cleared the same issue after finding this thread. I found the configuration file had a "bogus" entry, that when removed allowed MCX to open and handle files using all my settings. Below is the corrupt section:

<ASToFra.Utils.UtilsSettings>
<setting name="FormState" serializeAs="String">
<value>MainWindow;2139;194;845;501;False|SceneryObjectsEditor;474;323;463;415;False|GroundPolygonWizardSeasons;104;104;263;260;False|MaterialEditorForm;701;484;1086;566;False|OptionsForm;515;271;1422;500;False|AnimationEditorForm;1006;249;420;491;False|TextureConverterForm;130;130;568;569;False|MoveDialog;156;156;190;180;False|MergeObjectsForm;78;78;238;482;False|BatchConvertForm;156;156;774;405;False|HierarchyEditor;796;180;705;365;False|ObjectInformationForm;100;196;791;464;False|ScaleDialog;160;49;325;205;False|LODCreator;182;182;410;414;False|RotateDialog;156;156;190;190;False|AttachedObjectEditor;814;209;535;316;False|</value>
</setting>
</ASToFra.Utils.UtilsSettings>
 
Hi,

That entry stores the location of the various forms, so that they can be reopened at the same location and size. The values in their don't look corrupt or so to me.
 
Well oddly, it worked. Then MCX locked again and I could not find anything that looked out of place, clearly a default user.cfg would not have a record of stored form positions. Anyway, I took that same user.cfg file, the one that only appears corrupt, with the stored form positions section removed, copy/pasted that into the user.cfg and voila, it worked again and saved me having to click out all those tool paths. So now I have a copy, all ready to paste in.

One thing I noticed, is that the paths in the default user.cfg appeared to be valid, but were not the ones I'd chosen and use. Apparently I collect SDK's like old birthday cards, so, perhaps there are software tool paths that MCX prefers?
 
For certain tool paths MCX has hardcoded default values, for others the default is an empty string. On startup MCX will check if the entered path exists on your system and if not use the registry to try to find where that SDK is installed.
 
The cause of the hang occurs when I slide MCX to monitor #3 and close it. If I close MCX on the main monitor the hang does not occur and this explains why removing the <ASToFra.Utils.UtilsSettings> section clears the hang.
 
Is that monitor to the left or right of your main monitor? I'll see if I can reproduce issues with bigger values for the stored position.
 
The monitor is to my right. These are the stored values:

<ASToFra.Utils.UtilsSettings>
<setting name="FormState" serializeAs="String">
<value>MainWindow;2051;94;935;701;False|</value>
</setting>
</ASToFra.Utils.UtilsSettings>

I also tested and found the hang when closing from the left monitor, which is really just for movies and storing open apps, etc.

<ASToFra.Utils.UtilsSettings>
<setting name="FormState" serializeAs="String">
<value>MainWindow;-1387;135;935;701;False|</value>
</setting>
</ASToFra.Utils.UtilsSettings>
 
You must log in or register to reply here.
Back
Top