Corsac

In what systems are the coordinates saved? Right now you can't enter specific coordinates in the route tool and if you try to set it semi-precisely and then edit the file, well you're stuck with coordinates like: ["y"] = -748623.4375, ["x"] = -186536.484375, which don't really look like real coordinates (maybe they're only relevant to the current map area or something).

Hi, This is a followup to another thread but specifically about the wishlist parts: the current TACAN database in the Hornet only includes beacons from Caucasus and Nevada. With some help and a bit of investigation we noticed that the current implementation comes from (DCS)\Mods\aircraft\FA-18C\Cockpit\Scripts\Computers\MC_No1.lua and has some issues and missing parts: it relies on get_terrain_related_data("name") which doesn't work with maps other than Caucasus or Nevada apparently. I'm not sure if it's an issue in the internal function or something which should be provided by the terrains themselves. Apparently that function is used by a lot of modules and mods so maybe it should be fixed (one way or another), but a workaround is to use get_terrain_related_data("id") (and use the self_ID from entry.lua in the various terrains) it only selects specific entries for Caucasus and Nevada. I understand it requires a coordination between ED and the terrain maker but it would be nice to select and add beacons for all the available maps. I think it's especially useful for maps used in cold war scenarios where GPS might not be available, and Cold War Germany is a prime example here. There are examples on the linked thread but obviously ED (and Ugra Media) might have way better idea than us. I have the feeling this could be rather fixed by implementing it in the DTC but I understand it's a work in progress and I'm not sure when the beacons part is supposed to be implemented. Any implementation would be ok for me (although currently it's a bit difficult to work with DTC for a lack of real "default" DTC).

My changes are basically the same except I used: local theatre_ = theatre or get_terrain_related_data("id") or "none" and then a different selection : elseif theatre_ == "GermanyCW" then TACAN_Data = { getTACAN('world_0'), -- HAM (Hamburg) getTACAN('world_10'), -- NTM (Nattenheim) getTACAN('world_14'), -- FUL (Fulda) getTACAN('airfield200_2'), -- BIT (Bitburg) getTACAN('airfield235_0'), -- BUE (Buchel) getTACAN('airfield163_6'), -- FFM (Frankfurt) getTACAN('airfield16_1'), -- GSO (Gutersloh) getTACAN('airfield165_2'), -- RMS (Ramstein) getTACAN('airfield29_1'), -- TOF (Tempelhof) getTACAN('airfield32_1'), -- WUN (Wunstorf) }

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.

Thanks for the pointer to that file, I'll take a look as well.

Hi, I've started flying on CW:Germany with a date before GPS, so having to rely only on INS navigation. There's obviously some drift after a while and the advice from the manual is either to update position using a waypoint over a recognizable feature, or use the tacan database. It seems that the Tacan database is only populated on Caucasus and unpopulated on all the others I could test (Cold War Germany, Marianas, Persian Gulf, Sinai). Manually adding a TACAN at the beginning of each flight will rapidly become old, so is there a way to populate that database differently? I assume at some point there will be a DTC interface for that but it's not yet the case. I can see the maps have a Beacons.lua (or beacons.lua) file defining those so I'm unsure what would be needed. It'd be really useful for those CW scenarios.

Thanks!

Thanks, I'll give some more trying but I don't think it matters: looking at the fuel page the ext tanks do fill up (even without refueling probe extended), it just takes (too much) time.

Thanks for the feedback. It's been bothering me for a while but wasn't sure. I guess in the meantime I'll just drop my tanks before landing or replace it when rearming.

Hi, when refueling on the ramp with an empty centerline tank and nearly full internal tanks, the centerline tanks won't be full after refueling ends. It seems that the fuel transfer *to* centerline is slow and the internal tanks are full before, stopping the refueling process. I guess it's the same with wing tanks. And rearming wont replace the external tanks with "new" ones, unless I first remove it and then add it back. It looks like a bug to me but maybe I'm not doing the refueling process correctly (I didn't select anything wrt. transfert, xfeed etc.)

So we're back to my earlier message. That won't really work for MP servers, which in turn don't seem to enable it, so everybody loses.

Thanks for the tip. I'm using Open Mods Manager so I copied CoreMods/aircraft/FA-18C/DTC/ALR67/CMDS_defs.lua to my mods library (using the same relative path) and edited the file there to my liking and enabled that mod. Now after a cold start, if I go to MUMI and load the ALR67 I get that modified default configuration. No need to load a custom DTC for DCS UI after slotting in. Works just fine for me even if it's not entirely satisfying. I noticed that in CoreMods/aircraft/FA-18C/DTC/defaults there are multiple test.json files which might also be relevant but I have no idea how to use/tune them and anyway they're still in the main install path and not in Saved Games so it's not really more useful than tuning CMDS_defs.lua. It'd definitely be nice to be able to have a default configuration in saved games for users to tune.

What about all the other slots (5/9/11/14 for cat1)?

I found this topic because I was using exactly that trick (editing Mods\aircraft\FA-18C\Cockpit1\Scripts\TEWS\device\CMDS_ALE47.lua) to setup the CM the way I liked it, and it doesn't work anymore. As I read that thread it looks that if I load the "DEFAULT" DTC from the MUMI page by boxing the ALE47, I should get what it's in that file? But apparently it doesn't, not on my install at least. Any clue on what to do? Or maybe the new path is aircraft\FA-18C\DTC\ALR67\CMDS_defs.lua ? That file doesn't exist here but maybe I should create it?

Sorry I might not have been very clearnull. If there are statics on cat 1 you might want to put stuff on slot 1/5/9/11/14 so noone can be spawned there. Unfortunately that means that at landing you might have to collide with the statics on slot 1 when taxiing.