reported TEDAC Export does not switch off when switching to PLT seat

[BIGNEWY]

6 minutes ago, GeoS72 said:

@BIGNEWY, ED Staff, @jonsky7, and fellow users,

We need to garner more attention to this bug. We are 1 month away from it's 2yr anniversary and little to no action was taken to resolve this problem. If you are passionate about this module then please speak up! We need to upgrade this bug from "Reported" to "Fixed".

The TEDAC remains ON after leaving the CPG seat and will remain ON until the client leaves the server or restarts DCS. During 1 multiplayer server session, it doesn't matter if the client changes to a different aircraft, such as F/A-18C, F-16C, CH-47F, etc. After the client picks another Apache pilot slot, the TEDAC will be ON and the image will be frozen from the initial CPG instance. Furthermore, the Autopilot ControlsIndicator overlay is masked by the TEDAC display or blank out screen when in the Pilot seat. That is another problem because modifying the ControlsIndicator.lua file will fail Integrity Check (IC). I have a separate thread about that problem.

Speak up and let your voice be heard. The more people complain about this problem should help to resolve this issue. I'd like to play more as the CPG but this bug prevents me from jumping between seats since the frozen screen presents too much of a distraction. I need your help to bring resolution to this problem. If you have time to press the "Like" or "Thanks" button, then please take a moment to comment. It's time to fix this TEDAC bug!

I know you feel this should be a much higher priority, its clear it is an important issue for you and I am sure others, and I would like to see it resolved also. But the fact is only a small percentage of the community use exports compared to the masses, the team have other bugs, tasks and issues with much higher priority ahead of it. 

I am happy to highlight it to the team again, but making "noise" isn't going to make a fix happen any sooner. 

So apologies if this seems dismissive, but it is the reality of the issue. 

thank you 

bignewy

[Floyd1212]

@BIGNEWY Although it is a small percentage of the DCS user-base that uses display exports, it is arguably the most passionate slice of the user-base, and probably the ones that spend the most money on peripherals and modules.

ED is constantly thanking us for our "passion and support", but you seem to be ignoring (or at least downgrading) some of the requests from your most passionate supporters. Please consider allocating some resources to this and other "niche" bugs (like display exports being too dark).  These passionate users tend to spread the word about how awesome DCS can be, and I would think keeping them happy is worth something.

 

[GeoS72]

@Floyd1212,

Thank you for those supportive words and sharing a sentiment that has been brewing inside for some time. Please read along!

@BIGNEWY,

I digress from the main topic for a moment to address these sentiments stirring from within and as Floyd1212 kindly shared. Allow me to share my passion and support with the following:

1. I own just about EVERY module, terrain, asset pack. The few that I don't own are the Christen Eagle, MiG-19, and Hawk. I currently have 2 modules on pre-order.
2. I am one of those passionate players who support Eagle Dynamics and other third party developers. Not a day goes by without friends & family hearing me preaching from the gospel of DCS World. 
3. I created a virtual squadron and rent a Fox3 server to host unit events. We play on a weekly basis and enjoy the camaraderie that often comes from military veterans. I am a proud veteran and many of my squadron-mates are also vets. This is where we go to "unplug" or decompress after a stressful week at work.
4. The modules that I fly the most are the F/A-18C Hornet and the AH-64D Apache. I would say that the hours spent in the Apache has surpassed the hours of time spent in the Hornet. Fun fact: I worked on the F-14A/B/D Tomcat and F/A-18C Hornet for many years. So you could say that I know a thing or two about these aircraft.
5. I own a few pieces of kit to help support my DCS "habit" such as WinWing F/A-18 Throttle, Stick (plus the F-16EX grip), Virpil rudder pedals, TrackIR, Cubesim monitors, and Cougar MFDs. All of these devices yield a benefit that I take full advantage of, chiefly to aid my aging eyes.
6. I have the pleasure of fixing several issues with the core and module-specific bugs. Three that come to mind: Constant heat seeker tone when playing as a MANPAD unit in Combined Arms, base coordinate error in the South Atlantic map, and the F/A-18C Pilot survival rate(*). Many of these bugs were left untouched for 9 months or past 1 year after being "fixed". As I recall, the IR tone for the MANPAD was supposedly fixed 1 year before I re-addressed the topic. Here's a 4th change: I was also responsible for pushing for a change in how sound files are stored in the mission files. Before, certain sound files would arbitrarily reset. That's like playing a game of whack-a-mole in a large multi-player mission!

* - You fought me and other clients tooth and nail - claiming the pilot survival rate was perfect. It was FINALLY changed after an outcry from several Hornet players and supplying data to back it up.

7. While I don't play DCS every day, a large part of my weekends - Thurs through Sun revolve around playing in one of my squadron multi-player missions. It's not uncommon for me to fly for 6+ hours per day.
8. There feels like there is an "Us vs Them" mentality when it comes to reporting bugs. It appears the stance from any ED team member is denial of a problem or at least deflecting the problem to a user-induced problem. I'm sure there's data that may prove casual users induce many problems. For many years (and still ongoing), ED counts on a core of passionate players to submit bug reports or suggestions to make each module better. Which was the reason to have an Open Beta branch. However, constantly saying "there's no problem here" or to dismiss a bug/suggestion because I represent a small percentage of players is flatly a slap in the face. Your model for improvement was centered on player feedback.
9. I believe that a module dies from a thousand "paper cuts". I mean to say that while a module may provide a lot of features, there are fine cracks that can be easily seen when looking beyond the casual player's mentality. Here is where attention to detail will spell success or failure for a module. Hey, I want to do X...too bad. Not supported. Why is feature Y broken? You represent a minority so don't hold your breath for us to fix it. Oh, an update just broke my helicopter. Each time I start the aircraft, the CPG windshield wiper turns on and will not shut off (where have I seen that problem manifest?).
10. ED needs players like myself and Floyd1212 to identify bugs and provide invaluable feedback to improve each module.

I have ranted long enough. There are a few more points that I wish to address but this is long in the tooth already. Please do not misconstrue my talking points as a personal attack or making ED appear to be the bad guy. That is far from the case. I wish to point out some examples as a learning process. I am always available to talk via DM, Discord, email, and/or experience my squadron. Send a DM if you would like to set something up.

Getting back to the AH-64, I really believe ED hit one out of the park when this module was initially released. If it supplanted my time in the F/A-18C Hornet (and knowing my background) then that's one HUGE compliment! There are many small improvements that need to be made to make it a superior module. Dare I say it should be a flagship module! Making adjustments to the TEDAC display is one and wrangling GeorgeAI is another avenue for improvement. But dealing with GeorgeAI is a topic for another thread!

How's that for passion and support? Now, for a little humor and to paraphrase Pulp Fiction: can we, pretty please with sugar on top, fix the effin' Apache?