I know that due to it being over a decade old, it's not going to be expected to run perfectly even if you have top-of-the-line hardware due to internal software limits, but I'm sure that having such huge FPS drops is a strange issue that has some sort of solution. After all, other people can play intensive maps on the same or even lower specs than mine, yet run perfectly fine.
Thanks in advance.
Edited 2.32 hours after the original posting.
Press CTRL+SHIFT+ESC and have a look at what is chocking your CPU, if anything at all.
If your CPU has no run-away processes, what is your "com_hunkMegs" set to? Is it too high? Personally, it should not be more than 128. Setting it too high will cause a memory issue.
If you still have the issue, it could be a damaged shader in a PK3. Remove a few PK3 files at a time, start up ioquake3 and repeat until the issue goes (hopefully) :]
PS. Thanks for the bug report! The error has been fixed. It was related to a code update. Do you mind editing your post to remove the file path details please.
And you're welcome. :) (Regarding the bug reported, and edited as stated)
I had a constant FPS of 125 (running "com_maxfps 125") and no lag spikes. The issue appears to be at your end.
Did you try removing extra PK3 files? Strip your baseq3 folder back to basics (just pak*.pk3) and map-13void_xt.pk3 and see what happens. I find making a "tmp" folder and placing everything else into it is the quickest. It is also very quick to restore if that is not the problem.
System memory can die and can be tricky to debug. Have a look at www.memtest.org/ if you think system memory may be the issue.
Have you got r_flares disabled and v-sync off? Updated your gfx card drivers to the latest? Made sure you don't have anti-aliasing, anisotropic filtering and v-sync forced on in your gfx card settings?
Only registered members can post a reply.
Already registered? Sign in.