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

SimConnect not found

Helli

Helli

Messages
2,192
Country
germany
Hello!

The Problem

My ADE V1.35 shows in the lower right corner the red message:

"SimConnect not found"

The FSX & SDK Configuration

FSX: RTM ==> SP1 ==> SP2
SDK: RTM ==> SP1A ==> SP2

Details

When searching this forum for help I found the thread
"TOOLS > TOOLS Support > AIRPORT DESIGN EDITOR > Can't connect to FSX" or http://www.fsdeveloper.com/forum/showthread.php?t=8697

The problem of that thread is not the same as mine here.
But the confusion and uncertainties which I found there, namely concerning the various types and versions of "SimConnect.dll", which accumulate by the nerve-raking installation modes for FSX and the SDKs made me thoughtful.

I searched my HDDs for "SimConnect.dll" and this is what I found:

Simconnect.jpg


The different versions - marked in (#) - are

(1) 10.0.61637.0 (FSX-Xpack.20070926-1421)
(2) 10.0.61355.0 (fsx-sp1.20070510-2038)
(3) 10.0.61637.0 (FSX-Xpack.20070926-1421)

(5) 10.0.60905.0
(6) 10.0.61355.0 (fsx-sp1.20070510-2038)
(7) 10.0.61637.0 (FSX-Xpack.20070926-1421)

My first reaction, caused by one's primitive urge for symmetry, is:

(5) to (7) in the SDK-Folder reflect the installation "history" of the SDKs.

(1) in the WinSxS-Folder is out of "Symmetry".

Questions

(A) Since Jon stated in the other thread:
--------------------------
"ADE uses the earliest one 10.0.60905.0. In any case to be one the safe side you need all the versions related to the different SPs you have installed. MS did not make this one particularly easy"
---------------------------
should the first entry of SimConnect-Versions in WinSxS also be the RTM-Version?

(B) If "Yes", how does it get there?

(C) Is there another reason for the error message of ADE above?

Your kind advice is highly appreciated.

Helli


Addendum:

It might be interesting to note, that my other tool "Instant Scenery" from Flight1 does not work with FSX either.
It uses SimConnect as well.
The Flight1 experts tried to help but left me finally without a solution.
 
Last edited:
Try running the program called Airport Design Editor Environment Test Tool. This is in the program group with Airport Design Editor. It will try and find simconnect also. ADE uses the RTM version of SimConnect. If Instant Scenery cannot find it either then it does seem that you installation has a problem of some sort
 
Hello Jon!

I am sorry to bother you with a trivial thing.

I cannot find the Airport Design Editor Environment Test Tool.
The location indicated by you:
"This is in the program group with Airport Design Editor"
is somewhat unclear to me. Could you be more specific what you mean by program group?

Helli
 
Start Menu > All Programs > Airport Design Editor > Airport Design Editor Environment Test Tool :)
 
Thanks Jon!

This "entry" to programs I never use, therefore its english name is unfamiliar to me.

And when looking through the ADE files, the name "ADE-Check.exe" did not ring a bell.

Anyway, I ran the Checker.
Here is the report:
---------------------------------------------
Date of Report: 05.08.2008 17:29:01
Operating System: Microsoft Windows XP Home Edition
OS Service Pack: Service Pack 2 (2.0)
OS Version: 5.1.2600 (32 Bit)
OS Language: Deutsch (Deutschland) => separator: '.'
Nodename: TONI
ADE installed: yes
ADE Path: G:\FSX Design\ADE\Airport Design Editor
ADE Version: 1.35.0.0
ADE Info: Airport Design Editor Version 1.35.0.0 (Patched from 1.20)
FXS installed: yes
FSX Path: G:\FSX\
FSX Version: 10.0.61472.0 (fsx-sp2.20071210-2023)
RTM Simconnect: yes
SP1 Simconnect: yes
SP2 Simconnect: yes
SDK installed: yes
SDK Path: G:\FSX\SDK\
BGLComp Version: 10.0.61472.0 (fsx-sp2.20071210-2023)
BGLComp >= SP1: yes
Shp2Vec found: yes
.NET 1.1 installed: yes
.NET 2.0 installed: yes
---------------------------------------------------

I klicked the button "SimConnect" to run SimConnect Life. In a first run the SimConnect.dll" was copied to ADE.
The second run told me that FSX has to be started and that Simconnect was disconnected. After starting FSX the third run produced all green messages.

But then I started ADE ---------- SimConnect not found---- is still there.

I matched the airports in FSX and ADE but nothing happened.

What else could it be?

Helli
 
I think that Martin (gsnde) may be able to offer some help here. He wrote the environment checker.
 
Jon, I just checked, which version of "SimConnect" was added to the ADE folder. It is the FSX-Xpack version, not the RTM version.

But on second thoughts, did not the ACE-guru, who participated in the other thread which I mentioned above, say something that SimConnect.dll need not be resident in the application?

Well, the search goes on.

Helli
 
Hello Jon!

The search is over, I have ADE telling me that "SimConnect Is Found".
At least it is partly over.

Remember my first posting yesterday (5.8.08 15:36), where I was suspicious, that the "Simconnect.dll"-version in line (1) should be 10.0.60905.0 and not 10.0.61637.0 - in order to reflect the install history?
That was the culprit - also for "Instant Scenery" and for "FSUIPC4". All three applications search for version 10.0.60905.0.
You (ADE) and FSUIPC told me, InstantScenery told me indirectly and I failed to see it.

The search is only partly over, because I am not sure about the role of the SimConnect-entries in Windows\WinSxS.
- the uninstallation of the SDK does not remove them. (I had to delete them manually).
- None of the 3 SDK-installation steps (RTM, SP1a, SP2) did generate them.
- After each step I had to run the relevant "SimConnect.msi", which was established in ...SDK\SimConnect SDK\lib.
- Each run created a related version of "SimConnect Client" - and the required new entry in WinSxS.

I can't imagine that this is the normal procedure, since I did not see it mentioned anywhere (I stumbled over it by chance).
I guess, that the ACES did not foresee, that some bloke like me waits till FSX-SP2 is installed before he takles the SDK-installation.
I guess, that the "normal" way would have been to install each SDk directly after each FSX-update.
But I am only guessing.
And I do not intend to verify this by re-installing both FSX and SDKs.

I write this information broadly, so that you could use it, in case somebody else encounters the same problem.

My final word: the whole issue is not the fault of ADE but lies in the ACES' front garden.

My final final word: Many thanks Jon for letting me bending your ear.

yours truely

Helli
 
Last edited:
Good to know that you have it fixed :)
 
Hello Jon!

One last idea or remark on this thread here.
It concerns the "Environment Checker".

Remember when I ran it (before I found the solution) it told me after its scan, that SimConnect was connected - although it wasn't.

I suspect, that the Checker looks under ..\Windows\WinSxS\ for the folder "x86_Microsoft.FlightSimulator....._10.0.60905.0_x-ww_429211e9" as proof, that SimConnect is established.
But probabely it does not look, whether it contains the proper SimConnect.dll-version (which in my case it didn't).

Maybe my case is so rare, that Martin should not be bothered.
But maybe it is a quick and easy thing.
I do not know Martin, therefore I leave it in your hands.

Many thanks

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