PiedDroit

Yes, see this the thread on the same topic: Dassault's philosophy behind the M-2000Cs armament?

I can't tell from the video - note that I'm not telling that it's right or wrong. Whatever the reason is, if we don't fireball any aircraft with several hits then the DEFA's stats should be beefed up a bit...

Yes, I agree. It looks like such damage doesn't occur in DCS and other effects are taken in account, effectively making the DEFA look inferior.

I remember those, it looks like the targets are bursting into fireballs. Currently in DCS it looks like there is no incendiary effect, it looks like damage is done through kinetic and explosive power (not only Mirage's gun). I suspect that the DEFA has inferior kinetic stats (in the game) which leads to less damage since there is no incendiary effect. Maybe if that type of damage was more effective the gun would be put on equal footing with the other guns. edit: I definitely agree, I had a test mission with 4 SU-25 as targets from the beginning of the beta, if you don't rip their wings off they will continue flying like it's nothing. In air to air gun I only flew MiG-21 and Mirage-2000C, against different types of AI, the DEFA seemed on par with the MiG's 23mm as far as I remember. I did only one flight in SU-27 against a friend and the gun was brutally effective, ripping his plane like paper... I only summarized the content of the thread. I'd like it to be more effective too. Was it against AI? They continue flying even if you remove both elevators and rudders

I don't know if the difference is huge or not ;) There is one for sure. I also find the round feels a bit unpowered, but I don't have any info that would tell it is realistic or not :cry: That post about AP rounds is a good find, I forgot about it :thumbup:

The topic has been discussed a bit already, you might find some additional info: http://forums.eagle.ru/showthread.php?t=156771 P.S. Quick summary : DEFA round are much smaller than Gsh30's, also damage model against AI seem to be different than against player controlled aircraft

OR implementation in DCS can't zoom, it's a fact, there is no bug please don't derail thread ;)

F7 not working in radio commands F7 key died AWACS Radio Menu doesn't work? Hint: TrackIR :D

Also radar still unlocks if you press lock while already in STT, super annoying.

Hello, for what it's worth, I did the upgrade to Win10 from Win7 Pro, I didn't deactivate any module or reinstall anything and it worked just fine. I can't tell if Win10 works better. It's same or better than Win7, no issues at all for me but you may get some depending on your hardware, do some resarch first. P.S.: Actually the only problem I had was with Saitek rudder, my mouse would freeze and beep when unplugging the rudder. After a while I did an in-depth cleanup of inf files, registry keys related to Saitek and it's all good now, I can unplug the rudder without fear of freezing my computer.

If you have a thrusrmaster WH you can use the idle detent for that purpose. When at 0 throttle, lift the throttle and move it further back. Moving it back again should unlock the levers and start engines in the cockpit, provided you kept the default mappings. For the zoom issue, go to controls, axis commands, and map TrackIR Z axis to longitudinal movement instead of zoom view which is the default.

Check this post: http://forums.eagle.ru/showpost.php?p=2715926&postcount=1376

The worse that can happen is that your controller has a new ID when reconnected to the computer, if you use a different port. In that case you only need to copy the configurations files from the old controller to the new controller. They are located in Saved Games directory, example for my WH: \Saved Games\DCS\Config\Input\A-10C\joystick\Joystick - HOTAS Warthog {89141D80-9A0F-11e2-8001-444553540000}.diff.lua This file contains everything, mapping and axis tuning.

"modders"? haha this is a bit more than a mod, that's a full feature module :D

Ok, that was a DCS-specific question, nevermind then - I didn't fly with the new RWR yet. I will wait for the next stable release then I might be able to comment ;) Regarding systems, there is only one switch for the RWR, so it should be quite straightforward. No funky configuration that I know of.

I don't think the IR detection works at such distance, otherwise all fighters would have it already, in practice it seems only fitted on A-G specialized A/C. The one (D²M) that exists for the Mirage-2000 is used on the D version which is the ground attack variant. How does that translate on the RWR? Sorry not familiar with all terms (nail?). Thanks!

Yes, that's what "pitbull" is - going active with on-board radar. My understanding is that launch warnings against SARH were possible when the radar would change it's emitting pattern from STT lock to weapon guidance, the RWR would pick up the difference. To sum it up, here's what I understood from various discussions: SARH: Lock warning when locked in STT Launch warning when switching to weapon guidance. [*]ARH (with datalink): Lock warning when locked in STT Maybe Lock warning when locked in TWS (probably not) NO launch warning, Missile alert when the missile goes pitbull­

Limiting insurgents make sense (it's not really a country), otherwise, I really hope those will be available to all countries. Aircraft inventory limitations should be done at the mission design level only.

I think the manual has to be updated and the correct behaviour is the one you see in the sim now. I'll let someone more knowledgeable dive into the fine details ;)

Something's not clear to me, are we supposed to get a warning from an AIM-120? I thought it was guided by datalink begore going pitbull. Which means you won't get a launch warning. Lock warning at best.

Good you got it sorted :thumbup: If you have kept the old files maybe a diff would help understanding what was the problem.

I don't have much clue... What does it says in the axis tune applet? And is the TAD cursor still moving after you fiddle with the ministick? I remember that the default axis setting had a a big neutral zone and small Y saturation value. 30 for both I think.

This might be why:

This :thumbup: The correct way is to push the stick, not use the brakes (as the "push down speed" is usually too high for safe brake operation).

Maybe it's not the WH's ministick that controls your crazy TAD cursor? Try unbinding it and see if the problem is still here.