FSX & Magenta ??

[Thomas Richter]

Another thing:
can you please post your Wideserver and Wideclient ini`s here in that thread to see maybe something jerkey there in mine ?
Just to compare mine with yours - would be nice

The way I create a WideClient.ini is by deleting it and starting WideClient, it creates a new one. That's it !
I don't use any "ServerName=" or "ServerIP=" settings!!
The WideClients find the WideServer by it self over the network, it is just itself created ini file with NO changes.
And my Server (FS9/FSX) is running Vista Home Premium 32, Clients are Windows 2000Pro, XP Pro and Vista Home Premium 32.
The WideServer.ini is as well only the self created one, no changes.

I have not deleted the orginal AP Gauge it´s a xml gauge what have for every switch a entry , but i deactivated the master AP switch
and APPR and some other AP related gauges and have the same result.

So you DON'T take care of the announced information! Why not?
The FSX default AP's has its own logic that cannot be overwritten by PM's MCP/FCU !!
If you don't remove, "Really remove", the lines with those logic gauges from your panel.cfg's you will EVER have problems and cry that PM has bugs in there software.

Please give your wife a steering wheel as well when YOU drive the car, if this will work then we are able to drive with two DIFFERENT working AP's !!

Any system gauges in FS9 and FSX has EVER to be removed, if not it would mean you are crying "Please give me a problem, it's so boring".

A/C's
There are also A/C's out they use there own build-in logic, built-in means it is part of its .air file. Like PMDG's 747 has and those A/C models are not useable (see above).
FSX's Airbus has as well a line in its CFG where the build-in FBW is activated and if it is active our FCU cannot control the A/C really effective because this system decreases the FCU controls in special situations where it is needed to control more hard, but then you have again problems.

So it is ever needed to follow our informations / instructions we give, it is not only some rubbish we spray out for fun. We testet those things ever on different places (Jonathan in the SIM, Enrico in Italy and me 500km north of Jonathan) and situations, and this means in many many hours (you know then each "gras-blade" of this test-area).

[JonathanRichardson]

>can you please post your Wideserver and Wideclient ini`s here in that thread to see maybe something jerkey there in mine ?
Just to compare mine with yours - would be nice

Honestly, it is not necessary and may lead to confusion. I tested this in my office set-up and the simulator - both situations worked.

>Would you try the aircraft ??

Afraid I don't have time. Plus I think the problem is that the FSX AP (as per Thomas' reply) is fighting PM. I would also advise trying a different model - perhaps there is something very bad in its config file - one never knows with third party models.

Regards
Jonathan Richardson

[brianwilliamson]

I still have not solved the problems yet. Did 4 ILS approaches in a row in FSX all 100 percent, and on the next take-off as soon as I engaged the Auto Pilot the aircraft went into an un-controlled pitch into the Earth !!
I then decided to re-load everything and try FS9, and on the second take-off, it was uncontollable as soon as I hit the Auto-pilot. So at the moment I am waiting to put the FCU on a spare computer, and see if I can find the problem from there.
Cheers..............Brian W.

[brianwilliamson]

While waiting for the key for the FCU to arrive I have been doing some circuits without the FCU. AND still problems. Turns out to be our old favorite............SIMBOARDS again !!
..............Brian W.

[Thomas Richter]

While waiting for the key for the FCU to arrive I have been doing some circuits without the FCU. AND still problems. Turns out to be our old favorite............SIMBOARDS again !!
..............Brian W.

Hi

In this case I would first check the Network, WitClient Logs (on that PC) and WideServer Log.
I would not search first for the problem on the SIMBOARDS hardware, the Network is ever the Key.

The problems are really most related to the Network and don't forget the Network works like the "Quiet Post".

Companies with more than 5 PC's in a Network have ever a Specialist on board who does this things at the same time of his normal job.
And greater companies need a Network Administrator who does nothing else than to manage the Network.

EACH software/hardware (PM, AST, Phidgets, Simboards and all others) that works over the Network can ONLY work as good as the Network does !!
And if you build in somewhere a "Funnel" it will only works up to the moment the funnel input is bigger than what can come out of the funnel mouth.
So only a clean and poor Network setup is the base of all.

And a big problem of course is to set up this Network because we/or others can only give a line.
Why ? Easy !!
Every one sets up his PC, sometime (safety, poor, easy ...).
And in any different installation of Windows (with/without/multiple password ...) the Network setup is totally different to give rights for clients, safety Network rights or not and and and ...
And in addition we have to fight with Vista, XP and 2000Pro all in one Network, and all with different needs and rights.

Btw - Our small tool pmFileCheck is not only to check the FsPlans folder and the NetDir folder, it checks the Network connectivity on that PC where it is running to FS-PC.
That means you need to run it on EACH Client when its PM program and FS is running, best is when all Clients and their programs are running at the same time. So you will see in the Logs of pmFileCheck where/on what Client are may be problems.
We see many times that customers have problems to "see" the FsPlans folder or FS folder, but only on one Client. Then they search for hours/days on FS-PC for problems and change things in the Network there. The result is ever that they get more problems because they search on the wrong end. E.g. in those cases the problem is direct on the Client PC (different Network handling) or just there is no right for that PC on the FS-PC. And again that is a indication that the Network setup is tooooo safety, if you need to give special rights. In addition it means that Windows ever checks the rights on communication with clients and that will slow down the communication speed of course.

So all in all, if you ever have problems check first your Network. E.g. transfer a 200 or more MB file from one PC to the other.
Is the transfer speed constant or slowing down up to the end ?
Do you see small pauses ?
All those easy things will help to find problems.

[Mario Görs]

Hello Thomas

Today i deleted / moved my Wideserver.ini in modules Folder
to let em Build a new one and saw after a conection over FSX and
Wideclient with PM ( after close all Progs ) no new one in the modules Folder

Is that normal ??

Did that with Wideclient .ini , too but after shutting down
there was a new .ini build as awaited.

Is Wideserver not making a new .ini File after close FSX ??

And here is my Wideserver .log is there anything wrong here ??


********* WideServer.DLL Log [version 7.205] *********
Blocksize guide = 4096 (double allowed)
Date (dmy): 20/12/07, Time 13:59:35.522: Server name is MARIOGOERS-IQC2
15772 Initialising TCP/IP server
15772 Initialising IPX/SPX server
_______________________________________
Is here something wrong ???
_______________________________________
15772 IPX/SPX socket() failed [Error=10047] Address family not supported by protocol family
15772 Failed to start IPX/SPX Server
15772 Initialising UDP/IP server
16099 Broadcasting service every 1000 mSecs
137640 Incoming connection Accepted ok (skt=8504) TCP
137640 Restarting service due to zero reception!
137640 Failed to start IPX/SPX Server
140650 Incoming connection Accepted ok (skt=6992) TCP
140744 Failed to start IPX/SPX Server
143614 Incoming connection Accepted ok (skt=8896) TCP
143895 Connected to computer "939-3500A64" running WideClient version 6.750 (skt=8896) TCP
1756368 Error 10053: client socket disconnected at Client: removing (skt=8896) TCP
1836787 Incoming connection Accepted ok (skt=8764) TCP
1836834 Connected to computer "939-3500A64" running WideClient version 6.750 (skt=8764) TCP
1942790 Error 10053: client socket disconnected at Client: removing (skt=8764) TCP
2034861 Incoming connection Accepted ok (skt=7984) TCP
2034955 Failed to start IPX/SPX Server
2039791 Incoming connection Accepted ok (skt=6992) TCP
2039931 Connected to computer "939-3500A64" running WideClient version 6.750 (skt=6992) TCP
2623235 Close signalled to clients
2624327 Closing down now ...
Memory managed: Offset records: 2408 alloc, 2407 free
Read buffer usage: 18426 alloc, 18426 free, max in session: 1
Write buffer usage: 47859 alloc, 47859 free, max in session: 1
Throughput maximum achieved: 22 frames/sec, 12061 bytes/sec
Throughput average achieved for complete session: 9 frames/sec, 2043 bytes/sec
Average receive rate from "939-3500A64": 9 frames/sec, 997 bytes/sec
********* Log file closed *********


regards
Mario Görs

[Thomas Richter]

Hello Thomas

Today i deleted / moved my Wideserver.ini in modules Folder
to let em Build a new one and saw after a conection over FSX and
Wideclient with PM ( after close all Progs ) no new one in the modules Folder

Is that normal ??

Did that with Wideclient .ini , too but after shutting down
there was a new .ini build as awaited.

Is Wideserver not making a new .ini File after close FSX ??

And here is my Wideserver .log is there anything wrong here ??


********* WideServer.DLL Log [version 7.205] *********
Blocksize guide = 4096 (double allowed)
Date (dmy): 20/12/07, Time 13:59:35.522: Server name is MARIOGOERS-IQC2
15772 Initialising TCP/IP server
15772 Initialising IPX/SPX server
_______________________________________
Is here something wrong ???
_______________________________________
15772 IPX/SPX socket() failed [Error=10047] Address family not supported by protocol family
15772 Failed to start IPX/SPX Server
15772 Initialising UDP/IP server
16099 Broadcasting service every 1000 mSecs
137640 Incoming connection Accepted ok (skt=8504) TCP
137640 Restarting service due to zero reception!
137640 Failed to start IPX/SPX Server
140650 Incoming connection Accepted ok (skt=6992) TCP
140744 Failed to start IPX/SPX Server
143614 Incoming connection Accepted ok (skt=8896) TCP
143895 Connected to computer "939-3500A64" running WideClient version 6.750 (skt=8896) TCP
1756368 Error 10053: client socket disconnected at Client: removing (skt=8896) TCP
1836787 Incoming connection Accepted ok (skt=8764) TCP
1836834 Connected to computer "939-3500A64" running WideClient version 6.750 (skt=8764) TCP
1942790 Error 10053: client socket disconnected at Client: removing (skt=8764) TCP
2034861 Incoming connection Accepted ok (skt=7984) TCP
2034955 Failed to start IPX/SPX Server
2039791 Incoming connection Accepted ok (skt=6992) TCP
2039931 Connected to computer "939-3500A64" running WideClient version 6.750 (skt=6992) TCP
2623235 Close signalled to clients
2624327 Closing down now ...
Memory managed: Offset records: 2408 alloc, 2407 free
Read buffer usage: 18426 alloc, 18426 free, max in session: 1
Write buffer usage: 47859 alloc, 47859 free, max in session: 1
Throughput maximum achieved: 22 frames/sec, 12061 bytes/sec
Throughput average achieved for complete session: 9 frames/sec, 2043 bytes/sec
Average receive rate from "939-3500A64": 9 frames/sec, 997 bytes/sec
********* Log file closed *********


regards
Mario Görs

1. FSX WideServer don't has its own ini file, it is part of FSUIPC4.ini with its own section "[WideServer]".

2. Did you run and closed the WideClient on "939-3500A64"-PC multiple times manually?

[Peter Dowson]

Is Wideserver not making a new .ini File after close FSX ??

The FSX version of WideServer is built into FSUIPC4, and, as Thomas says, its parameters are in a section of the FSUIPC4.INI file. You shouldn't have any WideServer files in the FSX Modules folder excepting its Log.

And here is my Wideserver .log is there anything wrong here ??

Probably not. This part:

15772 IPX/SPX socket() failed [Error=10047] Address family not supported by protocol family
15772 Failed to start IPX/SPX Server

only means you haven't installed the IPX/SPX protocol in Windows, but that doesn't matter if you aren't using it (which you are not).

This errors:

137640 Restarting service due to zero reception!

is probably only occurring because FSX and WideServer wasn't ready at that time.

143895 Connected to computer "939-3500A64" running WideClient version 6.750 (skt=8896) TCP

It won't be any different for you, I suspect, but there is a later version of WideClient (6.757) available in the Downloads announcements on my Support Forum.

1756368 Error 10053: client socket disconnected at Client: removing (skt=8896) TCP

You had two of these. Were they due to you closing and restarting Wideclient?

Incidentally, the WideServer log is only part of the story. You really need to look at the WideClient log too. Maybe there are errors at that end?

Finally:

Throughput maximum achieved: 22 frames/sec, 12061 bytes/sec
Throughput average achieved for complete session: 9 frames/sec, 2043 bytes/sec

Is your FSX frame rate averaging between 9 and 22 fps? That last figure seems a bit low, but of course that includes two longish periods with no connection. The figures reported in the WideClient log should show something close to your average FSX frame rate.

Anyway, so far, no specific problems to be seen.

Regards

Pete

[Mario Görs]

Pete

Thanks for fast reply

> You had two of these. Were they due to you closing and restarting Wideclient?

I think it was - doeing some testing

> Finally:

Throughput maximum achieved: 22 frames/sec, 12061 bytes/sec
Throughput average achieved for complete session: 9 frames/sec, 2043 bytes/sec

Is your FSX frame rate averaging between 9 and 22 fps? That last figure seems a bit low, but of course that includes two longish periods with no connection. The figures reported in the WideClient log should show something close to your average FSX frame rate.

It looks like this in the Wideclient.log:

6027498 ****** End of session performance summary ******
6027498 Total time connected = 6025 seconds
6027498 Reception maximum: 22 frames/sec, 15215 bytes/sec
6027498 Reception average whilst connected: 18 frames/sec, 538 bytes/sec
6027498 Transmission maximum: 53 frames/sec, 3400 bytes/sec
6027498 Transmission average whilst connected: 37 frames/sec, 156 bytes/sec
6027498 Max receive buffer = 1126, Max send depth = 10, Send frames lost = 0

So looks like this part is not bad ??
maybe should be DL the newer Wideclient for see if ther is something different !

So , Thanks a lot

regards
Mario Görs

[Peter Dowson]

It looks like this in the Wideclient.log:

6027498 ****** End of session performance summary ******
6027498 Total time connected = 6025 seconds
6027498 Reception maximum: 22 frames/sec, 15215 bytes/sec
6027498 Reception average whilst connected: 18 frames/sec, 538 bytes/sec
6027498 Transmission maximum: 53 frames/sec, 3400 bytes/sec
6027498 Transmission average whilst connected: 37 frames/sec, 156 bytes/sec
6027498 Max receive buffer = 1126, Max send depth = 10, Send frames lost = 0

So looks like this part is not bad ??

Correct. 18 fps is quite good for FSX -- is that what you are seeing, on average?

There are no connection problems showing up at all, judging by these logs. Did you still notice something awry, or were these just lucky flights?

maybe should be DL the newer Wideclient for see if ther is something different !

I don't think there's anything wrong that it would fix, but I do always prefer folks to be using the latest in any case.

Regards

Pete