Posted June 07, 2015
The following may be a rant following installing patch 1.05 and discovering new crap went wrong.
I had great expectations for this game.
Don't get me wrong, this is a beautifully rendered game. It's yet another testament of how far real time rendering has progressed over the last two decades.
I preordered this game over 6 months ago. By principle, I normally do not preorder games because I see it as yet another money grubbing attempt by marketing executive.
I did preorder THe Witcher 3 because:
A) I really liked the first two games.
B) I like gog.com's promise to gamers about DRM free games.
C) I expected it to come out in February, which was only a 3 month wait time when I bought it.
As to point C, the release date was delayed 3 more month. http://linuxgamenews.com/post/104701463250/the-witcher-3-release-delayed-until-may-2015. That article claims that CDPR sent an open letter to the fans. I apparently wasn't on the recipients list..
The release date was delayed to allow more bug fixes. Which kind of makes me wonder, what the fuck really happened there? Patch after patch fix some issues but create several more.
TO THE DEVS, I say:
I know that software development is a complex business but I also know that for many problems solutions already exist. The witcher 2 was a fine engine. I can only assume that you used that as your base for the witcher 3. Why so many regressions then?
If you are using Agile development method to manage the project, STOP THAT RIGHT NOW. Agile works for code that can be implemented in small increments and not even then sometimes. Timeboxing is a horrible side effect of wanting to do Agile right. Any large project where subsystems have to interact a lot only suffers more and more tech dept as the sprints go by. If you're not using Agile, either carry on or fall back and regroup and rethink your strategy moving foward.
Try to automate your debugging? Unit testing of sorts. The story tree (quest/dialogues descision trees) and NPC and PC interactions could be sandboxed, i.e run independently of the whole game. Test the expected outcome against the actual outcome, state of the tree, position (x,y,z coords) and state of various entities at each states, etc. There's probably a few hundred quests, a few thousand NPCs and interactables at most. It seems like a large number but perhaps one of you clever lads can figure out how to programmatically generate testing scenarios and reports on the outcomes. Sure there may be millions of scenarios, but it would cost less to have a computer run overnight to generate and test the scenarios than have humans trying to figure out what's wrong. Even if the automated tests detects 50% of remaining bugs, it means you know 50% of what you have remaining to do. Algorithms can always be perfected and you can gradually move towards better bug detection.
Allow the game to load loose files instead of reading the bundle/cache files et al. Modders can help you fix bugs you don't have the resources to reproduce.
Perhaps, open up a bug tracker of sorts to the public? It will reduce the number of duplicate reports, probably help manage what must be the sheer numbers of complaints coming in and very probably allow the community to help out.
Perhaps we should all submit out bug reports through the support system:
http://www.gog.com/support/contact/technical_issues_with_games/the_witcher_3_wild_hunt_preorder
then maybe our grievances will get to the right people faster.
I had great expectations for this game.
Don't get me wrong, this is a beautifully rendered game. It's yet another testament of how far real time rendering has progressed over the last two decades.
I preordered this game over 6 months ago. By principle, I normally do not preorder games because I see it as yet another money grubbing attempt by marketing executive.
I did preorder THe Witcher 3 because:
A) I really liked the first two games.
B) I like gog.com's promise to gamers about DRM free games.
C) I expected it to come out in February, which was only a 3 month wait time when I bought it.
As to point C, the release date was delayed 3 more month. http://linuxgamenews.com/post/104701463250/the-witcher-3-release-delayed-until-may-2015. That article claims that CDPR sent an open letter to the fans. I apparently wasn't on the recipients list..
The release date was delayed to allow more bug fixes. Which kind of makes me wonder, what the fuck really happened there? Patch after patch fix some issues but create several more.
TO THE DEVS, I say:
I know that software development is a complex business but I also know that for many problems solutions already exist. The witcher 2 was a fine engine. I can only assume that you used that as your base for the witcher 3. Why so many regressions then?
If you are using Agile development method to manage the project, STOP THAT RIGHT NOW. Agile works for code that can be implemented in small increments and not even then sometimes. Timeboxing is a horrible side effect of wanting to do Agile right. Any large project where subsystems have to interact a lot only suffers more and more tech dept as the sprints go by. If you're not using Agile, either carry on or fall back and regroup and rethink your strategy moving foward.
Try to automate your debugging? Unit testing of sorts. The story tree (quest/dialogues descision trees) and NPC and PC interactions could be sandboxed, i.e run independently of the whole game. Test the expected outcome against the actual outcome, state of the tree, position (x,y,z coords) and state of various entities at each states, etc. There's probably a few hundred quests, a few thousand NPCs and interactables at most. It seems like a large number but perhaps one of you clever lads can figure out how to programmatically generate testing scenarios and reports on the outcomes. Sure there may be millions of scenarios, but it would cost less to have a computer run overnight to generate and test the scenarios than have humans trying to figure out what's wrong. Even if the automated tests detects 50% of remaining bugs, it means you know 50% of what you have remaining to do. Algorithms can always be perfected and you can gradually move towards better bug detection.
Allow the game to load loose files instead of reading the bundle/cache files et al. Modders can help you fix bugs you don't have the resources to reproduce.
Perhaps, open up a bug tracker of sorts to the public? It will reduce the number of duplicate reports, probably help manage what must be the sheer numbers of complaints coming in and very probably allow the community to help out.
Perhaps we should all submit out bug reports through the support system:
http://www.gog.com/support/contact/technical_issues_with_games/the_witcher_3_wild_hunt_preorder
then maybe our grievances will get to the right people faster.