GeoS72

For those who need a graphical reference, this is the option that I mentioned above. When flying in a multi-crew cockpit, I would often ask my human CPG to redesignate a target to ensure the AGM-114L Hellfire has accurate data. This is very helpful after evading incoming missiles!

@Flappie, Merci beaucoup!

@BIGNEWY, Thank you for breaking the silence on this thread. I also noticed the tag was changed from "investigating" to "reported". Given your reply, it appears the tag is a downgrade. From the perspective of a guy with multi-monitors, this annoyance discourages multi-crew flights. Additionally, the frozen TEDAC screen will be on during the same session, regardless of other aircraft used in between. So if I were to fly as CPG then switch to flying an F/A-18, F-14, CH-47, etc, and then return to Pilot an AH-64, the image that remained in the TEDAC display will once again reappear and not go away. The only way to remove it would be to start a brand new mission, leave the server & rejoin, or restart DCS. That is a "less than optimal" solution to this problem. While this bug is a low-priority, it will quickly come up on a 2yr anniversary; 1st reported by @jonsky7 on 25 Oct 2023. What is needed to elevate this task to a higher priority? How much more time will pass before this problem would be resolved?

@_Hoss, I don't understand why some people don't have an issue while others, like myself, have the issue with diff braking in the Corsair. I confirmed the problem still persists after the Jul 23 update. @-Rudel-, do you have visibility on this issue?

@BIGNEWY, this is becoming more and more frustrating. Can this problem be addressed, please? Can we get some further traction other than "Investigating"? I could avail myself for a Discord chat or other means to dialog about this long-standing issue. Here are more items to point out about the TEDAC display. 1. Spawned in first AH-64 in Pilot seat. 2. Autopilot Controls Indicator display blocked by black overlay. 3. Switched to CPG seat, didn't play with TEDAC. 4. Jumped back to Pilot seat, TEDAC display still on; Auotpilot Controls Indicator display blocked by TEDAC display. 5. Spawned in to new aircraft, CH-47F. Nothing unusual about the displays. 6. Spawned in to a second (different) AH-64 in Pilot seat. 7. TEDAC display still on from the first spawn! It was immediately present because the rest of the cockpit was still being rendered. Notice the blurry segments? First screenshot represents first spawn. This was taken after I moved from Pilot to CPG then back to Pilot seats. Note the Yellow Box showing the TEDAC overlay and the purple arrow shows the Autopilot Controls Indicator being blocked. Afterwards, I spawned into a CH-47, nothing unusual with the displays. Unless you count the Left MFD not being displayed. Lastly, I spawned into a different AH-64 slot, in the Pilot seat. While the cockpit was being rendered (see blurry segments), the TEDAC display remained on. That was 2 aircraft spawns ago! Why does the TEDAC display remain on after switching between 3 different aircraft slots?

@BIGNEWY, The GeorgeAI is getting better. It still has issues lasing a target. Hearing him say, "Constraints" is a good reminder to line up the shot prior to missile launch. I can't imagine the struggles the ED team had to work the kinks out of this new system. Well done! I have a recommendation with all of the new GeorgeAI features incorporated in the Jul 23 update: I noticed the ability of GeorgeAI to lase a target when de-WASed by short press right on the GeorgeAI panel. Again, that is while the CPG has nothing WASed. Would it be possible to add the same "lase" command while the RF missile is selected? See my screenshot as an example. In this example, the "DESIG AGAIN (Designate Again)" function would be similar to the "Laser On" function when the AI is de-WASed. This would force the CPG to lase the target and send target data to the RF Hellfire before a launch. A short press to the right would allow the CPG to momentarily lase the target again for a firing solution. I can create a wish list thread for this idea, if you'd think it would help.

@Saxman, thanks for the clarification! I'm not sure why I didn't understand it at first.

@M1Combat, @Saxman,& @GTFreeFlyer, am I missing something? Maybe I misunderstand your post? You can bind the oil, intercooler, and cowl flaps to buttons. They function similarly to the P-47D controls. Granted, they are not on axes, but I never experienced a problem mapping either of these controls to discrete switches on my HOTAS.

@tekwoj, yes, it is noticeable in external view, with or without trim set.

It looks like the Gun Charge key binds were added/fixed in the early July patch. They can be found under: Guns, left, charge OFF Guns, left, charge ON Guns, right, charge OFF Guns, right, charge ON

Confirmed. The Master Arm, Gun Sight Light, and Gun Sight Brightness key binds work!

Tail wheel authority is still not correct. I hope this will be addressed in the next DCS update.

Last weekend, I flew the AH-64 using a dynamic slot on my squadron's server. The aircraft went down and while the pilot was killed I must have switched to the CPG just before exploding into a fiery hole in the ground. Afterwards, I spawned in a few more time as the pilot in different Apaches. One thing remained constant: The TEDAC display was ON any time I jumped into the cockpit. Can this problem be addressed? It's been on the books for a very long time with no updates (1yr 9mo+) from the ED Team. Here is a screenshot of my cockpit setup with multi-monitor configured (Main monitor plus 3 Cubesim MFDs). The main viewport is on the left, the TADS Page is on my Left MFD, the Weapons Page is on my Right MFD, and the errant TEDAC display is on my Center MFD.

Floyd, et al: GeorgeAI still misbehaves with all conditions being met: good line of sight, altitude, and constraint box within limits. The point to make: this problem still persists after 1 year of the initial complaint. Any improvement to the AI logic is small but also not advertised. Case in point: months ago, I discovered the AI ability to swap between Laser and RF missiles. I believe it coincided with the addition of Target Zoom function (Long Press Up in the AI wheel). That was not advertised in change logs. You would think that adding this new capability would be showcased in a short video; nope! Hell, I would have welcomed the change if it were mentioned here (as an example). I'd be more than happy to host a day/time on my server to demonstrate the shortcomings of GeorgeAI; this way all invited guests can see with their own eyes, collect data, and dissect that data. DM me for details.

This problem still persists. The issue with capturing GeorgeAI behaving badly in a track file is also a concern. I play almost exclusively in the multiplayer environment. With that, the track files are large and the time taken to reach a target can be a while - 20+ minutes. The problem of GeorgeAI lasing when he wants can be mitigated by using a mixed Hellfire loadout (e.g. 3 RF + 1 laser missiles per pylon). The AI will habitually lase from 10,000m down to 8,200m every 15 - 20 seconds (maybe longer, it's been a while since I timed it). Then he will take a lunch break at ranges under 8,000m; lase whenever he feels like it. To combat his lunch breaks, I long press left on the AI wheel to cycle between RF and Laser Hellfire. That kinda helps to put him back on track. He will often double lase the target when switching between Laser and RF missiles when using this technique. I want to make this clear: The GeorgeAI lasing problem still persists. By no means is my workaround a permanent solution to this on-going problem. It is a field-expedient remedy to a problem that can be resolved above my paygrade.

@BIGNEWY, Has there been any progress on this issue with the AH-64 TEDAC video export? It's been under investigation for well over 1 year and 9 months. But who's counting anyway?

Bumping up the thread. Now going on 2 months without much of a peep from the team at ED.

Bump to garner the attention of ED team members. Thread is now 2 months old. Will ED please address the modification of ControlsIndicator.lua files and Integrity Check?

Yes, this is certainly a bug that should be addressed. As needed, my thread could be merged into this one: Bug/No Bug Differential Braking (link also has track file). @-Rudel-, would you kindly add this to the list of issues to address?

Thank you for the rapid reply, @-Rudel-! I also have a similar controls indicator request for the Prop, Throttle, Mixture, and Blower axes here:ControlsIndicator Overlay Wishlist Would that request also be taken into consideration?

Could the wheel brake indicator be added to the ControlsIndicator overlay for the Corsair? If it's already in-work, is there a time frame to expect it?

FWIW, there is no difference when using the rudder AND wheel brake at the same time. An adjustment to the wheel brake/tail wheel caster effect is requested.

It would be very helpful to add text to the Controls Indicator overlay to differentiate between Propeller, Throttle, Blower (Super Charger), and Mixture axes. I added text using GIMP; the text may be oversized but it could be resized accordingly. I wanted to have the vertically oriented text be superimposed on the respective axis with it outlined & filled. But GIMP was not cooperating with me. As an alternative, adding P (Propeller), T (Throttle), B (Blower/Super Charger), and M (Mixture) at the bottom of the axes would also be informative without being intrusive. Could this be added to the module?

When you takeoff, skid off the runway then land on your nose...and not die. It looks like the spinning prop acted like a gyroscope and kept the aircraft wobbling like this. You could even raise the gear, fire guns and rockets with no detriment to the pilot or plane!

UncleStains, I already have a bug report for that keybind issue.