![]() |
|
|||||||
| IL-2 Sturmovik: Cliffs of Dover Latest instalment in the acclaimed IL-2 Sturmovik series from award-winning developer Maddox Games. |
![]() |
|
|
Thread Tools | Display Modes |
|
|
|
#1
|
||||
|
||||
|
Testing is optional, if you dont want to be a tester then dont install the patches until they are official.
__________________
|
|
#2
|
|||
|
|||
|
Quote:
We all want the game to be running as good as possible, hence we will all try any patches, especially after waiting for 7 months or so to have severe problems fixed. The track record shows no matter what a patch is call, alpha, beta or official we still are very much still testing. No patch to date has been release without a plethora of issues still being present, ironically enough the alpha patch has been the best yet. which is nice, progress is being made. But that is all rather off topic. I'm surprised there is no test team, as it sounds like there isn't. |
|
#3
|
||||||
|
||||||
|
Quote:
Quote:
Quote:
Quote:
Quote:
Quote:
There are just a few which show they have an internal testing team, even if it is the developers themselves. You can find these yourself if you search posts by blacksix, it took less than 5 minutes. |
|
#4
|
|||
|
|||
|
Actually i'm with Sith on this one. What you say effectively translates to "i want only the final patch".
Sith says "you have the option to not install the intermediate testing patches and wait for the final". It doesn't make any difference whether the alpha is public or not: in both cases you don't install the alpha patch. The fact that you can doesn't mean you have to, if it contradicts your wish not to test it. In fact, the main differences between the two approaches (what we have and what you suggest) are: 1) with the current approach you have an option, with the one you suggest you don't and 2) public testing = more testers = statistically more probable for issues to be encountered = bugs get discovered faster. I really don't see how this is worse than internal testing only. |
|
#5
|
|||
|
|||
|
Quote:
Quote:
Having a volunteer, i.e not paid, team, testing specific changes to the game not only improves efficiency but relieves the developers from this work. The devs & testers share info on a closed forum under a NDA.. this is the kind of setup that I think could only benefit CloD...BS like 'don't download the patch if you don't want to test'.. is well BS. Last edited by MadTommy; 05-15-2012 at 02:08 PM. |
|
#6
|
|||
|
|||
|
Quote:
Quote:
Same way some people don't join the RO2 public beta tests that are happening now. They are not mandatory. Also, its nothing to do with being quoted, it's that the devs have responded to questions over whether they test online, when this was brought to your attention you ignored it saying "I'm surprised there is no test team, as it sounds like there isn't. ". Nothing to do with "forum ego" just you ignoring things that don't suit you, hence why I showed you some quotes from the devs that show there is a "test team". Last edited by GraveyardJimmy; 05-15-2012 at 02:24 PM. |
|
#7
|
|||
|
|||
|
Quote:
Quote:
The open source testing has been amazing for this game. Once the devs decided to collect crash dump data from the community their knowledge base went through the roof - and so did their ability to respond. So it's obvious that providing the patch to everyone who want's to help out, is a good, good thing. So, therefore it's here to stay... No-one is forced to adopt the alphas/ hot fixes. They're not automatic updates, but freely downloadable. There are still servers online running the pre-patch versions. You opt-in to test. And if people are not interested in being part of that testing process, then they need not. |
|
#8
|
||||
|
||||
|
Quote:
BUT we are not before release we are a year into it. I and everyone else here have atleast 60 buck invested in this puppy, so an open Alpha/Beta of the new graphics engine is honestly expected on my part. If they were to do a closed testing session under an NDA the forums would just implode more so than they already have by people wearing tinfoil hats and screaming conspiracy. And lets be honest, most closed Alpha/Beta testing is only moderately successful, when games go full release or full open beta thats when you start seeing the fixes, I think at the point this game is at, and what it needs as much quality info as it can get, open release testing is always going to get you more of that. Maybe before BoM comes out, or before they release playable vehicles a closed testing session should be considered, or they start adding a volunteer testing team from the community that will see releases in the future before general release, but I think they are approaching this current situation in the best possible way right now. Imagine these forums if only a handful of players had seen the recent patch/hotfix? Now imagine the patch/hotfix without the amount of data they have collected because the only had a handful of people testing...
__________________
|
|
#9
|
|||
|
|||
|
Quote:
It's certainly not BS when you've been clearly informed beforehand that it's a test patch and not a final "fix X issue" patch: the purpose is to try things out in the code in order to pick the best solution and some of those things, well, they will not work. And that's how they get to pick the solution, by getting feedback about what doesn't work during testing. It's not something we install to go fly for 10 hours on multiplayer. The fact that many do so without problems is not because that is the purpose of the testing patch, but just a side effect of it working well on their systems. I agree on some of your other points though. Internal testing is good for a simple reason: dedicated testers and focused feedback. Public testing has a harder to evaluate feedback range, but it has the advantage of a larger sample pool. I think having both is the way to go and by the looks of it, that's what we have currently. Also, what Sith said (again). |
|
#10
|
|||
|
|||
|
I meant it BS in regards to the subject of this thread..
Last edited by MadTommy; 05-15-2012 at 03:25 PM. |
![]() |
| Thread Tools | |
| Display Modes | |
|
|