Kinkkujuustovoileipä

My point was that when we chose to leave Polychop due to our disputes with Sven, we obviously could no longer continue working on the Kiowa or Gazelle. Both projects meant - and continue to mean - a lot to us personally. We felt that we had lost them. It's hard for us to see the issues being reported and know we can't do anything - especially for Rober and I who keep reacting like "hey I know how to fix that!" and Dan really has a strong connection to the Gazelle, after all he was instrumental in organizing and making the 2024 updates happen with all the new liveries and features for it. That really was all his leadership and management and work with the community contributors making that happen. It's hard to see all of that just stop and a now disaffected community when you know you have the experience and capability to change or fix it.

No, I understood what you said. I'd like to try and explain myself with some contextual points: 1) Every other third party developer I've interacted with has cared about their modules. However they work within the capacities they have available and sometimes that just means they don't have the resources to maintain older modules at the expense of working on new projects 2) Adding to the above, I don't think you understand the 'drop off' in sales after a release and just how severe that can be. DCS for developers is like a dog - it's not just for Christmas, it's for life. A DCS module has no finite end. It goes on forever, yet the money it is making later on is just not enough to justify the investment required to renovate it. You'd have to most likely pay tens of thousands of dollars for a full art overhaul, for example - which is one of the most obvious and common issues with older modules - and it simply will not make that money back. There are ways to do this e.g. BS3 or A-10C2, but in order to justify selling an update you end up having to invest even more because you need developer time to design and create marketable features on top of QOL or art updates - or risk the wrath of the community. It's not easy. 3) There are legal methods in place that guarantee modules do not simply disappear. I realise the irony of saying this after Razbam's modules have been removed from sale, but again, that situation is not comparable to what happened with PC. 4) I'm grateful for your thanks regarding the quality, professionalism and communication that people like Dan, Rober, Joose and I brought to Polychop. We worked very hard on that. Especially Dan. It was not easy. 5) I think that most of your ire is directed at Razbam, and I get it. But that's an extreme situation and I think it's fair to say both parties have learnt a lot from it. I don't think it's fair to point to that situation and declare that PC is special - rather I think you should recognise that the RB situation is what is special, or unique, or more extreme, whatever comparison you want to make. And the reactions of the people involved reflect that. I certainly can't hold a moral high ground on those developers who spoke out, because I haven't been through what they went though. But given what we ex-developers of Polychop went through, I can absolutely understand the emotional distress and difficulties experienced having put so much of themselves into their work. Losing the Kiowa and Gazelle wasn't easy for us, especially after all the work we did to fix the reputation of Polychop, but at least it was our choice to do so. They didn't have that choice. Anyway, I hope this helps clarify my position a bit. I do understand your feeling, but I feel directing it at Razbam is pointless and possibly unfair given that situation, and aiming at any other developer (including ED) would similarly be unfair.

This is complete rubbish. The Polychop situation has nothing to do with ED.

Thanks, this is probably the most unhelpful bug report so far! Want to try again and see if you can do a little better? Hint - try including a track file.

Simple explanation is that the pitch, roll and yaw switches control SCAS. Autopilot is separate system that requires all SCAS channels enabled to function. If one of the SCAS channels is disabled, autopilot will also disable.

Sorry, I'm not aware of what you're referring to? Perhaps some screenshots showing comparison could help?

ED.

...I wasn't talking to you...I was talking to the person with the ED Translator status who AFAIK has access to internal testing builds. ED decided not to add the KW changes to this hotfix. I am not very happy with them, to be quite honest.

Well thank you for noticing my 'smart' code As for your issue, it's actually already fixed internally. You're correct that 'pressed' was causing problems, it's been updated and waiting for the next patch. Regarding the general state - we're going through all of the issues as they arise and fixing them. I can't promise there won't continue to be some bugs in the next patch but we've definitely smashed the most important/most reported input issues this cycle. Once you get the next update, please keep reporting issues

Understood, this is expected behaviour

Please upload a track and we can take a look

Correct as is, thank you for your passion and support.

Please upload a track file of this occurring when you can, thanks.

If you have specific issues bring them up in the Kiowa testing channel on ED Discord please, not here - you'll get a faster response from me or Rober. However as I wrote in the other thread, these are already fixed in CB, feel free to test.

Duplicate. Issues are already reported and resolved for next update.

It's already fixed and you have access to test it. As I've said in another post, we have asked ED for a hotfix to include this and other more serious issues.

Already fixed internally.

We've asked ED to release a hotfix as we've also fixed a serious CTD that was discovered internally regarding the VOIP system, but we are expecting them to say no.

Fixed for next patch.

Hopefully fixed for next patch, there are some other WCAS issues we are looking at too.

Hi, track is not so helpful for us for AI issues. Please could you upload the miz?

Please attach a track, I am unable to reproduce the issue.

Fixed for the next update. Thanks for reporting!

Interesting discovery, thank you for sharing!

Sorry, this is not something I'm able to help with directly, but have you tried looking at how SRS gets this information?