https://www.euroscope.hu/wp/2023/02/25/v3-2-3/
New version out. Thank you GC for your development!
https://www.euroscope.hu/wp/2023/02/25/v3-2-3/
New version out. Thank you GC for your development!
According to the discussions in the VATEUD discord, ATIS maker urls without the letters won’t allow to send the ATIS request.
ATIS update messages to other controllers are still duplicated (you get two messages with the same content right after each other). The same happens to function calls by plugins originating from edit fields (OpenPopupEdit). There is no issue when you send a fixed value (as it is also the case for the ATIS message). But it causes issues when the function called uses a logic based on dynamic values.
Example: a function toggling ADES and alternate. Using such a function regularly will show no change, because ADES and alternate are initially changed, but because the function is then called again, they are immediately switched back.
This is only one example of an issue that is around for quite some time. I’m sure it’s only a minor logic thing somewhere in the core which could potentially solve a number of resulting issues (maybe even some where the relation is not that obvious).
Adding some long-lasting issues to the list of fixes required:
With v3.2.3 you should be able to use functions without letters.
While we are at it,
Could we make the ATIS letter a data field that all controllers and plugins can see? I know this has been a request in TS and it makes sense as an ACC or APP to see ATIS letters from airports that you hadn’t connected the atis for. Also, ATIS code in PDC anyone?
Right now, the the only way the get this data is through the vatsim-data.json which is complete overkill.
Plugin interface improvements would definitely be highly appreciated as well. Here is my wish list
Here’s some bigger ones that are out of reach for plugins:
Mirrored connection
Use case: Groundworks for a coordinator position whereby the connecting party sees the traffic just like the source controller. It works mostly like a non-local proxy connection (but with an extra connection/callsign to the network). Could also be handy for observing.
Tag positioning awareness
Use case: Anti-overlap logic for tags.
Native insets
Use case: Little windows of other asr files (VRC style) for better monitoring. Or even just to make it easier to have multiple ASRs on one screen without having the whole ES top and bottom bars as you would now with the current ‘‘screen position window/menu’’.
Question, any update on the condition line? COPX feature request - EuroScope - VATSIM Community
And to jump in the request wagon, middle mouse click actions would be amazing!
When opening an proxy connection to a 2nd EuroScope window mid-session, it will not carry over data such as CFL, assigned squawk, ground state etc.
Example - Left one is main ES and the other is proxy connection.
(Data input excisting in proxy one is data added after proxy connection was opened)
Hi! I tried using $atisairport
, but it is unable to extract the function names from the URL.
Error: Unable to extract function names from URL:
Error: https://vatatis.nz/gen?arr=$arrrwy($atisairport)&...
Can you copy the whole ATIS maker URL.
Something like: https://vatatis.nz/gen?arr=$arrrwy($atisairport)&dep=$deprwy($atisairport)&metar=$metar($atisairport)&info=$atiscode
It looks OK in my side.
I had problems when the METAR was not available or the dep/arr RWY was not selected for the airport.
Not working here
ATIS maker URL: https://www.vatatis.nz/gen?arr=$arrrwy($atisairport)&dep=$deprwy($atisairport)&metar=$metar($atisairport)
Extracted URL: https://www.vatatis.nz/gen?arr=14&dep=28&metar=LSZH%20041050Z%20VRB01KT%204200%20BR%20FEW020%2006/00%20Q1022%20BECMG%205000
ES still cannot extract the function names, but the extracted URL works fine if used in a browser.
It is really strange that you have the error message while the URL itself is extracted well.
Does it work with $atisairportA value?
Yes, when using the $atisairportA value, it works again.
Is there any solution regarding having two different ATIS letters when running seperate DEP and ARR ATIS? Currently the METAR list can only display one.
Edit: Seemingly neither the DEP or ARR ATIS seems to be sending any ATIS letters to neighbouring possitions?
Is there a need for this restriction that DEL can not open an ATIS?
As @1158939 confirmed, my ATIS URL was:
https://vatatis.nz/gen?arr=$arrrwy($atisairport)&dep=$deprwy($atisairport)&metar=$metar($atisairport)&info=$atiscode
For the sake of clarity, I made sure only one airport was currently active. Alas, the same error occurs.