MA_Seyo

The app does not seem to work with the Mirage F1 EE (only CE works). Is there a known fix for this? Granted the EE released recently

Having tested it yesterday this still happens, even though the thread is marked as fixed. Not that it's a particularly major issue. It sits at an even 50% after startup, but after throttling up and down again it starts jumping between 47 and 52%

It's for this reason that I'd much prefer a 2000D if we're going to beg for any new Mirages, but as has been said already Razbam's plenty busy and we're of course at the mercy of the AdA

That one yeah. I have a Virpil throttle as well, CM1 V3, but you can see in the screenshot I posted that all non-keyboard devices are greyed out for the weapon selection rotary for me. Interesting that it works for you

It works but the default head position is pretty high so you need to lean down to see the reticle (see image)

Hello! The Ka-50 has got a wonderful feature where it raises the helmet mounted sight further up on the screen so that you do not have to look up to designate a target right in front of you. It would be great to have this feature for the Hind's Petrovich designator crosshair as well. To illustrate what I mean I'll show some pictures. This screenshot is taken immediately after re-centering the TrackIR view, looking straight ahead. The crosshair is in the center of the screen, meaning you would have to look up to designate any target that you see. The Ka-50 has got an option in the Special settings called "Helmet ring displacement" that moves its helmet-mounted designator up or down from the center, like this (image). This option makes it more comfortable to designate targets since you don't have to look up to designate something, you can just look at the target normally. It would be great to have this option for the Hind as well.

The weapon selection rotary switch can also only be bound to the keyboard right now, not the HOTAS. Image

Hello! When performing an ATGM attack with Petrovich in the front seat he will launch ATGMs outside of range if set to Weapons Free. In Wags' ATGM tutorial he describes that Petrovich should only fire once within range (timestamped link) and on page 71 of the Quick Start Guide the Weapons Free mode is described as "If ROE is green (Weapons Free), Petrovich will launch and guide an ATGM as soon as launch parameters are met.". However, in my tests with Weapons Free mode Petrovich will launch an ATGM as soon as his sight is on target and he gets a launch tone. This seems to happen about 7.5 km from the target, making the missiles detonate mid-air since they do not have enough energy to reach the target from that range. This is consistently reproducible. Here's a video showing the issue using Active Pause. PetrovichRangeTest2.trk

The tanker issue is because it's a KC-135, i.e. the boom tanker that the Tomcat can not refuel from. If it's switched to a KC-135 MPRS it should work. Edit: The tanker on mission six that is an MPRS does not reply for some reason though (after completing the mission), anyone else experienced that?

Hello. I'm playing the SC version in MP and we're stuck on mission 2, it simply won't launch us from the cat. The jet blast deflector is down and the ground crew is simply standing around as if we're not there. Ground crew does not respond to commands (request launch/salute), and since we are stuck on the catapult we can not try a different cat. The other flight does however take off normally and the jet blast deflector is up for our wingman. We've tried restarting the mission and the same thing occurred. Screenshot attached. Edit: Same on mission 3. Also noticed that in mission 3 the non-SC carrier's deck is lots more populated than the SC carrier's. The non-SC carrier could launch us FWIW. UPDATE: The host MUST take the pilot slot for the SC ground crew to launch the aircraft. If the host is in the RIO slot it does not work.

I have to agree with Furiz. While it's admirable that ED wants to consider the comunity's opinion on this it seems like a black or white issue where the weapons either can or can not be used from those pylons.

Late reply, but yes to both in case others have the same question

A note about the bug in row 14. It says that required taxi RPM is roughly 65%, but I tested it just now and it's closer to 45%. (See video: ) The 65% number also isn't mentioned in the linked bug report.

I'll rarely say no to "do you want X in DCS", but I'll probably say "yes, but I want A, B, and C first". I'd love a C-130 if we get a logistics system tied into the dynamic campaign/MP, for example

Back that stuff up now, before you need it! Hard drives can (and will eventually) fail.