There's a couple of problems I've been having with Quake 1. I'm using GLpro 3.50. First of all, I can't aim completely up for down. Can only aim 85-90% either way vertically. I've always had this problem. GLpro has a command called pq_fullpitch, which at 1 allows you to look completely up or down. This only works when not connected to a server though. When used at a server, my view spazzes out everytime I look too high or too low, like it just does whatever it want, while I lose control for about a second. So that's definitely annoying. I'm not sure why it works in offline quake and not on servers. I've been playing on pq_fullpitch 0 for a long time. I want to be able to aim fully up and down, not sure how I can fix it up to work like that. Any ideas?
Second problem is even weirder than the first. Exactly every other time I boot up quake, I can barely move and feel like I'm pinging 800, this is simply fixed by exiting and launching quake again, where everything is then back to normal...that is, until the next time I start up quake. This goes on and on and on. Instead of using the short term fix of just re-launching quake, I'd like to completely eliminate this problem. I don't understand why this would happen every other time I start quake, I wonder what happens differently when it doesn't work correctly...every other time. Weirdness. I've had this problem for a long time now also. I've tried using a different quake directory.
I guess I could try a different client, but I'm used to GLproquake and I like it. So I'd rather just figure out what causes these problems and fix them. I'm curious to find out anyways.
Second problem is even weirder than the first. Exactly every other time I boot up quake, I can barely move and feel like I'm pinging 800, this is simply fixed by exiting and launching quake again, where everything is then back to normal...that is, until the next time I start up quake. This goes on and on and on. Instead of using the short term fix of just re-launching quake, I'd like to completely eliminate this problem. I don't understand why this would happen every other time I start quake, I wonder what happens differently when it doesn't work correctly...every other time. Weirdness. I've had this problem for a long time now also. I've tried using a different quake directory.
I guess I could try a different client, but I'm used to GLproquake and I like it. So I'd rather just figure out what causes these problems and fix them. I'm curious to find out anyways.
Comment