WorldFlight 2015

[Britjet]

Correct! You can't affect anything..

[cagarini]

Ok!

I'll take a look anytime soon :-)
Thx "Britjet"

[Gary Oliver]

Yep no problems at all jcomm.

[cagarini]

Unfortunately, setting in "Preferences / Basics", under "Main network":

"This client connects to: 52.30.35.172",  "On port: 10747",  and then under "Network / Main" trying to choose "A main client" I get a cyclic error message: Version disagree: 10.0.6a Navtech, Inc. (cycle 1503) :-(

[Britjet]

You need to update to version 6a?

Peter

[cagarini]

Peter,

I'm on 10.0.6a already, since it was made available last week.

[Britjet]

I'm not an expert on these things of course - but the guys are definitely using 6a and I can connect OK.
You are sure that you have 6a and not 6?
Version mismatch can be the only cause I can think of...

[Britjet]

@asboyd:-

Just be clear - you can connect to the read-only stream and then use your PSX instance as a boost server to P3D ver 2.5 via VisualPSX and the P3D scenery is stable? (Is no constant re-loading).

Peter

[Hardy Heinlin]

Version disagree: 10.0.6a Navtech, Inc. (cycle 1503)

This means PSX 10.0.6a and navigation database Navtech cycle 1503 are required. These versions are essential for network synchronization.

[cagarini]

Version disagree: 10.0.6a Navtech, Inc. (cycle 1503)

This means PSX 10.0.6a and navigation database Navtech cycle 1503 are required. These versions are essential for network synchronization.

Thx Hardy,

I guess that cycle is the one which can be bought as an optional add-on from Aerosoft, because other than that I am running 10.0.6a, I see.

[Hardy Heinlin]

Here's the nav database update:

http://aerowinx.com/board/index.php?topic=2631.0

[cagarini]

Thx!

Problem solved :-)

Now connected and watching, for the first time since I use PSX, a "paper" from the flightdeck printer ...

P.S.: And indeed, can't make a stable connection to FSX:SE through VisualPSX :-/
Did anyone with XView have success ?

[Mark]

If anyone out there who is having issues with VisualPSX are experts at debugging - please see if you can identify if there is a particular PSX network variable (or lack of) that is triggering the problem?

[evaamo]

Just watched Britjet land at Kai Tak, very cool landing! Very immersive in Gary's full simulator.

Very interesting hearing Peter's explanation. The jettison was cool as well.

Looking forward to flying along with you guys during the week! It's been a while since I've done any online flying!

cheers
-E

[Panos Bilios]

Perfect Kai Tak landing Peter!
very entertaining


Panos

[Jan]

Today After startup PSX client 52.30.35.172 port 10747.
PSX starts with "FATAL ERROR"
What is wrong ?

[Jan]

sorry I mean "FATAL DAMAGE

[Mark]

SwitchPSX restarted, how is it now?

[Hardy Heinlin]

Off-topic tip: Wing anti-ice is inhibited when the flaps are out :-)

[Mark]

Hardy,

When Hessel joined, I captured this debug data (this is everything his client attempted to send to the server):

Code Select Expand

New Client!
Client: 2 Lexicon sent!
CLIENT IN: Qs352=URL;ORN;11420A720;11360A720;03090F;03310F;10970A240;10970A240;10970A240;;;;;;
CLIENT IN: Qi225=2000
CLIENT IN: Qi130=1
CLIENT IN: Qs352=URL;ORN;11420A720;11360A720;03090F;03310F;10970A230;10970A230;10970A230;;;;;;
CLIENT IN: Qs108=121800;121950;137000;132940;118950;121800;22786;22607;23999;18701;100;100;0;0
CLIENT IN: Qs107=121800;121950;137000;132940;118950;121800;22786;22607;23999;18701;100;100;0;0
CLIENT IN: Qi208=6882
CLIENT IN: Qs425=487;487;487;487;487;487;73;73;73;73
CLIENT IN: Qs439=111277;110204;110245;111024;0;0;0;0;0;
CLIENT IN: Qs451=0;0;0;0;33;322;0;0;0;0;0;0;0;0;0;0;0;0;0;0;0;
CLIENT IN: Qs450=0.0;0.0;6142;0;0.9109275020154136;0.9530741748555953;320460;30680;0.0;0.0;6142;0;0.0;0.0;6142;0;0.0;0.0;6142;0;0.0;0.0;6142;0;0.0;0.0;6142;0;
CLIENT IN: exit
EXIT from client

This isn't the full picture as it would be useful to see what a client is receiving from the server; when I get to the sim later I'll run PSX on a standalone machine and connect it to the public read-only IP through a man-in-the-middle debug logger. (I'll quickly code one up... how hard can it be?!)

You never know; there might be a clue in what I captured above, Qi225 and Qi130 (undocumented) look interestingly relevant...