Kinkkujuustovoileipä

Works fine for me

No worries, it's been an interesting evening full of surprises so right now if something is fixed or working for you it's a positive!

October Patch PSA Dear all, the latest update for DCS has unintentionally included the work in progress update for the Kiowa Warrior. While I'm sure you're all happy to finally receive some much needed bug fixes and the Echo19 sound update, this update also includes changes that were not finalised or had not finished testing. We're still working out exactly how this happened and what the current state of the Kiowa. Needless to say, we're also considering the next steps once we know more. What we do know/suspect: Echo19's sounds are included, but they are NOT complete or finished The input system overhaul is included, but there will be many non-functional or incorrectly functioning bindings The damage model code is included but not the associated art changes All of the bug fixes in our dev changelog should be included (at least something good comes of this!) We ask you for your patience as we try to determine what has happened and how we can best solve it. Sven, Dan, Joose, Rober, & Kinkku

October Patch PSA Dear all, the latest update for DCS has unintentionally included the work in progress update for the Kiowa Warrior. While I'm sure you're all happy to finally receive some much needed bug fixes and the Echo19 sound update, this update also includes changes that were not finalised or had not finished testing. We're still working out exactly how this happened and what the current state of the Kiowa. Needless to say, we're also considering the next steps once we know more. What we do know/suspect: Echo19's sounds are included, but they are NOT complete or finished The input system overhaul is included, but there will be many non-functional or incorrectly functioning bindings The damage model code is included but not the associated art changes All of the bug fixes in our dev changelog should be included (at least something good comes of this!) We ask you for your patience as we try to determine what has happened and how we can best solve it. Sven, Dan, Joose, Rober, & Kinkku

Posting a notification here, also see announcement in Discord.

Oh, the irony. Looks like we did, even if we didn't want to.

This is known. You may have a fix for this in the latest patch.

No, that would be stupid thing to do. It removes the pixelation effect applied when zoomed in because there is some DCS bug with this that causes a picture in picture type bug with clouds and ED haven't fixed that for us yet. So removing it for now is only option.

This is being looked into. We have all your data, thanks. Not sure why no one replied sooner, we've just been busy doing the actual work, sorry for that. We're pretty sure the main performance problem was caused by an overcomplex damage model, especially with the blades. Testing has shown improvements but it's difficult as performance is a very subjective issue between hardware and users. We're doing what we can and hopefully you'll see improvements in the next update.

Those options already exist. Please read the manual.

We were informed by SMEs that HHM in the Kiowa was somewhat unreliable IRL and so modelled it to be so in sim.

NVG effect is a DCS core thing, not something Polychop will touch.

This is getting a bit silly now, so I'm asking you to all stop being Cassandraic and take a step back. Early Access does not refer to quality or bugs or even performance. It simply refers to the amount of completed features at release vs. the planned amount for the product. In that sense, the Kiowa is not considered Early Access since all the features we planned for the module are implemented with one or two exceptions that have already been discussed. Compare this to other modules where you're still waiting for various weapons or whatever feature five or six years later. I want to be super clear here - I am not saying the module doesn't need improvement, or that there aren't issues to be looked at and addressed. I'm simply saying that arguing it is an Early Access release because of these issues is factually incorrect. Your definition of what Early Access means is not what is used by Polychop or Eagle Dynamics, or any software developer or game studio I've been a part of in my career. It is about delivery of planned features, that is all. Quality is not a *feature* (although I would absolutely agree the world would be better if it was, and I personally try to push that where I can - hence WHY the fixes are taking longer than you want). As for "Didn’t even know they reacted “we fly from inside the cockpit”…. Even more reason not to spend my money on them." - I don't know where this came from, nor do I care. It's not my opinion, therefore as long as I am part of Polychop it's not fair to say it is the opinion OF Polychop. No matter what someone else may have said. I've said this earlier, I will repeat it again: We have listened to what you've said, we're aware of the issues and we are currently working out how to address them. I can't give you better answers than that because I am not the artist, I'm sorry. All I can ask for now is patience. I know you don't have it. I certainly don't either

1) Art issue. I can't speak for this or any other art issues, sorry. 2) Known issue, I believe resolved internally already or tracked to be fixed. 3) DCS issue. Believed to be linked to DLSS settings. Reported to ED on the 6th of June, nothing has happened since. Look, I understand your concerns and frustration. But the idea that we're not doing anything about it is false. You only have to look at our WIP changelog to see that. Bugs happen. I don't think you can judge us negatively on releasing with some bugs compared to any other module. What matters is that we are addressing them. It takes time because we do so methodically and carefully, and the update release process has been chaotic until recently due to the CH-47 and other changes. I will not release an update until it has been fully tested to my satisfaction, and until now there has not been a release window large enough to allow that. Again, I can only speak for code issues. But do not think the art issues you raise have not gone unnoticed. I just can't provide any answer to those at this time. null

I've seen similar behaviour, I'm quite certain it's to do with DCS lighting on MT builds. Consider it a DCS problem, not a Kiowa issue, since I've seen it change by itself and in multiple instances. Plus we don't do anything with lighting other than cockpit IBL which is common to all aircraft.

Is know and reported to ED

Why should I care about Italy? Great, it flew Bell helicopters. So did Uganda. Shall we add a Uganda livery too? Countries were picked either because the devs are from there or just at random. Topic is closed as far as I'm concerned.

Understood, will see if we can add some options to fix this.

This would be great, except that's an OPFOR shape. Which is why I refuse to implement it until ED fix it. The pointed tip does not signify a helicopter but instead HOSTILE affiliation.

Unfortunately ED don't understand the MIL-2525 standard properly and there is no accurate recon helicopter symbol at this time.

Should be able to do it by just adjusting the heading manually? I.e. just move it one notch right and then back left or wherever you need it.

I suspect one of you switched the MFD to backup mode.

Did you turn on RTE SEQ? Initial page 2 IIRC.

Don't really see how a livery of a country that didn't fly the aircraft can be considered 'missing'. We have no intention of adding further fictional liveries at this time. Community liveries are already becoming available and I'm sure there will be many more when the paint-kit arrives.

This is a very old post. The Gazelle can slingload. And you can take troops using CTLD or similar system.