Announcement

Collapse
No announcement yet.

Couple of problems I've had for a while

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • Couple of problems I've had for a while

    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.

  • #2
    pq_fullpitch is a hack and was never a REAL command in quake. q1 never intended for you to be able to look straight up. It wont work on servers because the hack im guessing needs to be server side as well as client side

    .exe - +pq_fullpitch 1 (etc etc etc)
    Yet I still beat you more easily than a hammer can beat a fresh batch of Rowntree's fruit jelly.
    The 300pingGOD ( july '98 )

    Comment


    • #3
      PQ_FULLPITCH must be supported (pq_fullpitch 1 must be set) by the server AND the client for it to work. I dont see it as a "hack" since its only 2 lines of code that merely change 2 values.

      A "hack" would allow you to use fullpitch reguardless of the server settings.

      As for your immediate poor performance on load, edit the quake.rc file and delete the playdemo line. Possibly your cache is loading all the textures as the demo is playing?

      Try another client, something like fitzquake or arq-lite. (IE. small footprint).
      or post your commandline here ??
      www.quakeone.com/qrack | www.quakeone.com/cax| http://en.twitch.tv/sputnikutah

      Comment


      • #4
        Ok, thanks.

        I don't have a quake.rc file. The reason the problem is so weird is that it only happens every other time I start quake, and the rest of the time there's no problem at all. Here's my command line, nothing special i think:

        glpro.exe -zone 1024 -width 1024 -height 768 -bpp 32 -game arena

        Comment


        • #5
          Also, quake won't minimize anymore, which is annoying. I can minimize but when i come back half the screen is screwed up.

          Comment


          • #6
            Originally posted by Adaman View Post
            Also, quake won't minimize anymore, which is annoying. I can minimize but when i come back half the screen is screwed up.
            All the authentic style engines do that to me (ProQuake, Enhanced GL, FitzQuake) but I don't have this problem with graphically enhanced engines (JoeQuake, Qrack, DarkPlaces, FuhQuake, etc).

            I have to live with it -- at least on this computer with the vid card it is using.

            I generally don't have the above issue with my laptop or most other computers.

            I also had this issue on my old computer so if you aren't using the same hardware as in the past, there might not be a fix for it -- although you can update video card drivers and hope it resolves the issue.
            Quakeone.com - Being exactly one-half good and one-half evil has advantages. When a portal opens to the antimatter universe, my opposite is just me with a goatee.

            So while you guys all have to fight your anti-matter counterparts, me and my evil twin will be drinking a beer laughing at you guys ...

            Comment


            • #7
              What are your PC specs? specifically your video card?

              Telling us this will help further identify the problem

              One thing I do to get around the tabbing out of GLPRO 3.50 is to run it in window mode the exact same size as my desktop. Then its more like switching windows while im in quake. Theres Pros and Cons to this method however
              QuakeOne.com
              Quake One Resurrection

              QuakeOne.com/qrack
              Great Quake engine

              Qrack 1.60.1 Ubuntu Guide
              Get Qrack 1.60.1 running in Ubuntu!

              Comment


              • #8
                Are any other clients allowed on "cheat-free" servers yet?

                My system specs:
                A64 Opteron 146 CPU @ 2.7 ghz - Stock voltage
                ASrock DualSATA2 Motherboard
                1GB Corsair Value Select Memory
                22" ChiMei 221D-NBC Monitor
                ATI X800XL
                Creative Labs Audigy 2 ZS
                Windows XP SP2

                Desktop resolution is 1680x1050

                Comment


                • #9
                  "Cheat-free" servers only work with ProQuake. If that ever changes, it probably wouldn't be until next year at the earliest. It would require a lot of coordinated changes to the engines and server.

                  I figure it will happen eventually, I don't figure that it will happen soon.

                  Your "lag issue" -- the 800 ping thing -- make sure pq_maxfps is set no higher than 200. If you have your FPS set too high, Quake chokes!

                  This is just a guess. If you are using wireless there is a post from Solecord where he had and fixed a problem that sounded similar, but that would only apply to wireless (if you are using that).
                  Quakeone.com - Being exactly one-half good and one-half evil has advantages. When a portal opens to the antimatter universe, my opposite is just me with a goatee.

                  So while you guys all have to fight your anti-matter counterparts, me and my evil twin will be drinking a beer laughing at you guys ...

                  Comment


                  • #10
                    Thanks. I'm not on a wireless connection. Is there a sure way to setup quake so it won't get all screwy when minimized? Thanks.

                    Comment


                    • #11
                      My FPS is still crazy high even though I have pq_maxfps at 100 in my config, that sounds like the right command, but it's not affecting anything. Is there any other FPS max command?

                      Comment


                      • #12
                        You might consider downloading the ProQuake Launcher and playing around with the various resolutions and such. It sounds like you have a difficult to identify problem that might be solved via the command line and the ProQuake Launcher makes that easy and has help buttons that explain each setting.




                        My command looks like this:

                        c:\quake\glpro.exe -width 640 -height 480 -bpp 16 -gamma .65 -dinput -nocdaudio -heapsize 24000 -zone 2048
                        Quakeone.com - Being exactly one-half good and one-half evil has advantages. When a portal opens to the antimatter universe, my opposite is just me with a goatee.

                        So while you guys all have to fight your anti-matter counterparts, me and my evil twin will be drinking a beer laughing at you guys ...

                        Comment

                        Working...
                        X