On my Mac when 2.5.1 starts the gameplay sometimes becomes *extremly* jerky. Very jerky, like a .5 fps or lower framerate. This can be seen reliably when playing the "bench1" demo. It starts and within a few seconds just starts jerking. At this point even typeing in the console is slow. I've seen this on the "strength" map when playing in single player as well.

Yet it plays fine in 2.5.

I'm on a MacBook Pro (Geforce 8600M) and this is with both the "standard" version and the SDL version.

Zardoz wrote:On my Mac when 2.5.1 starts the gameplay sometimes becomes *extremly* jerky. Very jerky, like a .5 fps or lower framerate. This can be seen reliably when playing the "bench1" demo. It starts and within a few seconds just starts jerking. At this point even typeing in the console is slow. I've seen this on the "strength" map when playing in single player as well.

Yet it plays fine in 2.5.

I'm on a MacBook Pro (Geforce 8600M) and this is with both the "standard" version and the SDL version.

i had a problem playing the bench1 demo on my macbook in 2.5...i think its just from a slow processor or something..

MC SE7EN wrote:i had a problem playing the bench1 demo on my macbook in 2.5...i think its just from a slow processor or something..

I generally get OK framerates (40-80 fps) on the Pro with the default settings. This isn't slow processor, this is "WTF is broken" .

Zardoz wrote:

MC SE7EN wrote:i had a problem playing the bench1 demo on my macbook in 2.5...i think its just from a slow processor or something..

I generally get OK framerates (40-80 fps) on the Pro with the default settings. This isn't slow processor, this is "WTF is broken" .

well, i can tell you i usually get decent framerates as well, unless theres an obscene amount of stuff going on like there is on the bench1 demo..so it may just be that theres a lot of activity..

MC SE7EN wrote:well, i can tell you i usually get decent framerates as well, unless theres an obscene amount of stuff going on like there is on the bench1 demo..so it may just be that theres a lot of activity..

Aw well, let me rephrase: I usually get OK framerates on the Pro with the default settings while viewing the bench1 demo in 2.5.

It's only in 2.5.1 where it breaks.

Zardoz wrote:

MC SE7EN wrote:well, i can tell you i usually get decent framerates as well, unless theres an obscene amount of stuff going on like there is on the bench1 demo..so it may just be that theres a lot of activity..

Aw well, let me rephrase: I usually get OK framerates on the Pro with the default settings while viewing the bench1 demo in 2.5.

It's only in 2.5.1 where it breaks.

oh ok..well then i have no clue..

*butts out*

Seems on 2.5.1 simply setting:

r_glsl_deluxemapping "0"

makes the bench1 demo run smoothly again. Again, this wasn't needed in 2.5.0 on my MacBook Pro but seems to be necessary in 2.5.1.

(Note all other effects are essentially the default settings).

that was already disabled for me and it still doesnt run smoothly on that demo..even on the lowest video settings..

MC SE7EN wrote:that was already disabled for me and it still doesnt run smoothly on that demo..even on the lowest video settings..

But are we talking about the same thing? Are you seeing simply low framerates or is it pausing every few seconds. I guess that would be a better description of what I'm seeing, or was anyway.

Zardoz wrote:

MC SE7EN wrote:that was already disabled for me and it still doesnt run smoothly on that demo..even on the lowest video settings..

But are we talking about the same thing? Are you seeing simply low framerates or is it pausing every few seconds. I guess that would be a better description of what I'm seeing, or was anyway.

no, i mean its really jumpy and skippy..it pauses every few secs, but only when theres a lot of action going on.

gl_texturecompression "1"

This seems to help too. "0" is the default in 2.5.1 while "1" is the default in 2.5. The MacBook Pro just can't handle the textures being uncompressed in the strength map I guess .

That means you're running out of texture memory.

Texture compression was turned off again as default because of Intel drivers crashing with it, and because it looks bad.

Another way to reduce texture memory is increasing gl_picmip.