appears that the 1.0.7 and .8 both have this issue of not restoring the videomode once done.

Also, Changing from fullscreen to window ingame causes the game to crash.

spider@Darkmere> ./vendetta ~/.vendetta
X Error of failed request: BadValue (integer parameter out of range for operation)
Major opcode of failed request: 135 (XFree86-VidModeExtension)
Minor opcode of failed request: 10 (XF86VidModeSwitchToMode)
Value in failed request: 0x2800002
Serial number of failed request: 378
Current serial number in output stream: 379
./vendetta 1167.46s user 1567.19s system 94% cpu 48:27.16 total

Have either of these been addressed? I still have both of these problems.

Mmm, i don't play games in my workstation X session, what i do is create another X session (i'll call it gaming X) running on DISPLAY :1.0 , then i setup a xterm in my workstation X session to execute display on the gaming X session:

1.) Goto console, log in as your normal user
2.) Execute command: X :1.0
3.) Go back to your normal X session
4.) Open an xterm
5.) Execute command: export DISPLAY=:1.0
6.) Check display via: echo $DISPLAY
7.) Execute/run vendetta binary from xterm

If Vendetta doesn't restore the video mode when you exit, it doesn't matter since it doesn't mess with your normal X session, you can just close of your Gaming X session when you're done.

I started doing this when i would get crashes from games like ut2k4, this way i don't have to start X again and all my normal apps, if X crashes it only crashes your Gaming X session.

evilvar, thanks for your response. That is pretty handy. I knew it was possible to make multiple sessions, but wasn't sure how to do it until now.

After messing around with it a little bit, I've gotten it to work, but not without a few quirks. If I try to run the vendetta executable from my :0 display, it crashes with this error:

X Error of failed request: BadValue (integer parameter out of range for operation)
Major opcode of failed request: 135 (XFree86-VidModeExtension)
Minor opcode of failed request: 10 (XF86VidModeSwitchToMode)
Value in failed request: 0x200002
Serial number of failed request: 39
Current serial number in output stream: 41

But if I run update.rlb or xterm on :1, and launch vendetta from that it opens fine. There is a minor annoyance with this, however, because I can see the mouse cursor in the game, represented as a greenish dot.

The funny thing is on display :1 it seems to reset the resolution correctly when vendetta exits, and also the game no longer crashes when going into window mode. I also noticed that toggling window mode seems to fix that cursor problem as well.

maybe the problem is not in vendetta

maybe the problem is in linux

What???

Everyone knows Linux is a perfect OS, and has no problems :)

"maybe the problem is not in vendetta
maybe the problem is in linux"

There's always one in the crowd isn't there. Unless you have something constructive top say, i'd suggest you take your trolling elsewhere.

At any rate, I thought I'd post some specs about my system. Perhaps others could also post experiences if they have also seen/delt with something like this.

Gentoo w/ gentoo-dev-kernel 2.6.7-r14
XFree86 ver. 4.3.0-r6
Geforce 2 GTS
nvidia kernel and glx drivers 1.0.6629
I'm also running Gnome 2.6 incase that makes any difference. At some point I'll be switching to Xorg, but I don't feel like breaking my system atm.

Ananzi, as you are admittedly anti-linux it would be appreciated if you didnt post on the linux forum.

Well, I actually kinda agree with Ananzi in that Linux OpenGL drivers are not as stable as they are on the other OSes.
Some X servers, especially ones from nvidia tend to have issues as well.
But everything else about linus seems fine (well except the poor support of joysticks, and very crude audio drivers).