Forums » Bugs
version 1.8.140 framerate limiter
running arch linux 64 bit. Have an nvidia gtx 260 oc graphics card and I run it through a matrox triplehead2go.
if any value for framerate limiter is set X crashes. the game loads to 100% and then locks up X. I had to manually remove the setting in the config.ini to get the game to work again
if any value for framerate limiter is set X crashes. the game loads to 100% and then locks up X. I had to manually remove the setting in the config.ini to get the game to work again
config.ini, change maxframerate=x to maxframerate=0 under the [Vendetta] section.
wow you guys are fast!
yeah i just found that and changed my post before i realized there was a reply. thank you for you quick reply
yeah i just found that and changed my post before i realized there was a reply. thank you for you quick reply
I can't log in now: as soon as I changed the framerate to 60 and hit apply, the game froze in full screen mode. no escape. hard reboot. tried logging in again, but now the login screen is frozen. can't even enter a password.
I'm running Mac OS 10.6.4. brand new install, and fresh install of vo...
I guess I won't be logging in till this gets fixed. :(
I'm running Mac OS 10.6.4. brand new install, and fresh install of vo...
I guess I won't be logging in till this gets fixed. :(
CD: edit config.ini like slime said
1.8.140.1 still hangs on 10.6.4
1.8.140.1 still hangs on 10.6.4
The fix that slime pointed out works for Mac as well (verified on 10.6.4). The framerate limiter is still broken, but you can avoid its effects.
Just to clarify, this is still happening with 1.8.140.1. Whenever the limit is set to a number above 0 and below a value that the fps actually hits, the entire game hangs as described. If it's set above any reached fps value, it doesn't hang. Don't know if that is helpful at all.
Just to clarify, this is still happening with 1.8.140.1. Whenever the limit is set to a number above 0 and below a value that the fps actually hits, the entire game hangs as described. If it's set above any reached fps value, it doesn't hang. Don't know if that is helpful at all.
Ok, the Mac version should be fixed with 1.8.140.2.
It was my fault. The mac update didn't make it out on the .1 release.
It was my fault. The mac update didn't make it out on the .1 release.