Jump to content

Flies backwards within 2 seconds, catches fire, and tumbles to the ground...


sleat

Recommended Posts

Hello,

 

First off, this looks like a great module, so I'm obviously doing something terribly wrong.

 

All the other aircraft and helicopters fly perfectly after configuring the HOTAS and axes.

 

If I start from the runway, using instant action->takeoff...the aircraft simply won't come unstuck. From an external view, I can visually confirm I'm getting full range movement of the elevons. They don't seem to put any moment or force onto the airframe at all.

 

Control surfaces check out fine, move in the right sense, and are not double-mapped to multiple axes. The aircraft simply accelerates past the rotate speed without being able to rotate, and if I don't abort the takeoff, the L/G fails and the plane slides to a halt and catches fire.

 

Now, I assumed "maybe I'm in some sort of wrong FBW mode" except there are no warning lights.

 

Further testing, Instant Action->Free Flight. The flight lasts for 5 seconds!

 

The pilot instantly blacks out, the aircraft does a nose-down somersault within 1 second, flies backwards, parts fly off, it catches fire, and tumbles to the ground. Total flight duration < 10 seconds!

 

Control Setup: HOTAS Warthog, and Saitek Rudders

 

Attached: Track File and Briefing (.log renamed to .doc) for the instant disintegration from Free Flight Instant Action.

 

I really hope someone can advise what might be wrong. Again, no problems at all flying anything else.

Mirage 2000 10 second flight.trk

Mirage 2000 10 second flight_log_renamed to.doc

Link to comment
Share on other sites

What is the version of your M2K module?

 

Sent from my SM-G935W8 using Tapatalk

--Maulkin

 

 

Windows 10 64-bit - AMD Ryzen 9 5900X @ 3.7 GHz - 32 GB DDR4 3600MHz RAM - EVGA FTW3 RTX 3080 - Asus Crosshair VIII Hero motherboard - Samsung EVO Pro 1 TB SSD - TrackIR 4 Pro - Thrustmaster Warthog - Saitek rudder pedals - Lilliput UM-80/C with TM Cougars

Link to comment
Share on other sites

Did you remove all the bindings for pitch and roll for every controller except your flight stick? Those axes are mapped by default for all controllers.

 

Yes, of course. Every new airplane gets the same treatment. As I mentioned nothing was "double-mapped" to multiple control axes.

 

It's very strange. Perhaps I'll try un-mapping pitch and see what happens.

 

Thanks for the quick response!

 

**********************************************

 

UPDATE: It's not the joystick! Same behavior trying to take off with the keyboard alone, joystick completely unmapped. Won't come unstuck at all, despite the elevons moving just as they should!


Edited by sleat
More information
Link to comment
Share on other sites

1.5.5 Beta it says.

Could you also check in the lower right corner of the main screen to get you client version? I will look something like this: 1.5.#.#### I think

 

Sent from my SM-G935W8 using Tapatalk

--Maulkin

 

 

Windows 10 64-bit - AMD Ryzen 9 5900X @ 3.7 GHz - 32 GB DDR4 3600MHz RAM - EVGA FTW3 RTX 3080 - Asus Crosshair VIII Hero motherboard - Samsung EVO Pro 1 TB SSD - TrackIR 4 Pro - Thrustmaster Warthog - Saitek rudder pedals - Lilliput UM-80/C with TM Cougars

Link to comment
Share on other sites

Could you also check in the lower right corner of the main screen to get you client version? I will look something like this: 1.5.#.#### I think

 

Sent from my SM-G935W8 using Tapatalk

 

Yes indeed! That's 1.5.6.3930 The problem is in that version.

 

AFAIK that is the latest version as of right now.

 

Incidentally, the problem is not universal. Identical setup in OpenAlpha 2.0.5.3889 but there the controls work.

 

I just discovered the flying at least is perfect in OpenAlpha.

 

Just did some night circuits in Vegas, a few takeoffs and landings, the Mirage is a very easy aircraft to fly. Handles great (it's the FBW I guess) you just have to remember it's a delta when you land! I didn't read the P charts, but it handles much like any delta, you have to approach fairly fast, since you lose it all in the flare.

 

Still a problem, though, as I can't do any of the training, it needs to work in Release DCS.

Link to comment
Share on other sites

1.5.5 is outdated and had issues similar to this for many modules.

 

1.5.6 is the latest version.

 

Do you mean 1.5.5 DCS, or 1.5.5 Beta M2000C module?

 

My DCS is 1.5.6.3930. My M2000C is 1.5.5 Beta.

 

If there is a Mirage 1.5.6 how do I get it?

Link to comment
Share on other sites

I forget the direct link but do a google on "DCS updater"

 

Sent from my SM-G935W8 using Tapatalk

--Maulkin

 

 

Windows 10 64-bit - AMD Ryzen 9 5900X @ 3.7 GHz - 32 GB DDR4 3600MHz RAM - EVGA FTW3 RTX 3080 - Asus Crosshair VIII Hero motherboard - Samsung EVO Pro 1 TB SSD - TrackIR 4 Pro - Thrustmaster Warthog - Saitek rudder pedals - Lilliput UM-80/C with TM Cougars

Link to comment
Share on other sites

Do you mean 1.5.5 DCS, or 1.5.5 Beta M2000C module?

 

My DCS is 1.5.6.3930. My M2000C is 1.5.5 Beta.

 

If there is a Mirage 1.5.6 how do I get it?

 

Oh. If the game is 1.5.6 you should be fine. The module always updates with the game.

DCS modules are built up to a spec, not down to a schedule.

 

In order to utilize a system to your advantage, you must know how it works.

Link to comment
Share on other sites

Oh. If the game is 1.5.6 you should be fine. The module always updates with the game.

 

Yes, you'd think, but no, no it doesn't. For some reason the DCS updater just glossed over this (and who knows what other) aircraft all those times I ran it.

 

Force-updating RAZBAM_M-2000C with the updater via command-line did the trick!

 

Flies fine now! Like night and day, really. Or maybe pointy-end blunt-end.

 

Not sure how this happens considering that the updater runs every time DCS runs.

 

Makes me think I'd probably better force-update everything after checking the versions.

 

I couldn't find the list of the latest version for each module in the post that Maulkin mentioned, so I might just have to do 'em all.

 

The M2000 was the only one obviously playing up, though.

 

Gentlemen one and all, thanks a bunch! That was the quickest resolution of what seemed like a serious issue I've seen in a good while. Well done!

Link to comment
Share on other sites

DCS_Updater.exe CLEAN

DCS_Updater.exe REPAIR

DCS_UPdater.exe UPDATE

 

If the Module is not installed properly it will not update it.

 

Autoupdate.cfg should have a string that shows which modules it will download files for.

(Do not Edit this File).

 

if Any Moduules you own are missing, they need to be re-installed properly

DCS_Updater.exe INSTALL <MODULE_ID>.

 

DCS Updater Guide:

https://forums.eagle.ru/showthread.php?t=114030

 

Thread has Version History as well as Module IDs

 

Last Post has Link to DCS Updater GUI Utility which would make it a but easier if you dont want to type command prompt strings./

Windows 10 Pro, Ryzen 2700X @ 4.6Ghz, 32GB DDR4-3200 GSkill (F4-3200C16D-16GTZR x2),

ASRock X470 Taichi Ultimate, XFX RX6800XT Merc 310 (RX-68XTALFD9)

3x ASUS VS248HP + Oculus HMD, Thrustmaster Warthog HOTAS + MFDs

Link to comment
Share on other sites

  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...