I totally agree, but this game wont be finished for another month or so, so hopefully by that time, Geforce’s are out! :o
LWJGL gives tons of display mode debugging if you but ask it to…
Cas 
[quote]LWJGL gives tons of display mode debugging if you but ask it to…
Cas
[/quote]
Wonderful. In which, case it definitely needs a higher-level API on top of it, because I’ve never seen an LWJGL game which gives an error message any more verbose than “couldn’t select screenmode”.
Which, as noted above, is entirely useless. You might as well not have any text at all, and just display the “error” icon! (many games don’t seem to say anything much beyond “invalid” or “failed” :()
EDIT: and JOGL games don’t seem to be any better ?
Typical amateur (hah! professional too) code looks like this:
try {
Display.setDisplayMode(someModeIJustPickedFromThinAir);
} catch (Exception e) {
// ignore
}
Except without the // ignore comment.
There is actually an org.lwjgl.util.Display class that lets you filter, match, and sort display modes and then tries everything it can until it gets one that works before it throws its hands in the air and raises an exception.
Personally I am 100% against allowing the user to select a display mode from a game. Ever.
Cas
So, you’re saying it’s just an education problem? …time to get the LWJGL doc projects going? 
I too believe it should be unnecessary, although I haven’t tried it enough in recent years to have your conviction that it truly isn’t ever necessary.
[quote]EDIT: and JOGL games don’t seem to be any better ?
[/quote]
Actually this is one of the areas in which Jogl fails badly in. LWJGL (as above) raises an exception right when you try creating a display, giving you an option to try something else instead of giving up. Jogl on the other hand continues just fine on creation, only to give you a rather cryptic “context could not be made current” when you actually get round to drawing anything. Made even further complicated by the fact that the same error gets kicked off for practically any Jogl error. :S
End result being that although LWJGL display creation is tricky, it can be much more robust than the current Jogl create-and-pray method. >:(
[quote][…]
Personally I am 100% against allowing the user to select a display mode from a game. Ever.
[…]
[/quote]
Ye… I wish there won’t be TFTs :-/
Maybe I should just stay with a fixed 800x600 resolution? I don’t know.
More and more I’m inclined to either insist one a particular resolution - 8x6 is good - or use the user’s desktop resolution without changing the display mode.
Cas
right, enough of the hijacking of my thread and back to the original subject ;D
We got “Infiltration XVII”, any more? Keep em coming in.
Invade a Furrin Country And Murder Them While They Sleep?
j/k!
Cas
[quote]Invade a Furrin Country And Murder Them While They Sleep?
[/quote]
Hmmm. Didn’t they already make one called “America’s Army?” 
“Covert stealth infiltration hideyness XVII”
“Easy in/easy out”
“Subtle for crude”
“America’s Irony”
“Bob’s your uncle” (this last one involves a character named bob being the uncle of the protagonist- this could be integrated with the plot in some way or left as a mystery)
Sorry, I’m not helping much am I? It’s been a long week…
Mission XVII
Death Squad XVII
Death Squad Mission XVII
XVII Pounds of Death
XVII Ways To Die
XVII < XVIII
XVII Miles To Go
XVII Guns In The Sand
XVII Types Of Sand to Jack Up My Treads
I love XVII < XVIII ;D, dudes, now seriously, all that brain power and not a single linguist?
Ive thought of a couple myself, so we have now:
“Infiltration XVII”
“Serious XVII”
“Big XVII”
Intrepid 17? Liberation? Fire Team 17? “Battle Tactics”?
Kev
kev, youve dont it again. Intrepid XVII it is then! ;D
I like it very much!
…what brain power???
Cas
oh blah^3, the new version is up for you to mess around with the properties.cfg file.
If anything works, can you please tell me the configuration.
DP