Request for OSX commandline option testing

[LordHavoc]

I replied to this already but it seems my submit failed or something, or someone deleted my post, I don't know... so I'm writing this reply all over again, days later.

http://dp.deathmask.net/log/nex_mac_glsl

OS X 10.5.1 , Geforce 7900GT

Your beloved hackintosh?

There appears to be massive z-fighting with the skybox texture. -notexturenonpoweroftwo made no difference on anything. glsl was a bit faster.

r_depthfirst 0 may make this problem go away, however it may run slower also.

Does this problem happen with glsl on and off, or just when it is on?

Interestingly, running a second tdem demo1 w/o glsl would crash the entire engine, with glsl on, it would work fine.

A backtrace from gdb (or whatever frontend Apple provides) would be appreciated.

log1 is as in original post
log2 is with -notextureonpoweroftwo

-notexturenonpoweroftwo shouldn't affect that card anyway (I'm told it doesn't support non power of two 3D textures - but who cares).

[Willis]

r_depthfirst 0 may make this problem go away, however it may run slower also.

Does this problem happen with glsl on and off, or just when it is on?

Only happened with glsl on. r_depthfirst 0 did indeed solve those problems. However, upon further testing, I see I didn't test enough maps, I'm also getting the rotating 2d in certain maps akin to pictures posted previously by others. (In warfare for example, no applicable warnings that I could tell).

A backtrace from gdb (or whatever frontend Apple provides) would be appreciated.

The problem does not appear to be happening on SVN, so I'm not going to debug for now.

[iSuck]

Ok, here's an update:
I tried the SVN, and turned on glsl shaders in the options menu, and the exact same thing happened as when I initially typed that thing in my agl. The rainbow textures appear, and I lag horribly.
It doesn't do that in 2.3 though, so please don't make the SVN changes permanent in the GL department.

[LordHavoc]

Ok, here's an update:
I tried the SVN, and turned on glsl shaders in the options menu, and the exact same thing happened as when I initially typed that thing in my agl. The rainbow textures appear, and I lag horribly.
It doesn't do that in 2.3 though, so please don't make the SVN changes permanent in the GL department.

All changes are permanent, reverting substantial renderer redesigns is not practical or even desirable when they gave speed gains for most people - all I can do is disable use of features that do not work on certain hardware.

Please supply a screenshot of the rainbow textures problem you are describing, I'd like to see it.

Please also try the -notexturenonpoweroftwo option.

Please also try +gl_vbo 0.

Do any of these fix it?

[AceOfThumbs]

The Jan 04 engine build works on my Mac Pro, ATI X1900XT, OS 10.5.1. It's nice to have the new HUD again.

I still get the spinning menus with the GL 2 shaders on, but it's not a big deal.

[LordHavoc]

The Jan 04 engine build works on my Mac Pro, ATI X1900XT, OS 10.5.1. It's nice to have the new HUD again.

I still get the spinning menus with the GL 2 shaders on, but it's not a big deal.

It is a big deal - the GL2 shaders are a nice fps boost.

I'll continue experiments later.

[AceOfThumbs]

It is a big deal - the GL2 shaders are a nice fps boost.

I'll continue experiments later.

Well, I'm happy to hear you say that. I would like the higher fps too. I appreciate all of the work the developers do and didn't want to sound ungrateful about the GL2 problem.

[iSuck]

Sorry for leaving this topic for so long. But I have a problem.
I can't recreate the rainbow textures. I can change the settings all around, but nothing happens. All I get is the black weapon models. I took lots of pictures this time. I'll post those later.

[LordHavoc]

Sorry for leaving this topic for so long. But I have a problem.
I can't recreate the rainbow textures. I can change the settings all around, but nothing happens. All I get is the black weapon models. I took lots of pictures this time. I'll post those later.

Rainbow textures are generally video memory corruption (in this case due to driver bugs possibly), it can be very hard to reproduce such errors - they generally look different every time.

[iSuck]

Well, Apple just released the newest addition to the Macbook line. You know why that pisses me off? Because that means they spend all year working on that, and not fixing the GL drivers that are obviously broken
Could you look at this, LordHavoc, if you haven't already? Are they claiming they support all the OpenGL things that don't work? or are they aware of it and just not fixing it.

http://developer.apple.com/graphicsimag ... abilities/

I need to get my imageshack account back. I think I entered a fake email address when sgining up, then I'll post pictures.