Robin_Hood

First, thank you for this great update, I can't wait to try out all the new stuff :thumbup: This being said, it seems there is a bug with the CCRP release. Apparently, after having dropped bombs once, subsequent bombing passes will see the selected number of bombs being released as soon as the trigger is pressed, and then one more bomb released as the release point is reached. I have attached a very short track that shows it. 8 Mk-82, RIP QTY 02, RIP INT 00. - 1st pass, 2 bombs are released as planned when release solution is reached (they hit slightly short, but that is probably another problem). Bombs left: 6. - 2nd pass, 2 bombs are released as soon as I press the trigger to give consent, and then one more is released at the cue. Bombs left: 3. - 3rd pass, exactly like the 2nd one; 2 + 1 bombs are released. CCRP_release_bug.trk

The manual says (emphasis is mine): So, no mixing rockets and bombs either.

Sure, but actually no. It works different from a paper map. Grid North is used in place of True North pretty much everywhere but for coordinates. Thanks, good to know. Well, I guess this will stay a peculiarity we'll have to live with for some time, then. It can be quite puzzling when you come across it.

The workaround currently is to have one aircraft per group for clients. A return to old days, unfortunately (hopfully not for too long). So if you want a group of 4 aircraft, place one group, set everything, then Ctrl+C / Ctrl+V it three times and you should be good (you might want to copy/paste them before setting the first waypoint on takeoff, just so their initial positions are close enough).

Hi all, I know this has been more or less discussed several times, but I'm not sure there have been definitive answer, so I'd like to know your thoughts about this. Note: I am using the Mirage 2000C to get bearings, so if you think it is an implementation problem within that module, I'll report it, but I think the problem is deeper Inside DCS World. Here's the thing, plain and simple: Flying north along a constant longitude line. Here are the headings I get from various sources. HDG Mag (M-2000C): 346° (approx) HDG True (M-2000C): 352.6°* HDG F10 map: 352 (approx) * From the INS reading Magnetic Variation is 6.1. Since 346° + 6.1° = 352.1°, this sounds alright (Mag + Var = True). However, the meridian is clearly not pointing to the true North there. In fact there is, at that location (somewhere South of Gori) a 80 difference between "F10 North" (as implied by the game) and "Meridian North" (as implied by the meridians on the map - and indeed the coordinates). Could it be that the F10 map actually shows Grid North (which would sound logical), and that the module(s) incorrectly use that as True North and to derive magnetic headings ? Also, as the coordinates indeed agree with meridians, might that not cause trouble in some places* ? * I have already noticed that if you want to deduce coordinates from a starting point and bearing + distance, you should add the F10 North-to-Meridian North difference to gain a good order of accuracy. Also, let me know if I wasn't clear. EDIT: I have just come across this post that states that, indeed, Grid North (F10 North) is used in place of true north by aircraft modules (eg, magnetic headings are calculated via Grid North).

Well, I must admit I have only recently started using it in multiplayer, so I cannot comment too much. I am sure it can is very useful at least to practice* correct tactical formations (such as line abreast) or trail, with set distances, and help you see where you should be. Also, it can help a the rejoin of a lost wingman, or of your second element after a split. Suren it doesn't give bearing (and admittedly, bearing alone might arguably be more useful in that situation than range alone), but it gives you valuable information : how close you are, and if you are getting closer or not. I fell that combined with a bit of communication (such as current headings), it can really help a rejoin. * you wouldn't use them in actual combat because you are, in effect, broadcasting your presence (if not your position) In any case, I feel it is a help, but never a primary means of navigation. It's just a handy extra information.

We are talking about A/A TACAN, right ? I checked the F-5 manual (probably the one you are talking about): - the ARN-65 does not have an A/A position (only OFF, REC and T/R) - the ARN-84 has an A/A (which is a T/R) - the ARN-118 has both A/A REC and A/A T/R I think the manual simply forgets to mention that A/A (REC or T/R) provides bearing from suitably equipped aircraft (ie. KC-10, as I believe this is the only aircraft with a 'directional' TACAN). A/A TACAN between fighters has never given bearing, only distance. By the way. As a side note: T/R needs to be selected for both aircraft to have range (because it works with an interrogation-response system), while REC modes can receive bearing from a suitably station (ground or airborne), but not provide distance (since it is not willing to emit an interrogation). In short, receiving bearing is passive, determining distance is not (of course, transmitting bearing is not passive either). And lastly, TACAN equipment are pretty standard through NATO aircraft, so don't expect wildly different behaviours across the board. I am not sure what is the exact model the Mirage 2000C uses, but is is interesting to note that (in RAZBAM's cockpit at least) the control panel is in English (ie. it has an OFF position instead of A), contrary to almost everything else. EDIT: Compare the wording in the F-15A-D manual: The only inconsistency in the current behaviour of the TACAN in the Mirage 2000C that I can see is that the needle on the HSI does not rotate, but stays fixed instead. EDIT 2: As a further clarification, here's what the F-14D NATOPS flight manual has to say about the TACAN, which is the AN/ARN-118 (the same as on the late F-5s) (emphasis mine): So, you can interrogate one aircraft, answer to five, and the AN/ARN-118 is not capable of transmitting bearing information.

Select OBL* on the PCA (far right), from "normal" mode (no weapon selected, Master Arm OFF). Then the diamond appears and you use the INS Update button to command the update. Finally, validate the change on the PCN with VAL. * Recalage oblique

From my several testings, it seems that the update actually works (in Release version at least), but it always works perfectly, ie. if you purposefully update it on the wrong places, it still acts as if you did the update properly. I have that behaviour in both OBL and overfly modes. So, currently, the update works however badly you are updating it. That is why you can only test it by actually waiting so that the INS has drifted? You cannot test the update procedure by updating it on a wrong position on purpose.

Sometimes when you spawn in a russian plane, the SPO (RWR) immediately and constantly sings as if you were locked by someone. Only way to fix it AFAIK is to leave the plane and respawn again, and hope it doesn't do it anymore. It's been a while since I have flown those, though, so I don't know if it evolved into something else.

We are having the same problem. It doesn't seem to be linked to any particular switch or action in the cockpit. Sometimes it happens shortly after spawning, somtimes it takes a little longer. The comms menu even does come back sometimes, like after landing. FWIW, we are using Univers Radio, although I fail to see how that could have an impact.

Mine seem alright. They get registered as 91, then 92 and 93, I can select them as DEST and they appear to be roughly were I intended (the INS is never very accurate). However as mentionned, I cannot get them as PREP, and therefore I cannot check their coordinates after validation, or modify them. Also, I wonder if it is possible to clear them, in order to make now ones ?

As Frederf says (thanks for the very informative post!), both are technically infrared lasers (else the beam would widen much quicker). Remember that the IR band is quite large, and NVGs only get a small part of those (the closest to visible light). I wonder what wavelengths the russian NVGs (as on the Ka-50) are able to work with.

The thing is, it is impossible to select marks as PREP. It doesn't register ; and although I have been able to get "PREP 91" displayed, by using the copy function (PREP x2), it shows empty coordinates.

I am reading the reverse, they say : Sight setting = sight depression from flight path [from chart] + ZSL AoA at release that is, 112 mils + 13 mils = 125 mils. The rest of the page doesn't seem to talk about the sight setting. PS: I do not have the game manual of the F-5E, so I have no idea what it says.

How did you get those 80 mils setting ? F-5E manual shows 120 mils for those parameters, and any correction that I would expect would add to that. I just did a test with your parameters and didn't get bad results : impact point was about 180 to 240 ft away from the aimed point. Here's my procedure, and then the screenshots to show my (last) test pass. Step 1: look up the charts This time I used the F-5E chart. Page 6-59, 20° 1500ft, 400KTAS => 120 mils (FYI, the Mirage III chart gives 116 mils) Step 2: add the boresight correction As I mentionned in my previous post, I have had good results adding 43 mils to every setting. 43 mils is where the canon boresight is. => 163 mils Step 3: add the angle of attack correction For bombs you will want to correct for angle of attack. I simply looked up my AoA on a level flight @400KTS, which was 3.5°, that is, 61 mils. Add that to your setting. => 224 mils This is your final setting. Set your pipper to that. Now, screenshots. #1: my sight picture at release ; notice the pipper position. #2: my parameters at release ; 20°, 402 KTAS, 1475 ft (slightly low), 3.3° AoA (slightly less than planned) #3: my bombs ; the racks fall shorter, which is expected ; the single bombs are probably the interesting ones here #4: impact point for the bombs ; they are slightly long #5: map view ; bombs fell between .03 and .04 nm, which is between 180 ft and 240 ft - can the map view show feet under a certain distance ? I think it used to do that. ____ Note that I look up some of my parameters in external view. I find it very hard to get an accurate reading of pitch, especially.

Ok, thank you, that's the only way in the real aircraft too ? It will drop everything at once, won't it ? I will try that for Mk-82 later

Does anyone knows if there is a way to drop bombs manually, just for training with the aux gunsight ? I have made a few tests, with the gun and both Mk-82 (HD and LD), using the F-5E charts in emko's post for the gun and the Mirage III charts (found them somewhere on the forum) for the bombs (but the Mk-82 charts in the F-5E manual give rather similar depression settings as far as I can tell). For the gun, I have had rather good results using the aux gunsight. For the bombs, what I did was try to compare the CCIP pipper or the CCRP release point with the aux gunsight, and I managed to not have it wildly off ; although, it's hard to tell sometimes and I have not done a massive amount of testing either. Here's what I did to get those results : For the gun Testing with the gun, I realized the gun boresight was at 43 mils, so I had to start from those 43 mils and then add the depression setting, so if the mil setting for the gun pass shows 20 mils, enter 63 mils. As I said, I had good results with that, but I encourage you to try it. I think I "only" tried different profiles that gave 20 mils, like 10° dive, 1000 ft above target, 400 KTAS and 20° dive, 2000 ft above target and 400 KTAS. For the bombs The bombs have another problem, which is AoA (they are sensible to that, whereas the bullets are not). So in addition to the boresight correction (yes, I still had to use it), I corrected for the AoA, usually about 2.3° = 40 mils. What I did was start by using the CCIP pipper to find the correct depression setting in level bombing. Then I tried to find out how to get to this setting from the charts. In all my testing, charts + AoA + boresight gave me a fair approximation of the correct setting. I cannot test actual bomb accuracy, because I don't know how to manually release the bomb (especially in CCRP).

The battery switch should be flipped on at the very beginning of the procedure. The other are actually never flipped off, this must be why they are on by default now.

Another possible temporary "fix" would be to roll back to the last version until then - of course this means letting go of the other changes

I tested A/A TACAN shortly after release, I'm not surprised it still doesn't work, but I would love to see that in the future. A few things about A/A TACAN, though, according to my understanding of the system : - X or Y channel have nothing to do with A/A TACAN, you can do A/A in X channel - although yes, Y channel is mostly used for A/A mode - in A/A mode, you have to tune a frequency 63 channels apart to get the distance (and you only get the distance). So if your KC-135 is on channel 11Y, you would tune to 74Y. - you should be able to do that with another Mirage 2000 or A-10C, in theory, and get the distance from him - the KC-135 (IRL) AFAIK only has A/A mode, so it will only give a distance (therefore I suppose you would use A/A mode), while the KC-10 has a full TACAN with distance and bearing (I therefore suppose you would use T/R mode, not A/A mode). In DCS the KC-135 has the full TACAN while it shouldn't (although I think I saw in the editor it can be set to give only the distance). I must admit I don't even know if it is properly implemented in the A-10C.

Multiplayer servers are by version, not branch. That is, currently, Open beta servers are compatible with Release servers, because both are currently the same version number. If/when Open beta gets patched in advance of Release, servers will not be compatible until Release catches up.

I have done some testing, and although I am not sure what the markings on the "boule" (ADI) should be, I consistently get weird readings (like 43° for a mark). I am using the "status bar" (in external view, or internal view with Ctrl-y) to compare AoB with ADI markings. 11° 21° 32° 43° 54° 66° And here's what it looks like with exactly 90° AoB

Indeed, the fix works, thanks.

I know there is ground mapping, I was just wondering how it can affect actual computation and accuracy.