Robin_Hood

I would sure love to have good depression tables for the Mirage. However I am still not sure how accurate the F-5E tables are. I did this test some time ago and requested for comments (maybe I am doing something wrong), but I still don't know if I'm using the tables incorrectly or if there is something wrong in DCS.

Mods do not necessarily have to pass the IC (and I don't think anyone wanting to have the Mica on the 2000C expects that to pass IC). Servers can choose not to IC.

Yesterday while flying a mission, I came across a bug ; there are certain (valid) coordinates that the INS won't accept. I found two sets of those for latitudes, I have not tried longitudes. For example, entering those latitudes results in an error: N41°01.01, N41°01.02, N41°01.03 and also N42°01.01, N42°01.02, N42°01.03 N41°00.00, N41°01.01 and N41°04.01 (for example) work fine, however. Is this a known bug ? Can anyone confirm it does it for them as well ? I attached screenshots of the PCN just before and after pressing INS to validate coordinates.

Yes, the AG designate/Magic Slave/INS Update initiates radar update (recalage oblique), while the Magic Search/Nav Update initiates the overfly update (equivalent to pressing REC button on the PCN). So whatever type update you want to make, you do not have to take your hands off the HOTAS.

I just noticed this: when the waypoint 0 is selected on the VTB (ie: digital BRA is displayed), changing to Cv Nac on the HSI changes the bearing from magnetic to true. However, when some other waypoint is selected, then it does nothing, and true bearing is always used. I don't know if this is intended, but this is a little weird (especially since Bullseye calls should use magnetic bearings AFAIK).

The Mission Editor has this bizarre quirk where the wind direction is the direction the wind is blowing to (or, maybe it's simply how it's done in Russia) instead of from. Seems the JTAC does that too. Not sure if it is possible to (like the coordinates format).

You have to put a waypoint on the position of the bullseye, then.

Alright, interesting choice. And yeah, I forgot Low PRF is also used for AG radar, my bad. So one might see more difference between HFR and BFR than between the F-15C's HI and MED PRF, possibly ? But of course it'll all depend on signal treatment and filtering. Does the RDY has 4 settings then, or does it not have an interleaved setting ? Not that this is relevant for this discussion.

In any case, PFR selection certainly does something, simply because in BFR radar contacts are displayed as squares and cannot be locked. This is just to say that the switch is quite functional and does something. Now, does it really improve detection on low aspect targets, I couldn't tell, but it is certainly Worth testing. By the way, I suspect that BFR (Basse Fréquence) "Low PRF" is a bit of a misnomer (or at least confusing if you are used to US terminology), and is simply what americans would call Medium PRF, as there is no middle setting, just High, Low, and Interleaved, just as the US radars have High, Medium, and Interleaved). Of course, I could be wrong, but I think what the US calls Low PFR is mostly used in large search radars, for long range search, and I would be rather surprised to see that in a fighter aircraft.

As for the knobs in question, I also Wonder if they are: 1. Not implemented in DCS, 2. Non functional in the real aircraft, or 3. Functional in the real aircraft but never used I'm afraid jojo's answer could be interpreted as any of the three.

Also, if you drop your bombs you won't be able to lock anything (probably bombs are still selected even though they ar gone). Selecting a weapon, or POL mode should do the trick.

Fisrt thing that comes to my mind is: have you entered a leading 0 for the coordinate ? The INS requires that you input 7 digits for the east coordinate, but 6 for the north coordinate, so for example, N 42 23 52, E 041 43 25.

What you want to do (if in air-to-air configuration) is select the 530D on the PCA, and have the three switches (actually three positions of the same switch) mentionned by Azrayen ready at your fingertips. Then you will have a very efficient way of selecting exactly the weapon you want : - for Magic, press Magic select - for guns, press A-A Gun select - for 530D, press PCA select Note that currently, pressing PCA select a second time (that is, if you are already in PCA select) will cancel the 530D selection. I imagine this will change in the future (IRL it is not possible to do this, because PCA select is the neutral position of the switch).

Pretty sure you can make additional skins without overwriting old ones, using the Liveries folder (either in DCS World/Bazar/Liveries, or in Saved Games/DCS/Liveries). Make a description.lua that will call the texture file(s) that you need. These texture files will have to be added via a mod. If you don't know how to do that, ask away :)

I know this is an old thread, but since it didn't got a definitive answer, I'll put it in here for others who might come across the same problem, as have I today. The problem is with the setting of the AWACS. The Invisible action should be placed before the Orbit option, or it will be ignored. The Immortal action will probably be ignored too. Not sure if it's intended, but apparently when it comes to the Orbit action, the game stays there (as long as it is orbiting I imagine) and ignores the others. If you push those actions up, and let Orbit be the last one, it should work. This will not work: But this will work:

I have the same experience. It used to work as a toggle, though.

Entropy has posted his POV of the whole thing (sunday) on Youtube here: It is not the POV of the JTACs, obviously, but he does work with us during the course of the video.

Indeed there is an oil field around there. There should be an oïl refinery in Tuaps I think also, but it is not present in game. IIRC, it should take up almost all of the southern bank of the river.

Sure, but this is probably not what we are seeing here (those kind of errors would be more random). I am under the impression that the designation is inaccurate. I tried designating a target from ~4 miles in a 20-30° dive, and when coming closer and closer, I can see that the impact point is behind what I designated. I don't know if this accounts for most of the problem, or if what I am seeing is inaccuracy of the cross placement in the HUD (wasn't it supposed to go, BTW ?), but it could count for something.

Sorry, I can't make it for 1700Z; 1800Z, possibly.

I would be interested as well, to flesh out my knowledge in this regard. Question : I understand from your OP that this will be 1 theory lesson session, followed on different days by 2 events to put it in practice (3 separate days on the whole) ? I normally fly @1900Z, but could probably make 1800Z if needed.

Yes, indeed, these were not entirely finished and polished, but I plan to add the version used next time (indeed I did just that on a previous similar undertaking). I may make a quick test for ITR (which is much quicker to do) just to see if it has changed a lot in this regard (although I expect that STR has changed more), but I have halted the tests at the moment. I am waiting for the FM to stablilise a bit (last changelogs had FM changes), although I don't really expect the FM to stay the same after my next series of tests anyway (fine tuning a FM being a long process).

I think this is as good a place as any to put this. Here are some charts that I did for the DCS Mirage 2000C. It shows the maximum instantaneous and maximum sustained turn rates. Please note: I only did one configuration ; I did 20kft but haven't made the full E-M chart yet, so attached is the turn rate only ; also these were made in march and therefore obsolete (I should do them all over again with the latest FM changes), but nevertheless I think they are a start. Everything comes from in-flight testing. Here we go, I hope you find it useful.

Problem is, the KC-135 we currently have is boom-only. I hope ED will have us a probe-and-drogue compatible KC-135 with the F/A-18C, at least, if none has come out yet. The best would be to be able to choose which configuration in the payload screen: boom only, boom drogue adapter, or MPRS (Multi-Point Refueling System).

I just tested it in the latest release, and it seems fixed there at least. I have tested with these exact units : - Russian Igla-S - Georgian Stinger - Georgian Igla All gave a launch warning - track attached. To be fair, though, the very first time I tried, against Igla-S, I didn't have a launch warning. But I don't expect this kind of system to be infallible. MANPADS MWS.trk