Do some reaserch, find out, get your facts... verify for yourself



Publisher calls (defines) the state of what it is they are publishing.



Agreed that constructive critiscism is good (I assume you mean critiscism, yes?) but it is atm, is harrassment - pure and simple



why should anyone "ancknowledge" anything after the vindictive which has been hurled their way??



now, there's a thought... try practising that one :)

The FM of Take On Helicopters in this new patch is really great...

I'm really divided! Will get "Hinds" DLC today!

I'm thinking about that one, too. DI's Hind was a sim I enjoyed very much, and beside the IL2 the only Russian hardware I really like.

that is exactly the point...

You hit the bull's eye.

Eehh, 6S.Manu,

whining is NEVER productive and by no means related to constructive criticism!

Whining is what happens after the states of constructive criticism and then nagging criticism!

And now for something completely different....

http://3.bp.blogspot.com/-5OR2Aghz-9..._different.jpg

How do we celebrate the first birthday of COD ?

Any suggestions?


http://www.cheesebuerger.de/images/s...frech/c025.gif

play it maybe

:rolleyes::rolleyes::rolleyes:

Language barrier's issue here... with whining I mean making clear that the problem is, not senseless crying or name calling... very few here are actually crying IMO, so it's no a valid reason to attack every "whiner" (the former type) as guard dogs...

A real life example: I work as developer of industrial software (italian shoes) and I'm in contact with many persons who are "allergic" to PC... you know, guys pressing on the keyboards with the forefingers alone.

One of my biggest problem is not thinking to these guys when I'm develping a new version, and so there will be a function not really user-friendly.
The program is working in the right way but some of these persons write to me with constructive criticism ("it might be better if the UI is made in this way"), others whine (even in offensive ways...) by telephone/email since they don't understand how to use the program.

In BOTH cases I must accept what they're saying (because it's true, the application IS NOT user-friendly) and so I analyze the issue together with my boss and decide if the UI have to be reworked.

And here we are talking about a working software... if it does not work there's nothing to talk about... you make the update now.

I can't ignore them... I (or the boss) answer to them in a honest way ("Good, we're going to change the UI" or "The development of that UI needs too much time and it's not crucial: we'll do in the next months, be patient").

They are my customers... if I don't listen to them I can't improve my application (I know nothing about shoes' production or selling) and above all I lose them.

Sure... You begin and I'll follow.