![]() |
#21
|
|||
|
|||
![]() Quote:
My thoughts exactly. |
#22
|
||||
|
||||
![]() Quote:
__________________
|
#23
|
|||
|
|||
![]()
The only thing i see helping this community is for Luthier to man up and present us with information directly himself. Real meaningful info. Not this charade through Blacksix. i think we deserver that much at least. Too busy to post, working all hours without holidays etc etc is simply not believable any more. You can't work that hard for that long with so little progress.
Let us know what is really going on.. warts and all, that is the only thing that will restore any faith in this dev team. |
#24
|
||||
|
||||
![]() Quote:
Spot on. QFT & 100 % at your side Ataros. I won't add anything because your post is already perfect in my point of view. @Mr Schevchenko, I always wish you all the luck, but this time , my wish is that you read Ataro's post and have the greatness of recognizing such a good diagnosis you've been gifted. It not only pinpoints the problems, but also gives you solutions.
__________________
|
#25
|
|||
|
|||
![]()
Not that I disagree in principle ... but I disagree with the bug/feature selection. Because - looking at the current Top 30 at bugtracker - all are either minor features or aircraft systems issues or typical online issues. I haven't found a single gameplay or single player relevant issue there and two gameplay-relevant things in the Top 50. That's a predictable result - an online platform will always produce results heavily biased in favor of online issues, but totally ignoring the gameplay and offline part (which is by far the least developed ATM) is only going to enhance the problems and generate more bad blood.
|
#26
|
|||
|
|||
![]()
Single player is going the way of the Dodo, havent you heard?
![]() |
#27
|
|||
|
|||
![]()
Nah ... that's what those simple-minded folks want to tell you. Don't believe every overrated hype.
![]() |
#28
|
||||
|
||||
![]() Quote:
Last edited by 6BL Bird-Dog; 06-23-2012 at 12:03 PM. |
#29
|
||||
|
||||
![]()
Great post Ataros!
__________________
i7 2600k @ 4.5 | GTX580 1.5GB (latest drivers) | P8Z77-V Pro MB | 8GB DDR3 1600 Mhz | SSD (OS) + Raptor 150 (Games) + 1TB WD (Extra) | X-Fi Fatality Pro (PCI) | Windows 7 x64 | TrackIR 4 | G940 Hotas |
#30
|
||||
|
||||
![]() Quote:
I support the majority of what you have stated except item #3. While I understand your statements of procedure to support your claim of "Luthier either does not get feedback from community or sets priorities wrong:" . . . there is no empirical data that shows that Luthier does not receive the information - ie., he may receive it from alternate sources. The priorities listed via the bug report are not IMHO, all the issues that are on the table to be weighed to create a priority list. For example, how can bugs be resolved if they have not yet gotten the engine to work optimally? My position is: that this is a priority that would circumvent any other implied priorities. All other priorities are placed in drawer B while items in drawer A are being resolved. Other than that I think that your post has much merit. I would go further (as a prior IT person and major project leader) and state that: It is not whether issues are being corrected (because we know that they are), but rather - managing customer expectations and utilizing appopriate methods of communicating. When dates are specified, expectations are raised and those dates are expected to be met. Sometimes issues arise wherein those dates are impacted and they slip. BUT . . . . . this cannot become the norm. It is the management of expectations through communication that is extremely important in business to realize business goals. Cheers. |
![]() |
|
|