tws71669
16 Feb 04, 21:29
Hi everyone, some of you may have read this in a seperate thread but it bears some repeating here so please take a gander...
Quote:
Originally Posted by tws71669
Scott,
Thanks for all your work in this forum and for really working hard to live up to your own expecations. This is exactly the kind of integrity I wish those big fat money sucking corporations that just dump software out of the abyss should be studying!
It’s really cool that folks are trying to help us out. :D
I think a standardized format would be a good idea. In particular this is the information we really need:
1) Description of the problem.
2) Whether or not the problem can be recreated by loading in the last saved file. If yes, all we need is that file so skip to step 6.
3) The place it occurred in the program execution - the more exact the better (“when giving movement orders” or “turn 1, pulse 2 sighting phase - progress bar about halfway across”).
4) Any text that appears down at the bottom left corner of the main screen.
5) Operating system and graphics card.
6) The last saved files (autosave.ops and lautosave.ops).
As for posting the reports and such in a sticky topic to avoid duplication... that is a very tempting proposition, and I’m sure it would save me time in the short run. But, as nice as that would be - in reality I think I’d actually have to discourage it. The reason is that I’d rather be the one to decide that something is a duplicate rather than having players do it. As complicated as this program is... I guess it’s better to be safe than sorry, even if it is less efficient and means more work for me.
Thanks again, and talk to you soon.
-Scott
__________________
Well, that pretty much speaks for itself.
If everyone would like to follow this advice I think we as the "community" could really help streamline some of the bug hunting process and provide accurate feedback.
So, if you are going to send a bug in with your saved games then it would help Scott and Co. if we followed the above directions.
The payback is that Scott gets a clear idea of what the problem is from the gamer's information and from the savegame too. It's less amorphus and more of an information enhancer. Second, it should get patches out that reflect the needs we are having issues with (I think... I can only speak from guessing.)
Thanks for your time and Mr. Maddox, thanks for the forum here for us to blab-blab on... otherwise this game might well have gone off the radarscope weeks ago.
- Tiberius
;)
Quote:
Originally Posted by tws71669
Scott,
Thanks for all your work in this forum and for really working hard to live up to your own expecations. This is exactly the kind of integrity I wish those big fat money sucking corporations that just dump software out of the abyss should be studying!
It’s really cool that folks are trying to help us out. :D
I think a standardized format would be a good idea. In particular this is the information we really need:
1) Description of the problem.
2) Whether or not the problem can be recreated by loading in the last saved file. If yes, all we need is that file so skip to step 6.
3) The place it occurred in the program execution - the more exact the better (“when giving movement orders” or “turn 1, pulse 2 sighting phase - progress bar about halfway across”).
4) Any text that appears down at the bottom left corner of the main screen.
5) Operating system and graphics card.
6) The last saved files (autosave.ops and lautosave.ops).
As for posting the reports and such in a sticky topic to avoid duplication... that is a very tempting proposition, and I’m sure it would save me time in the short run. But, as nice as that would be - in reality I think I’d actually have to discourage it. The reason is that I’d rather be the one to decide that something is a duplicate rather than having players do it. As complicated as this program is... I guess it’s better to be safe than sorry, even if it is less efficient and means more work for me.
Thanks again, and talk to you soon.
-Scott
__________________
Well, that pretty much speaks for itself.
If everyone would like to follow this advice I think we as the "community" could really help streamline some of the bug hunting process and provide accurate feedback.
So, if you are going to send a bug in with your saved games then it would help Scott and Co. if we followed the above directions.
The payback is that Scott gets a clear idea of what the problem is from the gamer's information and from the savegame too. It's less amorphus and more of an information enhancer. Second, it should get patches out that reflect the needs we are having issues with (I think... I can only speak from guessing.)
Thanks for your time and Mr. Maddox, thanks for the forum here for us to blab-blab on... otherwise this game might well have gone off the radarscope weeks ago.
- Tiberius
;)