EmileB

Yes that's correct AFAIK. For example, FSInn communicates with FSX through SimConnect and I didn't need to do anything with SimConnect to get FSInn to work (runs on the same PC as FSX). I take it from there that SimConnect is installed with FSX. Your guess is as good as mine :( . I'm not a programmer. But I AM trying to run ASX on a notebook over the LAN, NOT on the PC that FSX is installed on, maybe that's why. The ASX documentation has clearly defined steps to follow on the FSX "server" as well as the client PC in order to get ASX to communicate with FSX on the other PC. This includes running a file called simconnect.msi on each client PC. Now, this file is found in one of the installed SDK subfolders and copied to the client PC where it is then run to install SimConnect on the client. After running it on my 64 bit notebook, SimConnect Client does appear in the list of installed programs. Yet ASX still gives me a warning. But it DOES/DID run on two other client PCs set up in EXACTLY the same way, that's what gets me. Why not on the notebook - because it has a 64 bit OS ? Got that, installed it, and it all looks OK (see attached screen capture from the FSX PC). Am I supposed to run this from the client notebook as well ?Thanks,Emile.

I run FSX (SP2) on a very fast, two month old Windows 7 Home Premium (32 bit) machine. The FSX SDK SP2 is also installed on it.I used to run ActiveSky X over my home LAN on a Compaq notebook SimConnect client which ran with Windows XP (home edition), without any problems. That notebook died just over a week ago :( . It's been replaced with a new Compaq notebook that came with Windows 7 Home Premium 64 bit installed. On that new Compaq, I installed SimConnect as a client, in accordance with the instructions in the ASX documentation. Then I installed ASX and all service packs. But now whenever I try to load ASX, I'm getting the dreaded "Simconnect SP1 managed version was not found to be correctly installed on this system..." message during startup.The weird thing about this is that on my old XP Compaq notebook as SimConnect client, ASX worked flawlessly over the LAN. In addition, today I installed SimConnect as per instructions, followed by ASX and all service packs, on my wife's PC which runs Vista Home Premium (32 bit) - and from this SimConnect client ASX connected immediately to my FSX over the LAN ! This has got me beat :( Another thing that happened when I installed ASX on the new notebook, is that when I specified the location of the FSX and AppData folders (which are found on the network on the server PC, of course) on first running ASX, I was asked for a username and password. Just typed in my username and hit Enter and the connection was made. But this did not happen when I installed ASX on my wife's PC. I did not put any passwords on the FSX PC anyway.It must be something to do with my new notebook. Are there any known issues when running SimConnect client under Windows 7 Home Premium 64 bit ? Or is there anything else I could try on my new notebook ? Would the username/password request have something to do with it ? Any help much appreciated.Thanks,Emile.

Thanks - looks like this utility is best left alone then. Guess with a quad core 3.4GHz CPU and ATI Radeon HD 5800 series with 1GB memory I won't have much to worry about anyway (well, better not, otherwise there will be a bit of explaining to do to my wife :( ).BTW I know native speakers of the language whose English is less good than yours (to put it mildly :( ) : you have nothing to apologise about IMHO.

Why would this be, Stefan ?I'm following this thread because I've just purchased a brand new quad core system and was thinking of using Multicore Environment to squeeze a bit more FSX performance out of it, but of course don't want to cause any damage. Hence my question.

Many thanks for leaving this thread up, Triple7. I came across exactly the same issue today when attempting to install ASX on my spare networked laptop and your solution worked for me as well :(

Hi Bryan, I've just done the tutorial flight and did not encounter any problems :( . The "fake" joystick buttons have been maintained in FS2CrewX.ini and the red & green ones that I assigned via FSUIPC work fine. FS2Crew enhances the experience tremendously IMHO !

I do not want FS2Crew to assign either the red or the green button function to any of my joystick buttons since all button numbers 1 to 25 are already in use (yeah, believe it or not :( ). Therefore I made the following changes in the [KeybJoySettings] section of the FS2CrewX.ini file :cbGreenJoy767=98cbRedJoy767=99Buttons 98 and 99 are non-existent on any of my controls (which consist of four extensively programmed Control Manager devices). Therefore I thought that doing this would ensure that FS2Crew won't do anything with existing joystick buttons. I have assigned the Green and Red button functions to two joystick buttons of my own choice through FSUIPC (I figured after reading a number of posts that trying to find out which is my "primary" joystick would be too much of a PITA :( ).The Start Centre loaded normally after this and just shows blanks for the Joystick Green Button and Red Button fields. But is what I have done likely to mess things up without me knowing :( ? Thanks a lot for any feedback.

Cool - thanks a lot :( Emile.

Damian,I don't know if this is of use to anyone now (or if I should be adding to this thread at all as I don't want to confuse anyone). But I started getting the same problem with ASX/FSX, on the weekend before last when VATSIM evidently were in the process of a server upgrade or had just completed it. Ever since then I've been experiencing this premature shutdown of Xengine as well. But I don't think the issue is related to Vista, because my PC runs XP. I did however discover that if I disabled VATSIM weather downloads in the ASX settings, the problem did NOT occur. Wish I'd read this thread before spending most of an afternoon finding that out for myself :( . Looking forward to the SP4 public beta : will its release be announced here ?Thanks,Emile.