Page 1 of 1

Whazzup Issue with Ver 3

Posted: Sat Jul 10, 2021 2:25 pm
by canuck21a
Since I changed from Ver 2.2.6 to 3.0.0 my hub's whazzup.txt file is not containing the departure/arrival nor the correct models for connected clients.

When I check the whazzup file on the client it shows the correct values; however, when I then look at the result on the hub the depature/arrival/model are incorrect. Also other clients, when checking the aircraft list also do not see other details as they should be.

I have tried using 3.0.3T on two clients hoping that they would show each others details correctly. This did not happen.

Is this likely due to the hub having an issue? I did not try 3.0.3T as the hub as it is presently in use.

The hub's whazzup file (limited to top items)
//////////////////////////////////////////////////////////////////////////////////////////////////////////////////////
!GENERAL
VERSION = 1
RELOAD = 1
UPDATE = 20210710092422
CONNECTED CLIENTS = 5
CONNECTED SERVERS = 29
!CLIENTS
GCVYE:StuartMac:StuartMac:PILOT::63.4022920713107:-20.0777252637051:21506:353:/C172:::::JoinFS:::0::::VFR:::::::::::::::::303:::
HH210:cap3:cap3:PILOT:113.5.:63.9824658669077:-22.6505796154973:137:0:/C172:::::JoinFS:::0::::VFR:::::::::::::::::132:::
DVC1720:DVC1720:DVC1720:PILOT:112.3.:49.0981935614921:-124.386633205676:5202:113:/C172:::::JoinFS:::5072::::VFR:::::::::::::::::283:::
N1716B:DW1716:DW1716:PILOT:112.8.:48.5255213455312:-123.026338750547:116:0:/C172:::::JoinFS:::1200::::VFR:::::::::::::::::268:::
N208EH:DV1716D:DV1716D:PILOT:112.8.:48.5237983614252:-123.026245292269:118:0:/C172:::::JoinFS:::1200::::VFR:::::::::::::::::269:::

!SERVERS
///////////////////////////////////////////////////////////////////////////////////////////////////////////////////
Hub-JoinFS-300-1024.jpg
Hub-JoinFS-300-1024.jpg (134.31 KiB) Viewed 6810 times
FSX-JoinFS_300.jpg
FSX-JoinFS_300.jpg (190.36 KiB) Viewed 6810 times
P3D-JoinFS-300-900.jpg
P3D-JoinFS-300-900.jpg (211.71 KiB) Viewed 6810 times

Re: Whazzup Issue with Ver 3

Posted: Sat Jul 10, 2021 2:35 pm
by Peter
Ok, thanks for finding that. It will be due to the information now being obtained via the variables. Must have missed the bit of code that propagates those values.

Will get a fix in v3.0.4

Peter

Re: Whazzup Issue with Ver 3

Posted: Sat Jul 10, 2021 6:16 pm
by canuck21a
Thanks Peter !

Re: Whazzup Issue with Ver 3

Posted: Wed Jul 21, 2021 12:00 pm
by canuck21a
May I infer that the new Beta 3.0.4 will rectify this situation?

Re: Whazzup Issue with Ver 3

Posted: Wed Jul 21, 2021 12:08 pm
by Peter
Hopefully 3.0.5. ;)

Peter

Re: Whazzup Issue with Ver 3

Posted: Wed Jul 21, 2021 9:51 pm
by canuck21a
Alrighty then,
Maybe next month.

Re: Whazzup Issue with Ver 3

Posted: Mon Jul 26, 2021 8:50 pm
by canuck21a
Greetings Peter,
I tried Ver 3.0.6 today on my client PC and my hub.
Things are look better but not showing what I expected.
Was it something I did or did not do this time?
The flight plan is not showing up on the hub

The website map now shows the model but no flight plan:
CyberpowerPC-JoinFS-Map-306-2021-07-26.jpg
CyberpowerPC-JoinFS-Map-306-2021-07-26.jpg (15.32 KiB) Viewed 6695 times
My client PC seems to show the flight plan:
CyberpowerPC-JoinFS-Whazzup-306-2021-07-26.jpg
CyberpowerPC-JoinFS-Whazzup-306-2021-07-26.jpg (39.76 KiB) Viewed 6695 times
The hub screen showing all of the items:
T510-JoinFS-306-2021-07-26-1920.jpg
T510-JoinFS-306-2021-07-26-1920.jpg (255.43 KiB) Viewed 6695 times
Need more files?

Re: Whazzup Issue with Ver 3

Posted: Mon Jul 26, 2021 9:14 pm
by Peter
I was rather hoping that would fix it. Could you try temporarily disabling hub mode, and instead just create a normal session. Have the client PC connect to that session (should be able to connect by local IP address) and see if you can get the flight plan appearing in the whazzup. Because that situation worked for me here when I tested it.

Peter

Re: Whazzup Issue with Ver 3

Posted: Tue Jul 27, 2021 11:43 am
by canuck21a
I shall do as you have asked a bit later when I have a chance to do some testing.

Re: Whazzup Issue with Ver 3

Posted: Tue Jul 27, 2021 6:54 pm
by canuck21a
Update:
Tried a few things today.

1. I disabled hub mode on my stand-alone PC that is used for multi-connect.
1a. Made sure that both client and target were using 3.0.6
1b. Created a numbered session to connect to on the hub PC.
1c. The client when connected had a whazzup file that contained the model and flight plan but the target although showing the model had no flight plan.

2. I decided to try between two clients with the target PC (hub) disabled; one an FSX system and the other MSFS
2a. One client (MSFS) was set to be the point of contact so a session was created.
2b. The FSX system then used that session value to connect.
2c. Once again the local client saw its flight plan but the remote did not.

Truncated whazzup files from test 2

!GENERAL
VERSION = 1
RELOAD = 1
UPDATE = 20210727143738
CONNECTED CLIENTS = 3
CONNECTED SERVERS = 35
!CLIENTS
DVC1716:::PILOT:112.4.:44.2126387178598:15.1666366212402:40:0:/C172::LD57::LDZD:JoinFS:::7000::::IFR:::::::::::::::::114:::
N208EH:DV1716D:DV1716D:PILOT:112.8.:44.2057617008043:15.1613267697376:48:0:/C208:::::JoinFS:::1200::::VFR:::::::::::::::::017:::
AEE453:::PILOT::44.1576962416129:14.6358422488186:34945:0:/C172:::::JoinFS:::0::::VFR:::::::::::::::::126:::
!SERVERS

!GENERAL
VERSION = 1
RELOAD = 1
UPDATE = 20210727143702
CONNECTED CLIENTS = 2
CONNECTED SERVERS = 34
!CLIENTS
N208EH:::PILOT:112.8.:44.2057617008043:15.1613267697376:65:0:/C208::LD57::LDDU:JoinFS:::1200::::VFR:::::::::::::::::017:::
DVC1716:DVC1716:DVC1716:PILOT:112.4.:44.2126387178598:15.1666366212402:63:0:/C172:::::JoinFS:::7000::::IFR:::::::::::::::::114:::
!SERVERS


Not sure what to do at this point..............

Re: Whazzup Issue with Ver 3

Posted: Tue Jul 27, 2021 7:27 pm
by Peter
Ah, it could be to do with the new variables as well. Could you try editing the flight plan in the JoinFS aircraft window to manually set the from/to details? Then see if that appears on the other machine's whazzup.

Peter

Re: Whazzup Issue with Ver 3

Posted: Wed Jul 28, 2021 12:40 pm
by canuck21a
I am somewhat confused by the request.
Are you suggesting that on system 1 that shows the correct values in whazzup that I change the joinfs values to be the same DEP/ARR to see if they then somehow propagate to the remote system2 ?

System 1
Local ->DVC1716:::PILOT:112.4.:44.2126387178598:15.1666366212402:40:0:/C172::LD57::LDZD:JoinFS:::7000::::IFR:::::::::::::::::114:::
Remote ->N208EH:DV1716D:DV1716D:PILOT:112.8.:44.2057617008043:15.1613267697376:48:0:/C208:::::JoinFS:::1200::::VFR:::::::::::::::::017:::

System2
Local ->N208EH:::PILOT:112.8.:44.2057617008043:15.1613267697376:65:0:/C208::LD57::LDDU:JoinFS:::1200::::VFR:::::::::::::::::017:::
Remote ->DVC1716:DVC1716:DVC1716:PILOT:112.4.:44.2126387178598:15.1666366212402:63:0:/C172:::::JoinFS:::7000::::IFR:::::::::::::::::114:::

Re: Whazzup Issue with Ver 3

Posted: Wed Jul 28, 2021 12:59 pm
by Peter
Are you setting the flight plan using JoinFS or is it getting the from/to from the simulator? If you open the aircraft window in JoinFS you can select the aircraft, right-click, select 'Edit Flight Plan' and change the from/to data for that aircraft. Try doing that and see if the data then propagates to the other machine.

Peter

Re: Whazzup Issue with Ver 3

Posted: Wed Jul 28, 2021 9:20 pm
by canuck21a
Thanks for the confirmation. I shall try what you have asked with and without a loaded fight plan. It may not be until Friday as MSFS SU5 is taking much of my free time to sort.

Re: Whazzup Issue with Ver 3

Posted: Thu Jul 29, 2021 9:14 pm
by canuck21a
I did find some time today to test "File Flight Plan..." option.
First I started MSFS with no plan and connected to my normal 'hub'.
I then opened Aircraft and selected the file flight plan option. I made an entry and accepted.
I then turned to my hub and saw that there was now a DEP/ARR as well as a plan in its joinfs aircraft list.
I also checked my web map and the details were as I had hoped they would be.

I then restarted the flight and added a plan using World Map. When it connected to the hub there was no DEP/ARR.
I then refiled the joinfs plan and then it appeared. (Note that the DEP/ARR were blank when I opened the file flight plan dialogue box)

So I guess that things are working but something is getting skipped during the process of grabbing and sending the DEP/ARR?

Re: Whazzup Issue with Ver 3

Posted: Thu Jul 29, 2021 9:48 pm
by Peter
Ok, thanks. That confirms my findings. I think it might be just the DEP/ARR not getting picked up because they are now accessed using the new variables. Should hopefully be an easy fix.

Peter

Re: Whazzup Issue with Ver 3

Posted: Tue Aug 03, 2021 2:26 pm
by canuck21a
I just tried v 3.0.7 on client and hub.
No change.
I had to use the file flight plan option in client side Aircraft to get it to update.

Re: Whazzup Issue with Ver 3

Posted: Tue Aug 03, 2021 2:30 pm
by Peter
canuck21a wrote: Tue Aug 03, 2021 2:26 pm I just tried v 3.0.7 on client and hub.
No change.
I had to use the file flight plan option in client side Aircraft to get it to update.
There was no bug fix for this in 3.0.7. Please check the release notes, https://joinfs.net/install.html, thanks.

Peter