Search the Community
Showing results for tags 'name'.
-
Hi everyone, I appreciate this is minor (though on the flip-side, fixing it is trivial), but what we have in DCS is not a MiG-29A. IRL the actual MiG-29A (product 9-11A) was a speculative concept from the 1970s that was never built beyond small, scale models. Here's what it may have looked like if it was ever actually built (note 29A written on the nose): This was essentially a stop-gap aircraft, using avionics (including the radar) of late MiG-23ML aircraft (and you can see an R-23R missile depicted under each wing). This model can also be seen in the documentary Wings of the Red Star - the Last Generation about the MiG-29 and Su-27. Here's another image showing prospective loadouts (including the K-25 - more-or-less a copy of the AIM-7 Sparrow), here depicted with semi-recessed stations on the corners of the engine nacelles - much like the Hornet (though you can find numerous other MiG-29A designs - such as this one and even this SAAB 35 Draken-looking one Note how "радиолоцанная станция" (radar station) is listed as "САПФИР-23М" i.e SAPFIR-23M. SAPFIR-23 being the radar fitted to the MiG-23. What we have in DCS is actually just "MiG-29". I'd propose renaming it to "MiG-29 (9-12A)" or "MiG-29 (9-12A) Fulcrum-A", as that's where the As actually belong and this is what the aircraft actually is. Including Fulcrum-A is out of convention for DCS (though DCS' naming convention is inconsistent to begin with), though were it to be done, I'd include NATO reporting names for all Soviet/Russian/Chinese aircraft, as has been done with some ground units. The Ural-375s got corrected to what they actually are (Ural-4320s), let's hope this can get corrected too. I've attached a modified MiG-29-Fulcrum.lua, changing line 410 to have a more accurate display name that fixes the issue - this resides inside CoreMods\aircraft\MiG-29-Fulcrum (ironically the name of the .lua file and the name of the folder gets it right). This will break the Integrity Checker so ensure to retain a back-up of the original. MiG-29-Fulcrum.lua
- 28 replies
-
- 8
-
-
- name
- mission editor
- (and 4 more)
-
Hi everyone, Another minor issue: the Igla-S is given the NATO designation and reporting name SA-18 Grouse, it should actually be called the SA-24 Grinch. SA-18 Grouse is the designation for the preceding 9K38 Igla (which in DCS, uses the same missile as the Igla-S, if the infobar is accurate). I'd suggest renaming the unit to "9K338 Igla-S [SA-24 Grinch] MANPADS".
-
- igla-s
- designation
-
(and 1 more)
Tagged with:
-
Hi everyone, Minor issue - the HY-2 is incorrectly designated SS-N-2 Silkworm/Styx, when it should actually be designated CSSC-3 Seersucker. SS-N-xx is the designation for Soviet/Russian, surface-vessel/submarine launched, anti-surface (including land attack, anti-ship and anti-submarine) missiles. SS-N-2 is the designation for the ship-launched version of the P-15 Termit, which is given the NATO reporting name 'Styx'. The HY-2 originates in China (even if it's derived from the P-15). As such, it should be given a CSS designation. As we have the land-based/coastal-defence version, it should be designated CSSC-xx (meaning Chinese origin, surface-to-surface, coastal-defence). As stated above, the correct designation for the HY-2/C-201 is CSSC-3. The NATO reporting name 'Silkworm' is for the land-based (i.e coastal defence) version of the HY-1 missile, which is considerably shorter-ranged than the HY-2. The NATO reporting name for the HY-2 missile is 'Seersucker'. And the export name for the missile is C-201 (appropriate for Iran). Personally, I'd suggest renaming the launcher to "HY-2 (C-201) [CSSC-3 Seersucker]" and the radar to "Mys-M1E", as that's what they're both actually called. Source 1, source 2, source 3 (see page 2 for a distribution statement).
-
- name
- designation
-
(and 1 more)
Tagged with:
-
Hello, I have 2 questions here: One is if I can open 2 instances at the same time, different versions with a different Saved Games folder (this is what seems to cause the "one instance per write dir" but I may be wrong), I have 2 different save folders for each version separate, I rename them depending on which one I use. Having the 2 instances, it would be easier to replicate my mission, because it has more than 50 aircraft & triggers and I'd like it to be easier to "copy/paste" basically. Two is if the above is impossible or unlikely, I'd like to know if there's anything I can do to save the missions I have, deleting files, renaming, etc, which can be read below. For context, I am using 2.7 Steam Version and 2.5 Standalone and playing these missions on both (haven't seen issues with this before). However, most issues occur when editing names with 2.5. The Problem: I open a mission, edit a group name, click save, I go check and it's back to the old name. I open "Dictionary" and it's all over the place. I am aware it does not clean itself, but it is weird that it doesn't have entries shown on the mission editor. I also noticed that in the F10 menu, the button I have to stop all the sounds (includes a message) does not work for stopping and not for displaying the message, but the other buttons I set to play sounds do work fine with the corresponding message. What I Have Tried: For the missing entries in the "Dictionary", I have manually added the corresponding number, and it worked, but it's way too much to fix this way (50+ names). I deleted the "Dictionary" and renamed everything from scratch in 2.7, the file was created but without entries after saving. I have updated the names and used Save As..., same issue. Changing the "MissionEditor" folder to another name. This sounds far-fetched but I'm trying to consider everything: maybe the Config, NS430 & Scripts folders inside the .MIZ file exclusive to 2.7 conflict with 2.5, for whatever reason, and doesn't let it make editing changes, but allows new additions? Then again, the mission I edited in 2.7 with the renaming from scratch, also didn't save anything and seems to do what 2.5 does. It displays DictKey_sortie_5 (for example) instead of the text I had there. I saw someone explain here how to move triggers from file to file and I did that, worked for others but that might've messed up the dictionary names when I changed the trigger contents. I just can't understand why the editor does not create or update "DictKey...." entries unless I add something new instead of editing. I really apologize if this is super confusing. If anyone has any ideas, please let me know, I'd be interested in trying out stuff. I don't know if it's useful to attach anything (.MIZ file is above 100mb in songs but I can remove them if needed).
- 5 replies
-
- editor
- dictionary
-
(and 1 more)
Tagged with:
-
I'm not sure exactly when it changed, but I noticed that the AIM-120C no longer is listed as "AIM-120C-5" (which it definitely once was - see this screenshot, taken from this post from September 2022) but just "AIM-120C". So, a couple of questions: What AIM-120C variant do we actually have in DCS? Or at least, what is it supposed to be? AIM-120C-5 is from the early-ish 2000s and so is appropriate for the F-15C, F-15E, F-16CM and F/A-18C. Was the C-5 designation a mistake and that we actually had the base AIM-120C variant from the mid 1990s? If it is still supposed to be an AIM-120C-5, why the name change?
- 9 replies
-
- 4
-
-
- weapon list
- variant
-
(and 3 more)
Tagged with:
-
Hi folks, What file I need to edit to change the name on ICP??? I'd like to chance the 337M... Thanks a lot.