GeoS72

I'd find it very entertaining to see the phrase "One Ping". Just one of many quotable quotes from Hunt for Red October.

@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?

@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!

Wow, I'm surprised that no one else has spoken up about the ControlsIndicator breaking IC.

@-Rudel-, your thoughts on adding this detail to the ControlsIndicator overlay? Also note the lack of an indicator for the wheel brakes.

@-Rudel-, could you please add this request to the list of bugs to address?

Bumping the thread for increased visibility. The ICS Mode Switch UP/DOWN keybinds work. However, the discrete HOT MIC, PTT, and VOX keybinds do not work. They are animated but have zero functional effect.

Either my idea sucks the south end of a northbound horse or it needs more visibility. What does the community say?

Does anyone else like to have this feature added? If the answer is "YES", then please chime in. More users speak up directly relates to incorporation of features. Are there any ideas for another term for "DESIG AGAIN"? How about "VERIFY RANGE" or keep the "NOT LASING" / "LASING" terms?

@GTFreeFlyer, That is easier said than done. One may not be able to adjust wind parameters in a multi-player server or single-player mission. For example, playing on a 4YA server or running a training mission. From my experience, having a small wind component at 33 ft will help to dissipate any smoke that is on the airfield. For example, an aircraft running a smoke canister will create a large cloud of colored smoke if it is turned on while the aircraft is on the ground. Wind set 1 kt or above will cause that cloud to blow away over time. This is very helpful when someone forgets to turn off smoke when landing. Talking about adjustments to wind values in a mission diverges from the primary purpose of this thread. I do not want to lose focus on the Corsair's differential braking performance. I hope that @-Rudel- and his team of programmers will soon tackle this problem with differential braking. I appreciate his candor and ability to share the list of bugs that require attention.

Would it be possible to add support for animated PNG or GIF files during game play? It could be used for a variety of things - news flash, intel update, or a meme. It would be added thru the Mission Editor. Good idea or bad idea?

@HR-Crumble, the above quote was the latest reply from the Dev. The quote below has a link to the list of bugs the Dev will work on. Welcome to the club! Sorry to hear you are also affected by the diff brake bug. Do the links answer your question?

@ex81, Thanks for posting your remarks. Trying to steer on the ground via keyboard must be very challenging in most war birds; it must be impossible to steer in the Corsair. I'm trying to read through the fluff. To be blunt: Do you have problems turning the Corsair on the ground or not? Is the intent of your post to record the same problem or is it to offer words of encouragement?

@-Rudel-, I appreciate the candor in your dev's list of priorities. What good is adjusting the water injection system or engine damage model when many users can't taxi the plane to the runway for takeoff? As stated earlier, I will not fly the Corsair until diff braking/on deck steering is resolved. The plane is simply unplayable in its current state.

@jonsky7, Wow! This thread has some longevity to it! Kudos. I used it to reposition my kneeboard. It worked like a charm!

This is the struggle that most of us experience. In this track file, I attempted to taxi to the takeoff spot in the Corsair School campaign. The player is directed to taxi forward, turn left to the takeoff point (indicated by green smoke). I wasn't able to get there. Without using the brakes, the plane started turning right, all on its own. I don't know if there was a cross-wind or wind component. I attempted to use the power up then pivot left. I couldn't even do that. See the track file. This module is massively bugged and is a BIG fail. A player struggles just to take off. That has 0 fun-factor. I will NOT fly this plane until the diff braking problem is resolved. Please address this problem SOONER than LATER. What good is an airplane if you can't taxi to the runway? 2025-08-16 Corsair School Cant Turn to Takeoff.trk

Gents, Thanks to @-Rudel- for posting this link to their priority list of items to address. This is a cross-link from @Saxman's thread about Gun Convergence adjustments. Gun Convergence Adjustments-Dev Priority List Post

Addendum: What is the best course of action? The hacks that some presented are user workarounds to a problem. That easily has negative consequences when attempting to taxi a Corsair ashore or afloat. Taxiing under high engine RPM to lift the tail wheel is NOT recommended. It can spell disaster when completing a single-player campaign, multi-player mission, or other evolution.

@JupiterJoe, @Doughguy, & @-Rudel- Here are my tests in an F4U and P-47 with diff braking. See relevant track & MIZ files. These conditions are confirmed: 1. Damage to Corsair at initial spawn. 2. Corsair "slams" on deck after repair - potentially damaging tail wheel; no notice for sustained damage. 3. Poor turn radius with tail wheel unlocked (before and after repair). 4. Sharp turns in Corsair under 0 wind conditions by increasing engine to takeoff speed. Tail lifts off deck and diff braking is achieved. 5. Demonstrated the dangers of diff braking with high engine power & tail off deck in the Corsair. 6. Corsair track file with repair has accelerated time after initiating the repair cycle. 7. P-47 repair cycle NOT triggered at spawn point. 8. P-47 can perform sharp turns when engine near takeoff power. Tail lifts off deck & diff braking achieved with tail wheel locked. 9. External views yielded a visual difference between Corsair & P-47 tail wheel caster effects. Corsair shows limited, approx (+/-) 20 deg caster; P-47 tail wheel showed 90 deg caster. Conclusion: F4U-1D Corsair tail wheel model appears to be damaged at spawn and/or aircraft has too much weight on the tail wheel to prevent full caster. @JupiterJoe, I never put a lot of thought behind the repair cycle for aircraft. Thanks for sharing that pearl of wisdom! 2025-08-16 F4U Turn Rate-No Wind.trk 2025-08-16 F4U Turn Rate-No Wind-Repair.trk 2025-08-16 P47 Turn Rate-No Wind-Repair.trk Corsair-Turn Test-No Wind.miz

@-Rudel-, have you independently confirmed this bug exists, besides reading this thread? Making sharp turns in the Corsair is not possible in its current state. Do you require more information or data? Are you suggesting that the users are SOL ("Still" Out of Luck) for differential braking?

Gents, Raising the tail does not require additional wind on deck. Increasing throttle above 30 PSI of manifold pressure raises the tail off the ground. This is covered in one of the Training Missions for the Corsair. When the tail comes off the ground, you can release 1 brake pedal and the plane will pivot on the held brake. It is VERY precarious because you can easily nose over. I wish to reiterate: If you have to go full throttle, stand on 1 brake, and add rudder (rudder yields no result, btw) just to make a sharp turn in the Corsair, then something is flat-out wrong!

@Skyspin, Confirmed. I just tested the diff braking effect. It's still broken. There was no mention of it in the change log. I wanted to see if the problem was secretly solved. That is a resounding "NO." Can we get a few more Corsair flyers to chime in, please? We need to squeak more loudly to get some grease.

@Cgjunk2, Thanks for the confirmation. I agree with your remarks! I attempted to put things into perspective when it comes to fixing bugs. I would bet dimes to donuts that other game-braking things would be a higher priority to resolve. For example, crash to desktop, incurring damage/landing gear collapse just by spawning into the unit, or engine explodes when applying throttle past 50%.

@flanker0ne, Thanks for the suggestion. However, my test resulted in no action being taken. For example, after moving the switch to PTT (Push to Talk) in multiplayer, I would hear a distinct audio pop to indicate the mode changed from VOX to PTT. There was no audio pop to indicate the ICS mode change. This is a problem that should be investigated further.

GTFreeFlyer, Good for you to put a lot of faith into a dev to rack & stack their priorities. I ask about the priority to resolve this issue because it can be easily overridden for a seemingly nice-to-have feature. How many times have we seen DCS World (in general) or a module break after introducing a new feature? More importantly, how long does it take for that broken feature to get repaired? Do you remember how long it took for ED to fix the Multiplayer Scoreboard? The answer is ~ 9 months. I suspect it would have been longer had it not been for users to complain often about it. Fixing discrepancies in DCS is a topic for another time. Getting back on-topic of differential braking: If you have to go full throttle, stand on 1 brake, and add rudder (rudder yields no result, btw) just to make a sharp turn in the Corsair, then something is flat-out wrong! There is a problem with the flight model regarding tail wheel castering/differential braking physics. The Corsair should be no different than any other tail-drager when taxiing with it's tail wheel unlocked. If I can't easily taxi this bird on the deck then it will collect dust. It would be a shame if this problem does not get addressed. To sum things up, diff braking is broken for the Corsair. It affects basic ground/flight deck handling. Many users, like myself, have issues with it. I would like to see this problem get addressed sooner rather than later. This shouldn't be the top priority but should be grouped with higher-priority items.