1.4.20 - Whazzup
1.4.20 - Whazzup
I installed this newer version today over an existing 1.4.18 on my club hub.
When started the whazzup file was being updated but none of the clients appeared in the file although it appeared that the client count was being updated
I uninstalled and put 1.4.18 back in and the whazzup file then started showing clients from both 1.4.18 and 1.4.20.
Something I did wrong again ?
When started the whazzup file was being updated but none of the clients appeared in the file although it appeared that the client count was being updated
I uninstalled and put 1.4.18 back in and the whazzup file then started showing clients from both 1.4.18 and 1.4.20.
Something I did wrong again ?
Re: 1.4.20 - Whazzup
I've had this before.
I normally tick and UNTICK the whazzup box and restart the App until the whazzup file populates.
I don't think it's isolated to version 1.4.20 (although I may be wrong) and I've never thought it a problem, as the clients have always appeared in the end.
I put it down to running my JoinFS on linux, which is slightly uncharted territory.
I normally tick and UNTICK the whazzup box and restart the App until the whazzup file populates.
I don't think it's isolated to version 1.4.20 (although I may be wrong) and I've never thought it a problem, as the clients have always appeared in the end.
I put it down to running my JoinFS on linux, which is slightly uncharted territory.
Re: 1.4.20 - Whazzup
Ok,
I shall try that at my next opportunity.
I shall try that at my next opportunity.
Re: 1.4.20 - Whazzup
Hi,
We (CyberAvia) have made the upgrade of the joinFS server from 1.4.18 to 1.4.20
I try the trick of ATC Roo, but netherless, no aircraft on the map.
Is there any other action to do to make the map work again ?
Basicaly, it is the whazzup file wich is empty of aircraft (server list is ok).
Thks for the help
We (CyberAvia) have made the upgrade of the joinFS server from 1.4.18 to 1.4.20
I try the trick of ATC Roo, but netherless, no aircraft on the map.
Is there any other action to do to make the map work again ?
Basicaly, it is the whazzup file wich is empty of aircraft (server list is ok).
Thks for the help
Re: 1.4.20 - Whazzup
I think this is related to this similar bug, viewtopic.php?f=2&p=4450#p4450
I'll try to get a fix in 1.4.21, but be careful because that version will have some heavy changes.
Peter
I'll try to get a fix in 1.4.21, but be careful because that version will have some heavy changes.
Peter
Re: 1.4.20 - Whazzup
Thanks Peter,
I shall tread carefully.
I still use 1.4.18 as my central hub and source for my map although I am using 1.4.20 on some test clients.
I shall tread carefully.
I still use 1.4.18 as my central hub and source for my map although I am using 1.4.20 on some test clients.
Re: 1.4.20 - Whazzup
Hello Peter,lerak wrote:Hi,
We (CyberAvia) have made the upgrade of the joinFS server from 1.4.18 to 1.4.20
I try the trick of ATC Roo, but netherless, no aircraft on the map.
Is there any other action to do to make the map work again ?
Basicaly, it is the whazzup file wich is empty of aircraft (server list is ok).
Thks for the help
We've installed the version 1.4.22 test this evening and everything works fine now.
Many thanks, in the name of CyberAvia, for your great support.
Best Regards
Marc from CyberAvia Staff
Last edited by Timonier on Tue Jan 15, 2019 1:12 am, edited 1 time in total.
Re: 1.4.20 - Whazzup
Thanks for the update, Marc. Glad it's back to normal.
Peter
Peter
Re: 1.4.20 - Whazzup
We
Flybywires are having the same issue.
I do not see a downloadable version 1.4.22 may we have it as well?
Flybywires are having the same issue.
I do not see a downloadable version 1.4.22 may we have it as well?
Re: 1.4.20 - Whazzup
That's the current development build, not for general use I'm afraid. There should be a new stable version 1.4.23 out on Monday so long as nothing bad is reported.justme wrote: I do not see a downloadable version 1.4.22 may we have it as well?
Peter
Re: 1.4.20 - Whazzup
Just checking Peter.
But do you know that the callsign is missed from some of the lines in the whazzup?
Both in .20 and development .23
But do you know that the callsign is missed from some of the lines in the whazzup?
Both in .20 and development .23
Code: Select all
!GENERAL
VERSION = 1
RELOAD = 1
UPDATE = 20190120122643
CONNECTED CLIENTS = 7
CONNECTED SERVERS = 3
!CLIENTS
:Roo:Roo:PILOT::53.5553334084273:-6.20796530103432:21000:428:/B739::EGNR::EIDW::::0431::::IFR:::::::::::::::JoinFS:::::::072:::
LFTW_TWR:::ATC:122.800:43.7574424743652:4.41634702682495:0:0::::::::::4:84:::::::::::::::::::::::::::
FGIKS:FCY-BPT (Bernard 21):FCY-BPT (Bernard 21):PILOT::42.774974822998:-4.54264402389526:4996:144:/DR400::LPPR::LEBB::::4221::::IFR:::::::::::::::JoinFS:::::::061:::
FCYNU:FCY-DML:FCY-DML:PILOT::63.7076568603516:-55.1799163818359:33461:486:/B744::LFPG::KLAX::::1200::::IFR:::::::::::::::JoinFS:::::::258:::
VETiTi:Echter:Echter:PILOT::41.2378273010254:-8.67297744750977:232:0:/B738::::::::1200::::VFR:::::::::::::::JoinFS:::::::079:::
N307AS:BLEW:BLEW:PILOT::33.1924018859863:-95.500358581543:36446:366:/B739::::::::1200::::VFR:::::::::::::::JoinFS:::::::310:::
FCYJGT:VE-NANEX:VE-NANEX:PILOT::41.2372093200684:-8.6727409362793:232:0:/at72::LPMA::LPPR::::4274::::IFR:::::::::::::::JoinFS:::::::081:::
!SERVERS
Re: 1.4.20 - Whazzup
Do you mean the line with ATC?ATC Roo wrote:Just checking Peter.
But do you know that the callsign is missed from some of the lines in the whazzup?
Both in .20 and development .23
Code: Select all
!GENERAL VERSION = 1 RELOAD = 1 UPDATE = 20190120122643 CONNECTED CLIENTS = 7 CONNECTED SERVERS = 3 !CLIENTS :Roo:Roo:PILOT::53.5553334084273:-6.20796530103432:21000:428:/B739::EGNR::EIDW::::0431::::IFR:::::::::::::::JoinFS:::::::072::: LFTW_TWR:::ATC:122.800:43.7574424743652:4.41634702682495:0:0::::::::::4:84::::::::::::::::::::::::::: FGIKS:FCY-BPT (Bernard 21):FCY-BPT (Bernard 21):PILOT::42.774974822998:-4.54264402389526:4996:144:/DR400::LPPR::LEBB::::4221::::IFR:::::::::::::::JoinFS:::::::061::: FCYNU:FCY-DML:FCY-DML:PILOT::63.7076568603516:-55.1799163818359:33461:486:/B744::LFPG::KLAX::::1200::::IFR:::::::::::::::JoinFS:::::::258::: VETiTi:Echter:Echter:PILOT::41.2378273010254:-8.67297744750977:232:0:/B738::::::::1200::::VFR:::::::::::::::JoinFS:::::::079::: N307AS:BLEW:BLEW:PILOT::33.1924018859863:-95.500358581543:36446:366:/B739::::::::1200::::VFR:::::::::::::::JoinFS:::::::310::: FCYJGT:VE-NANEX:VE-NANEX:PILOT::41.2372093200684:-8.6727409362793:232:0:/at72::LPMA::LPPR::::4274::::IFR:::::::::::::::JoinFS:::::::081::: !SERVERS
Peter
Re: 1.4.20 - Whazzup
Top line under !Clients
MISSING_CALLSIGN: Roo:Roo:etc etc
MISSING_CALLSIGN: Roo:Roo:etc etc
Re: 1.4.20 - Whazzup
Hi,
Today I installed the newest test version 1.4.23 and proceeded to review how FSX-SE, P3D v4.4 and XP 11.30 behaved together.
My hub was tested on a closed LAN with each client having its own port. I used a C172 as my test aircraft as it is common to all my sims.
Generally the FSX and P3D systems did not exhibit any obvious differences from what was experienced in prior versions.
XPlane however is a different beast entirely. As indicated in various posts it is true that connecting the JoinFS using XP requires a series of careful steps; furthermore, any changes to XP whilst using the client results in a client simulator disconnection. This was not unexpected. Simply re-connecting then sim seemed to resolve the missing activity.
While connected and watching the JoinFS map that I use I noticed that the XP plane was apparently switching its orientation from 0 to 180 on a regular basis. Checking the sims there was no such change so it must be that the whazzup file might be changing and rendering the map in this fashion. I did have the new AI setting for whazzup activated on the hub.
When connecting I had XP set to have up to 10 AI available. While I had but two JoinFS participating aircraft the sim decided to generate more AI and they joined in on the fun.
Interestingly whilst testing I disconnected JoinFS on the XP system and restarted the flight. Although not connected the previous aircraft from P3D and FSX-SE appeared where they were before. Only if I shut down XP and restarted did that seem to go away. Upon reconnecting JoinFS those aircraft, as hoped, then came back where they were before.
I also made a short circuit of the test airport with P3D and XP in hopes of the XP sim plane catching up to the P3D plane so I could see how they showed up, if at all.
After taking off with P3D and establishing a GPS route to follow I used the same plan in XP. With the P3D plane going much slower I was able to catch up. Unlike P3D/FSX there appears to be no in-sim aircraft highlighting that could show an aircraft within the 10 mile range. Maybe there is but I do not know about it.
In any event I was able to spot the P3D plane from XP and follow it. Having no expectations I was pleased to see that there were no great impacts on either plane controls when both aircraft were close; however, I did notice that when I took a screen shot in XP the plane seemed upset and jostled about for a while.
Upon landing both aircraft I decide to see how the animations went. From P3D the lights and propeller animation from the XP plane seemed to work as expected. From XP there was no such concurrency.
Today I installed the newest test version 1.4.23 and proceeded to review how FSX-SE, P3D v4.4 and XP 11.30 behaved together.
My hub was tested on a closed LAN with each client having its own port. I used a C172 as my test aircraft as it is common to all my sims.
Generally the FSX and P3D systems did not exhibit any obvious differences from what was experienced in prior versions.
XPlane however is a different beast entirely. As indicated in various posts it is true that connecting the JoinFS using XP requires a series of careful steps; furthermore, any changes to XP whilst using the client results in a client simulator disconnection. This was not unexpected. Simply re-connecting then sim seemed to resolve the missing activity.
While connected and watching the JoinFS map that I use I noticed that the XP plane was apparently switching its orientation from 0 to 180 on a regular basis. Checking the sims there was no such change so it must be that the whazzup file might be changing and rendering the map in this fashion. I did have the new AI setting for whazzup activated on the hub.
When connecting I had XP set to have up to 10 AI available. While I had but two JoinFS participating aircraft the sim decided to generate more AI and they joined in on the fun.
Interestingly whilst testing I disconnected JoinFS on the XP system and restarted the flight. Although not connected the previous aircraft from P3D and FSX-SE appeared where they were before. Only if I shut down XP and restarted did that seem to go away. Upon reconnecting JoinFS those aircraft, as hoped, then came back where they were before.
I also made a short circuit of the test airport with P3D and XP in hopes of the XP sim plane catching up to the P3D plane so I could see how they showed up, if at all.
After taking off with P3D and establishing a GPS route to follow I used the same plan in XP. With the P3D plane going much slower I was able to catch up. Unlike P3D/FSX there appears to be no in-sim aircraft highlighting that could show an aircraft within the 10 mile range. Maybe there is but I do not know about it.
In any event I was able to spot the P3D plane from XP and follow it. Having no expectations I was pleased to see that there were no great impacts on either plane controls when both aircraft were close; however, I did notice that when I took a screen shot in XP the plane seemed upset and jostled about for a while.
Upon landing both aircraft I decide to see how the animations went. From P3D the lights and propeller animation from the XP plane seemed to work as expected. From XP there was no such concurrency.