I consider them useless. I do stuff in a way it will not crash, it would try to recover from any error internally. Thus they are mostly useless in my case. I would need to create few internal testing stuff, which would write reasonable information about what internally happened, stack dump is mostly useless. In fact a lot of stuff where stack dump might be of some value should be caught in QA, thus companies that are doing QA don't need these reporters.How do game companies feel about crash reporters?
There is an additional problem of user data and privacy laws. A working crash reporter need info about user's computer, which is of course a major problem.They seem extremely useful for QA and continued support. I really don't understand why this technology hasn't spread like a STD.
Actually, releasing debug builds is illegal in most cases.
MoM is not a good game...
MoM is not a good game...
Yet it's still the best fantasy 4X (or strategy game at all). None have come even close.MoM isnt a good game in the sense that its not balanced or fair, not made for MP and random factor is very strong in it. But its a FUN game like most oldschoool games.
Good old times when no one bothered with things like accessibility or balance...
Yet it's still the best fantasy 4X (or strategy game at all). None have come even close.MoM isnt a good game in the sense that its not balanced or fair, not made for MP and random factor is very strong in it. But its a FUN game like most oldschoool games.
Good old times when no one bothered with things like accessibility or balance...
Quis custodiet ipsos custodes? I'm with you 100% that good code is aware of, and directly addresses, most of its own issues - be that by on-the-spot validation / adjustment, or silently giving up and proceeding. It's a dying art which, like other "you either can do this or can't" aspects of software development, is severely downplayed in education... usually in favor of syntax, algorithm nicknames, and in the worst cases, 2nd-grade math homework that happens to be in binary.I do stuff in a way it will not crash, it would try to recover from any error internally.
All Visual Studio projects require ultra-privatized Microsoft intellectual property, whether they use formal debugging or not... but that's why they've always bundled it into those neat little redistributables and encouraged you to include them with your installer. MS's developer policies and licensing have always been loose as beer-shits.By releasing a debug build you are releasing something that contains code from another party (Microsoft if you use visual c++, etc), specifically the debug module.
Oh look, another person taking a dump on GalCiv, how difficult. Maybe you already knew there is only 1 race to choose in Galciv? Kinda hard to say imbalance is fun when you only play as 1 race. You play as humans and that's what the game is, it's not attempting to be MOO4 or make you feel like a kid in a candy shop, it's GalCiv. Oh and the enemy races actually do act very differently, each has a very different personality and once they become a blob all pose challenges in different ways. GalCiv1 is one of the best 4x I ever played, you just have to accept it for what it is.While the Stardock games (Elemental and GalCiv) which are trying to be super balanced lack soul and just aren't much fun to play.
Oh look, another person taking a dump on GalCiv, how difficult. Maybe you already knew there is only 1 race to choose in Galciv? Kinda hard to say imbalance is fun when you only play as 1 race. You play as humans and that's what the game is, it's not attempting to be MOO4 or make you feel like a kid in a candy shop, it's GalCiv. Oh and the enemy races actually do act very differently, each has a very different personality and once they become a blob all pose challenges in different ways. GalCiv1 is one of the best 4x I ever played, you just have to accept it for what it is.