Update Preferences

[NormKoger]

Hey guys,

I am still a bit busy, testing and responding to problem reports, so it will be a few days before I can get back to regular participation here. But I am curious about something, and would like a bit of guidance.

We have two realistic update release options: update as things are fixed or improved, or update only when all reported issues have been resolved. It has been brought to my attention that some users would very much prefer that we not provide auto-updates to the game until all reported issues have been resolved, rather than our recent practice of providing updates as some, but not all, fixes and improvements have been implemented.

So here's the question: Do you want us to continue the current practice of updating when we feel we have substantial improvements to offer, or should we hold the updates until they address all reports and have been through a thorough test program?

[Neutrino 123]

I'm surprised that this is even a consideration. Definitely release updates as they become avalible. Updates are optional, and even a small update might fix all problems a given individual is experiancing.
The only drawback to regular updates is that people experiancing regular crashes need to 'test' the updates to see if their problem is fixed, but surely this could be dealt with easily by including an update log.

[Roberts]

I'm surprised that this is even a consideration. Definitely release updates as they become avalible. Updates are optional, and even a small update might fix all problems a given individual is experiancing.
The only drawback to regular updates is that people experiancing regular crashes need to 'test' the updates to see if their problem is fixed, but surely this could be dealt with easily by including an update log.

I haven't seen any substantial problems yet, but keep updating as updates are available.

[cwmark]

The current system seems to work for me - the showstopper bugs are fixed ASAP.

Speaking of bugs - since the 3rd patch - As the Russians, I'm experiencing the disappearing fleets on the Campaign maps after successfully disengaging from the Japanese.

Also a (new to me) bug has shown up in the Port Arthur surprise attack map during the campaign. Atempting to change targeting status to Free on the Russian frontline cruisers facing the Japanese DDs cause a black screen lockup. This appears to happen very reliably - even with fresh campaigns.

BTW thanks Norm for helping get me back into DG once again!

[Mowers]

That some of the bugs are show stoppers require quick fixs otherwise its going to hurt you in sales.

I therefore suggest quick fixes for show stopping issues.

[Porkchop]

I say keep 'em coming. That way we're helping you to help us. If there's any problems with the updates we can let you know as we all move forward.

[Rhetor]

I am for more updates ASAP than one big update once in a long while.

[Grouchy]

Since with the current builds I'm stumbling on bugs that are show stopper for me (CTD's and blackscreens/hardlocks), I'm hoping you continue with the current practice of updating as soon as some bug is squashed.

And if possible add a changelog/readme in each update.

[Spharv2]

Update as you go. The more problems that you can fix soon, the more people will be able to get into the game that much faster. Seems pretty simple to me. I can understand people not wanting to introduce something that might break things, but for those people, just don't update until you see the forum response. Seems like the current system already gives us the choice on method.

[Bullethead]

So here's the question: Do you want us to continue the current practice of updating when we feel we have substantial improvements to offer, or should we hold the updates until they address all reports and have been through a thorough test program?

I like the current system of frequent, relatively small patches. My only wish is that:

1. You make a subfolder for announcements of updates
2. In these announcements, you say what got fixed and how big the download is.
3. You include a readme(version#).txt file in the updates so those who miss the above announcements can still get the important info.

Hopefully, doing these things will make cut down on redundant reporting of problems, making it easier for you to focus on outstanding issues. Also, if something was supposed to have been fixed and somebody still has the problem, they'd know to report it ASAP.

Also, at some point, I'm sure someday we'll have to have a HUGE update download (revised 3D shapes, etc.). When that happens, I'd REALLY like to know in advance so I can hold off updating until I get to a place with broadband.

[Jim Cobb]

As a reviewer, I'd like bigger, less frequent updates so I know what I'm writing about before the ground shifts under me. As a gamer, the quicker the better.

[mbv]

Another supporter for the current system of updating here. I know that effectively turns us into testers for the game each time an update comes out, but I would rather be able to get back into the campaign ASAP rather than waiting for one big release which could be weeks or months down the line.

[PJJ]

Just keep 'em coming. The quicker you crush bugs (and possibly add new features), the better.

[scl]

Trickle updates are good for me too. It's quick and painless. It's got my vote! :D

Cheers
Ken

[KGB]

Hey guys,

I am still a bit busy, testing and responding to problem reports, so it will be a few days before I can get back to regular participation here. But I am curious about something, and would like a bit of guidance.

We have two realistic update release options: update as things are fixed or improved, or update only when all reported issues have been resolved. It has been brought to my attention that some users would very much prefer that we not provide auto-updates to the game until all reported issues have been resolved, rather than our recent practice of providing updates as some, but not all, fixes and improvements have been implemented.

So here's the question: Do you want us to continue the current practice of updating when we feel we have substantial improvements to offer, or should we hold the updates until they address all reports and have been through a thorough test program?
The problem is that if u implement some changes this can cause some new bugs as well. But implementing one thing after another is easier way (at least it seems so for me, QA engineer) to test and found bugs. So u can make regression type of tests without differentional testing. The less new strings of code u implement - the lesser will be the probability of causing new bugs. And lets not forget about older bugs, which are in some cases left as is.

[pad152]

Patching Issues.

So far in the two updates released, there has been no release notes, telling the user what issues are addressed by the patch, any changes to game play or any new features added.

Is there a check to verify both players in multiplayer are running the same version?

[Daedalus]

I am just now getting the money together to buy the full version, and I am still playing with the demo.but I vote to keep releasing the patches as you get them done. I think that will keep all working better than having to wait for who knows how long, and you may have a issue that will not let you play till the fix is out. so I say keep em comming.

And I do not mean to sound like it is or would be taking a long time for the patches.
I think you are doing great and the game is awesome.

So far the demo is working great, I have not seen the weird graphic block over the last ship in the line on the russian side sense I lowerd the Res back down to 1024x768.

I will try the others when I can get the full version.

[vertical]

I vote to release updates no matter how big or small.

vertical

[Percopius]

...in the 'update availible' dialog that pops up, that the patch is a 'beta' or whatever you what to call it. Every so often, either depending on an amount of bugs fixed or once a time period, make an 'release' patch that is the current version tested with official stamp of QA aproval.

[saddletank]

Updates and fixes on the fly please, any alternative is a no-brainer.

[philbill]

Small patches as and when they are ready gets my vote.
Phil

[BigBog]

but add a readme so we know what has been addressed... helps us provide feedback to you!

Regards,
BigBog

[AlfredR]

update when available

[jethro]

Keep them coming... with readme, please.

Best
J