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

Runtime error?

Thank you Sandra & odd_waves :)

The corrected ADE9X Environment Checker 1.3.7 is linked here.

Works for me - I initially got an error message about the trailing \ and clicked the repair under FSX section even though I don't have FSX installed, only FS. Then I restarted and no errors other than the red FSX warning, which I expected since that is not installed.

Many thanks for such a quick fix.

Nigel
 
Works for me - I initially got an error message about the trailing \ and clicked the repair under FSX section even though I don't have FSX installed, only FS. Then I restarted and no errors other than the red FSX warning, which I expected since that is not installed.

Many thanks for such a quick fix.

Nigel

Nigel,

did you had FSX installed on that computer once and removed it? Because you should not get the repair backslash option if the application is not installed. That would be another bug :o
 
Nigel,

did you had FSX installed on that computer once and removed it? Because you should not get the repair backslash option if the application is not installed. That would be another bug :o

Or maybe an indication that an uninstall did not complete correctly but left registry entries behind?
 
did you had FSX installed on that computer once and removed it?

Or maybe an indication that an uninstall did not complete correctly but left registry entries behind?

Yes, that is what I suspect (or should I say hope for? :rolleyes:)

But I need to make another change anyhow. See that ridiculous pathetic "\" at Sandra's screen shot? This is not how it is supposed to be :o

Zwischenablage05-1.jpg
 
Last edited:
I never had FSX installed but my screenshot looks just like Sandra's. That was because I "repaired" the FSX section because I got an error message on start, although after that the application ran fine. After I did the repair, I could start without any error messages.

When I started ADE, I got a box witch asked which version of FS to use. I didn't like that even though it only took a second to choose. I went into the registry and deleted the key for Flight Simulator 10 and that fixed starting ADE - it defaulted to FS9 with no dialogue box on start.

I then started the Environment Checker and there were no errors. The section for FSX was red as expected, but this time "na" appeared in the boxes and I assume that is how it should work.

Hope this helps!

Nigel
 
Last edited:
I never had FSX installed but my screenshot looks just like Sandra's. That was because I "repaired" the FSX section because I got an error message on start, although after that the application ran fine. After I did the repair, I could start without any error messages.

When I started ADE, I got a box witch asked which version of FS to use. I didn't like that even though it only took a second to choose. I went into the registry and deleted the key for Flight Simulator 10 and that fixed starting ADE - it defaulted to FS9 with no dialogue box on start.

I then started the Environment Checker and there were no errors. The section for FSX was red as expected, but this time "na" appeared in the boxes and I assume that is how it should work.

Hope this helps!

Nigel

If you never had FSX installed I am curious how a registry key could exist for it in your system?
 
If you never had FSX installed I am curious how a registry key could exist for it in your system?

That is an easy question to answer! ADE Environment Checker created it when, in the FSX section, I clicked the repair trailing backslash box because of an error message on starting the Environment Checker. The error message referred to a trailing backslash and since the FS9 section was ok, I went ahead and did the FSX repair to see if that fixed the startup error message.

Sure enough the registry had an entry for path of "\".

Next I started ADE. ADE must check the registry on startup and caused the FS9 or FSX selection dialogue to appear. After deleting the bogus registry key, that dissapeared.

After deleting the registry key, I rechecked the Environment Checker, the FSX section had "na" in all items pertaining to FSX and that is what I would expect to see. The only reason I went through all this was to try to help debug the Environment Checker since ADE, so far, apears to work brilliantly!

I promise, I don't even own FSX and have never installed it or the demo version that was available. I knew my old computer was not up to it! :)

Nigel
 
Fair enough. I am sure Martin will look at how to stop this happening in future.
 
The only reason I went through all this was to try to help debug the Environment Checker since ADE, so far, apears to work brilliantly!

Nigel, I am aware of this and I am grateful that you help me with this tedious task :)

We will get there, although this will require some guesswork on my site (as did the initial crash error) because I am completely unable to reproduce either behavior :confused: Let me go over my code again. I will report back.
 
Back
Top