Gazelle unfinished flight model

[Whisper]

Please don't mistake reporting potential bugs and unusual behavior for "dev bashing".

We all want their current and future modules to shine as we have invested time, money and effort to support it. :thumbup:

The way I see it, the more info we can give Polychop now the easier time they have validating it through their sources when time comes for that. Supporting claims with videos and documents will only ease their labor.

When a certain group of people spam these boards every day with the repetition of how the FM is bad and requesting immediate dev answers every day, in nearly every topic about the Gazelle, yes, some think about dev bashing.

 

There has been asknowlegment that Poly doesn't consider FM as finished, ie they are still working on it, can we please move one?

[Penshoon]

When a certain group of people spam these boards every day with the repetition of how the FM is bad and requesting immediate dev answers every day, in nearly every topic about the Gazelle, yes, some think about dev bashing.

 

There has been asknowlegment that Poly doesn't consider FM as finished, ie they are still working on it, can we please move one?

So you don't want people to report bugs to help the developers improve the module? Somebody gotta do it if it's to improve :(

[Holbeach]

Or we can stop dev bashing and let them finish as already said, No wonder devs never share anything with us.............................

 

Don't mistake dev. bashing with constuctive feedback.

 

It's a beta and the only way devs. will get to know what's good or bad, is from people who are prepared to put some effort in to finding things out and letting them know.

 

Or shall we all sit back and do nothing.

 

..

[Coxy_99]

The thread finished at post #16

[Whisper]

So you don't want people to report bugs to help the developers improve the module? Somebody gotta do it if it's to improve :(

 

Where the hell did I say that???

[NineLine]

Don't mistake dev. bashing with constuctive feedback.

 

It's a beta and the only way devs. will get to know what's good or bad, is from people who are prepared to put some effort in to finding things out and letting them know.

 

Or shall we all sit back and do nothing.

 

..

 

They have acknowledged the issue now, so no need to keep hammering on them, that said as they update and release patches, I am sure they appreciated any input and testing everyone will offer up.

 

Just keep a balance guys. If this is truly meant to be a bug report thread, than only information helpful to them should be posted here, if this is meant to be a thread purely to poke them to make sure they are still working on it, it will get closed.

[Mt5_Roie]

Always fun to read these threads after a long day at work. So here's a couple tidbits.

 

First, keep giving us bug report...don't stop. BUT make sure you use the template provided in the sticky for bug reports:

https://forums.eagle.ru/showthread.php?t=166931

 

The reason the template was created is because I have over 20 years in software design and I know pin pointing issues is key to solving them. So instead of us having to ask you guys a zillion questions to get the information we need - the template get most of it for us. It saves us time and helps us resolve the issue faster. I happen to notice this thread doesn't have this template anywhere in it.

 

As for the negativity, I would prefer if were all a little more civil on these threads. At the end of the day, we all just want to fly a fun helicopter. So what I like to do is for every minute I spend on these forums, I do about 10 minutes in the pit flying. Because after all, flying relaxes me and makes me feel good.

[Hook47]

Thanks for the reply Poly, totally agree- the negativity needs to be dropped. Flight model programming is immensely complex, just based on the very nature of aerodynamics. I'm a real world pilot, with reasonable amount of time in "light" helicopters and even though the Gazelles FM ain't perfect it's very good and delivers the feel of flying a real world helicopter.

 

Ease up and let the guys work, the issues are acknowledged. Actual bug reports- good! Tireless debate and reputation- bad...

[zaelu]

I want to tell you something about this perceived negativity.

 

Imagine an experiment.

 

You have a Game or game module... You have 3 guys that test this game or module

 

1. First guy is payed to test it

2. Second guy pays to test it

3. Third guy is neither payed nor he pays anything to test it

 

Imagine they stumble on the same bug (just to keep the experiment simple)

 

How do you think their emotions will be? Which one you think will be the coolest bug reporter?

 

If you reach the same conclusion like me then why would you ask a paying customer to be cool as ice when reporting bugs and not expect them to be... a bit hot or acid and no get touchy about it in the first place?

 

Also about the use of template. I am all for it as it really helps but don't push it beyond reasonable as not taking reports into account because they are not formatted. After all we all "love" to get in line for customer support an be "formatted" with eliminatory questions. After all if I call SFR and ask them about why my internet goes to drain when I turn on the TV I wouldn't like to be answered... "it's the tv box doing its magic... and by the way... your name makes me think you speak like Donald Duck... ha ha".

Edited September 28, 2016 by zaelu

[Mt5_Roie]

All I did was ask them to fill out the bug report template and to be civil to each other. If you look at it from a programming perspective: a bug is reported. But the information I need to resolve the bug is somewhere in four pages of the thread and between people arguing back and forth. So that's not conducive to me finding the answers I need to resolve the issue.

 

So again, lets keep the thread on topic and be nice to each other please.

 

I want to tell you something about this perceived negativity.

 

Imagine an experiment.

 

You have a Game or game module... You have 3 guys that test this game or module

 

1. First guy is payed to test it

2. Second guy pays to test it

3. Third guy is neither payed nor he pays anything to test it

 

Imagine they stumble on the same bug (just to keep the experiment simple)

 

How do you think their emotions will be? Which one you think will be the coolest bug reporter?

 

If you reach the same conclusion like me then why would you ask a paying customer to be cool as ice when reporting bugs and not expect them to be... a bit hot or acid and no get touchy about it in the first place?

 

Also about the use of template. I am all for it as it really helps but don't push it beyond reasonable as not taking reports into account because they are not formatted. After all we all "love" to get in line for customer support an be "formatted" with eliminatory questions. After all if I call SFR and ask them about why my internet goes to drain when I turn on the TV I wouldn't like to be answered... "it's the tv box doing its magic... and by the way... your name makes me think you speak like Donald Duck... ha ha".

[Whisper]

Not that again.... people that can't avoid being "touchy" for beta testing (paying or not) should simply not be beta testing. Simple. You perfectly know that the product will be bugged and unfinished, if this is too much for people, waiting for full release status is the answer.

 

In current case, perceived response from Ploychop ("all is fine is the FM") has triggered the "whole thing". Now we have the actual stance from Poly on the subject, case closed. Back to beta testing, and that mean bug/issues reporting, without the negativity.

[Dudikoff]

Given the rather advanced state of the module in general, I can certainly appreciate how the FM behavior in the video if true can seem quite worrisome and IMHO it takes a lot of optimism to qualify it simply as "a bug" given the minimal comments on the matter provided by the devs.

Edited September 28, 2016 by Dudikoff

[Spacehamster]

It would also be great if forum moderation would be civil towards customers. After all we forked over 40 space credits so we bought ourselves the right to an opinion. And the FM feels too floaty and raily. More specific, the magical banking runaway input.

[Mt5_Roie]

Everyone is entitled to their opinion. I'm just trying to get people to use the bug report template so we can address them better.

 

It would also be great if forum moderation would be civil towards customers. After all we forked over 40 space credits so we bought ourselves the right to an opinion. And the FM feels too floaty and raily. More specific, the magical banking runaway input.

[dimitriov]

Hey guys, keep calm a bit please.

 

1) Roie said to you that there still was work to do on the FM.

2) He manages to remain polite with you, quite happy that I don't do such job ;)

 

I don't know what you imagine, kinda like introducing VRS, reactions to collective depending from wind etc are just 2 lines to edit. looks like you never saw a FM code file and its thousands of code lines.

 

So please, it is perfectly understood and accepted that there are still lacks in the FM, but as said by Roie, all which is needed is you to complete the template so they can deal with them. And complete them quietly, with peace, love, and teddy bears in mind. By buying a Beta, you accepted this way of working, you knew it. Work is being done on it, so please remain civilized, developers are not your enemies ;)

 

(Teddy bears are not included in the final product)

 

Thank you <3

 

Nicolas

Edited September 28, 2016 by dimitriov

[msalama]

Hey guys, keep calm a bit please.

:thumbup: Hey Dimi, you rock. I think we're all on the same page now. i.e. this fine chopper is still in beta & the FM will thus be improved, also based on what input knowledgeable folks provide. So it's good, isn't it?

[Focha]

One easy way of ending all the behaviour is to... Release only final version and keep closed betas! TA RA!!! :D

[dimitriov]

Yes but teddy bears may not be suggested in this case.