Latest Patch HURRICANES NOT STARTING AGAIN???

[LoBiSoMeM]

Boring...

How can i start red fighters?

If all the fanboys here can't explain me how, i'll assume that dev team release a porked patch, sorry to say... No excuses for such flaw don't be adressed BEFORE the release, it's not a "minor" bug, it's a HUGE, GIANT bug!

Simples as that!

[CaptainDoggles]

Originally Posted by zapatista

i think the whole context is a little different in this case

as was already stated over 9 months ago, work on CoD had/has essentially stopped, and their main focus was rebuild/create a new gfx and game engine while simultaneously working on BoM. if BoM is not released on schedule this time and proves to be a relative success, then the whole project and series is folded and they close their doors (have a guess at the amount of whining then, and the glee and joy from people like tree)

the last beta patch, and largely this current RC, are primarily the beta introduction of the major progress milestones of the new gfx engine, with a few critical fixes for CoD added (like the CTD's etc). the "comprehensive fix of major CoD problems" has/is not included in this, there are some partially tested and some quick hurried CoD fixes included, but most of that hasnt gone through an orderly in-house testing process (which the gfx engine fixes have by all indications)

my main concern is that the cluster of perpetually negative people here (not you specifically) and the disgruntled and frustrated newcomers swept up in that mindset, are so limited in only spewing out aggressive and rude "negative feedback" , that as a result it will collectively be responsible for missing the boat in getting the many badly needed fixes for CoD included in the final patch. what we should instead be focused on is to present the major bugs and missing features (AI not working etc..) in a way that makes it easier for luthier to deal with and setting priorities in their fixes (dont expect him to wade through long winded threads that are full of bickering and negative jibes, neither expect him to go looking at other websites to get "outside" input. its largely up to the russian and english CoD forum users to provide them with that information in a way that makes it easier for luthier, and at least for our forum it is obvious this does not exist (no idea what the russian forum is like)

Why do you continue to assert that it's somehow the community's fault if CLOD doesn't get fixed or if MG goes under?

The game is bad. They deserve negative feedback.

If the sequel is good, then they will get the positive feedback that they deserve.

It's not the community's responsibility to fix CLOD. That's what the developers get paid for. The fact that we had to set up a "community bugtracker" should be viewed as a huge embarassment for Maddox Games.

[LoBiSoMeM]

Originally Posted by LoBiSoMeM

Boring...

How can i start red fighters?

If all the fanboys here can't explain me how, i'll assume that dev team release a porked patch, sorry to say... No excuses for such flaw don't be adressed BEFORE the release, it's not a "minor" bug, it's a HUGE, GIANT bug!

Simples as that!

I need tho quote myself, because i really want to start the engines of red fighters...

Fanboys, it's possible? Tell me how!

By the way, i love the Su-26 and general performance increase, but we still have particles issues...

[Chivas]

Originally Posted by CaptainDoggles

Chivas, this is not a Beta any longer. It's a "Release Candidate". Release Candidates are not supposed to have serious bugs.

Obviously it is YOU who does not understand the lifecycle of a piece of software.

Unbelievable.....If it were the Release Candidate it would be sent to Steam for download. This is still a beta patch of a possible RC path, sent out to the community for testing.

[Chivas]

Originally Posted by Catseye

Geeze Chivas,
"If you understood the beta process . . . . . "
I really think that you have a reading comprehension issue . . . . or a communication problem wherin you are not able to prepare a sentence or comment without insulting the intelligence of the other posters. You assume so many things about others without facts.

You just don't get it! The beta process is to eliminate problems. If problems are re-introduced, they are caught as a part of the process of evaluation of the changes made before giving it to the testers. You check your work!! It's not up to the testers to check the programmers work!

The startup issue is not just a minimal issue. It is a game-breaker issue! Who the heck was asleep at the wheel on this one?

If you are going to play around with the mixture settings, one would think that someone went through the process of checking to see if the aircraft would start or even fly and that the mixture settings really worked in action.

I'm putting this one to bed. The issues speak for themselves.

When you wake up, asks some friends what beta testing is. Then you might not be so incredulous when you find errors and bugs, while beta testing.

[furbs]

Originally Posted by Chivas

When you wake up, asks some friends what beta testing is. Then you might not be so incredulous when you find errors and bugs, while beta testing.

Chivas, i find most of your posts pretty fair and reasonable, even if a little "rose tinted" but on this issue i think your just being blinkered and stubborn.

Its ok to say the devs made a mistake, they wont cry.

In the process of coding the mixtures and start up procedure, the person making the changes must of a some point said "its done, finished Luthier"

How did they know they had "finished" with out testing the changes he/she made?

You make changes to the start ups but dont try and start the planes yourself in game?

Come on Chivas...

[MadTommy]

Originally Posted by Chivas

Unbelievable.....If it were the Release Candidate it would be sent to Steam for download. This is still a beta patch of a possible RC path, sent out to the community for testing.

Incorrect.. Release Candidate.. is just that a candidate. Not a release version.

Originally Posted by Chivas

When you wake up, asks some friends what beta testing is. Then you might not be so incredulous when you find errors and bugs, while beta testing.

The patch released was released under the title " Friday, September 28 - Patch Release Candidate and Su-26!".

You are just making an assumption to suit your own ends.

Why you feel the need to defend the presence of glaring bugs is not easy to understand. Let the bug be reported and move on.

If you understood software development you would know that development starts, then an alpha build is generated, this progresses to a beta build. In both these stages the developers know bugs will exist. But to a lesser extend in beta than alpha. Then when the developer hopes has has solved all the bugs a RC is released to receive feedback and to catch any bugs that remain. The bugs in a RC are normally hard to find and only located when the software is put out to a very number of users.

I'm sorry but not being able to start a plane in a plane simulator is NOT an bug that should be in a RC or even a beta patch. That is something that should not make it out of alpha stage.

[LoBiSoMeM]

Originally Posted by MadTommy

I'm sorry but not being able to start a plane in a plane simulator is NOT an bug that should be in a RC or even a beta patch. That is something that should not make it out of alpha stage.

+1. It's just that.

Now the fanboys can PLEASE tell me if i can start RAF fighters engines?

[SlipBall]

Originally Posted by furbs

Chivas, i find most of your posts pretty fair and reasonable, even if a little "rose tinted" but on this issue i think your just being blinkered and stubborn.

Its ok to say the devs made a mistake, they wont cry.

In the process of coding the mixtures and start up procedure, the person making the changes must of a some point said "its done, finished Luthier"

How did they know they had "finished" with out testing the changes he/she made?

You make changes to the start ups but dont try and start the planes yourself in game?

Come on Chivas...

I have to agree here there can be but one explanation, the work was not tested.

[Chivas]

Originally Posted by Tree_UK

Then surley if this is the case you would expect all be the most foolish to test that the same old problems haven't been reintroduced before releasing the patch, otherwise we just go round and round in circles like we have been doing for the last 19 months, I'm sorry Chivas but on this I completely disagree with you.

Its your right to disagree, but that doesn't make you right. I don't know why people can't understand the complexity of the task. If the game was "finished" and it was just a matter of fixing bugs it would be an easier task, BUT they are not just fixing bugs, they are also optimizing code, and adding code to further refine features. ANY code change whether its to optimize, fix bugs, or finish features, can cause bugs in related and unrelated ways. The developers obviously sent out another beta patch to the community, not an RC to Steam, to help test and find bugs, why people are incredulous when they do find them is beyond me. Its frankly quite disconcerting, you gotta hope they are just trolling.