Domonkos Ujhelyi (1623074) Hm, it's still not good. I can see that I can trigger the airspace download from the proxy and it affects the main instance too, but there are still no airspaces on the proxy instance.
There are no changes in that area in this version, so this is expected. By toggling a feature such as NOTAM on in that window, it is communicated to the other instances, and when the primary instance gets that information, it will download any missing data such as NOTAMs (and then forward the data to the proxy clients). The problem here most likely is that the NOTAM data had already been downloaded by the primary instance sometime earlier and the proxy instance hadn't been ready to receive it then.
There may be improvements in this area sometime in the future, but for now the safe course of action is to first connect all the proxy instances, and only then download any data such as NOTAMs. This should ensure all the proxies have the same data as the primary instance.
Ricardo Sousa (1110850) When OP_TEXT2 is already populated and then you make a speed assignment, often times you get the /ASP=/ issue
I'm not sure if having OP_TEXT2 already populated is a key difference here or not, but as it turns out, trying this finally enabled me to reproduce the issue which usually is a major step towards being able to resolve it. Sometimes it's one tiny detail that's enough...
Mark Jansen (810676) There seems to be an unwanted/extra space in front of the LIST CALLSIGN tag item.
The space is there by design, to give space for the CPDLC "box" which might be needed in any list. If you really need to save every bit of space in the Departure list, you can use the default Callsign item as fairly few of the plugin-specific coloring rules for the plugin's Callsign item have much use in that list. Otherwise, just increase the column width by one character.
Nicolas Borovich (1036101) Is it possible to get some kind of log in addition to the one created by euroscope when logging in?
A crash dump is sometimes very helpful. Where to look for one depends on your EuroScope version.
First you can see if relevant dump files exist in %localappdata%\CrashDumps folder. They'll be files called EuroScope.exe.00000.dmp (where 00000 is some number). These crash dump files are automatically created by Windows.
If that folder doesn't exist, or doesn't contain a dump file corresponding to the crash, you can try to find a dump file generated by EuroScope instead.
For versions prior to 3.2.8, EuroScope saved crash dumps in the same folder with EuroScope.exe. The dump file would be named EuroScope_crash_.dmp, and only the latest one would be available.
For later versions, you can search for ".sentry-native" on your computer. If found, there will be a folder called "reports" inside it, and there you'll find crash dumps.