Kinkkujuustovoileipä

It's on ED, so don't expect a deadline.

This is known, we have a ticket with ED as something is broken/changed on their side.

Actually, the Beta testers are the Beta testers. But I still expect tweaks needed after release because that's just how dev is.

I will happily annoy someone else about this on your behalf.

Down -> pressed for certain inputs is one of the plannes changes.

And the Force Trim still doesn't work? Do you have Force Feedback enabled in the module settings?

Which trim option are you using in the Gazelle module settings?

Hi! I think this is just one of those 'age of the module' things. Some inputs were designed for toggle switches, others for buttons. I've recently gone through and overhauled all the inputs for the OH-58D so they have both toggle and moment type inputs for switches, I plan to do the same for the Gazelle, but please be patient as it is time-consuming work. I hope it can be available for the next patch after the February update (that deadline has already passed).

Hej Rune! Forgive me, this is one of those bugs that just keeps slipping through my workload. I'm going to add the binding now, but unfortunately it won't make the February patch release. In the meantime, you can add the following line to your SA342 keyboard and joystick binding luas in the Mods/SA342/Inputs folder. This will function as a toggle. {down = device_commands.Button_3, cockpit_device_id = devices.TABLET, value_down = 1.0, name = _('Show/Hide Tablet'), category = _('Tablet')}, Please note that in the February update the folder structure is changing and you'll have to re-add the line to the SA342-CORE input luas. MVH -Kinkku

When I read these types of comments, they often affect me quite strongly. I wonder why it is that, on top of a full time demanding job, a family, and a social life, I put in far too many hours developing modules for DCS. This is why I left the public Polychop Discord, and why I will now also stop reading the ED forums too. Because I am tired of you, the effect people like you have on my mental wellbeing, the complete lack of understanding you have about the complexities of simulations and software development, the dismissive tone you have of the hard work and the sheer number of hours I have put into the Gazelle and Kiowa this year. Deep down, I know, and have to reinforce the belief, that I am good at what I do. No one else has brought you a complete FM overhaul; weapons overhaul; new features like the periscope sight and tablet. No one else took the Gazelle and rebuilt it; I did that, and I continue to do it. But when I read your comments, I am just overcome with the feeling that I don't want to anymore. So thanks for that. I will get through it, and continue my hard work on both modules, but it's not for you, or because I care about what you want anymore; I do it for myself, because *I* can. Because it's a badge of my skill, ability, pride, passion for what DCS is, and what these modules can be. I recently had a chance to reflect on the work we've put into at Polychop over the last year. It's full of positivity and reflection of the great work we've done this year, and what's coming, both for the Kiowa and Gazelle. But this is my other end of year reflection; the balance to all that positivity is that all that work I've put in has a cost, and I pay it in the emotional pain and despondency that people like you thoughtlessly throw out. If the community wants to know what the 'dark side' of DCS development is, well here it is. It's the human cost. So long. -- Kinkku

Lighting at the spawn positions in Al-Tanf does not illuminate aircraft or cockpit models. Compare with e.g. Haifa where the spotlights illuminate aircraft geometry. Issue is present in all tested builds (OB, internal testing and dev builds) and both ST and MT. Attached is a screenshot comparing lighting at Al-Tanf and Haifa.

Thank you, I really appreciate you taking the time for writing this

Hi, yes it is, but we still have a number of future features planned and some already in progress. Unfortunately we don't have the capacity to both implement them and document them at the same time (given we're also doing this for the Kiowa), so once we reach a certain cut off point on the Gazelle we will update the documentation.

Henry the auto-Hoover is the highest priority on the Gazelle, but there is only one of me to work on it and the Kiowa is a higher priority right now. Rest assured, as soon as I have time it is the first thing that will I will do on the Gazelle.

Autopilot will come back, just give it time. We are a very small team and the Kiowa is highest priority. Autopilot is my highest Gazelle priority, as soon as I can work on it.