Nexuiz on MacPro quad 2,66

[esteel]

Well as others have said: Other operating systems that that kind of stuff automatically. When apple does not it might because its not safe to enable it for all applications.
But maybe Nexuiz is lucky and does not get problems when enabling it

[ikir]

Thanks! I will test the new release when it comes out! Thanks you Do you have an ETA?

Ah Mac OS X 10.4.9 is out, 3D games are faster... and Nexuiz is not an exception. Indeed it gains few fps. Now with all turn ON i go from 60 to 15 fps it depens from the area... it isn't playable yet at max settings but still good.

[Zaarock]

Ah, exellent news, Im willing to beta test this multithread script with my 1.8ghz mac mini.

Ikir, I didnt see any such thing on the updates page, anyone bother link me?

[GreEn`mArine]

well, probably divVerent could temporarily create a current release (which includes the mac binary too) and give it to the people who are already willing to test it, especially since LordHavoc included a cvar to use that multithread opengl feature now.

[ikir]

Indeed i'm waiting too

Speed increase was referring to Mac OS X 10.4.9

PS: how i can make a "timedemo" with Nexuiz?

[esteel]

just enter tdem demo1 or any other demo name in the console. but demo1 and demo2 are included in Nexuiz so everyone can use those to compare and demo1 has more action in it and is longer so its the better one for a benchmark..
(Open the console with shift-escape and close it again with escape)

You should run that at least twice as the first run might compile some stuff on the graphic card and is slower then the following runs.

For example my nv 6600gt gives me on default settings:
2.2.3: result 1909 frames 35.0140000 seconds 54.5210487 fps min/avg/max: 17.2413793/54.5210487/250.0000000
upcoming 2.3: result 1909 frames 29.6720000 seconds 64.3367484 fps, one-second min/avg/max: 37 64 95

The min and max in older versions are a bit meaning less as those are the absolute min/max fps but people want to know the one second average.. But still thats a improvement from 54 to 64 fps on average = 18%

At my usual play settings its:
2.2.3: result 1909 frames 20.3980000 seconds 93.5876066 fps min/avg/max: 41.6666667/93.5876066/500.0000000
upcomming 2.3: result 1909 frames 16.8920000 seconds 113.0120767 fps, one-second min/avg/max: 92 114 149
improvement from 93 fps to 114 on average = 22%

Hmm not sure what wrong with my sytem today, maybe its beryl, yesterday i got:
result 1909 frames 15.6910000 seconds 121.6620993 fps, one-second min/avg/max: 100 123 157
But thats just a bit faster anyway..

[melk]

so is the cvar for multi-threaded OpenGL enabled by default in 2.3 test builds?

how can I display every cvar?

[esteel]

yes multithreaded opengl is enabled by default in 2.3.. i'm not sure which 2.3 test release had it enabled by default but we'll do a FINAL test release later today where its enabled for sure!

You can list all variables with cvarlist in the console..

[zenwalker]

"tdem demo1"

Didn't know that, been using: timedemo demos/demo1.dem

Is there a way to loop this timedemo? As a log is generated it could be useful for testing overclock stability

Thanks.

[esteel]

Hmm not from inside the game.. but the command line option -benchmark demos/demos1 will do a timedemo and close afterwards. If you start it from a shell like 20 times that should be similar enough. You can also use the option +forceqmenu 1 to make it NOT load the menu which is a huge speedup for such tests.
BTW yesterday we released the LAST test candidate for 2.3 which has multithreaded opengl active by default so this is a good thing to test NOW and report back