Simconnect.xml comprises a number of
"modules" Each one slooks like this.
<SimConnect.Comm>
<Disabled>False</Disabled>
<Protocol>Auto</Protocol>
<Scope>global</Scope>
<Address>*192.168.0.2*</Address>
<MaxClients>64</MaxClients>
<Port>4506</Port>
<MaxRecvSize>4096</MaxRecvSize>
<DisableNagle>False</DisableNagle>
</SimConnect.Comm>
The
above is for Plan-G (Port 4506). You MUST open a different fort for
Teamspeak.
Teamspeak uses Port 8767 by default
e.g.
<Port>8767</Port>
You
can't use the same port for two applications at the same time.
So
your Simconnect file must contain two modules as below
<SimConnect.Comm>
<Disabled>False</Disabled>
<Protocol>Auto</Protocol>
<Scope>global</Scope>
<Address>*192.168.0.2*</Address>
<MaxClients>64</MaxClients>
<Port>4506</Port>
<MaxRecvSize>4096</MaxRecvSize>
<DisableNagle>False</DisableNagle>
</SimConnect.Comm>
<SimConnect.Comm>
<Disabled>False</Disabled>
<Protocol>Auto</Protocol>
<Scope>global</Scope>
<Address>*192.168.0.2*</Address>
<MaxClients>64</MaxClients>
<Port>8767</Port>
<MaxRecvSize>4096</MaxRecvSize>
<DisableNagle>False</DisableNagle>
</SimConnect.Comm>
Don't
forget to put the header and footer on your simconnect file. The Plan-G
Manual has all the details in Chapter 20.3.1. What it says in there
applies to
more than just Plan-G so is worth reading. ;-)
The IP
address 192.168.0.2 is the IP address of the FSX PC. Yours may be
different.
Whatever it is, if you can, you should reserve the address in your
router
for the FSX PC. I can help further on this if necessary.
If you
want to cover your backside, add two more modules identical to the
above,
but change
<Protocol>Auto</Protocol>
to
<Protocol>IPv4</Protocol>
in
both.
They may be redundant, but they cost nothing to include, and
sometimes "Auto"
doesn't work.
Having said all the above, I
couldn't get IvAp to work across my network, but I
don't think I
installed the SDK on my non-FSX PC. That is probably vital as it
includes
the simconnect.dll module which drives it all. Having the correct
version
of simconnect.dll is vital for success. If you have SP2 FSX, you need
SP2
SDK installed as well.
I agree it's a nightmare, but that's the
unfinished symphony called FSX I'm afraid.
Peter
>
--------------------------------------------------------------------------------
>
>
Frank Turley
<mailto:frank.turley1@xxxxxxxxxxxx>> 06 May
2012 14:34
>
>
> Hi Paul,
>
> When I set
up the link for Plan-G, all I had to do re Simconnect was to edit
>
and save a simple .XML file in the FSX folder in the AppData directory
tree. I
> used a standard template, I just had to edit the IP
address and the Port No.
> If Simconnect is already sending the
right FSX data to the right port, I would
> have thought that the
IvAp installation routine running on a slave machine
> would be
able to allow for this already being in place, and allow you to skip
>
this step, rather than terminate the installation.
>
> Of
course, I did have to set up matching parameters in the Plan-G options,
in
> a parallel way to that set up on the multi-options tab of
the IvAp software.
>
> Frank T.
>
>
>
>
>
>
--------------------------------------------------------------------------------
>
>
Paul Reynolds
<mailto:paul@xxxxxxxxxxxxxxxxxxx>> 06 May
2012 13:20
>
>
> Actually putting the SDK on the
second machine would only have been
> necessary to get to each
version of SimConnect. If you've had FSX with the
> SDK installed
on your FSX PC as the versions progressed then it would seem
>
reasonable that you would have used each version of the SimConnect
installer
> on the remote PC so it would have progressed at the
same time as each one
> was upgraded. The process of installing
the three versions on the remote PC
> was simply to get to the
same point but without impacting on your FSX PC.
>
> Once
you have the required version of SimConnect running you can then remove
>
the SDK itself if you don't need it.
>
> Paul
>
>
-----Original Message-----
> From:
jhb-bounce@xxxxxxxxxxxxx
[
mailto:jhb-bounce@xxxxxxxxxxxxx] On Behalf
> Of Frank Turley
>
Sent: 06 May 2012 08:08
> To:
jhb@xxxxxxxxxxxxx> Subject:
[jhb] Re: Teamspeak on Not FSX IVAO PC?
>
>
> Hi Paul,
>
>
Wow, I don't want to clutter up machine 2 with the SDK. Its a shame
>
IVAO don't allow you to set up the part just needed for the remote
>
Teamspeak easily, I'm guessing that anyone using Simconnect for
>
another function is going to struggle like me.
>
> In the
circumstances I think the option of moving the headset across
> to
the FSX machine is the easiest option.
>
> Thanks for your
help.
>
> Frank T.
>
>
>
>
>
--------------------------------------------------------------------------------
>
>
Frank Turley
<mailto:frank.turley1@xxxxxxxxxxxx>> 06 May
2012 08:08
>
>
> Hi Paul,
>
> Wow, I don't
want to clutter up machine 2 with the SDK. Its a shame IVAO don't
>
allow you to set up the part just needed for the remote Teamspeak
easily, I'm
> guessing that anyone using Simconnect for another
function is going to
> struggle like me.
>
> In the
circumstances I think the option of moving the headset across to the
>
FSX machine is the easiest option.
>
> Thanks for your
help.
>
> Frank T.
>
>
>
>
>