Ummm... Yeah... Basically, I've been having my controls lock up ingame every couple minutes or so. It doesn't seem to happen in any other games, and it appears to be at random (but frequent) intervals. I've tried updating my laptop's drivers, and it hasn't done anything... I've been having the bug since 3.3 or so, but it hasn't been anywhere near this bad.

IBM ThinkPad T40
1.5 GHz Pentium M
512 MB DDR-SDRAM
40 GB HD
32 MB ATI Radeon 7500 Mobility
Windows XP Professional

Is it where you would slide around out of control for any length of time between a couple hundred milliseconds and two or three seconds?

Yeah, that's probably it... What causes it, though? Lag? I'm on 768/128 ADSL...

No, it seems to be caused by Vendetta unknowingly rendering several frames ahead of time. Usually the drivers prevent this. I was able to fix it by limiting the number of queued blits in RivaTuner, but I don't think that will work for ATI cards. I bet if you switched to OpenGL mode it wouldn't do that, but that is obviously not an ideal solution.

Yeah, make sure you have the latest ATI Catalyst drivers installed.

I updated them from the IBM updates site last night, and it didn't seem to do anything...

Edit: Hmmm... a1k0n, I'll try running it in OpenGL tonight. I'll compare FPS at the loading screen, and let you know what the results are.

Edit (2): Wow... Loading screen has 60 FPS for DirectX, 260 for OpenGL. Is OpenGL cutting anything out?

Oh, you obviously have vsync enabled in DirectX. Try turning that off, perhaps.

Oh yeah, vsync... Forgot about that... Actually, I tried playing with it last night, and I had problems no matter what...

Yeah, 310 FPS in DirectX with vsync off.

Here's my config.ini, by the way...

[directx8]
windowmode=0
vsyncoff=0
gamma=8
triplebuffer=0
mipmapfiltering=2
texturefiltering=1
envmap=1
bumpmap=1
specular=1
illummap=1
textureresolution=1
texturequality=16
dxtc=0
aa=0
multipass=0
ps_hack=1
surroundmode=0

[Mouse]
xaxisinvert=0
yaxisinvert=0
sensitivity=6
mlook=1

[Vendetta]
Username=Pyro
AudioDriver=Windows Sound (WAV) driver
VideoDriver=DirectX8.1 GKGL driver
xres=1024
yres=768
bpp=16

I found a similar problem described with Call of Duty. Suggestions there included:

1) switching to OpenGL
2) Turn off Fast Write
3) Drop AGP down to 4
4) Turn off vsync

My laptop can only hit 4x, so that isn't it... It seems that turning the graphics options up helped a bit. It's sort of a hack, but it seems that dropping the framerate helps...

"No, it seems to be caused by Vendetta unknowingly rendering several frames ahead of time. Usually the drivers prevent this. I was able to fix it by limiting the number of queued blits in RivaTuner, but I don't think that will work for ATI cards. I bet if you switched to OpenGL mode it wouldn't do that, but that is obviously not an ideal solution.
"
I just want to clarify:
Rivatuner supports Catalyst drivers... But ATi doesn't support mobile chipsets..

Its worth a try to Download Rivatuner and see if it works, the worst you'll get is "Unsupported Driver".

http://downloads.guru3d.com/download.php?det=163
^ Download link, just scroll down and you'll see 2 mirrors.

Sooo... Yeah, it's still happening, and worse than before... I just got killed by a Drone II because I couldn't move... I want my credits back... -.-

Edit: No supported drivers for RivaTuner...

...

I've lost 3 ships (2 cents, 1 wraith) so far because of this damned bug...

Make that 3 centurions.

try dropping AGP lower than 4.

RivaTuner crashed when I tried to switch it through there, and my BIOS doesn't have an option for it, so I'm willing to guess that my laptop doesn't like doing that...

Yay, now it's 4 centurions. Blah, it's impossible to test for bugs with this damned thing...

Still happening ... even today. (Nvidia 64MB Geforce2 card on Linux with current Nvidia drivers).

It never occured in OpenGL Spunk. It was a DirectX problem which could always be fixed by switching to OpenGL mode. So you have a new bug.

(Update bug reports filed)

Summary: The slide out of control bug occurs when killing bots at close range and can be 'corrected' by killing another bot at close range.

Note: This has happened to me occasionally in the 'old' versions of Vendetta though with no regular pattern. Now, it happens every time I go on a bot hunt and kill some (one?) at close range. (old versions up to a year ago)