An Open Question to HTC-

[hitech]

With ut most respect possible for the work you guys do Id like to ask you a question. Why does it take so long to fix apparently simple bugs? (I realize that some arent so simple and its not so easy.) It seems to me fixing a gauge or damage bug shouldnt be too difficult. Or the things like the CoG issue with the mossi and Me-163's incorrect fuel burn rate?

First what many people post are bugs are not.
2nd what you may think is an easy fix may or may not be, it could be a simple change to a model, but it can also be a systemic problem in which case it can be a huge thing to fix.

3rd on every release we go threw every bug reported in the bug forum and address them. If they are a straight forward fix we address them.

If they are not a straight forward fix, but important we fix them.

Once we are finished with a release cycle, I.E. all patches released, many times we freeze the code because things become incompatable once major surgery begins, so it is almost impossible to do bug fixes until the new version is ready.

Your example with the 163 was not a simple fix, and 2 it really has very little impact on things. ( if my memory is correct, pyro and I did fix this one for the next release) The mossie falls under that same category of not a simple fix, and  in the overall sceam of game play , is not very important.

HiTech

[Shuffler]

On the flip side M$ has a lot more code in windows and other software. Percentage wise they may be closer than you think. The last perfect man has not walked this earth in some time.

[Strip]

First what many people post are bugs are not.
2nd what you may think is an easy fix may or may not be, it could be a simple change to a model, but it can also be a systemic problem in which case it can be a huge thing to fix.

3rd on every release we go threw every bug reported in the bug forum and address them. If they are a straight forward fix we address them.

If they are not a straight forward fix, but important we fix them.

Once we are finished with a release cycle, I.E. all patches released, many times we freeze the code because things become incompatable once major surgery begins, so it is almost impossible to do bug fixes until the new version is ready.

Your example with the 163 was not a simple fix, and 2 it really has very little impact on things. ( if my memory is correct, pyro and I did fix this one for the next release) The mossie falls under that same category of not a simple fix, and  in the overall sceam of game play , is not very important.

HiTech

Thanks for the reply....

<S> Strip

[SkyRock]

The last perfect man has not walked this earth in some time.

I walked this morning.....does that not count?

[LLogann]

Give me lip but thank him for saying the same thing?  Good Job. 

Thanks for the reply....

<S> Strip

[CountD90]

Your example with the 163 was not a simple fix, and 2 it really has very little impact on things. ( if my memory is correct, pyro and I did fix this one for the next release)

HiTech

YES!!!!! ITS AN UPDATE FROM THE NEXT PATCH!!!!!!!!! lol

On a serious note, keep up the great work HTC. Best game to play pretend luftweenie

[SlapShot]

SlapShot: I once hired a programmer who claimed to want to do optimization in assembler. I knew I was in trouble when I saw he was a slow 2 finger typer.

I once hired a color blind artist. He actually did good work.


HiTech

Assembler ... you should have asked him to code it up on "coding sheets" first ... then if he asked "what are coding sheets ?" ... ya reach out and slap him.

[Superfly]

My 2 cents to HT's last reply:

Sometimes when you fix one thing, you end up breaking three other things, which can sometimes have a snowball effect.  It is a rare occurance, but this is just another example of how something that seems easy to fix, in reality, can turn out to be very difficult.

Sometimes you have to nuke all your previous days or months worth of work, because it was a dead end.   That really sucks when it happens!  Thankfully, such cases a rare, and you learn a lot from your mistakes.

[68Raptor]

Sometimes you have to nuke all your previous days or months worth of work, because it was a dead end.   That really sucks when it happens!  Thankfully, such cases a rare, and you learn a lot from your mistakes.

Like not letting Sudz order carpaccio? That kind of learning 

[SlapShot]

<--- Loves carpaccio

[Mustaine]

<--- Loves carpaccio

looks good, but I don't know if it is better than cannibal sandwiches

http://www.onmilwaukee.com/dining/articles/yumyuck.html

(bottom of the article, I can't find a better reference)

It is delicious, and only a few butchers in Milw will sell it to you. the beef has to be prepared a certain way, and the salt and pepper mixed in shortly before sale / use.

[Shuffler]

looks good, but I don't know if it is better than cannibal sandwiches

http://www.onmilwaukee.com/dining/articles/yumyuck.html

(bottom of the article, I can't find a better reference)

It is delicious, and only a few butchers in Milw will sell it to you. the beef has to be prepared a certain way, and the salt and pepper mixed in shortly before sale / use.

Has ecoli written all over it. I was in the meat business for 20 years...... that is highly dangerous.

[4deck]

I just poked my head in. Good thread. 

Eitherway, best game by far Ive ever played.  Im 41 so been around gaming since pong.

[SKJohn]

My 2 cents to HT's last reply:

Sometimes when you fix one thing, you end up breaking three other things, which can sometimes have a snowball effect.  It is a rare occurance, but this is just another example of how something that seems easy to fix, in reality, can turn out to be very difficult.

Sometimes you have to nuke all your previous days or months worth of work, because it was a dead end.   That really sucks when it happens!  Thankfully, such cases a rare, and you learn a lot from your mistakes.

He used the "n" word - the B-29 is on it's way!