[jhb] Re: FSX add-ons - some progress
- From: "Paul Reynolds" <paul@xxxxxxxxxxxxxxxxxxx>
- To: <jhb@xxxxxxxxxxxxx>
- Date: Mon, 10 Nov 2008 17:37:41 -0000
Jus to add to the SimConnect tale, if you were to install Active Sky X, it
insists on using the correct version of SimConnect. As I prefer to run this
on a remote machine, I had to go through the rigmarole of installing the
original SimConnect module, then SP1's version and finally SP2's (or
Acceleration in my case). This needs to be done for both flying and
non-flying machines. A right PITA.
Paul
-----Original Message-----
From: jhb-bounce@xxxxxxxxxxxxx [mailto:jhb-bounce@xxxxxxxxxxxxx] On Behalf
Of Mike Lucas
Sent: 10 November 2008 16:28
To: jhb@xxxxxxxxxxxxx
Subject: [jhb] FSX add-ons - some progress
I have to say that banging my head against a brick wall wasn't half
sore, but things are much better now that I have demolished the wall.
After another stiff drink, lie down, darkened room (I managed without
the nurse and the screens this time, Paul) I can report some progress
with WideFS and the IVAO pilot client.
The problem with WideFS turned out to be a fairly simple one - a short
but critical line missing from wideclient.ini (the default version)
which cues the TCP connection. I spotted this when I looked at the
corresponding ini file for my working FS9 WideFS setup.
With IvAp over my LAN it took rather longer to work out where I was
going wrong. A fairly cryptic error message when I tried to connect my
laptop to my FS machine alerted me to something called SimConnect, which
my laptop required but couldn't find. A little bit of research revealed
that this is included in FSX's SDK - which therefore had to be
installed. Ah, but - its version has to match the version of FSX
installed: so that meant SP1 and SP2 for the SDK. After installing
these I tried again for an IvAp connection from laptop to FSX PC - still
the same error: looking for SimConnect. Then Frank F suggested that
*BOTH* laptop *AND* FSX PC need SimConnect (OK - perhaps I should have
thought of that). So install SDK, SP1 and SP2 again on second machine.
Getting excited now - this should work ..... , but - no. IvAp *still*
could not find SimConnect. Then I had my Eureka moment - SimConnect
should have been installed *BEFORE* the IVAO pilot client. So uninstall
IvAp, then re-install it - and, yes, a message during installation that
it had detected SimConnect. I should point out that, during the initial
installation, there had been no message saying SimConnect installation
needed first. At last my laptop will talk IvAp with my FSX machine,
although I have yet to enter my user data and connect to IVAO (I think I
have had enough excitement for this afternoon).
I know we're all guilty at some time of not taking the time to RTFM.
But the problem here is that there is no FM that I can find to read for
the FSX IvAp client (version 1.98) on the IVAO web site - certainly not
one included with the software download. The manual for the FS9 version
(v 1.38) does not cover the crucial SimConnect issue.
Grrrrr
Mike L
Other related posts:
