ED, we need help as this module have been abondonned by Polychop

[peeter]

Hi ED,

There is an issue with one of your 3rd party.

As you may know, Polychop's Dev team have all quit the company leaving only the CEO.
For some time now the CEO is not even answering on his discord and there is more and more unresolved bugs on the SA342 Gazelle and some on the OH58D Kiowa. 

The bugs vary from missing textures (on dipole antenna), wrong axis, keybindings issues, multicrew desynch and bugs, kneebord mixed up  and more.
Those bugs were reported from month or years, but nothing is done...

For example here is some non revolved bugs :

• Reported on July 2 2023 : --https://forum.dcs.world/topic/329727-tm-warthog-throttle-mouse-axis-problem-on-tv/
• Reported on June 8, 2023 : --https://forum.dcs.world/topic/327589-pedal-trim-not-working-propertly/
• Reported on July 20, 2024 : --https://forum.dcs.world/topic/354334-multicrew-issue-pilot-and-copilot-affects-night-vision-google-employment/#comment-5672503
• Reported on July 20, 2024 :--https://forum.dcs.world/topic/354333-multicrew-issue-with-nadir-even-when-copilot-leaving-the-gazelle-and-rejoin-entering-and-editing-waypoints-not-working/
• Reported on september 14, 2024 : --https://forum.dcs.world/topic/357716-the-windscreen-wipers-do-not-wipe-when-you-press-the-pilot-wiper-button-on-the-stick/
• Reported on september 14, 2024 : --https://forum.dcs.world/topic/357715-floating-metal-clip/
• Reported on april 2, 2025 : --https://forum.dcs.world/topic/371479-i-love-the-gazelle-but-continuing-to-be-patient-for-a-joystick-slew-fix-for-the-minigun-variant-unable-to-point-minigun-to-the-front-of-aircraft-also-unable-to-point-fully-up-and-down/#comment-5654828Reported on June 27, 2025 : --https://forum.dcs.world/topic/375569-pilot-position-windshield-wiper-clickable-cockpit-switch-issue-as-of-291711733/
• Reported on August 5, 2025 : --https://forum.dcs.world/topic/377214-multi-player-seat-switch-issue/

Of course there is more bugs than those mentionned here, it's just to show that some bugs are here since years ago.

 

Now, what can ED do ?

Well 3rd party have to maintain their products (which is not the case for Polychop Simulation).
I expect mesures to be taken by ED toward Polychop to remedy this bad situation

 

If this is not enough, maybe the Gazelle IP could end up in someone else hands, someone who will actually take care about this module, either ED or an other 3rd party.

Thank you,

Peet

 

Edited Monday at 06:15 PM by peeter

[hannibal]

Im sad that the healthy of a module comes down to community trying to petition to keep a module healthy.

I agree with @peeter!

Im not sure ED has source code..but I hope there will be fixes for this great module and modules 

Long live gazelle!

[ochilov]

I already lost my favourite aircraft, the Mirage-2000 and now i'm loosing my favourite helicopter. It really breaks my heart to see what's happening to DCS.

 

I hope this situation gets resolved soon.

Edited Tuesday at 08:04 AM by ochilov

[flyingshaft]

Hello everyone,
this is Shaft, from Myself Dynamic!

As an active participant in the gazelle community, a day one fan of this historical module (one of the first 3rd party module) in DCS, and a livery creator for Polychop, I must say I'm 100% with what was written by @peeter

It is not because the gazelle is a "niche" module that Polcyhop can act like if it doesn't matter, and we really need to get people at ED involved in this. There are guidelines, rules, commitment toward costumers, and some basic criteria are just not met by Polychop right now.

We know for sure that not a single resource is dedicated to the gazelle, and this is a reality for over a year and a half almost.. There is a long list of easy fix that is just lying there and no one cares about it... 

Please, someone have to make it right. 
For the sake of the gazelle, and the credibility of both Polychop (and by them, ED...)

Take care all

[OhNoMyHookBroke]

To add, I enjoy the Gazelle a lot, and it would be a shame for it to go away. After the resignation of most, if not all, of the Polychop developers, I don't think the future of Polychop's modules are guaranteed, especially the Gazelle, when it comes to them being supported and updated. ED needs to make sure that Polychop (Sven) maintains this module and clarifies that he'll do so.

Edited Tuesday at 08:16 AM by OhNoMyHookBroke

[OmasRachE]

Dear @NineLine,

 

could you give some information about this topic? I don´t own Gazelle or Kiowa but I am getting quite concerned about investing my money in 3. party modules seeing them dropping like flies. # StrikeEagle

[Dup]

There's a lot of modules we may lose with upcoming versions of DCS... I hope Polychop work will not follow the same path...

[Tonker]

Well said @peeter - good points, well made. 

Looking forward to hearing from ED about how they're managing the problem generally, and from Polychop about the Gaz particularly. 

[BIGNEWY]

Hi all, 

I have passed on your concerns, 

with that said please ensure feedback posts here keep to the rules. 

[Mispunt]

The Gazelle is one of my favorite modules. It had a rough start but has come a long way with its updated flight model and skins.
Right now, within the DCS hangar, the Gazelle is a unique and valuable addition: it is the only blue- and redfor light helicopter in DCS, its low complexity makes it easy to learn and its excellent sensors allow a pilot to punch above its weight.
In short, it's a joy to fly and it forces you into a different and very dynamic play/sim style compared to the usual heavy hitters. 
Needless to say I share the concern with OP, I believe the last update to the Gazelle was in July last year after a commendable push from PC to fix and revitalize a module that was not ever going to make them any real money. 
Now more than a year after the last update to the Gazelle it's really getting awfully quiet over there. 

Edited Tuesday at 11:36 AM by Mispunt

[designoner01]

i love the gazelle and many of us only hope that there is continued support for this airframe! thank you for your ear!  @NineLine

as for others, lets just keep sharing bugs and keep reporting them, that is all that we can do as customer!

[Schmidtfire]

This is a part of an open post from one the guys in Polychop (regarding lack of Gazelle updates, posted on the Polychop Simulation Discord, 2025-07-23)
 

As previously stated, the devs are in a Crawl > Walk > Run phase learning module code by essentially reading it backwards and deciphering it.
Learning two entirely different sets of code at the same time and trying to manipulate both does not fit this model of learning or progression.

The 58 is the more recent module to be released, therefore it is going to receive the attention. Sorry if you don't like that, but that's how it goes.

The 58 has more bugs that need addressing (yes we have a list for both modules and this is in fact the case) so they will be ironed out before tending to the Gaz.

The 58 has been and continues to be the module with more consumer utilization by a considerable margin since it's release, therefore as previously stated, it is going to receive the attention (and again sorry if you don't like that but that's how it goes).

Now, that DOES NOT MEAN THE GAZ IS DEAD and or will not receive work in the future. Nobody go running to Reddit referencing this post, claiming that it is dead and wont receive updates because that simply isn't the case. It will receive work in the future, just not right now, and no I can't tell you when no matter how creative you all get with rephrasing the question of "When Gaz Update."

I hope it's okay to post it here on the ED forums. Not great news for Gazelle enjoyers, but it is what it is. Getting the new team up to speed with unfamiliar code is not an easy task. Duplicate that by two modules. It will take time, no way around that. 

[OmasRachE]

At least they are trying to go ahead. Totally different story than "Polychop's Dev team have all quit the company leaving only the CEO."

[Esac_mirmidon]

The truth is out there

[DrummerNL]

3 hours ago, OmasRachE said:

At least they are trying to go ahead. Totally different story than "Polychop's Dev team have all quit the company leaving only the CEO."

Until you realise the guy who wrote that also quietly left the team. 

[MasaMan]

16 minutes ago, DrummerNL said:

Until you realise the guy who wrote that also quietly left the team. 

Ouch. Or more like we're effed.

[Slippa]

What’s the score then? Has everyone legged it?

I have both, I flew the Gaz for a bit only last night, nipping about, it flew ok as far as I could see. Didn’t arm it with anything, just tore it about for a while. These 3rd party deals ain’t much of a party are they.

[hannibal]

its still flyable now, but many of us are concerned for its future.. 

we just want to be heard that many of us love the polychop products and the airframes and wish that i wont fall by the way side

[MAXsenna]

Until you realise the guy who wrote that also quietly left the team. 

And now has been busy with the UH-60L 2.0 community module.

Sent from my SM-A536B using Tapatalk

[Raven (Elysian Angel)]

19 hours ago, Schmidtfire said:

As previously stated, the devs are in a Crawl > Walk > Run phase learning module code by essentially reading it backwards and deciphering it.
Learning two entirely different sets of code at the same time and trying to manipulate both does not fit this model of learning or progression.

The 58 is the more recent module to be released, therefore it is going to receive the attention. Sorry if you don't like that, but that's how it goes.

The 58 has more bugs that need addressing (yes we have a list for both modules and this is in fact the case) so they will be ironed out before tending to the Gaz.

The 58 has been and continues to be the module with more consumer utilization by a considerable margin since it's release, therefore as previously stated, it is going to receive the attention (and again sorry if you don't like that but that's how it goes).

Now, that DOES NOT MEAN THE GAZ IS DEAD and or will not receive work in the future. Nobody go running to Reddit referencing this post, claiming that it is dead and wont receive updates because that simply isn't the case. It will receive work in the future, just not right now, and no I can't tell you when no matter how creative you all get with rephrasing the question of "When Gaz Update."

Makes perfect sense to me. I'm not a programmer by any sense of the imagination but I had to debug a database made by someone else in an old job of mine, and that already gave me plenty of headaches... So starting a new job and having to work with someone else's code?... Have fun and good luck with that!

[peeter]

50 minutes ago, Raven (Elysian Angel) said:

Makes perfect sense to me. I'm not a programmer by any sense of the imagination but I had to debug a database made by someone else in an old job of mine, and that already gave me plenty of headaches... So starting a new job and having to work with someone else's code?... Have fun and good luck with that!

well :

- He quit

- having a module with bugs reported 2 years ago (and some beeing just .LUA to modify) is not a good sign

 

Now Bignewy said that the situation is reported to ED and we can hope for the best.

I hope community will be keep up to date about this topic.

[Kinkkujuustovoileipä]

1 hour ago, MAXsenna said:

And now has been busy with the UH-60L 2.0 community module.

Sent from my SM-A536B using Tapatalk
 

No, that was not written by me. And what is written there is not an accurate representation of the current state of Polychop Simulations at this time.

[MasaMan]

9 minutes ago, Kinkkujuustovoileipä said:

No, that was not written by me. And what is written there is not an accurate representation of the current state of Polychop Simulations at this time.

So what's the current situation?

[Raven (Elysian Angel)]

30 minutes ago, MasaMan said:

So what's the current situation?

Let's not bring more drama into it. The current internal situation at PolyChop is none of our business. But that being said, it would be nice to be kept up to date as to what a reasonable timeframe is we can expect progress on the modules.

[MAXsenna]

No, that was not written by me. And what is written there is not an accurate representation of the current state of Polychop Simulations at this time.

Oh, my bad then.

Sent from my SM-A536B using Tapatalk