Profile image

[KE-RP] MiG-9CN Fargo (REUPLOAD)

124k LunarEclipseSP  9 days ago

This is a reupload

Due to a frustrating problem with the XML update, I am unable to update the XML and I had no choice but to reupload it again. I had no idea how to deal with this, I mean like... what is the supposed max size of the XML file to update it?


Patch 1.0

  • Removed the airbrake, as it turns out the actual jet has none of those.

Overview

The MiG-9CN (NATE reporting name: Fargo) Is the very first jet aircraft to arrive in Kinda and the first jet for KLAAF by late 1944. It's the Kindese variant of the Socket Onion's original MiG-9 jet fighter, features the reverse-engineered Jerry BMW 003 engine.

History

In total, 610 aircraft were built, including prototypes, and they entered service in mid-1944 with the Socket Air Forces. At least 372 were transferred to the Kindese Liberation Army Air Force in late 1944 to defend Kindese cities against air raids by the Nationalist Kindese and train the Kindese pilots in jet operations. This jet powered fighter would prominently used by the People's Republic of Kinda in this ongoing Kindese Civil War against the Kindese Nationalist Party and Okayland, which also known as Republic of Kinda.


Features

  • War Thunder-ish weapons

Armaments

  • 23mm guns
  • 40x 37mm cannon

Controls

  • Normal flight controls.

Gun controls

  • Spacebar = Fire guns.
  • LAlt = Fire cannon.

Guidelines

Speed

  • 100% throttle = Full speed.
  • 50% throttle = Medium speed.
  • 20% throttle = Landing speed.

Landing

  • Throttle 20-10% until touchdown.
  • Brake immediately to reduce speed.

Trivia

  • This Knockoff Earth version of MiG-9 was developed earlier than it's real-life counterpart which is around 1946, that was because the "jet engine era" has begun around late 1943 and early 1944.
  • In real-life, the Chinese version of MiG-9 Fargo was delivered and operated by the PLAAF in 1950.

Creator's note:

General Characteristics

  • Created On Windows
  • Wingspan 32.2ft (9.8m)
  • Length 35.4ft (10.8m)
  • Height 10.3ft (3.1m)
  • Empty Weight N/A
  • Loaded Weight 8,009lbs (3,632kg)

Performance

  • Power/Weight Ratio 3.788
  • Wing Loading 33.0lbs/ft2 (161.0kg/m2)
  • Wing Area 242.9ft2 (22.6m2)
  • Drag Points 2934

Parts

  • Number of Parts 35
  • Control Surfaces 7
  • Performance Cost 253
  • Log in to leave a comment
  • Profile image

    No one likes my plane, only 6 upvotes, i am useless

    6 days ago
  • Profile image
    27.1k Rob119

    MiG-9CN Fargo? More like MiG-9CN wells fargo hehe uh... am I right?

    +1 8 days ago
  • Profile image

    @UnitedinOne90XCVBNKA bro I don’t use tik tok 😭

    +2 8 days ago
  • Profile image

    @Hahahahaahahshs its some abbreviation that tiktok users use.

    9 days ago
  • Profile image

    @UnitedinOne90XCVBNKA what

    +2 9 days ago
  • Profile image

    @Hahahahaahahshs Icl ts pmo u srs gng? 🪫🥀💔

    +1 9 days ago
  • Profile image

    i love eating gun fumes

    +1 9 days ago
  • Profile image

    0_0

    +1 9 days ago
  • Profile image
    2,129 crone

    tl;dr: made by the sobriety onion and used by the plafe

    +1 9 days ago
  • Profile image

    @WHNineTripleOne And now I would love to hear some feedback from the development team regarding the issues in this XML update method.

    +1 9 days ago
  • Profile image

    Once i had a same issue as yours. It basically like a gamble that if you're lucky enough the XML always invalid, despite we put a correct url ID, or the file could actually exceeding max side. We even had no idea what is the maximum size. But with my own method, as i remember, i copy an existing XML code with the smallest size, paste it somewhere else outside the SP folder, delete the XML script and replace it with the XML script from the desired build, and save it with the same name as the build you want to update. Basically you'll have the "reverse-engineered" version of the XML file, and try to update the XML again with the "reverse-engineered" version of the XML folder. That should be working again.
    .

    "Yeah sometimes a complicated problem always needs an even more complicated solution from the problem itself"

    +4 9 days ago
  • Profile image

    Calling developer teams regarding of this frustrating issue of XML updating (Always have been)
    .
    @AndrewGarrison
    @WNP78

    9 days ago
  • Profile image

    Socket Onion:
    @DeeganWithABazooka
    .
    Republic of Okayland/Kindese Nationalist Party:
    @Cuboidable

    9 days ago