FalcoGer

It might get truncated to 3 characters, which may or may not be correct. I got one though. When sending a FARM with 8 SAL + 38 rockets (2 pods) on, the receiving aircraft gets 16 SAL + 38 RKT displayed in their FARM page.

When creating your own target points, since the latest update (or maybe the one before it), they don't have threat rings anymore. The target points generating when spawning the aircraft are not affected, only those that are placed down after the fact, including those transmitted over datalink. To reproduce Create mission with hot start apache (for convenience) Place down SAM that will generate a threat/target, such as an SA-15 Start the mission in that helicopter Switch to ATK phase on TSD Goto TSD -> SHOW -> Enable Threat See the threat rings for the existing SA-15 Go to TSD -> Point -> Add Add a new TG with IDENT 15 No rings noThreatRings.trk

The roll limit and rate limit restrictions for the hellfire launch only works for a roll to the right. for a left roll, no inhibit is displayed or enforced. To reproduce: Load laser hellfires (more convenient to launch, since you can LOAL) Take off Select missiles and master arm on Roll right slowly Get ROLL LIMIT at around 10° Pull trigger (1st detent), no missile is fired Roll right fast Get RATE LIMIT Roll left slowly by up to 90° Get no safety inhibit until you get ACCEL LIMIT due to being in negative G land Pull trigger, missile will fire Roll left fast Get no safety inhibit safetyInhibitOnlyForRightRoll.trk

The "Get new plane - respawn" doesn't work. Whether the aircraft is fine, damaged or whether the CPG or PLT ejected. Selecting the same slot from "select role" also does not work to respawn. Get new plane should get a new plane, even if the current one is just fine. no_respawn.trk

Didn't do much testing, but when I ejected as CPG, I was able to use the "Get new airplane" keybind (default is RShift + RCtrl + Tab) and it respawned me in a singleplayer mission. Didn't test without ejecting or with PLT ejecting instead. Edit: Tried again. No respawn in any case. I think it might have been due to the helicopter actually being destroyed by landing in the trees that the keybind works.

What I find most frustrating is that When there is a column or group of vehicles, it is impossible to distinguish anything. it's just a yellow blob. When there is a yellow blob, I can't tell what NTS and ANTS is. When there is a yellob blow, I can't tell which unit I have already shot at. when re-scanning effective engagement is impossible because I can't distinguish which of the shot-at markers correspond to which radar return, and even if I could, the NTS button or manual selection of targets doesn't work in continuous mode. It's impossible to know which units have been hit or not. Really what needs to happen is, in order of priority Multicrew FCR sync LINK TADS to FCR NTS ZOOM RMAP might help a tiny bit, especially for closer targets and should be relatively straight forward to implement. it's literally the same as GTM, just the radar returns need to be drawn in different spots. A workaround is to use the TSD in PAN mode and zoom way in. But that's tedious and reduces SA by a great deal, especially with threat rings already marked out or when using the digital map for terrain avoidance. C-Scope would be neat, but not crucial.

I called him and told him to "Engage ground targets" and he said "Unable". I called him and told him to RTB, he said "Copy", and proceeded to continue to follow me. I said nothing and he flew straight into a tree and said "I'm hit". AI wingman are useless.

New update: AH64 DTC Feature

On the COM/Preset/Modem page the Protocol currently called "Datalink" should display "LONGBOW" instead. The "AUTO ACK" button, "RETRIES" button and "BAUD RATE" button should only be visible when PROTOCOL has "LONGBOW" selected. In particular, when None is selected, they should not be displayed. When the other protocols are selected, other options should be displayed. Since those will never be implemented anyway, the easiest option is probably just to bar them out.

I checked again. The documentation provided by ED is wrong. The VHF radio can be tuned 108.000 through 155.995, the VHF radio accepts the correct frequencies. The documentation about the step size is wrong. The UHF radio can be tuned 225.000 through 399.985 MHz in increments of 5 KHz. The DCS apache can only go up to 399.980. Again, documentation about step size is wrong. FM1/2 range is 30.000 through 87.995, in increments of 5 KHz. The DCS apache can only go up to 87.990. Documentation wrong about step size.

According to the DCS Documentation: Max freq for UHF radio in preset is 399.975 MHz, but AH64 allows entry up to 399.980 MHz Min step size for UHF radio preset is 0.025 MHz, but AH64 allows entries to a resolution of 0.005 MHz (for example 380.995, whereas it should be 381.0 or 380.975) FM radio max frequency is 87.975, but AH64 allows entries up to 87.990 FM radio frequency step size is 0.025, but it is actually 0.005, allowing entries like 77.995. Also the default preset that is tuned from mission start for an AH64 for FM1 is 30.015 (Preset 3) and for FM2 it is 30.020 (Preset 4), both of which are invalid, or the documentation is wrong. VHF min frequency is 116, but AH64 allows entries down to 108 VHF max frequency is 151.975, but AH64 allows entries up to 155.995 VHF frequency step size is 0.025, but AH64 allows resolution of 0.005, allows invalid values such as 116.995 Other things that are wrong but not in the DCS documentation: CNV for HF radio starts at 0, but valid options are only 1 through 6, when tuning an HF radio with crypto enabled and C0, this is not displayed. Only C1-C6 are displayed when a valid value is entered for CNV. Preset channel for HF starts at 0, but AH64 rejects anything that isn't 1 through 20. 0 can not be set once it has been set to something that is not 0. ALE Net starts at 0, but 0 can not be re-entered once it has been set to something other than 0. ECCM net starts at 0, but 0 can not be re-entered once it has been set to something other than 0 Tuning an HF preset any frequency results in a wrong frequency being tuned on the EUFD (5.0500A) Tuning that same preset again will push the correct frequency into the standby frequency, but SWAP doesn't do anything. It might just be a display error Some Presets start with HF being 0.0000 for XMIT and RECV. Tuning them results in 15.0000A being displayed in the EUFD.

Mode 1 is 5 bit, it should be 0 to 31, or 0 to 37 in octal, but accepts values up to 99 Mode 2 is 4 digit octal, so it should be 0000 to 7777 in octal, but actually accepts all decimal digits Mode 3A is also 4 digit octal, also 0000 to 7777, but accepts all decimal digits Mode S Address is 24 bit octal, curiously this one works correctly (0000 0000 to 7777 7777). Mode S Flight ID seems to accept any alphanumerical string, but it must be 8 digits long. no idea if that is correct. Mode 4 accepts A and B, which is correct. REPLY is mislabeled REPLAY (But correctly labeled in the submenu when clicking the OSB) Reply options should be "UFD" (Up Front Display), not UDP. While at it, pressing the ident hard switch on the radio panel doesn't invert the ident option on the comm->xpndr page. not sure if that is correct.

When FCR is sight, only RF missiles can be selected. When TADS is sight, either can be selected. When HMD is sight, only SAL can be selected. This works as expected for me.

please add a track. Also the X indicates that a target has been shot at with a hellfire missile. It doesn't require the FCR. When george is shooting, he uses the TADS to designate targets, not the radar. If you have a human copilot, FCR synchronization between crewmembers is not yet working.

Try it in the air, it's very funny. Unless they fixed the superman like powers for the pilots in the last few patches. Probably not, very low priority.

That bug's been around pretty much from day 1. Good job catching that. I think the issue is more fundamental in that sometimes autopage happens for one crewmember but not the other, not necessarily related to the rotor brakes. It could be engine parameters being calculated independently (instead of being sent by the pilot's client to the cpg for him to display the exact values the pilot also sees), and them being different due to lag or frame timings being different or whatever, triggering an engine page autopage on the back seat but not the front. I've had engine failure in the front seat due to maneuvering while for the pilot everything was just fine.

can you tell where to find that information? personally I think it's a bit inconsistent to have every other time stamp be dependent on the zulu/local setting but not that one. it's also a bit of a hassle if you want to compare the times to find out if it was shot 15 minutes ago or 1 hour and 15 minutes ago. I just think it's strange, especially considering the rest of the aircraft's avionics are very smartly designed and integrated with great UX design and quite intuitive.

I noticed that the SHOT reports when looked at will always display zulu time, regardless of the setting in the TSD->UTIL page. Is that correct?

I have read that you can have additional priority schemes loaded from the data cartridge on top of the 3 that are already coming with the radar by default. Though I don't know exactly what can be programmed in there or not.

I was not aware this to be a slang term. english is not my primary language and I am not familiar with everything people say on the streets. I thought you were talking about a physical process that takes place during EW. I also did not mean to offend you, I was posing a question of what you would do in a scenario where your target was protected by a short range air defense system and you were able to engage from relative safety, even if such a system was designed specifically to shoot you down. The problem I think comes from a doctrine that relies on complete air dominance and technological and numerical overmatch over anything the opposing forces can possibly throw at you. There is an SA-8? No problem when you have 120 F-35 in reserve and 2 aircraft carriers groups parked by the shore ready with 200 cruise missiles. That is simply not the case for DCS. Those scenarios is not what regularly is being placed in DCS missions, where the enemy is often a peer power with modern IADS that the real apache never encountered. A complete overmatch of technology and firepower where you deploy hundreds of aircrafts to basically wipe out 75% of everything the enemy has in 2 hours is neither fun, nor is DCS able to hande such scenarios, even if it were realistic. At the same time calling AI aircraft or artillery is impossible. I don't have any operational experience like you, nor have I had your training. But what works in DCS works in DCS, so I don't see a reason to say that it doesn't. And even without formal training I have been killed in DCS by an SA-8 once (I was surprised by it), while killing dozens of them with proper cover and tactics, even before the radar guided hellfires were a thing in DCS. Most of my deaths were by manpads in cities or by maneuvering elements with BTR-82, which is more effective than any shilka in DCS, or some dude with an RPG 1km away, which is ludicrous. And that was only before the laser warning receiver. At the end of the day we're all here to have fun and blow stuff up even if it doesn't conform to some doctrine, and all of that without any real consequences of death. So let's just get along and have fun.

That's not how it works. EM Radiation, such as radar and radio is an alternation of the electric and magnetic field and the force carriers are photons, not electrons. So what are you going to do if an SA-8 is in the way of your objective, say driving with an armor column? Sit there and wait for an F16 to be shot at by the SA-8, and exposing them to enemy air and LR sam systems, or in the absence of such assets go back home? Or just pop up from behind a hill, shoot a lima and be back down before it can retaliate, and also save a HARM missile for other, more important tasks, like the aforementioned LR sam systems? Also you can outrange shilka at 8km where it can only engage at around 3-4km max. I don't see the issue engaging that. Same with 2S6, it's actually quite short range considering it has missiles. It becomes an issue if you are surprised by them, in which case you didn't plan for them anyway, but the same goes for a BTR-82, which can kill you in 1 or 2 hits with it's gun, and certainly that's a valid target for an AH64, or even a dude with an RPG somewhere in the streets popping around a corner, popping you at 1km with their ridiculous aim. SA-15 and SA-8 can outrange you, but with some proper planning and using terrain features or buildings you can come out on top with relative safety all the time. Only when there is absolutely no way to mask, for example when they're sitting in the middle of a flat desert like east of dubai, I wouldn't go. Again, I'm not talking about taking on an SA-5 site 80 miles into enemy territory next to an airfield with an SA-10 and SA-8 and SA-15 every 3 miles. I'm talking local ADUs sitting next to tanks or artillery, which is to be expected.

The gun with track and shoot at whatever is targeted by your selected sight. Valid sights are helmet, TADS and FCR. If you select FCR as sight, the gun won't shoot if the ballistics are impossible (ELEVATION LIMIT / AZIMUTH LIMIT for the gun) or if there is no target selected as NTS (LOS INVALID). The same reasoning applies when selecting TADS as sight. the gun will shoot at what the TADS is looking at, not your helmet. As for being able to shoot with FCR as sight but before starting your first scanburst, that seems like a bug.

For me that's mission reset.

What about the static objects that are all over the map, like in the caucasus map a lot of airports have BMPs and BTRs made of explodium placed on them. I find them quite annoying to deal with since you never know if they're real or airport assets.

You can turn the FCR with the acquisition source by slaving, with cued search (later), with man track or with the arrow buttons on the FCR page, but only when the FCR is not currently doing a scan. So there are a few questions. From what I gathered, because the pilot doesn't have a slave button, so the FCR always slaves when the pilot selects an acquisition source, even if it's the same one that is already selected. And it will stop slaving when the pilot presses one of the arrow buttons. Is that correct? When the pilot selects an acquisition source before selecting FCR as sight, will it slave or will it just retain it's current orientation? If the pilot presses cued search, the FCR will turn towards the RFI detected emitter to correlate. Will it stay pointed in that direction or will it go back to the acquisition source and/or the previously selected heading afterwards? Will it return the scan cone size to what it was before? With cued search, how does it interact with an already running continuous scanburst? Will it not work? Will it slave the radar while it's scanning? Will it stop the scan and do a single scan or a scanburst? What will happen? Does slaving to acquisition source also change the elevation? Does it do so in automatic elevation also? When the radar is actively scanning it can not be slewed. How does it react to the helicopter turning? Will it retain the heading or will it stay relative to the helicopter? If it was previously slaved to a point acquisition source, will it keep pointing to it, even if you fly around it? What does it do if it deems that it should be scanning behind the helicopter? Can it do that? What's the scan cone angle vertically? The radar elevation display displays the angle of the radar cone in 6.25° steps (in RMAP and GTM modes), with the big dash being 6.25° down. Is this the bottom of the scan cone, the middle of the scan cone or the top of the scan cone? Not really on topic, but what happens if one crew member has selected FCR as sight, and the other one then selects it as sight? Will they both have it as sight and if not, what does the other crew member gets selected as their sight? does it default to HMD or does it go to the last one selected (ie. possibly TADS for CPG) What happens when one crew member is currently scanning with the FCR and then the other takes it as the sight? What happens when one crew member is currently scanning with the FCR and then they select a different sight? When selecting LINK with TADS, the radar should slave to the TADS LOS. You can't select TADS as ACQ when TADS is the selected sight, so this is the only way of doing that (unless the pilot uses TADS as ACQ and FCR as sight). If you do that, does the radar elevation gets adjusted as well? If so, only in manual mode or also in auto? If the pilot has FCR as sight and the CPG wants to get the TADS onto the NTS, is there a way other than selecting FCR as ACQ and slaving? Edit Here are my observations so far It will always slave, until the manual slew buttons are pressed See 1 N/I N/I No clue. Maybe? It stays on a heading, never anything else See 6 It seems to just turn all the way around, even scanning directly behind the aircraft. The manual turn buttons seem to get buggy sometimes with that, disabling the wrong ones or none at all. Also the tail boom blanking area is not being displayed. No clue. No clue. Probably center, no evidence though. FCR in multicrew is currently buggy and not really working as is. Can't really determine. I think the correct action is to boot the other crewmember to HMD as sight, didn't check though. I think it stops the scan. Didn't test, nor would I trust the test right now. The scan gets stopped No clue. Related to 5. Actually the same as 5. You can use CAQ on the NTS to create a TG point and and slave. The PLT can also mark the target using the FCR page's TGT function.