MegaGlest Forum
Archives (read only) => Vanilla Glest => Bug report => Topic started by: crazy on 9 January 2007, 11:02:48
-
after playing a bit, suddenly the game goes into warp speed, making it unplayable
fedora 6 - athlon - radeon 9200
-
The game plays great for all of about 30 seconds, and then it speeds up so fast that it's difficult to see what's happening - and then of course after the flurry of action is complete you get the nice little "You Lose" prompt, which kind of makes the experience a little comical.
I'm also using 64-bit Fedora (core 6) with an AMD processor and an MSI mobo (K8T Neo 2) with an nVidia GeForce 6800XT video card. The version of the game that I'm using is the one that I happened to see in the yum repositories, but which one escapes me at the moment.
Looks like a great game, I just wish I could move my mouse fast enough to keep up! :P
-
Same problem here, but it doesn't happen very often ( every 20th game I play )
ubuntu linux 6.06 32-Bit
Athlon64 3000+ , nvidia geforce 7600GS (nvidia-driver)
and
Athlon64 2800+ , nvidia geforce 4200 ((old) nvidia-driver)
-
You can change the game speed with the + and -, so maybe you can slow it down with the minus?
-
if you minimize glest without turning on pause, the game pauses until u restore it, but then go into warp speed to compensate time that it was paused. it usually don't take longer than 10 sec. but game goes very fast for that time. when you press Win key (for windows users, dunno what is for linux) glest minimize and start menu opens. before doing that you need to turn on pause. (this is probably my last post.)
-
not so sure about that! (no - this is my last post)
-
I might find the cause of problem. See: http://www.glest.org/glest_board/viewto ... 4558#14558 (http://www.glest.org/glest_board/viewtopic.php?p=14558#14558)
(Caution to Leopard users)
-
Thank you for this post!
I hope I can fix the problem now.
But I never had any trouble with newer versions of glest( versions > 3.1.0 ).
Probably there is something fixed now? Anyone still has this problem with a newer version?