Xytanx: that won't work AFAIK, because there won't be a screen-instance (read: windowmanager) the application can attach itself too - from where it would spawn the SDL/OpenGL window.
And again: it can't really be your graphics at fault either, since you say sauerbraten runs fine - AssaultCube uses the graphics basically in the same way, just much less so, as Sauerbraten does.
Your issue must be some place else.
I know you posted the "couldn't find matching GLX visuals" bit on your first post - but giving us the full output of your startup-log (use a pastebin) could possibly show up other (read: the real) problem.
Have you also tried removing your init.cfg from inside ~/.assaultcube_v1.1/config and running with added "-t" parameter (no quotes) to the assaultcube.sh !?!
A couple of "total shot in the dark" things here:
Assuming "lsmod" exists on Fedora; what I mean to ask is: is the propietary nvidia driver actually loaded. Usually (unless the X config includes the logo-hiding option) you should see an NVidia logo when X starts.
Also, you're absolutely sure you're not trying to start the game as some other user?!
Because the only times your system - it's not AC that's giving out that message! - complains about not being able to find matching visuals is when the user calling an non-CLI-but-X application hasn't got a matching X session running (see above). This either means the driver doesn't support it (but earlier checks in this thread lead me to believe you're fine there) or simply because it's not the user logged into the X-Session .. but that would require you doing extra stuff which I'd be wondering why you would .. but hey, funnier stuff has been known to happen.
As a final thought - you might be victim of the dreaded libjpeg.so.8 bug, which is addressed around the 2nd code block in the first 1.1-release-thread.
And again: it can't really be your graphics at fault either, since you say sauerbraten runs fine - AssaultCube uses the graphics basically in the same way, just much less so, as Sauerbraten does.
Your issue must be some place else.
I know you posted the "couldn't find matching GLX visuals" bit on your first post - but giving us the full output of your startup-log (use a pastebin) could possibly show up other (read: the real) problem.
Have you also tried removing your init.cfg from inside ~/.assaultcube_v1.1/config and running with added "-t" parameter (no quotes) to the assaultcube.sh !?!
A couple of "total shot in the dark" things here:
[SELECT ALL] Code:
lsmod |grep nvidiaAlso, you're absolutely sure you're not trying to start the game as some other user?!
Because the only times your system - it's not AC that's giving out that message! - complains about not being able to find matching visuals is when the user calling an non-CLI-but-X application hasn't got a matching X session running (see above). This either means the driver doesn't support it (but earlier checks in this thread lead me to believe you're fine there) or simply because it's not the user logged into the X-Session .. but that would require you doing extra stuff which I'd be wondering why you would .. but hey, funnier stuff has been known to happen.
As a final thought - you might be victim of the dreaded libjpeg.so.8 bug, which is addressed around the 2nd code block in the first 1.1-release-thread.