+- Xonotic Forums (https://forums.xonotic.org)
+-- Forum: Support (https://forums.xonotic.org/forumdisplay.php?fid=3)
+--- Forum: Xonotic - Help & Troubleshooting (https://forums.xonotic.org/forumdisplay.php?fid=4)
+--- Thread: [SOLVED] Weird performance issue (/showthread.php?tid=887)
Weird performance issue - vede - 08-28-2010
Whenever I go to test a map I'm working on (or any other map), I experience extreme lag (about a frame every second or so), but the game's FPS counter stays normal. I can see the frame tearing every few pixels down the screen, so whenever I move, it's as if the map warps backward near the top of the screen (top of the screen is from a few frames behind the bottom of the screen). Sometimes a vid_restart will fix this, but as soon as I enter the menu, it starts again.
I've changed the vsync option as well as the "wait for GPU to finish each frame" option to try to fix it, but nothing changes. Any idea what the problem could be?
Using Arch Linux right now, nvidia GeForce 9400 GT, 2GB RAM, 2.8 GHz dual-core AMD CPU.
RE: Weird performance issue - vede - 09-04-2010
This is still a problem, even after updating and recompiling just a few minutes ago.
Please, any help would be great. It's really frustrating not being able to test maps because of this.
RE: Weird performance issue - Joe le Kiffeur - 09-04-2010
Hi vede!
I have this same problem.
I hope it will fixed soon.
RE: Weird performance issue - Mr. Bougo - 09-05-2010
Are you two using any weird compositing windows manager such as Compiz? Do you have your gfx drivers correctly set up?
RE: Weird performance issue - vede - 09-05-2010
Hm, I was using XFCE's compositor (lolselfdefeating), and disabling it fixed the problem. This is still a big issue, though. Having to change WM settings to play a game is a bit of a hassle, and Nexuiz works just fine with the compositor on, so we know it's not unavoidable.
And thanks!
EDIT: Okay, turning the "Display fullscreen overlay windows directly" setting on in the compositor settings fixed the problem, but only in fullscreen. So I can have my pretty transparent terminals and Xonotic at the same time in normal circumstances, but it's still an issue for windowed mode.
RE: Weird performance issue - Joe le Kiffeur - 09-06-2010
I discover there is something wrong with SWAP.
While you are playing, there is a very big amount of SWAP.
On my Ubuntu 10.04.1 system, my 2 Gb RAM are used and there is about 1.5-2.0x of RAM after the SWAP is written.
Consequently, disk usage is very important during SWAP transfer.
I thought during that 'evenement' the minimal configuration was a 32 core with 8Tb of RAM...
RE: Weird performance issue - Mr. Bougo - 09-06-2010
vede, unfortunately that's a problem for every compositing WM, and it's up to the WM to solve it. You can't really have complex graphics + compositing...
The solutions you have are to either launch Xonotic in a different X session (beats the point of windowed mode though), have a global system shortcut to toggle compositing, or make a wrapper script that disables compositing while Xonotic is on and enables it back when the process exits.
Joe, can you tell us how much memory Xonotic uses? See in the system monitor or something like that.
RE: Weird performance issue - Joe le Kiffeur - 09-09-2010
(09-06-2010, 02:08 PM)Mr. Bougo Wrote: vede, unfortunately that's a problem for every compositing WM, and it's up to the WM to solve it. You can't really have complex graphics + compositing...
The solutions you have are to either launch Xonotic in a different X session (beats the point of windowed mode though), have a global system shortcut to toggle compositing, or make a wrapper script that disables compositing while Xonotic is on and enables it back when the process exits.
Joe, can you tell us how much memory Xonotic uses? See in the system monitor or something like that.
RAM + SWAP: up to 3Gb.
RE: Weird performance issue - divVerent - 09-10-2010
This is caused by our high resolution textures. Your choices are:
- enable texture compression in the menu
- reduce texture quality
- both
Sorry, we can't do much about this. Release builds will default to texture compression for this reason.