BUG: "Easier Controls" stay enabled

[Flagrum]

Once "Easier Conrols" were enabled during a DCS session, un-ticking the check box does not actually disable the feature.

 

To replicate:

1. Start DCS

2. Fly a mission, observe the helo's reaction to control inputs ("twitchy", "nimble", etc.)

3. End mission but STAY in DCS

4. Enable Options->Misc->SA342->Easier Controls

5. Fly a mission, observe that the helo now reacts more gentle

6. End mission, STAY in DCS

7. Disable Easier Controls

8. Fly a mission, observe that the helo is STILL in "gentle" mode: this should not happen!

9. End mission, close DCS, restart DCS

10. Go to 2.

 

 

PS: I'd like to have a bug subforum, not just a huge sticky thread...

Edited May 3, 2016 by Flagrum

[Mt5_Roie]

Thanks for reporting it...can you add it in the Bug Report thread sticky above. I'll get it added to our list.

 

Also, big thanks for all the steps, helps us to reproduce it nicely.

 

I'll about the subform as well. Being our first module, we'll start with the big thread. I go through it daily and add all the bugs and requests to our master sheet in google docs. So it's all being heard. But just makes it easier to find in the big thread then in normal threads that I might miss if I don't look on the forums during my normal work day.

[Flagrum]

Thanks for reporting it...can you add it in the Bug Report thread sticky above. I'll get it added to our list.

 

Also, big thanks for all the steps, helps us to reproduce it nicely.

 

I'll about the subform as well. Being our first module, we'll start with the big thread. I go through it daily and add all the bugs and requests to our master sheet in google docs. So it's all being heard. But just makes it easier to find in the big thread then in normal threads that I might miss if I don't look on the forums during my normal work day.

The single thread solution is a mistake, imho, and goes contrary to the established best practice of "one bug per thread". Imo you should get yourself moderator rights for your (sub)forums from ED - then you could add tags like "[reported]" to threads - like it is done in most other bugs & problem subforums of the other modules.

 

But anyway, I added this one to the sticky thead.

[Home Fries]

Concur w/ Flagrum on the subforum. This also allows us to see at a glance which bugs have been reported without having to sift through an entire thread.

[dotChuckles]

Yeo agree with the subforum. It will save your sanity. :-) and allow elaboration in a bugs individual thread.

 

Although have to say, it's good to see that the kinds of bugs being reported are more of the tweak or minor flaw variety. Very good to see in a first release :thumbup:

[SpaceCroissant]

Adding to what those said above, I'd recommend something more powerful than just Google Docs for cataloging bugs internally - for example Mantis.

[Aginor]

Mantis is actually very nice, and easy to setup and use.

 

And yeah, you need that subforum badly.

[Mt5_Roie]

Working on it.....and while I agree Mantis is nice, it would require setup and training for the team. For now, I'd rather invest our time in fixing things and making the Gazelle better and looking at a better tracking system afterwards.