PiedDroit

I can't say much about the other settings as my system if far from your specs, but I'd suggest turning "Halo Lumineux" OFF, as those options are only nice for adding cinema effects (when the sim is used to shoot mini-films).

I understand for the choppers but here the issue is for fixed wing aircraft. Any stick, especially with an extension, should be OK to fly a fixed wing in DCS. Is it possible that the OP has a duplicate input?

That is strange, increasing length should have opposite effect. Maybe something else is happening, when you move the stick, is it having a weird response (jumpy) ? Can you post a screenshot of the axis tuning applet for roll axis? To make it clear, is the aircraft rolling too fast or too slowly when you apply roll input? I just want to make sure we're talking about the same thing :D

hI'm not sure to understand, you increased the length of the stick and at the same tine increased curve to 40? What happens if curve is set to 0 (do not use negative number or it will get super twitchy in the the center)? Adding stick length will mechanically make it easier for fine manoeuvring, so it's probably a setup issue. If stick travel is too big for you (eg forces you to swing it too much), adjust "Saturation X" instead (default is 100,try a smaller value like 70). (see this thread: https://forums.eagle.ru/showthread.php?t=164669)

I'm also following this kind of stuff as I can't get a Rift right now but will probably get something soon. So far FOVE seems the most interesting to me for DCS as it looks pretty similar to Rift/Vive except with slightly higher resolution, which is all the two other I cited are lacking at the moment. OSVR and VRVANA look nice but they're not bringing much improvement in that area (given their current specs). Well, they both have RGB screen instead of pentile, maybe this will make them better. Starvr looks great for the FOV but I'd rather go for pixel density instead of FOV. There are also other systems with higher resolution but I have doubts they will be useable for DCS (VR820, PIMAX). P.S.: So far I tried OR DK1, DK2, CV1 with pixel density 1.0 and 2.5

TCAS, basically - finally available to mil users.

The auxiliary gun sight? It's not linked to TAS or RS.

Ok, what you are looking for is Radar Azimuth MIDDLE, NARROW or WIDE (respectively 30°, 15° and 60°). Narrow and middle will allow you to move the scan zone (by moving the TDC), 60° uses full coverage so it's not possible to adjust it (it's the default mode). I don't know what are the default key but it's easy to find in controls. In the cockpit, the switch is on the radar panel, on the left side, it is labeled "BALAYAGE" (=sweep) and "60, 30, 15".

What is "this"?

TDC is bugged, it has a hardcoded threshold. It only starts moving at 50. Try custom curve 50 to 100

I hoped it wouldn't derail. But it dit. I guess it's inevitable, some topics are just too tempting :doh:

Nice trolling attempt :mad: Please read the thread before posting, it ain't all in the title.

Pretty much technical and doctrine reasons. As an interceptor it doesn't need to be a missile truck. Mags and 530Ds are rail launched which prevent them to be used from belly pylons (gas ingestion). Mica missiles can be launched from pylons but no Mica's on the -C. Outer pylons can't carry 530D (too heavy). Only Greek Mirage can carry 4 MAGs (DCS version can do it too AFAIK). There are at least 2 threads on that specific topic unfortunately search is clunky on the phone so I can't link them now.

Try selecting the auxiliary radio, it worked a while ago, maybe it still does.

I know nothing new I'm just adding this for anyone who's completely new to the Mirage and might read this and think the box is a magical device :D

It does reflect it, although probably not 1 to 1. A real ILS doesn't know the angle, it only read DDM (difference in the depth of modulation) values, max DDM = max scale and that's it, it might be shown as a dashed line of 45° but the actual angle may not be 45° (probably less). This needs some more details, bindly chasing the box invariably leads to wild oscillations. The box only represents deviation, so you need to adjust your heading and altitude correction based on how close you are from the runway (just like you would fly ILS, because that's exactly what it is)...

Not only in theory, in real life too! The ILS deviations are really only deviations, the ILS antenna don't know anything about the runway heading. There is really two different things (deviation and director) and it's important to distinguish the two. - Deviation will only show you the deviation relatively to the course thanks to the ILS antennas. - Director will compute the flight path so you can intersect the runway heading, it needs the runway heading in addition to the deviations. The bars on the ADI can be of different types, depending on the aircraft. I'm not sure about A-10C but the way you describe it make me think they are director bars (edit: OK I saw your edit). On the MiG-21 those bars are flight director too, they will tell you how to fly the aircraft in order to intercept your radial or your runway, according to the course you set. But in the Mirage-2000C, the little square in the HUD - and the bars on ADI - is not a flight director, it only shows deviations, so you need to interpret it differently. In the end you must have the FPM on top of the square - and the bars in the middle of the ADI - but the way you will do it is different. Same for the dashed line, it doesn't show the heading, it only shows the deviations versus the localizer transmitter. If the dashed line is on the right, it means your position is too much on the left. You could be flying 90° relatively to the runway or on the same heading, that wouldn't change anything because it is only a deviation.

Maybe there's a confusion here, deviation bars are pure ILS and don't need any heading data, the dashed line as well as the box in HUD corresponds to the deviations. Director (ie flight director) will need heading data in order to compute the right intercept course, as you say the director will need a heading that comes either from pilot input or a database. In the Mirage's case, it's a database I think, the same that allows to draw the synthetic runway. I'm not sure what flight director looks like in the Mirage

It's probably an iterative process. SU-25T has the same issue with its laser ranging.

Ideally, the cursor would change aspect when hovering on a switch, showing how the click will affect the switch. That would make switch manipulation obvious. Example: ^v: left click up, right click down v^: left click down, right click up <>: left click left, right click right ><: left click right, rigth click left That is something that could be done for new modules I suppose, by adding a property to the switch, that would be read when setting the cursor aspect.

I personally prefer doing that kind of stuff solo or small group coop. Setting up public servers like this would drive people away I guess - not everyone wants to be doing this all the time.

Any keyboard character key that is held down will start to repeat after a couple of seconds, that is normal behaviour, your keyboard does that too. What you need to check is that if this repetition looks normal compared to what happens when you press the same key on the keyboard.

Do a simple test: open notepad, press the trigger and see how many characters are sent.

This might be caused by inaccurate altitude data. Make sure radalt is ON and RA is selected on PCA. TAS is even more accurate (uses radar) but I don't know if it's working atm. Also try level flight delivery (go fast)

Yeah that's what I meant. It appears that "set HUD as SOI" is written twice, only because the first time I advise to check all targets before starting the run. There is nothing fancy ;) There are many ways to quickly select your target in succession, I find the mark points easier to use. The main point here is to get all targets to be stored one way or another then make them SPI in succession. Also, having HUD as SOI allows quick Mav selection (China forward). edit: I added "optional" to the post so it's more clear.