Jump to content

Recommended Posts

Posted

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):

image0.jpg?ex=68db9fd9&is=68da4e59&hm=b3

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😞

md2ALwY.png

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 (ironically, the name of the .lua file gets it right), 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

  • Like 2

Modules I own: F-14A/B, F-4E, Mi-24P, AJS 37, AV-8B N/A, F-5E-3, MiG-21bis, F-16CM, F/A-18C, Supercarrier, Mi-8MTV2, UH-1H, Mirage 2000C, FC3, MiG-15bis, Ka-50, A-10C (+ A-10C II), P-47D, P-51D, C-101, Yak-52, WWII Assets, CA, NS430, Hawk.

Terrains I own: South Atlantic, Syria, The Channel, SoH/PG, Marianas.

System:

GIGABYTE B650 AORUS ELITE AX, AMD Ryzen 5 7600, Corsair Vengeance DDR5-5200 32 GB, NVIDIA GeForce RTX 4070S FE, Western Digital Black SN850X 1 TB (DCS dedicated) & 2 TB NVMe SSDs, Corsair RM850X 850 W, NZXT H7 Flow, MSI G274CV.

Peripherals: VKB Gunfighter Mk.II w. MCG Pro, MFG Crosswind V3 Graphite, Logitech Extreme 3D Pro.

Posted (edited)

Yes, it's been discussed before - and a pet peeve as well that I see people keep using wrong classifications. Including ED, who are quick to say "we are simulating an F-16CM from circa 2005 as been used by the USAF" but keep calling an actual in-service aircraft by the name of a concept that never materialised.
It's the equivalent of calling our F/A-18C lot 20 a YF-17.
 



Also, the naming conventions used inside DCS are not consistent. In the ME it's called "MiG-29A-Fulcrum" while in the Special Options it's - correctly - called "MiG-29 (model 9.12A)".

Edited by Raven (Elysian Angel)
  • Like 1
Spoiler

Ryzen 7 9800X3D | 96GB G.Skill Ripjaws M5 Neo DDR5-6000 | Asus ProArt RTX 4080 Super | ASUS ROG Strix X870E-E GAMING | Samsung 990Pro 2TB + 990Pro 4TB NMVe | VR: Varjo Aero
VPC MT-50CM2 grip on VPForce Rhino with Z-curve extension | VPC CM3 throttle | VPC CP2 + 3 | FSSB R3L | VPC Rotor TCS Plus base with SharKa-50 grip | Everything mounted on Monstertech MFC-1 | VPC R1-Falcon pedals with damper | Pro Flight Trainer Puma

OpenXR | PD 1.0 | 100% render resolution | DCS graphics settings
Win11 Pro 24H2 - VBS/HAGS/Game Mode ON

 

Posted (edited)
14 minutes ago, Raven (Elysian Angel) said:

Yes, it's been discussed before - and a pet peeve as well that I see people keep using wrong classifications. Including ED, who are quick to say "we are simulating an F-16CM from circa 2005 as been used by the USAF" but keep calling an actual in-service aircraft by the name of a concept that never materialised.
It's the equivalent of calling our F/A-18C lot 20 a YF-17

Yep, ditto for the Su-25 (correct in the mission editor, incorrect everywhere else), HY-2, U-Boat U-Flak, Chieftain Mk.3 etc.

I never thought to make the comparison to the YF-17, it is a pretty apt one, though at least that actually flew.

EDIT: I see this has been moved out of bugs and problems, despite it being an in-game inaccuracy - I guess ED are content with calling things what they aren't.

Edited by Northstar98

Modules I own: F-14A/B, F-4E, Mi-24P, AJS 37, AV-8B N/A, F-5E-3, MiG-21bis, F-16CM, F/A-18C, Supercarrier, Mi-8MTV2, UH-1H, Mirage 2000C, FC3, MiG-15bis, Ka-50, A-10C (+ A-10C II), P-47D, P-51D, C-101, Yak-52, WWII Assets, CA, NS430, Hawk.

Terrains I own: South Atlantic, Syria, The Channel, SoH/PG, Marianas.

System:

GIGABYTE B650 AORUS ELITE AX, AMD Ryzen 5 7600, Corsair Vengeance DDR5-5200 32 GB, NVIDIA GeForce RTX 4070S FE, Western Digital Black SN850X 1 TB (DCS dedicated) & 2 TB NVMe SSDs, Corsair RM850X 850 W, NZXT H7 Flow, MSI G274CV.

Peripherals: VKB Gunfighter Mk.II w. MCG Pro, MFG Crosswind V3 Graphite, Logitech Extreme 3D Pro.

Posted

When ED decides to make a full-fidelity Su-27, let's hope they actually call it "Su-27" and not T-10-1" 😉 

Spoiler

Ryzen 7 9800X3D | 96GB G.Skill Ripjaws M5 Neo DDR5-6000 | Asus ProArt RTX 4080 Super | ASUS ROG Strix X870E-E GAMING | Samsung 990Pro 2TB + 990Pro 4TB NMVe | VR: Varjo Aero
VPC MT-50CM2 grip on VPForce Rhino with Z-curve extension | VPC CM3 throttle | VPC CP2 + 3 | FSSB R3L | VPC Rotor TCS Plus base with SharKa-50 grip | Everything mounted on Monstertech MFC-1 | VPC R1-Falcon pedals with damper | Pro Flight Trainer Puma

OpenXR | PD 1.0 | 100% render resolution | DCS graphics settings
Win11 Pro 24H2 - VBS/HAGS/Game Mode ON

 

Posted

I support the rename.

I wish ED was a bit more careful with internal naming scheme. For some aircrafts they use official designation but for some inofficial. And in some cases they actually duplicate designation for 2 variants (example Ka-50).

BTW it is interesting to note that X-25, X-29 was envisioned in this version already.

I wonder why they dropped that.

Off course X-29 came to 29 later, but it is worth noting that it was part of upgrade options for 9.12 operators.

Condition: green

Posted
9 minutes ago, Volator said:

I always took MiG-29A as a colloquial form of NATO lingo

Yes that's fine for Flaming Cliffs, but many people expect more from a full-fidelity module. If Heatblur can call their modules "F-14A-135-GR" and "F-4E-45-MC", then ED can call it "MiG-29 9.12A".
It will also make the distinction  between FC3 and FF easier for the more casual people 🙂 

Spoiler

Ryzen 7 9800X3D | 96GB G.Skill Ripjaws M5 Neo DDR5-6000 | Asus ProArt RTX 4080 Super | ASUS ROG Strix X870E-E GAMING | Samsung 990Pro 2TB + 990Pro 4TB NMVe | VR: Varjo Aero
VPC MT-50CM2 grip on VPForce Rhino with Z-curve extension | VPC CM3 throttle | VPC CP2 + 3 | FSSB R3L | VPC Rotor TCS Plus base with SharKa-50 grip | Everything mounted on Monstertech MFC-1 | VPC R1-Falcon pedals with damper | Pro Flight Trainer Puma

OpenXR | PD 1.0 | 100% render resolution | DCS graphics settings
Win11 Pro 24H2 - VBS/HAGS/Game Mode ON

 

×
×
  • Create New...