Althar93

Wow, the Gazelle feels so much lighter/twitchier ; I bought the module the other week when the fuel mass bug was present & it definitely felt very heavy. This is a night and day difference. I can now do a vertical take off with 90% fuel and 4 mistrals, whereas previously it was struggling to get past 5 ft running empty.

Hello all, Is the periscope meant to look like this at night? Is this a bug, or am I missing something like some brightness adjustement? I was under the impression the periscope was purely optical and wasn't a (IR) camera feed, but maybe I got the wrong end of the stick. Thanks!

Oh I don't have any issues flying/hovering from the copilot's seat and using the Vivianne at the same time. My issue is that in the Weapons training mission, even with 100% collective whilst in a stable hover a few hundred feet off the ground, my vertical speed won't remain positive, and the Gazelle will just slowly descends, all the way to 5 feet or so, where it seems happy to sit. Having tried a few loadouts with the mission editor following your advice, I acknowledge hovering with a constant altitude is not an issue with less fuel.

Thanks, just tried empty with 10% fuel and climbing /maintaining altitude in hover is no problem. I take it the instructions for the missile training mission, to first establish in auto-hover is not possible as a result of the loadout/fuel?

Hey all, I finally got the Gazelle in the Steam sales after eyeing it up for a little while / waiting for the new FM. I am enjoying it & its simplicity and have flown a couple of training & instant missions. One aspect that I am currently struggling with is : maintaining altitude whilst in a hover. I am not sure if this is related to the fuel / weight bug that has been discussed lately, or if I am doing something wrong, but essentially even at full collective, and with some good altitude to begin with, I simply cannot gain/nor maintain altitude. This makes it impossible for me to conduct pop-up attacks and also means that over time, if I do not have any forward motion, my Gazelle will slowly but surely descend back to the ground. Am I doing anything wrong / is this expected, or is this a (possibly the same fuel/weight) bug? Thanks in advance!

Hey all, I am not sure if this is a bug, intended behaviour and/or just me doing something wrong, but after completing alignment of the reference system after start-up, and witnessing the warning light extinguish, and I will turn my HUD on and verify everything is lined up with the horizon. I will then start to taxi and sometimes (maybe 1/10 times), after turning, the reference will tilt itself to the side and stay that way. I can easily fix this by turning down the reference system, waiting for a minute and running it again but I find this curious. Has anyone else been experiencing this behaviour? Cheers,

Great suggestion! I wouldn't mind if Aerges sped up every dial, trying to set a TACAN offset is also incredibly slow...

Hey all, I've seen this briefly mentioned in older posts but nothing current so I'll post it here again. It would be extremely useful to have the ability to toggle between 'Units' on the F10 Map in-game, without having to go back to the main menu/settings. This seems like a fairly trivial thing to add and would allow players to switch between Blufor and Redfor in SP or MP and be able to use the ruler with the corresponding measurements.

Well observed, my bad ; what I was trying to demonstrate was the inconsistencies when switching between TL & BZ and got confused in the process. Below is what you get if you switch to TL & then to BZ. Not sure if this is a bug or by design though. Here is the issue I was trying to demonstrate with TL :

Same issue for me, I have to switch back and forth several times for the TEL mode to work : same observation as other people, if there is radar noise then it picks up contacts fine, otherwise it does not. I have also seen the radar scope be broken when switching back out of either TEL/BPZ modes, whereby the noise will only render to a small narrow band (as if still in the TEL mode), but with the sweep going left to right on the full width of the scope. [EDIT] : The issue with TEL seems to happen if you switch directly from BPZ to TEL, rather than from the normal mode. TEL mode not working below

Well, it was designed and built in the 60s-70s, so a lot of its systems, 'HUD' included, are fairly primitive still & the plane won't hold your hand. The challenge is certainly where the fun is at for me. I wouldn't expect it to get any 'better' either, AFAIK, this is just how the plane flew/fought.

Maybe this is because I'm pretty used to flying the Mig-21, but the Mirage F1 feels extremely stable & easy to fly in comparison. I have a VKB Gunfighter Mk.III (placed on my desk, no extensions) & have my pitch/roll axes curves set to '20' The Mirage, just like the Mig-21 does seem to have a tendency to just drop out of the sky if you bleed too much speed ; worth noting, both of those plane will need proper rudder input to guarantee coordinated flight, or you will get a fair bit of adverse yaw.

Same issue here - the training missions are very well made and worked flawlessly until I got to training mission 10 and now all the subsequent missions I've tried after this have scripts not triggering and the whole training mission just soft locks.

You will find more information about this on the post that I created the other day which has now been moved to the resolved section : (with a neat video & photo to show the button in action on the real thing)

Just wanted to say thanks to Razbam for this amazing RDI update! Fired up the AA training mission to get myself accustomed to any changes (that and the fact I was terribly rusty). I was messing around with the radar modes in the second part of the training (Magic missiles on the jamming targets) and noticed this : Love the fact that the jammer is actually modelled and picked up by the display that way (I think I actually noticed the cone/noise on the display before the radar was even classifying it as a jammer signal) ! It does seem like this intermediate mode may be a good way of spotting targets that are so to speak 'under the radar', as long as you know what you are looking for.

I have also noticed this issue myself when running the Cold Star Training mission - it looks like the INS buttons are always fully lit and so it is impossible to tell what state they are in (e.g. the VAL button of the INS when you are ready to initiate alignment).

Ok, now that makes more sense, thanks!

Would it be possible to have the radar antenna axis be the 'target' elevation of the antenna, and just emulate button presses until the radar elevation matches the target, as it would if you were to press the button (so the behaviour can remain as it is now since the update), if having the 1:1 relationship between the axis value and elevation is what is deemed 'unrealistic'? Other than that, really loving the update! Great work all round! The M2000 is easily in my top 3 favourite modules for DCS.

I know the update notes mentioned some bindings had changed but I fail to understand why an axis would no longer work for the radar antenna. I can and have had to find an alternate binding but it was really useful for me to be able to bind this to an axis consistently like I have it working on other modules.

Hello, Perhaps I am getting this module confused with another but I seem to remember there being a separate axis for the radar antenna elevation (which I used to have bound to an axis on my X55 throttle). After the update, this axis seems to be gone and I can only see two separate bindings raising & lowering the antenna using buttons. Would it be possible to have a radar antenna axis (back?) as this is quite a useful way of controlling the radar antenna. Thanks!

Great, that's exactly what I wanted to know :). Thanks all!

My bad, I did mean DLC, not spoilers. As for the overall procedure on touchdown and trapping, I think I am following the procedure more or less correctly, at least to a point where I can get the wings in oversweep without breaking anything. In this instance, my issue/question is more with the inability to close the wing sweep cover once the wing sweep handle is in the oversweep position and whether this is correct behaviour or a bug?

Hello all, I got this module about a year ago during a sale and never had the chance to properly dive into it until now (which is a shame because it's been great fun). While I am getting to grips with the aircraft just fine, the wing sweep & surfaces of the wings are giving me the most trouble. I'll assume most of the following is down to user error but I have become a bit of an expert when it comes to : jamming the flaps, getting the wing sweep stuck, etc. I have been running through the carrier training missions, including the case 1 recovery. Upon landing, I retract the flaps, spoilers, etc. I then open the wing sweep cover, pop the handle out & pull it to the 68 degree position. Once all the relevant indicator/lights have extinguished I am able to pull the handle further back into the oversweep position (full aft). While this works, it appears that I then become unable to close the wing sweep cover after moving the handle to oversweep. Similarly, I lose the abilty to move the wing sweep handle at all after this & the only way to get it unstuck is by using the mouse wheel which just propels it into the full forward position. Any idea if this is the intended behaviour with the wing sweep cover, or am I experiencing a (known) bug? Thanks in advance

That could work although my post was meant more as a 'native' feature suggestion. While using Track IR is nice I am finding that I lose my SA when attempting to find a Jester option and subsequently having to look away from what I was doing. Being right handed I have my hand on the stick or the mouse but not both, so that's where the analogue stick (or 'whatever floats your boat' axis) would be nice to have.

Ok nevermind, I just ignored the 'coordinate' part of the instructions and upon setting the right switch to TID I am able to prompt Jester to perform the INS alignment. After all this, it would seem this is just a mix of user error and the training instructions being somewhat misleading (especially for a beginner).