![]() ![]() I didn't think there was a maximum FOV imposed in Q3A, and if so definitely not 120.Īny ideas? Like I said, increasing the FOV over 120 only has one effect, and that is making the equipped weapon drop further out of view until it is invisible. I love how good it looks in this resolution and aspect ratio, but its hard to relearn a new FOV, even if it is only a little bit off from my target. Quake 3 Team Arena on it was an unremarkable experience as a visible. I've played with the same FOV the entire time I've played quake 3 arena (almost a decade). Monitor Type/Size: TFT/Active Matrix Color LCD Native Resolution: 1280 x 768. It's been very frustrating, I've looked for potential console commands that might be limiting the maximum FOV to no avail. Super Mario 64 port at 60fps, widescreen is bliss - a night and day difference to that. I was wondering if any of the Q3A community here would be able to help me get past this barrier, as the FOV I need to establish in order to have a smooth transition from 4x3 to 16x9 is unattainable right now. Also I never realized this thread went up at 3 am where I live. Turns out that any FOV setting over 120 only makes my gun disappear more, the actual field of view stays the same as if it was still on 120. I set the fov to 124.6 and thought it was a little off still, so tried setting it a bit higher only to realize it wasnt changing a damn thing. I always used a fov of 110 with a resolution of 1024x768 (4x3 aspect ratio), and realized that by going to 16x9 this was bound to happen, so with a little math I calculated that I should set my new fov to 124.6 to be about equivalent to how I always had my FOV set. The effective sensitivity goes down and the mouse just seems not responsive enough to pick up flick moves correctly (they're translated to smaller crosshair movements).I just purchased my 1st widescreen monitor, set up quake3 to run in a custom resolution (1920x1080) and noticed that the fov was out of whack. When i enable vsync (r_swapinterval 1), i experience an significant slowdown when i flick the mouse from left to right (wrist movement). Perhaps the fact that i use my Razer Diamondback at 500 Hz USB polling rate makes it more noticeable. It has no magic com_maxfps numbers that give a speed boost (only some weird things happening at very low framerates).Ībout vsync affecting mouse input: i find the effect very noticeable. You move quite a lot faster than without pmove_fixed at 125, which makes doing strafepads in trickjump practice maps a lot easier.ītw, CPMa has replaced the pmove physics code and it's much more framerate independant than any VQ3 or any other mod. ![]() That equates to 125 fps and if your videocard renders less than that, things get choppy. Q3's physics are framerate dependant (evaluated at every new frame i guess), unless you use pmove_fixed, which forces every frame to last as long as pmove_msec (defaults to 8 milliseconds). It is used for tricking with overbounces, yes, but it gives an insane speed boost though. Pmove_fixed isn't always used for tricking and never for competitive play. Just looking for some facts and clarification, I've heard lots of uninformed opinions on both matters. Is this considered unfair play? I mean, people use it for tricking right? Do they not use it in competitive play, tdm etc.? Are their any good descriptions of what this does, what it compensates for? I mean, it's supposed to give you the optimum jump height every time or something, right? Well, if you don't usually get that optimum with pmove_fixed 0, then what do you get instead? And this is considered a cheat by punkbuster, right? ![]() I've also been told there might be a way to fix it. Download this: (link removed) Source code here: (link removed) Extract the files inside to your non-Steam Quake3 directory, overwriting any existing files. From what I can understand vsync supposedly drops sections of mouse inputs in between screen draws or something because it forces everything to be done sequentially and skips everything outside of the sequence. If you are using the Steam version, find the game directory (should be steamappscommonquake 3 arena) and MOVE/COPY it OUTSIDE of the Steam directory. I see no possible need for anything greater, and honestly I've never noticed any mouse lag at all with vsync. I mean, I would love to just have a 60 refresh rate and vsync on. ![]() Is there any fact behind the whole vsync mouse lag issue? ![]()
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |