Temple of The Roguelike Forums
Announcements => Traditional Roguelikes (Turn Based) => Topic started by: chooseusername on March 28, 2014, 08:56:26 PM
-
This is a Windows-only release of binaries for the 0.6.9Y2 release.
Changes:
- Fixed problem with save files not being found. This was because libtcod's pattern matching only handles one asterisk.
Note that Google Breakpad is integrated, which when an error occurs, will dump minidump files. So if either of:
- A red box is displayed saying "Error: ... [E]xit or [C]ontinue?"
- Incursion crashes and exits.
There will be minidump files located in the Incursion-0.6.9Y2 directory. Remember what you were doing at the time, and upload them to bitbucket in whatever issue applies.
Download the Windows binaries here (https://bitbucket.org/rmtew/incursion-roguelike/downloads).
Report problems here (https://bitbucket.org/rmtew/incursion-roguelike/issues?status=new&status=open).
-
I love you man!
-
Julian is the best!
Hooray for him, hooray for Incursion.
This is epic sweet.
-
Julian is the best!
Hooray for him, hooray for Incursion.
This is epic sweet.
It's a game the roguelike scene would be worse for the lack of. Good on him for open sourcing it.
-
Indeed, the future is brighter still for this having happened.
-
What is google breakpad? Spyware?
-
What is google breakpad? Spyware?
Why don't you google it? Or bing it, if you prefer..
-
"An open-source multi-platform crash reporting system"
Well that was clear. Why do anyone needs to report a crash to.. somewhere?
-
Well that was clear. Why do anyone needs to report a crash to.. somewhere?
Well, when an ordinary programmer (i.e. non-Krice) writes a game, it is initially full of bugs and sometimes crashes. Then a player reports the crash to the programmer who then is able to fix the bug. That's how we mortals improve software.
-
Well that was clear. Why do anyone needs to report a crash to.. somewhere?
Well, when an ordinary programmer (i.e. non-Krice) writes a game, it is initially full of bugs and sometimes crashes. Then a player reports the crash to the programmer who then is able to fix the bug. That's how we mortals improve software.
*grins* one of the things I love most in T-Engine is its error logging and reporting capabilities.
-
Then a player reports the crash to the programmer who then is able to fix the bug.
Why do we need google for that?
-
Then a player reports the crash to the programmer who then is able to fix the bug.
Why do we need google for that?
Because Google Breakpad makes a crash log. Before this, Incursion didn't keep logs. Now the programmers have something more to work with than Johnny's story of how the game crashed when he went down the stairs.
-
Why do we need google for that?
I am not sure what you are asking. It's almost like you're being obstinate for the sake of it.
Let me add something to what TheCreator wrote.
When you distribute your binary to someone, you generally distribute the release version. This does not come with debugging symbols, perhaps because you do not want someone to reverse engineer it, and also perhaps because of the smaller file size. Now if one of your users has a crash, they would before systems like Windows minidump and Google Breakpad were around, just post a report saying "when I am in the west hall and I am attacking somewhere in the attack it crashed". The programmer who received this would scratch their head.
However, with a minidump, the release crash metadata is written out. And in the cases where it is supported, sent to a remote server (reported). The programmer can look at this minidump and reconcile it to the debugging information they have for the given progam, and generate a callstack and perhaps even see values of variables. They can see exactly where it crashed, and perhaps even the reason why. I've even worked at a company where these dumps are automatically associated with an issue in the company's issue tracking system, and you don't even need to process them, the call stacks and debugging information are automatically added to the given issue and duplicates removed. So by the time you might get a reported issue, it might have a huge amount of automatically generated hugely useful information to help track down the cause.
The benefits are less if a scripting language is used. In that case you'd really need a custom system that extracted and appended scripting language frames into the callstack to show more than just virtual machine operation.
-
Why do we need google for that?
I don't know, never used it. But I might want to take a look, because the crash dump utility from Microsoft I've been using so far sucks.
-
Why do we need google for that?
I don't know, never used it. But I might want to take a look, because the crash dump utility from Microsoft I've been using so far sucks.
Crashpad uses Microsoft's minidump format as it's standard cross platform format, I believe. Maybe it might have better tools, but I've not had any dumps submitted yet.
-
Crashpad uses Microsoft's minidump format as it's standard cross platform format, I believe. Maybe it might have better tools, but I've not had any dumps submitted yet.
Microsoft's system is not totally bad, it's just not very comfortable for everyday use. You need to copy your symbol files from the original build and store it somewhere. Then, as you receive a dump, you need to copy it into the directory where the symbol files went (along with the original source code). Now if Google Breakpad automatizes this process just a little bit, it would already be a great improvement over the old system.
I have received several crash dumps from various people so far, but that never actually worked for me, so now I ask people to send me their saved games instead. Saved games always load smoothly for me, and if they don't, I can fix it in a minute. And they don't require any f***ing symbol files. However saved games not always allow you to find the bug. Sometimes you just can reproduce the crash with the steps provided by the reporting player, or you don't receive any reproduction steps at all. So crash dumps would be a great complement (if they really worked).
-
Maybe it might have better tools, but I've not had any dumps submitted yet.
Ugh. I had 3 crash logs a few days back, but it slipped my mind to upload them. And by now I can't remember what the circumstances were. I won't let future crashes pass me by!
-
Is there a way to play in fullscreen? I seem to remember the last official version having fullscreen. Can't seem to get it to run fullscreen on this one though.
-
Is there a way to play in fullscreen? I seem to remember the last official version having fullscreen. Can't seem to get it to run fullscreen on this one though.
There should be such an option in Options, duh, and if it doesn't work you can notify rmtew about it :) I never used it, so I don't know if it worked in 0.6.9I or not.
-
Is there a way to play in fullscreen? I seem to remember the last official version having fullscreen. Can't seem to get it to run fullscreen on this one though.
ALT+ENTER. However, in the current version there is a workaround which will prevent it working.
-
Is there a way to play in fullscreen? I seem to remember the last official version having fullscreen. Can't seem to get it to run fullscreen on this one though.
ALT+ENTER. However, in the current version there is a workaround which will prevent it working.
So it should hopefully work again in the future?
-
ALT+ENTER. However, in the current version there is a workaround which will prevent it working.
So it should hopefully work again in the future?
Definitely, but it's a matter of not having the correct support for it and scheduling. So whether it's next week, or a year from now, is yet to be determined. I've already spent several hours on it, and got nowhere special.