All right Segfault fixed (Thanks to 'G')
There seems to be a few bugs in q-gears in it's current inception.
Console output, if there is no OpenGL system etc. that can be used, it should say something like (on the CONSOLE)
"ERROR: No graphics context to open SEE game.log for details'
If the directory setup isn't as expected it should not segfault instead it should say
"ERROR: Directory structure does not match 'q-gears-ffvii' might not be in the right location ."
There should be something in a game.log file regarding the exact error point.
It should report errors if it can't find anything, it shouldn't segfault over those things.
The game.log file is where I found out I need to check GLX is installed for example
This is great, but what if the program doesn't have permission(s) to create game.log?
I'll be working on a few simple sanity checks instilled into the program that should be easy to test.
Critical Errors need (to be honest MUST is more like it) to be reported to the console or in some way to the user, and if active game.log. (I noticed in Linux it's automatic is that the same in windows as well?)
If it can't open a graphic context for visual output, this is a critical error because there is no way to close the program otherwise apart from CTRL-C or nuke it in someway using the OS. These kinds of errors should be reported to the user, so the user has a clue. Game.log should not be relied upon at all for exclusive critical error reporting, because not being able to make the game.log file might be the fault that caused a critical error.
Although not a critical error a missing config.ini should be reported to the user (not in game.log) before continueing running (This could mean other problems).
Perhaps we need to stratify the criticality of reporting?
CRITICAL ERROR: the program should stop running or can't continue running. (IE SDL_SetVideoMode failed: Couldn't find matching GLX visual)
ERROR: the program might be able to continue running inspite of this (missing config.ini etc.)
WARNING: This could be a problem. (IE OGL information is missing or like it current says Warning: data/savemap not found! )
INFO: stuff that it is helpful but not actually the reason for stoping or panicing etc.
on a critical error the program should just stop. I'm not sure why the program segfaults when it's not in the correct directory structure. I'll look into it (I'm sure this will be exciting work ).
Cyb