CCDS-R for EuroScope intends to bring a representation of the real-world CCDS-R system to EuroScope, primarily for VATSIM UK users, for a more authentic controlling experience. Some features include:
- Specific pre-determined code-callsign conversion for specific squawks, customisable via a JSON file
- Custom tag families that use the CCDS-R tag items
- Custom target data block (TDB) alerts, customisable via a JSON file
- COMING SOON: customisable TDB color alerts, such as STCA, oCAT, CAIT etc.
FAQs
Installation
Customisation
Troubleshooting
I appreciate that if you're not familiar with these systems, that's a lot of acronyms. I'll do my best to explain features in this readme as I introduce them. First, the easy questions.
Code Callsign Distribution System - Replacement (CCDS-R) is a system that correlates the squawk code an aircraft is wearing with a stored flight plan or otherwise pre-agreed callsign, and therefore allows the callsign and flight plan data to be displayed to the controller on the radar. It is currently used by NATS and NAV CANADA.
You don't. If you're looking for a more realistic radar representation for your TDBs, particularly for LTC, this is for you. If not, that's okay too.
I've developed CCDS-R for EuroScope to be completely customisable for the user. If you've got some idea of how a specific airfield you control regularly has their code-callsign-conversion set up, then you can emulate that exactly in CCDS-R for EuroScope.
Installation is wonderfully simple.
- Download the latest release
- Extract the
CCDS-R
folder to yourEuroScope\UK\Data\Plugins
folder - Extract the
tags.txt
file to yourEuroScope\UK\Data\Settings
folder and overwrite the existing file. MAKE A BACKUP OF THE EXISTING FILE FIRST. - You're done!
At the moment, only code-callsign conversions and TDB labels can be customised. All the relevant information and examples are contained in CCDS-R\Settings\conversions.json
.
There are a few possible causes.
There is an error in the conversions.json
file that is preventing it from being parsed. Have another look. If you're unsure, use this link to check the validity of your JSON.
"Invalid data found in the JSON file. Custom Code-callsign conversions and labels will be non-functional."
One or more of your custom labels or callsigns is either empty or too long. The maximum is 7 characters.
That shouldn't happen. Save the log, and raise an issue with the log file and as much information as you can remember about what happened.
The plugin hasn't loaded or hasn't loaded correctly. Unload and reload it.
If you're using easy mode, you won't notice any difference. You can change this by going to Other Set -> General Settings -> Correlation Mode