ATC with JOINFS

Suggestions, ideas and general discussion about JoinFS.
jopie_60
Posts: 23
Joined: Sat Apr 28, 2018 9:45 am

Re: ATC with JOINFS

Postby jopie_60 » Tue May 29, 2018 6:28 am

Coming week our DFN-ATC-er and me will fly a session and test ESJSF2018.

Perhaps is it an idea to make it visible which version of ESJSF2018 is used f.e. ESJSF2018 v2.1.0.0 and also let it know in the download and also a small manual.

We don't expect any (big) problems bus I'll let you know how the test session has been and when

:D :D :D the DutchFlightNetwork.nl :D :D :D has been transfered to the new programs

Regards

Hans

ATC Roo
Posts: 403
Joined: Sun Oct 16, 2016 9:24 am
Location: UK
Contact:

Re: ATC with JOINFS

Postby ATC Roo » Fri Jun 01, 2018 12:33 am

jopie_60 wrote:Coming week our DFN-ATC-er and me will fly a session and test ESJSF2018.

Perhaps is it an idea to make it visible which version of ESJSF2018 is used f.e. ESJSF2018 v2.1.0.0 and also let it know in the download and also a small manual.

We don't expect any (big) problems bus I'll let you know how the test session has been and when

:D :D :D the DutchFlightNetwork.nl :D :D :D has been transfered to the new programs

Regards

Hans


The latest version is always available from the download link in the first post.
I won't be updating it further as it works now and nothing more is needed.
The only exception is if something that makes the program unusable is found, then I would correct it and release a newer version.

I'm not sure a manual is needed as the tick boxes seem self explanatory?

The first post of this thread does provide basic connection instructions.

jopie_60
Posts: 23
Joined: Sat Apr 28, 2018 9:45 am

Re: ATC with JOINFS

Postby jopie_60 » Sun Jun 03, 2018 8:15 am

Last week we have done the last testing

There is difference between the flightplan (F6) generated by FSInn and JoinFS - ESJSF2018.

In the displayed flightplan generated by JoinFS -ESJSF2018 we missing the waypoints and the flightlevel, see screendumbs.

I'm not able to look in the whazzup.txt generated by FSInn to see is there any difference, I'll try to contact our servermanager and let tou know as soon as possible.

Regards

Hans
Attachments
FPL_FSInn.jpg
FPL_FSInn.jpg (13.57 KiB) Viewed 471 times
FPL_ESJSF2018.jpg
FPL_ESJSF2018.jpg (18.67 KiB) Viewed 471 times

ATC Roo
Posts: 403
Joined: Sun Oct 16, 2016 9:24 am
Location: UK
Contact:

Re: ATC with JOINFS

Postby ATC Roo » Sun Jun 03, 2018 9:02 pm

jopie_60 wrote:Last week we have done the last testing

There is difference between the flightplan (F6) generated by FSInn and JoinFS - ESJSF2018.

In the displayed flightplan generated by JoinFS -ESJSF2018 we missing the waypoints and the flightlevel, see screendumbs.

I'm not able to look in the whazzup.txt generated by FSInn to see is there any difference, I'll try to contact our servermanager and let tou know as soon as possible.

Regards

Hans


Hi Hans,

The ESJFS tools can only add the data that is available.

The flight plan Waypoints and Flight Level are not output from JoinFS at the moment.
Because of this Flight Level will be the current level the aircraft is at and the destination will display in the waypoints section.

Hope that helps.

jopie_60
Posts: 23
Joined: Sat Apr 28, 2018 9:45 am

Re: ATC with JOINFS

Postby jopie_60 » Fri Oct 05, 2018 12:31 pm

DutchFlightNetwork is about to make a switch from FSInn-vPilot to JoinFS - ESJFS2018
However, with the implementation of ESJFS2018 v2.1.0.0, the following problem may occur, for example that ESJFS2018 may not start up on some machines.

The startup of ESJFS2018 on my desktop and some others works without problems, however, if I want to start the same version on my laptop, a report.wer and a crash dump are generated.

In the past, ESJFS2018 has run normally on my laptop.

On my desktop and laptop are windows version and the framework versions are equal to each others.

Two colleagues DFN-er have no problems while 2 others can not lauch ESJFS2018 either.

Is this problem known or is a solution for this

Regards

Hans

content report.wer

Version=1
EventType=CLR20r3
EventTime=131832140204641578
ReportType=2
Consent=1
UploadTime=131832140214235360
ReportStatus=268435456
ReportIdentifier=f4f1415e-6ae0-444b-b04d-164f5872a3c1
IntegratorReportIdentifier=22930ac9-d71b-4d57-ae3f-9c20a318d96b
Wow64Host=34404
Wow64Guest=332
NsAppName=ESJFS2018.exe
OriginalFilename=ESJFS2018.exe
AppSessionGuid=00003218-0004-002a-c694-bc0ba25cd401
TargetAppId=W:000634bfb638ae261318c35de239646090fe00000000!00007c7d8d32b9dd515d3e99f8acb444ae4f8b258a7a!ESJFS2018.exe
TargetAppVer=2018//05//21:19:09:07!0!ESJFS2018.exe
BootId=4294967295
ServiceSplit=14
TargetAsId=3879
IsFatal=1
Response.BucketId=fc5a83c38cacc5a96c61c8253c6f560e
Response.BucketTable=5
Response.LegacyBucketId=2045135768056190478
Response.type=4
Sig[0].Name=Probleemhandtekening 01
Sig[0].Value=ESJFS2018.exe
Sig[1].Name=Probleemhandtekening 02
Sig[1].Value=2.1.0.0
Sig[2].Name=Probleemhandtekening 03
Sig[2].Value=5b031953
Sig[3].Name=Probleemhandtekening 04
Sig[3].Value=ESJFS2018
Sig[4].Name=Probleemhandtekening 05
Sig[4].Value=2.1.0.0
Sig[5].Name=Probleemhandtekening 06
Sig[5].Value=5b031953
Sig[6].Name=Probleemhandtekening 07
Sig[6].Value=87
Sig[7].Name=Probleemhandtekening 08
Sig[7].Value=e
Sig[8].Name=Probleemhandtekening 09
Sig[8].Value=System.IO.FileLoadException
DynamicSig[1].Name=Versie van besturingssysteem
DynamicSig[1].Value=10.0.17134.2.0.0.768.101
DynamicSig[2].Name=Landinstelling-id
DynamicSig[2].Value=1043
DynamicSig[22].Name=Aanvullende informatie 1
DynamicSig[22].Value=2beb
DynamicSig[23].Name=Aanvullende informatie 2
DynamicSig[23].Value=2beba6fb4680d73a8c78ca7c24ccdb46
DynamicSig[24].Name=Aanvullende informatie 3
DynamicSig[24].Value=b1f0
DynamicSig[25].Name=Aanvullende informatie 4
DynamicSig[25].Value=b1f0b380dbcd74b72a4df4e63607c2ae
UI[2]=C:\Users\jopie\Desktop\JFS_ES\ESJFS2018_v2.1.0.0\ESJFS2018.exe
LoadedModule[0]=C:\Users\jopie\Desktop\JFS_ES\ESJFS2018_v2.1.0.0\ESJFS2018.exe
LoadedModule[1]=C:\WINDOWS\SYSTEM32\ntdll.dll
LoadedModule[2]=C:\WINDOWS\SYSTEM32\MSCOREE.DLL
LoadedModule[3]=C:\WINDOWS\System32\KERNEL32.dll
LoadedModule[4]=C:\WINDOWS\System32\KERNELBASE.dll
LoadedModule[5]=C:\WINDOWS\SYSTEM32\apphelp.dll
LoadedModule[6]=C:\WINDOWS\System32\ADVAPI32.dll
LoadedModule[7]=C:\WINDOWS\System32\msvcrt.dll
LoadedModule[8]=C:\WINDOWS\System32\sechost.dll
LoadedModule[9]=C:\WINDOWS\System32\RPCRT4.dll
LoadedModule[10]=C:\WINDOWS\System32\SspiCli.dll
LoadedModule[11]=C:\WINDOWS\System32\CRYPTBASE.dll
LoadedModule[12]=C:\WINDOWS\System32\bcryptPrimitives.dll
LoadedModule[13]=C:\Windows\Microsoft.NET\Framework\v4.0.30319\mscoreei.dll
LoadedModule[14]=C:\WINDOWS\System32\SHLWAPI.dll
LoadedModule[15]=C:\WINDOWS\System32\combase.dll
LoadedModule[16]=C:\WINDOWS\System32\ucrtbase.dll
LoadedModule[17]=C:\WINDOWS\System32\GDI32.dll
LoadedModule[18]=C:\WINDOWS\System32\gdi32full.dll
LoadedModule[19]=C:\WINDOWS\System32\msvcp_win.dll
LoadedModule[20]=C:\WINDOWS\System32\USER32.dll
LoadedModule[21]=C:\WINDOWS\System32\win32u.dll
LoadedModule[22]=C:\WINDOWS\System32\IMM32.DLL
LoadedModule[23]=C:\WINDOWS\System32\kernel.appcore.dll
LoadedModule[24]=C:\WINDOWS\SYSTEM32\VERSION.dll
LoadedModule[25]=C:\Windows\Microsoft.NET\Framework\v4.0.30319\clr.dll
LoadedModule[26]=C:\WINDOWS\SYSTEM32\MSVCR120_CLR0400.dll
LoadedModule[27]=C:\WINDOWS\assembly\NativeImages_v4.0.30319_32\mscorlib\399032397425364b053c532bbbeacc09\mscorlib.ni.dll
LoadedModule[28]=C:\WINDOWS\System32\ole32.dll
LoadedModule[29]=C:\WINDOWS\system32\uxtheme.dll
LoadedModule[30]=C:\Windows\Microsoft.NET\Framework\v4.0.30319\clrjit.dll
LoadedModule[31]=C:\WINDOWS\System32\OLEAUT32.dll
LoadedModule[32]=C:\WINDOWS\assembly\NativeImages_v4.0.30319_32\System\6e52f5ddc8a0027c55a2c15df97d50a9\System.ni.dll
LoadedModule[33]=C:\WINDOWS\assembly\NativeImages_v4.0.30319_32\System.Drawing\aaa6eb8944c45fec21964e09ea5d8904\System.Drawing.ni.dll
LoadedModule[34]=C:\WINDOWS\assembly\NativeImages_v4.0.30319_32\System.Windows.Forms\ff99a9d58626979ee9a1e49e9cb7f8c5\System.Windows.Forms.ni.dll
LoadedModule[35]=C:\WINDOWS\assembly\NativeImages_v4.0.30319_32\System.Core\2d2bc5d43039ac23595b27676dcfcd3b\System.Core.ni.dll
LoadedModule[36]=C:\WINDOWS\assembly\NativeImages_v4.0.30319_32\System.Configuration\ce7b3ccf1b67903e135f62bd847db8dc\System.Configuration.ni.dll
LoadedModule[37]=C:\WINDOWS\assembly\NativeImages_v4.0.30319_32\System.Xml\536177f34c4c0eeb95bcccd76ca90847\System.Xml.ni.dll
LoadedModule[38]=C:\WINDOWS\System32\shell32.dll
LoadedModule[39]=C:\WINDOWS\System32\cfgmgr32.dll
LoadedModule[40]=C:\WINDOWS\System32\shcore.dll
LoadedModule[41]=C:\WINDOWS\System32\windows.storage.dll
LoadedModule[42]=C:\WINDOWS\System32\profapi.dll
LoadedModule[43]=C:\WINDOWS\System32\powrprof.dll
LoadedModule[44]=C:\WINDOWS\System32\FLTLIB.DLL
LoadedModule[45]=C:\WINDOWS\SYSTEM32\bcrypt.dll
LoadedModule[46]=C:\WINDOWS\SYSTEM32\CRYPTSP.dll
LoadedModule[47]=C:\WINDOWS\system32\rsaenh.dll
LoadedModule[48]=C:\WINDOWS\System32\ws2_32.dll
LoadedModule[49]=C:\WINDOWS\system32\mswsock.dll
LoadedModule[50]=C:\WINDOWS\SYSTEM32\wldp.dll
LoadedModule[51]=C:\WINDOWS\System32\CRYPT32.dll
LoadedModule[52]=C:\WINDOWS\System32\MSASN1.dll
LoadedModule[53]=C:\WINDOWS\System32\WINTRUST.dll
LoadedModule[54]=C:\Windows\Microsoft.NET\Framework\v4.0.30319\diasymreader.dll
State[0].Key=Transport.DoneStage1
State[0].Value=1
OsInfo[0].Key=vermaj
OsInfo[0].Value=10
OsInfo[1].Key=vermin
OsInfo[1].Value=0
OsInfo[2].Key=verbld
OsInfo[2].Value=17134
OsInfo[3].Key=ubr
OsInfo[3].Value=285
OsInfo[4].Key=versp
OsInfo[4].Value=0
OsInfo[5].Key=arch
OsInfo[5].Value=9
OsInfo[6].Key=lcid
OsInfo[6].Value=1043
OsInfo[7].Key=geoid
OsInfo[7].Value=176
OsInfo[8].Key=sku
OsInfo[8].Value=101
OsInfo[9].Key=domain
OsInfo[9].Value=0
OsInfo[10].Key=prodsuite
OsInfo[10].Value=768
OsInfo[11].Key=ntprodtype
OsInfo[11].Value=1
OsInfo[12].Key=platid
OsInfo[12].Value=10
OsInfo[13].Key=sr
OsInfo[13].Value=0
OsInfo[14].Key=tmsi
OsInfo[14].Value=131177
OsInfo[15].Key=osinsty
OsInfo[15].Value=2
OsInfo[16].Key=iever
OsInfo[16].Value=11.285.17134.0-11.0.85
OsInfo[17].Key=portos
OsInfo[17].Value=0
OsInfo[18].Key=ram
OsInfo[18].Value=8082
OsInfo[19].Key=svolsz
OsInfo[19].Value=868
OsInfo[20].Key=wimbt
OsInfo[20].Value=0
OsInfo[21].Key=blddt
OsInfo[21].Value=180410
OsInfo[22].Key=bldtm
OsInfo[22].Value=1804
OsInfo[23].Key=bldbrch
OsInfo[23].Value=rs4_release
OsInfo[24].Key=bldchk
OsInfo[24].Value=0
OsInfo[25].Key=wpvermaj
OsInfo[25].Value=0
OsInfo[26].Key=wpvermin
OsInfo[26].Value=0
OsInfo[27].Key=wpbuildmaj
OsInfo[27].Value=0
OsInfo[28].Key=wpbuildmin
OsInfo[28].Value=0
OsInfo[29].Key=osver
OsInfo[29].Value=10.0.17134.285.amd64fre.rs4_release.180410-1804
OsInfo[30].Key=buildflightid
OsInfo[30].Value=5f17aaf3-a675-41fe-91df-9dcdccde4c34
OsInfo[31].Key=edition
OsInfo[31].Value=Core
OsInfo[32].Key=ring
OsInfo[33].Key=expid
OsInfo[34].Key=containerid
OsInfo[35].Key=containertype
OsInfo[36].Key=edu
OsInfo[36].Value=0
FriendlyEventName=Werkt niet meer
ConsentKey=CLR20r3
AppName=ESJFS2018
AppPath=C:\Users\jopie\Desktop\JFS_ES\ESJFS2018_v2.1.0.0\ESJFS2018.exe
NsPartner=windows
NsGroup=windows8
ApplicationIdentity=E089C84DDE184E0731F34472923C4773
MetadataHash=-1056840896

ATC Roo
Posts: 403
Joined: Sun Oct 16, 2016 9:24 am
Location: UK
Contact:

Re: ATC with JOINFS

Postby ATC Roo » Fri Oct 05, 2018 1:35 pm

I'm not near my PC at the moment.
But a quick look at that report seems to point to your version of .net.

Off the top of my head I think I wrote ESJFS with .net 4.5.

Try running Windows update and/or installing the latest .net currently 4.7.2.

jopie_60
Posts: 23
Joined: Sat Apr 28, 2018 9:45 am

Re: ATC with JOINFS

Postby jopie_60 » Sat Oct 06, 2018 9:23 am

Thank you for the quick response.

As written, the two installations of both my desktop and the laptop are the same. The same windows versions, the same Bitdefender Security. The same version of framework was installed on both computers (4.7.2 windows update April 10).
On my laptop I have removed Bitdefender as an ultimate attempt and when I start ESJFS2018 the hourglass disappears within a few moments.
A new report is generated in the Microsoft / Windows / WER / folder.
I have no idea what to look for to solve this problem, especially since ESJFS2018 does not want to run on two of our three ATCs.
If desired, I want to copy and paste the last report.wer.

Regards

Hans

ATC Roo
Posts: 403
Joined: Sun Oct 16, 2016 9:24 am
Location: UK
Contact:

Re: ATC with JOINFS

Postby ATC Roo » Sat Oct 06, 2018 10:05 am

I have some time later today and will be controlling on JoinFS using SIMCOM X for comms.

So I'll investigate this further.
Something that stands out from your log above is
Sig[8].Value=System.IO.FileLoadException


This means the app is trying to read a file that isn't there.

Have you you got a whazzup.txt file in your JoinFS folder?
C:\Users\jopie\AppData\Local\JoinFS

If you have...

What files do you have in
C:\Users\jopie\Desktop\JFS_ES\ESJFS2018_v2.1.0.0\

jopie_60
Posts: 23
Joined: Sat Apr 28, 2018 9:45 am

Re: ATC with JOINFS

Postby jopie_60 » Sat Oct 06, 2018 11:44 am

the content of the first lines op the whazzup.txt is
!GENERAL
VERSION = 1
RELOAD = 1
UPDATE = 20181006133121
CONNECTED CLIENTS = 1
CONNECTED SERVERS = 40
!CLIENTS
EHAM_TWR:EuroScope Hans U.:EuroScope Hans U.:ATC:122.800:52,3086128234863:4,76388883590698:0:0::::::::::4:40:::::::::::::::::::::::::::
!SERVERS
following with serverals servers.

The map contents:
esjfs2018.exe
ESJFS2018.exe.config
contents
<?xml version="1.0" encoding="utf-8"?>
<configuration>
<startup useLegacyV2RuntimeActivationPolicy="true">
<supportedRuntime version="v4.0" sku=".NETFramework,Version=v4.5"/>
</startup></configuration>

METAR.txt
contents
$ARJoinFS:EGCC_APP:METAR:EGCC 031020Z AUTO 23010KT 190V260 9999 BKN033 12/04 Q1018 NOSIG

regards
Hans

ATC Roo
Posts: 403
Joined: Sun Oct 16, 2016 9:24 am
Location: UK
Contact:

Re: ATC with JOINFS

Postby ATC Roo » Sat Oct 06, 2018 11:53 am

I will investigate this properly in a few hours.

Until then I wonder if it's because you have a . After your username?

EHAM_TWR:EuroScope Hans U.


Return to “Discussion”