Robin_Hood

I'd like to add that it doesn't really make any sense to use a waypoint as a JSOW target (well, it won't when pre-planned targets can be entered in the mission editor), because it is essentially the same as inputing the waypoint coordinates in the PP mode directly. TOO mode will be more useful with other means of targeting, like the FLIR (Litening of ATFLIR), or the radar. For a target of opportunity, creating a new waypoint with given coordinates doesn't make sense since you are better off making a pre-planned target instead (of course I understand that right now waypoints can be a quick and dirty way to pre-plan targets).

Possibly to have two weapons on the same target (for a quick reattack, or double the effect).

Yes, indeed. Although by testing all combinations I found that you actually have two pilot options for the CBU-99 (and Mk 20) weaponeering. Primary mode Selected by MFUZ in VT. The canister will open at 1500 ft (actually from my tests, it will open 1.2 seconds after passing 1500 ; actual opening height will depend on the vertical velocity of the canister, and thus on the dive angle, altitude and airspeed at release). There is no backup mode apparently. If released below 1500 ft, the canister will never open (IRL there should be a 300 ft opening backup). Option mode Selected by MFUZ in OFF, or PRI (anything but VT). The canister will open 1.2 secondes after release. Notes - in all cases, EFUZ has to be on INST or DLY1 - the behaviour seems to model a FMU-140 fuze, although 3D models show an Mk 339 - this is the behaviour on the Hornet, other DCS modules have different behaviour - the height (HOF) for the primary mode is set on the ground ; in DCS it is fixed at 1500, as mentionned earlier

I know there was a discussion about that some time ago, and I might not be aware of the current status of that, but I just did some more testing on air-to-air TACAN (on tankers), with both bands, and here are my results, hopefully it may help understanding the problem (if there is indeed one). This does not seem to be limited to one single aircraft, as I had the same results with both the F/A-18C and the Mirage (tracks included). Here's the setup: Three tankers on the map, on on 11X, one on 43Y, one on 112Y. For each channel, I tried all combinations of T/R, A/A, X and Y modes. All three tanker TACANs did the same thing: - in X, T/R: I get nothing - in X, A/A: I get both distance and bearing (even when the tanker is supposed to be X) - in Y: I get bearing only (regardless of T/R or A/A mode) I included two tracks of the same mission (on PG, but I confirmed the same behaviour in Caucasus), one with the Hornet and one with the Mirage. Both tracks show the same procedure: - engage autopilot and set navigation displays to TACAN - tune TACAN channel number, on X band, in T/R mode - verify no info received - switch mode to A/A, verify distance and bearing - back to T/R - switch to Y band, verify bearing only - switch to A/A mode, verify bearing only - back to T/R, X band, switch next channel - repeat Notes - I did take into account the MIDS filter in the F/A-18C, which is why I chose one supposedly filtered frequency and two that should be safe. Also, I checked with the Mirage which shouldn't have filters. - I only tested with KC-135MPRS as tanker TACAN_XY_Hornet.trk TACAN_XY_Mirage.trk

I think maybe some confusion stems from the word "designate". In the quoted paragraphs, it really means "pushing the WPDSG button". It is not related at all to the definition of a waypoint as a TGT in the HSI DATA editing.

Pretty sure the updater should start where it stopped after restarting (and checking what was already downloaded). Not saying it wouldn't be useful to be able to use a standalone torrent client, though.

Chris, Sur l'image, tu es dans l'assignation de modificateurs de DCS, c'est seulement pour pouvoir faire des "Bouton 3 + Bouton 4" (c'est la même fonction que le "Shift" du CH manager). J'ai regardé un peu ton profil, je suppose que "trim reset" et "stationnaire on-off" ne fonctionnent pas, ou plutôt qu'ils font simplement le trim. C'est parce qu'ils sont configurés pour envoyer "t" lors de l'appui, tout simplement. Le "Shifted action" signifie qu'ils enverraient respectivement contrôle gauche et alt, s'ils étaient actionnés en même temps que la touche de "shift" (sauf qu'aucune n'et configurée). Pour envoyer "contrôle gauche + t", plusieurs solutions: - "CTL t". En utilisant CTL, SHF, ALT, la combinaison de touches sera envoyée. Note que les touches gauches sont utilisées ici. - "HOLD LCTL t". Ici, le LCTL précise le contrôle gauche (c'est nécessaire pour pouvoir utiliser les contrôle droit etc...). Le HOLD fait que les deux touches sont appuyées ensembles. - "+LCTL +t -t -LCTL". Ceci demandera explicitement d'appuyer sur LCTL, puis sur t, puis de lâcher t, puis de lâcher LCTL. Je te conseille aussi de bien vérifier avec le "Key Check" du manager, qui permet de regarder exactement ce qui est envoyé comment et dans quel ordre, pour vérifier que le résultat est bien celui voulu.

Alright, so from what I can see, with your profile, the joystick will behave exactly as it would without a profile. Let me try to summarize how CH profiles work: Joystick modes From the CH Control Center, there are three ways you can put your joystick in: OFF, Direct and Mapped. In OFF, mode, the joystick is seen by the CH utility, but not by Windows or any game. It is deactived In Direct mode, the joystick works as a DirectX input device, and is directly recognized by Windows and games. In Mapped mode, a profile is loaded that will create virtual joysticks and virtual keyboards to customize what your joystick will do. This is the mode of interest here. DirectX vs Virtual Keyboard In a basic (without scripting) CH profile, you can assign two basic function to any button on your device. Either it will be recognized as a DirectX input (and recognized like a joystick button by Windows), or it will send a key from a virtual keyboard (just like if you were to actually press the corresponding key on your keyboard). Axes are a little different, but usually you will want them recognized as DirectX axes. In the following screenshot, Button 2 is set as a DirectX input (DX Mode checkbox). You can see that it is set to send "Button 2" from the virtual joystick "CM Device 1". In this second image, the same button is set as a virtual keyboard, and will simply send the key "k" when you press the button. Note that you can choose to send a key when you release the button instead (or in addition to). There are more complex instructions that you can give, such as pauses, or sequence forcing (such as "press a - press k - release a - release k), but they are beyond the scope of my basic explanation. Note that in this case, no DirectX input will be sent, and if "Press" and "Release" are left blank, nothing will happen when you press the button (and it will not be recognized by DCS). Shift mode You can also use one button as a modifier. For example, if you use button 4 (the pinky) as the modifier, then Button 4 + Button 2 will have a different effect than Button 2 alone. Again, this action can be a key or a DirectX input. To set your modifier, check the "Shift" box. Then, for any button that you want to use a second action, use the "Shifted Action" boxes to set it. Note that you cannot mix DirectX and keystrokes for a single button (ie. send a DirectX input as normal action and a keystroke as shifted action). Master modes The Fighterstick (and the Pro Throttle) supports 3 independent modes, indicated by coloured LEDs on the base of the stick (red, green, yellow). Any button or axis can be assigned a different action depending on the mode you're in. You can set this using the Mode 1 / Mode 2 / Mode 3 tabs. Note that if you leave modes 2 and 3 blank, they will use the action for mode 1. You toggle between the three modes via the Button 3, on the right side of the stick (unfortunately, you cannot chose another button for that). __________________________ I hope this helps. I'm also attaching my old Flaming Cliffs 2 profile as an example - it uses all three modes, and also the shift (modifier); it even has a little script, but nothing really useful there. I am not sure what exactly you want to achieve with your profile, so if you need more help, I'll try to keep on checking this topic. FC2_profile.zip

Just to make sure, in one of your picture you are in direct mode; you know you should be in mapped mode for your profile to work, right ? Do you have working profiles in other games ? I used to use a CH profile with my Fighterstick and Pro Throttle, though I now switched to a Warthog (and had stopped using the profile at the end). I might be able to plug my fighterstick and take a look at your profile; maybe you can post it ?

However, you should be able to tune to a VOR station and use that for ADF. I don't know about US NDBs, but aren't the NDBs we have in Georgia out of the available frequency range of the ARC-210 ?

End of runway arresting gear is certainly not exclusive to naval bases. Air Force base also have them, and USAF aircraft also have hooks for that (but they are for emergency, and not in-flight retractable).

Another thing to be aware of (I've said this before, but I'll say it again here - pretty sure the references post talks about it also): what DCS calls "true north" is not lined up with earth parallels. If you follow a true north heading, your longitude will change (you can see this in the mission editor: "true north" is always up - check with the ruler - while you can see the geographic grid is not). Note that this does not cause too much issues (except for headaches), usually. I don't know how or if it affects the NS430 as I don't have it.

I would have though that on the contrary, you would want to drop your bomb just how you would if unguided, so that not to hit too far from the target in case guidance doesn't happen. For collateral damage reduction. As for the original question, it is obsiously possible to use the GBU-12 without guidance, just use the same settings. It just won't be nearly as precise. Oh, and it doesn't really make sense either, unless you really have no choice.

+1. Maybe they can do that with the mission data cards and the in-game mission planner that was mentionned

Well, the (current) manual says the following: So, it might not be that simple. Several comments: 1. AACQ isn't mentionned here surprisingly, although it is mentionned later 2. It says normal lock (with TDC over radar return) should not occur if the RDDI is not the radar display 3. It says it should be possible to use the LDDI as the radar display Again, though, how AACQ integrates with all that is not mentionned, and also, it is possible that the section is incorrect and will be modified.

Wags said that ID is based on several ROE factors, including IFF answer (only that at the moment in DCS), but possibly others. If I were to guess, I'd say that unknown contacts have yet to be assigned an ID (ie. some ROE factors have not yet been checked), while ambiguous contacts could be contacts that have some factors but not others (like a contact not responding to IFF, but otherwise exhibiting no other ROE factors for hostile). Only a guess, obviously. And not really modeled yet, since only IFF is taken into account for now.

Same as this, maybe: https://forums.eagle.ru/showthread.php?t=233754

Interesting, will do some more testing. Maybe check the channels outside of the MIDS filters (I wouldn't expect this to have been modeled before MIDS was, but who knows).

I posted this somewhere else, I'll repost here. I made this graphical summary of the TACAN channels and how they are affected by MIDS filters.

The TACAN is integrated into the MIDS. Whether this means you can't turn it off, I wouldn't know. The NATOPS talks about turning it on at least, but it doesn't say regarding MIDS-equipped aircraft.

How would the IFF positively identify an aircraft as hostile? If there is an answer, I'm curious. Oh, and "unknown" can mean, literally, unknown, as in, no attempt at identification has been made.

Not sure the filters are removed if you turn IFF and D/L OFF ; and yes, it blocks quite a range of frequencies for A/A TACAN. Air-to-ground isn't too bad, as it will just give you reduced range in certain conditions. However, I doubt that this is actually implemented.

The Sensor select switch depress is to IFF contacts, it has nothing to do with NCTR (I understand this was not very clear in Wags' video). NCTR works with a hard lock, completely independant from the IFF, and it does a very different information: - IFF tells you if the aircraft is responding correctly to your interrogation - NCTR tells you what type of aircraft you are looking at (it can't tell you if said aircraft is friendly or ennemy, though depending on the situation you may be able to tell)

Well, it's already in the OpenBeta

A/A TACAN is buggy I think, I also have experienced freezes, even between only two aircraft. The quickest way I found to have it working again is switch the band and back (if you using Y for example, switch to X and back) ; I find this slightly quicker than turning the TACAN OFF then ON. But you have to reset it regularly or it will freeze. That's what I'm seeing anyway ; I haven't noticed any particular condition for the freeze to occur either.