Announcement

Collapse
No announcement yet.

Quake III 1.27g Update Released

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

  • Quake III 1.27g Update Released

    http://www.quake3arena.com/news/index.html
    <TABLE BGCOLOR=Red><TR><TD><Font-weight="+1"><font COLOR=Black>The world just changed, Sep. 11, 2001</font></Font-weight></TR></TD></TABLE>

  • #2
    first impression: it fuxxored up my mouse movement! it added some kind of mouse acceleration that is horrible!!!!! how do I turn it off!@#@$?

    Comment


    • #3
      Hmmmm ... smooth as silk for me. I'd say a definite improvement.
      <TABLE BGCOLOR=Red><TR><TD><Font-weight="+1"><font COLOR=Black>The world just changed, Sep. 11, 2001</font></Font-weight></TR></TD></TABLE>

      Comment


      • #4
        Great now we just have to wait until all mods are up to date... if you use any mods that is
        -=And May The Schwartz Be With Ya=-

        Comment


        • #5
          Is it a stand alone update or do I need to install 1.17 and 1.27g over it ?

          Comment


          • #6
            Demos won't work and when using the console command it loads them till snapshot and kicks me back to menu, so no benchmarks.

            I can confirm dZeus' f***ed up mouse acceleration problem, it sucks.
            Are you using a USB mouse ? I'm using a cheap 2 button USB mouse (these sorts hold me the most).

            Comment


            • #7
              From release notes ...

              Known Issues
              Launching demos from the user interface does not work. To play a demo back, go to the console and type "demo demofilename" without the quotes. This is a bug that cropped up when we changed the extension for demos so they include the protocol number so demos show up properly in menus. This will be addressed in a later patch.
              I also get kicked out of the new demo via the console command. I even tried relocating all of my mods out of the Q3A directory structure.

              Where are you guys seeing this mouse problem? I'm using an USB mouse and I had great results in single player. I'll try multiplayer after doing my morning scouring of the MURC.
              <TABLE BGCOLOR=Red><TR><TD><Font-weight="+1"><font COLOR=Black>The world just changed, Sep. 11, 2001</font></Font-weight></TR></TD></TABLE>

              Comment


              • #8
                first of all, I am using a PS/2 mouse, the Logitech Mouseman + (called wheel nowadays?)

                There isn't a mouse-'problem', it's just that id enabled mouse acceleration in q3a by default now. If you move the mouse fast over a certain distance, it will cause a greater angle change than if you move it slow over that same distance. I am used to point release 1.17 where there was no such accel, and I would like to disable it. However, the command cl_mouseaccel already is at 0, that's the weirdest part! (and never was at anything else)

                Comment


                • #9
                  Well I don't see this accel effect while swinging my aim around slowly or more quickly. I tried changing cl_mouseaccel from default of '0' to '1' and didn't notice any change as well. I may just not be as attuned to the game as you as I haven't been playing much the last couple weeks.
                  <TABLE BGCOLOR=Red><TR><TD><Font-weight="+1"><font COLOR=Black>The world just changed, Sep. 11, 2001</font></Font-weight></TR></TD></TABLE>

                  Comment


                  • #10
                    If there's a way to get rid of it, I would die to get it!

                    It annoys the hell out of me!

                    Comment


                    • #11
                      Q: My sensitivity is all whack in the new version, help!
                      A: It seems that some USB Logitech mouse users (and others?) have experienced this problem. I'm not sure where he found it, but [McP]AtomicJew mentioned this on IRC:
                      I have studied the mouse sensitivity issue, and have conluded it is not the sensitivity but a very high accelleration that is at fault, and that having any mouse accelleration enabled anywhere on the system to even the tiniest setting will trigger it. The solution is to turn any and all mouse accelleration off.
                      I've also heard that using in_mouse -1 fixes things (I've always used this setting and haven't noticed any mouse issues in 1.27).
                      Disabling acceleration in the drivers (default win2k driver for my moue) fixed the issue

                      Comment

                      Working...
                      X