Blaine Stars

Criticism to ED regarding the AH-64D yaw instability after the latest update It’s extremely frustrating to see the AH-64D — one of the most complex and expensive modules in DCS — affected by such a significant regression in flight behavior, especially in yaw, right after an update. What’s most concerning isn’t just the bug itself, but the apparent lack of proper testing prior to the patch release. The yaw behavior is clearly off and directly impacts the basic handling of the aircraft. This should have been caught in any reasonably thorough QA cycle. On top of that, the lack of clear communication from ED about what’s going on and what’s being done to fix it only reinforces the feeling that, despite being a premium product, the Apache isn’t receiving the level of attention and ongoing support it deserves. As a long-time customer and flight sim enthusiast, I expect more responsibility, transparency, and commitment to quality — especially in modules that require such a high level of investment from the community.

Hi ED! I’d like to better understand a limitation I’ve been facing with the AH-64D in DCS. Why is the CPG unable to detect infantry on the ground using the sensors, even when they’re out in the open and at close range? Is this an intentional design choice, a limitation of the AI or sensor modeling, or something that might be improved in the future? Thanks!

problem solved.

nullI found where I set the elevation knob for the sight and there is nothing set, is this movement of the sight and the rotation of this knob when I move the cyclic right?

I made a video (link below) to show the problem. Whenever I move the cyclic forward, backward, left, or right, the sight and the elevation adjustment knob both move, which makes aiming very difficult. I've already checked and couldn’t find any incorrect key bindings — still looking for a solution.

One thing I’ve noticed is that the knob that adjusts the sight elevation keeps rotating left and right constantly, causing the sight to move up and down all the time.

Hi everyone, Lately I've noticed that the Mi-24P Hind's sight is behaving strangely. Every time I try to aim at a target, the reticle keeps moving constantly, even when the helicopter is stable, making it nearly impossible to hit anything. Before, the system worked just fine and was much easier to use — now I just can’t use the Hind effectively anymore because of this issue. After some research, I found out that a SYNC mode was implemented for the ASP-17V sight. I’ve tried to understand how it works and followed the instructions, but I still can’t get the reticle to stop “drifting” or moving on its own. Is anyone else experiencing this? Is there any way to disable this new mode or return to the previous behavior of the sight? Any help or explanation would be greatly appreciated, as the Hind has become almost unusable for me in its current state. Thanks!

What a magnificent solution, you have a beautiful map and you have to run it on the minimum graphics, great solution genius, you missed the opportunity to keep quiet.

Congratulations to Eagle Dynamics for the ongoing progress in the development of the F-15C, F-35A, and MiG-29A for DCS! It is remarkable to see the commitment to delivering increasingly detailed and authentic simulations to the community. These modules represent more than just aircraft; they are milestones in advancing our favorite simulator, offering new possibilities for immersive and challenging experiences. At the same time, it is important to emphasize that this journey requires patience and support. Unfortunately, a portion of the community continues to discredit the team’s hard work, fostering a negative atmosphere and dampening the enthusiasm of many. To those who truly understand the effort and dedication behind every detail, let us continue to support this incredible project. ED’s success is our success as aviation and simulation enthusiasts. Believe me, the future of DCS is bright – and together, we are part of this story. Fly safe, support strong!

I was testing the automatic flare and chaff system. The flare works normally, but the automatic chaff doesn't work for me. Is there something specific I need to do to make it work?

Hello Polychop team, I would like to suggest adding an option in the rearming menu for the Kiowa Warrior in DCS that allows us to enable or disable the PDU. This would provide added flexibility for mission planning and gameplay. Thank you for considering this addition!

Dear Eagle Dynamics Team, I hope this message finds you well. First and foremost, I would like to express my appreciation for your dedication to enhancing the DCS World experience. Your attention to realism and detail has undoubtedly made DCS the premier flight simulation platform. As an avid user of the platform, I am reaching out with a question regarding the Caucasus map. Considering the recent improvements made to other maps and the introduction of new technology in DCS, could you provide some insight into why the Caucasus map has not received similar graphical and performance enhancements? Despite being one of the oldest and most iconic maps, it appears that it has yet to benefit from the advancements seen elsewhere in the simulation, such as enhanced textures, updated scenery, or optimized performance. The Caucasus region holds a special place in the DCS community, and many users would highly appreciate any updates that would bring it closer to the graphical and technical standards of newer maps. Are there any plans to upgrade this map in the future, or is there a reason for its current state that users should be aware of? Thank you very much for your time, and I look forward to any information you can provide.

Look how interesting, on Polychop's Discord there is this channel #oh58d-dev-change-logs, so you enter the channel and look at the last post '— 16/06/2024 04:31'. In other words, the channel that should have information about the development process of the Kiowa/Gazelle is not being updated. Then someone has to go to the general chat and ask the question 'Is anything in ⁠oh58d-dev-change-logs making it in this one?' to get this response: 'I learned my lesson with the Gazelle patch that destroyed engines in any desert map. We'd rather have no patch than a buggy patch, and I guess we can all agree on that.' Seriously? Is this how a customer who bought the module and expects constant updates and information on development deserves to be treated? And there are still people saying this is hate. Why wasn’t a complete note with all relevant information posted in #oh58d-dev-change-logs and shared on the ED forum? Why wasn't it done? I would like an answer. It only got a response because someone had to go there and ask.

I appreciate your collaboration, but I personally have never had much luck on Polychop's Discord; I always received vague answers. It never happens to me, but I have flight buddies who tell me that the devs are very rude when questioned about something. However, I believe Polychop should change its approach. We are talking about a DCS module, and it's only fair for Polychop to post in the space created for them on the DCS forum. After all, it is a DCS module, isn’t it?"

Who provided the communication? Was it Polychop, or did someone have to go through their Discord, searching channel by channel to gather screenshots? If you're satisfied with that, good for you, but I'm not. I think Polychop has terrible communication, and in my opinion, it's disrespectful. This situation raises many doubts for me about Polychop. I was pleased with the turnaround they achieved by delivering an excellent Kiowa module, but it seems like they're repeating the same mistakes they made with the Gazelle. I hope they don't take too long with the continuation of the project, and I also hope they get their act together and PROVIDE ACCURATE AND COMPLETE INFORMATION IN A PLACE THAT EVERYONE CAN ACCESS EASILY AND QUICKLY.