This forum is no longer active. Reference only.

I had a quick look this morning Neville and I wasn't able to replicate the white background.

The only thing I can think of is that your system doesn't have, or won't use the color I set the background to for some reason?

So I've changed the background color of the app to a different black, to see if your system can use that.
Its the same black thats in the textbar on your picture, which does show.

The same download link as before will download the latest version (2.1.0.1).

Let me know if that helps.

Hi Andy,

Thanks, debug now working and repeating ' error loading wazzup locations'.

I should be able to test with traffic this evening.

colour change perfect, I suspect my system saw it as transparent.


Thanks again, be in touch,

Neville

neville wrote:Hi Andy,

Thanks, debug now working and repeating ' error loading wazzup locations'.

I should be able to test with traffic this evening.

colour change perfect, I suspect my system saw it as transparent.


Thanks again, be in touch,

Neville

Ah good stuff.

I'll also be on this evening.

I'll have Euroscope open in the UK and I'll be Testing SIMCOM X if you have any queries.

Hi Andy,

Had an A/C on the ground and in the air, could not see him in ES, said it was connected.

Should I be pulling in VATSIM returns beyond my TWR range?, I do.

neville

This is where the Debug option will be helpful Neville.

With Debug open it will show all the positions that have been found in the whazzup file and sent to Euroscope.

If A/C callsign isn't showing in the Debug window, there's an issue.
I'd then check it was in your whazzup.

Else if it is showing in the Debug window, it is sent to Euroscope.

Regarding range..
You will see all aircraft world wide.
If include global users is ticked you see all aircraft on the network.
If only whazzup is ticked you see only users on your hub.

I could write something in to the app that would consider the range set in Euroscope, but thought that was adding something that wasn't really needed as a user can zoom in and out.

I've got to experiment with Peters new Global feature to see how that shows aircraft.

Are the aircraft showing in the Aircraft list in JoinFS, and is JoinFS connected to the simulator?

Peter

Peter,
Are you saying that in order to connect ES and JoinFS via ESJFS, I need to have FSX running?

Neville

If you choose the JoinFS tick box in ESJFS you don't need a SIM running.
You will need to tick whazzup.txt in JoinFS.

Settings for ESJFS2018 as below.
1. JoinFS ticked.
EsJFS2018 will read the aircraft positions from the JoinFS whazzup file.

2. FSX/P3D ticked.
ESJFS2018 will read the positions directly from the SIM using Simconnect.

3. FSUIPC ticked.
ESJFS2018 will read the positions from the SIM over FSUIPC (or XPUIPC for Xplane users).

A SIM is only needed to be run with option 2 or 3.

If no positions are showing with option 1 selected, check that you whazzup file is being populated by JoinFS.

The whazzup file is located in your Appdata/local/JoinFS folder.

Hi Andy,
Thanks, ES says ESJFS displayed/data; whazzup file = 3kb, static listing of 39 servers, 2 clients, though time stamp is progressing; ESJFS = JoinFS ticked, ES green, JoinFS green Debug= rolling 'Added Metar; Error getting wazzup positions.

I havn't been able to see any A/C.

Have set up ES with adc and .prf for EGKA-ROO.

Have to go in five, but will try again tomorrow night.

Neville

Are you using the lastest stable version Neville?
There is a problem with the whazzup in the latest stable v1.4.20.

Peter has fixed it in the test version, so assume it will be ok in the next stable version.

ATC Roo wrote:Are you using the lastest stable version Neville?
There is a problem with the whazzup in the latest stable v1.4.20.

Yes, it could be that. That problem was dependent on being connected to the simulator I think, but it's fixed in the next version. New stable version should be available Monday morning.

Peter

I'll also try and get on tonight, but can't promise.

I successfully controlled last night using the latest test version .25 and the Global option ticked.
This worked while testing with Peter last week too.

In the JoinFS settings I ticked the whazzup.txt and whazzup global users but left the AI unticked.

I didn't connect to a SIM or hub, I only selected the Global option on the main screen in JoinFS.
This showed everybody else that had ticked the Global option.

SIMCOM X now seems mostly stable and I did notice a few issues in ESJFS last night, so I'll rewrite the Euroscope tool ESJFS shortly and try and make it a little more user friendly.

Co-ordination between ATC is possible on Euroscope by using the proxy feature. We were using this but the problem is that there is no callsign for the aircraft, Euroscope will identify craft using that.

Could you set up ESJFS so it sets the callsign on the flight plan to either the crafts callsign/tail number? This would allow our controllers to control aircraft without having to either get the user to import a flight plan on FSX (which has severely out of date navaids and is a pain to get working) or the ATC having to copy/pasta the flight plan from our flight strips page.

All we need is the callsign on the flight plan to be updated automatically so Euroscope tracks the craft. It works perfectly fine when a callsign is set, but you can't set a callsign it only appears when a user files a flight plan (sometimes, kind of unreliable).

Tl;dr
Euroscope needs to have a callsign set on the flight plan to track changes on that aircraft. If you can set the callsign (on the flight plan) then you can use Euroscope with multiple controllers/instances. Euroscope doesn't let you set the callsign

The callsign is not synced with Euroscope (on the flight plan).

This is important as it allows Euroscope to track an a/c between clients (with the proxy) and is used to identify most information. Information like the squawk may remain but the entire flight plan would be lost.

We can solve this by getting our pilots to file any plan, doesn't have to be valid and the callsign will appear (sometimes) letting our atc all see the same information about a craft.

This could be solved by syncing the flight plan callsign with the one reported by FSUIPC, FSX etc.

Is it possible to do this or even a feature in the future?

Hi Brendantdj,

I'll be honest I'm not totally sure what you mean by this?

I'll be looking at the code in the near future, I've just got a major upgrade to simcom X to box off first.

A little bit of information from my side (off the top of my head)...

ESJFS gets the data from either the JoinFS whazzup file, FSX/P3D via SimConnect or through FSUIPC/XUIPC.

It puts together what Euroscope needs to see for a flight plan from the data gained and sends it to EuroScope.

The callsign is one of the bits of data it gains.
The arrival and departure airports are another.
So see if they are set and showing in the JFS whazzup file or in the ESJFS debug window.

The only instance of no callsign that I know of is when FSUIPC is used to gain the data.
I'm not sure why this happens but it only happens when FSUIPC is used.

When this does occur I told ESJFS to use the aircrafts squawk code instead.
This is so aircraft can still be identified and also adds realism as most Radar scopes I've seen show aircraft by squawk and not by callsign (although they can be code callsigned..., opening up a can of worms and going off topic....).

I'm also not sure how you are initiating handovers?
I've not written anything to do that and each EuroScope client is essentially not talking to each other.

As far as I'm aware (with the exception of area), radar handovers are normally conducted over the phone Controller to Controller.
Example: (Hello Edinburgh Radar its Glasgow Radar.
Do you see that 1234 squawk east of DeanCross tracking 090 degrees? Well that's GABCD, inbound to you....).

If you can pinpoint the issue a bit more (does it only happen using FSUIPC?) and let me know how your conducting your handovers(do you get a message in EuroScope when somebody tries to handover?) I'll have a look into it.

Roo

Hi all
i have joined JoinFs and im trying to run ESJFS1018 but it don open
in windows event i see 2 entries:
1 :
Aplicación: ESJFS2018.exe
Versión de Framework: v4.0.30319
Descripción: el proceso terminó debido a una excepción no controlada.
Información de la excepción: System.IO.FileLoadException
en ESJFS2018.Form1..ctor()
en ESJFS2018.Program.Main()
2:
Nombre de la aplicación con errores: ESJFS2018.exe, versión: 2.1.0.1, marca de tiempo: 0x5c419704
Nombre del módulo con errores: KERNELBASE.dll, versión: 10.0.18362.628, marca de tiempo: 0x54734dee
Código de excepción: 0xe0434352
Desplazamiento de errores: 0x00113db2
Identificador del proceso con errores: 0x2e40
Hora de inicio de la aplicación con errores: 0x01d5e714d0c8e008
Ruta de acceso de la aplicación con errores: I:\JoinFS\ESJFS2018.exe
Ruta de acceso del módulo con errores: C:\WINDOWS\System32\KERNELBASE.dll
Identificador del informe: ecc7b120-1da0-4de0-9e35-97ade346e43a
Nombre completo del paquete con errores:
Identificador de aplicación relativa del paquete con errores:

i have read all related topic with with subject without success

i have windows 10 (1903 updated)
i m devellopper and i have Visual studio profesionnal (2010,2012,2015,2017,2019)

i have launched with admin privilege
i have moved all the files to anothre place ( out of windows structure dir)

any idea?

thank all.

Trying to setup ATC using the new version of ESJFS
Whenever I choose JoinFs as the Data source the window stops responding - Running both programs on latest version and as admin - JoinFs stays red then the window becomes unresponsive
Any ideas?

If you reduce the range in JoinFS does that help?
It seemed to with me but not sure if it was coincidence.

Also try connecting euroscope to esjfs and then start JoinFS to see if that helps.

I was getting a few file read errors with the latest versions of JoinFS, which is why I released a slightly tweaked version.

If it's still having issues I'll have to have another look.

If you are reading this Peter, I'm not sure if you're able to close the Whazzup file between writes?
I've been getting some IO file in use errors.

ATC Roo wrote: ↑Fri Jan 08, 2021 10:23 pm If you are reading this Peter, I'm not sure if you're able to close the Whazzup file between writes?
I've been getting some IO file in use errors.

Just had a look. There's a small chance that it was left open due to an exception in the code, but that would normally show up as a message in the JoinFS monitor window.

Anyway, in that particular case it should always close it now.

Maybe it was just a timing issue, but the file write should happen very quickly.

Peter

I thought timing issue too, but thanks for checking.

I might have to look at another way if it gets troublesome.