So, thanks @Minskyfor pointing me to that file. I investigated a bit and initially reproduced your issue trying to add any other map than the ones currently in it (Caucasus and Nevadat). It turns out that it's because the file uses
get_terrain_related_data("name")
to get the current map name, and apparently it only works on Caucasus (and I guess Nevada), not on any other map I have (it returns NULL). The problem was actually identified in 2021 and a workaround was found (see
by using:
get_terrain_related_data("id")
If I do that and use the id found in the terrain entry.lua file (check for the self_ID field) then I can enter specific TACAN inside the database. I'm not really sure I can attach my MC_No1.lua (for IP reasons) but you should be able to reproduce easily locally (feel free to ask if needed). Obviously it breaks IC but on SP and PVE servers I think it should not be too much of an issue. Still it'd be nice to have it fixed/supported directly in DCS Hornet.
In the end I think there's a bug (either in DCS core or in all the external maps) where get_terrain_related_data("name") doesn't work. And if it's on purpose then I guess MC_No1.lua should be changed to "id". And then maybe a wishlist thread for adding relevant beacons for relevant maps.
