Search the Community
Showing results for tags 'bug reports'.
Found 3 results
-
I'd like to suggest two small changes that should make it easier to provide save games, as those as often asked for when reporting bugs. - Make it possible to turn off Ironman even for Insane. Especially now that the experimental patch makes the previous Veteran to be Insane. E.g. I myself play Ironman style even though I have that checkbox turned off, and this would help also with cases where somebody loses the whole game because the game crashes. It's ok if this is enforced for the final release, but I don't quite see the point now. - Make the game autosave more often. There are many cases where the save needs to be done before a problem occurs, but that's hard to do without a crystal ball. It would be useful if the game had additional autosave slots for right before ending turn in ground combat, right before entering air combat, and possibly more (right before starting ground combat, right before research is finished, etc. - I guess Matthew could have a good idea what saves he asks most often for). Saving, at least for me, is just a short moment, so I wouldn't even really notice. If it's not so for some people, this would be at least useful as a debugging option in gameconfig.xml .
-
Greetings! I've just gotten involved into this awesome game, and since this is, after all, a beta, I'd like to help any way I can! Do we have a bug tracker, a master list, or something similar? So far the game did look substantially light on bugs and crashes, but it would still help to keep a track of all the known issues.
-
I think I can safely say for everyone who has pre-ordered this game, we all want this game as bug free as possible on release. And, I suspect most of us want this game bug free like now. Having done some research into how professionals go about writing bug reports and how developers like bug reports, it seems that there are styles and forms of writing which make finding bugs in the code easier for a developer. The easier it is for a developer to find a bug, the easier it is to squash it. Now, not being a professional QA or tester (any professional QAs/testers among us other than Matthew?) what I thought I'd do is post some links to sites which talk about writing up bug reports so that those among us who write bug reports can have a look and see if they can use any of the advice and guidance in writing their own bug reports. Here we go! An essay on writing bug reports in general. Can get philsophical, not all of it useful. Very detailled, most of it useful for here, but quite formal. Too formal, perhaps? This is from writing bug reports for World of Warcraft, but you can take a lot from it to apply here. An example taken from generic software bug writeups.
