If I play a level that has liquidand the OGL 2 shaders are on, the text will drift around, making them unreadable. This screen is taken from the top of Oil Rig:

http://www.notam02.no/~clund/nexuiz/OGL2bug.jpg

I'm still playing 2.2.1 since the "Black menu screen" bug is still present in 2.2.2 and 2.2.3, so maybe this OGL2 bug has alrady been fixed?

Yes, a known bug in the OS X ATI driver. And one of the reasons why OpenGL 2.0 shaders are disabled by default on OS X.

Let's wait until Apple FINALLY fixes that, and the other OS X GLSL bugs (namely, jagged realtime shadows, bloom at wrong position).

The problem is, it isn't our bug - all we can do is work around it, and in this case, we disable OpenGL 2.0 shaders. The menu bug will also be just fixed by a workaround in 2.3 - we'll disable the texture non-power-of-two extension for OS X because OS X drivers report it as supported but then draw nothing.

All you can do is complain to Apple so they get their drivers fixed.

Same problem I had. Look here. Seems that the answer is simply not to play with OGL2.

http://alientrap.org/forum/viewtopic.php?t=1489&highlight=opengl

But i do not understand why you still have that black menu in 2.2.3.. the startup file for mac should disable the texture non-power-of-two extension which is causing this black menu. Sounds more like you did something wrong with updating..

divVerent wrote:Yes, a known bug in the OS X ATI driver. And one of the reasons why OpenGL 2.0 shaders are disabled by default on OS X.

Let's wait until Apple FINALLY fixes that, and the other OS X GLSL bugs (namely, jagged realtime shadows, bloom at wrong position).

Ah, ok. I wondered about that bloom thing too, but I generally play with it off anyway. I do that with OGL 2 on levels with liquids as well.

And I'm relieved to hear you'll find a workaround for menu thing in the next update of Nexuiz. B)

esteel wrote:But i do not understand why you still have that black menu in 2.2.3.. the startup file for mac should disable the texture non-power-of-two extension which is causing this black menu. Sounds more like you did something wrong with updating..

What I did was download the full version of N2.2.3, tossed the .nexuiz folder in the trash, and played from the N2.3.3 folder. I assumed that would mean all the 2.2.1 stuff would be ignored by 2.2.3...

Yes that should work fine.. can you please try the following:
Start Nexuiz, open the console with shift-escape, enter condump bla.txt and then find the file ~/.nexuiz/data/bla.txt and search for power in it?
You should find it two times.. the first in a LONG line starting with

Code: Select all

7GL_EXTENSIONS:

and the second time in this line:

Code: Select all

^7checking for GL_ARB_texture_non_power_of_two...  disabled by commandline

That second line is the important one as it confirms this extension IS disabled.. But on the other hand you can try the 2.3 test release we did in the forum. And we want to do a FINAL one later today.

esteel wrote:Yes that should work fine.. can you please try the following:
Start Nexuiz, open the console with shift-escape, enter condump bla.txt and then find the file ~/.nexuiz/data/bla.txt and search for power in it?
You should find it two times.. the first in a LONG line starting with

Code: Select all

7GL_EXTENSIONS:

and the second time in this line:

Code: Select all

^7checking for GL_ARB_texture_non_power_of_two...  disabled by commandline

That second line is the important one as it confirms this extension IS disabled..

power only appears once in bla.txt; in this line:

Code: Select all

GL_ARB_occlusion_query GL_ARB_point_sprite GL_ARB_texture_non_power_of_two

I'm using 2.2.1, though.

But on the other hand you can try the 2.3 test release we did in the forum. And we want to do a FINAL one later today.

I don't really have time to do that, I'm afraid (depending on how late "later" is, of course).

Clueless Newbie wrote:power only appears once in bla.txt; in this line:

I'm using 2.2.1, though.

I don't really have time to do that, I'm afraid (depending on how late "later" is, of course).

in 2.2.1 thats to be expected as it did not USE that extension.. that line is just a list of all the extension your graphic card and drivers reported.. So its no wonder its working.
The great question is: in 2.2.3 we normally USE that extension. On mac we disable this use as it leads to problems like you reported. Thats why i want to find out if that extension is REALLY disabled for you or not! IF is IS disabled we have a new bug.. And if its NOT disabled we have to find out why so..

And sorry i was unclear.. we want to do a final test release today.. But feel free to use one of the other three test released we did so far.. Look in the developer subforum..

esteel wrote:

Clueless Newbie wrote:power only appears once in bla.txt; in this line:
I'm using 2.2.1, though.
I don't really have time to do that, I'm afraid (depending on how late "later" is, of course).

in 2.2.1 thats to be expected as it did not USE that extension.. that line is just a list of all the extension your graphic card and drivers reported.. So its no wonder its working.
The great question is: in 2.2.3 we normally USE that extension. On mac we disable this use as it leads to problems like you reported. Thats why i want to find out if that extension is REALLY disabled for you or not! IF is IS disabled we have a new bug.. And if its NOT disabled we have to find out why so..

I found the time to test 2.3.3 after all (or whatever version of Nex that comes with data20070519d.pk3). And once again, I got the black screen. I entered the console - I think, but I was still looking at a black screen so I couldn't do anything useful there. B(

But there is one oddity I keep noticing each time I try these builds: Instead of deleting the .nexuiz/ folder, I either rename it or move it to the trash. Then when I'm done with the testing, I take the .nexuiz/ folder out of the trash or rename it .nexuiz/. The configs always change when I do this, and this time I even found a folder in .nexuiz/data/ that had a backup of the old .nexuiz folder, but with the temprorary name I gave it.

What's going on here? Does Nexuiz hide a copy of the configs somewhere on the HD or does a new install start by ferreting out an old config file on the HD? Or are older data(number).pk3s interfering somehow?

Are you sure Nexuiz only stores it's files in .nexuiz and whatever folder the game is in? There is no backup stashed away somewhere? I find this behaviour odd, to say the least. I'm beginning to wonder whether I'll have to not only trash but also delete all Nexuiz files and only then try the latest build.

In that case, we can't help you - I am the only one of the developers who has a Mac at all, and here it's just a Radeon 9200 "powered" Mac mini. Here it works fine, but this thing can't do OpenGL shaders at all.

So, try the following:

Start the game. When you got the black screen, blindly type:

Shift-Escape
condump test.txt
quit

after that, the game should exit. Then, go to the .nexuiz folder and in there, into data. Post the file test.txt somewhere and give us a link so we can check which graphics extensions were detected. You can also try:

r_glsl 0
gl_vbo 0
apple_multithreadedgl 0
r_restart

to check if it has any effect.

As for your weird config file issue - no idea. The engine for sure does not write outside its directory and ~/.nexuiz. Maybe when you delete the folder, an old instance (crashed) of the engine was still in memory - and exited and wrote its config? Before deleting the Nexuiz folder, make sure no Nexuiz instance is running. For checking this, open a terminal and in there, type:

ps ax | grep nex

This should show no nexuiz-osx-ppc-whatever. If it does, it is still running - then type

kill 3298

where you replace 3298 by the number in the left column.

divVerent wrote:So, try the following:
Start the game. When you got the black screen,

BTW: The screen doesn't go black immediately; I first get the "Nex" icon with the loading text.

blindly type:

Shift-Escape
condump test.txt

Ok. You can find the condump here:

http://www.notam02.no/~clund/nexuiz/condump.txt

You can also try:

r_glsl 0
gl_vbo 0
apple_multithreadedgl 0
r_restart

That's a bit much to type blind. But I noticed that the "r_glsl 0" line was already there, so I tried adding this:

r_glsl "0"
gl_vbo "0"
apple_multithreadedgl "0"

Didn't make any difference though.

There we have it.. From your log:
^7checking for GL_ARB_texture_non_power_of_two... enabled

Thats WRONG WRONG WRONG! This extension has to be disabled and normally it IS disabled when using 2.2.3 on mac. Something must be wrong with the way you installed 2.2.3. I guess that for some reason it did not update/overwrite the file Nexuiz/Nexuiz.app/Contents/MacOS/nexuiz-osx-ppc-agl or in the case of SDL Nexuiz/Nexuiz-SDL.app/Contents/MacOS/nexuiz-osx-ppc-sdl but i do not have a clue about Mac so i have no idea no how to do it better.. and well i also have no idea how you did try to do it..

esteel wrote:There we have it.. From your log:
^7checking for GL_ARB_texture_non_power_of_two... enabled

Thats WRONG WRONG WRONG! This extension has to be disabled and normally it IS disabled when using 2.2.3 on mac. Something must be wrong with the way you installed 2.2.3. I guess that for some reason it did not update/overwrite the file Nexuiz/Nexuiz.app/Contents/MacOS/nexuiz-osx-ppc-agl or in the case of SDL Nexuiz/Nexuiz-SDL.app/Contents/MacOS/nexuiz-osx-ppc-sdl but i do not have a clue about Mac so i have no idea no how to do it better.. and well i also have no idea how you did try to do it..

Well, what I did when I installed 2.2.3 was to rename the .nexuiz folder so it's contents would be ignored, downloaded the full version of 2.2.3, and played from that.

Oh well. When 2.2.1 is no longer compatible with whatever the servers are using, I'll wipe everything Nex off my HD before installing from scratch. Maybe that's what it'll take to make it work.

In the meanwhile, is there any way to disable that extension from the config file?

Clueless Newbie wrote:Well, what I did when I installed 2.2.3 was to rename the .nexuiz folder so it's contents would be ignored, downloaded the full version of 2.2.3, and played from that.

Oh well. When 2.2.1 is no longer compatible with whatever the servers are using, I'll wipe everything Nex off my HD before installing from scratch. Maybe that's what it'll take to make it work.

In the meanwhile, is there any way to disable that extension from the config file?

Well yes but what did you do with the OLD Nexuiz 2.2.1? Meaning were did you put Nexuiz 2.2.1 and were do you put Nexuiz 2.2.3? To me it seems like both are kinda mixed..

There is no way to fix this from the config file, you need to edit the file that starts Nexuiz. BUT THE VERSION 2.2.3 DOES INCLUDE a correct file. So there must be some error on your side in that it still uses some old files.

If you want to edit the file look for Nexuiz/Nexuiz.app/Contents/MacOS/nexuiz-osx-ppc-agl and edit it in some text editor.. add -notexturenonpoweroftwo to the end of the last line. And then PLEASE find out why you still have that old file

Actually, to enter that file, you Control-click on Nexuiz.app and then "Show package contents". Then you can go in further until you can open nexuiz-osx-ppc-agl in TextEdit.

esteel wrote:Well yes but what did you do with the OLD Nexuiz 2.2.1? Meaning were did you put Nexuiz 2.2.1 and were do you put Nexuiz 2.2.3? To me it seems like both are kinda mixed..

I left 221 where it was, and opened 223 in a diffrent folder. Or to put it thusly:

home dir/games/nexuiz ƒ/nexuiz 2.2.1
home dir/downloads/nexuiz|nexuiz 2.2.3

No apps or files were moved between these directories. 221 was left where it was, and 223 was left in the directory where I expanded it. And I renamed .nexuiz/ to something else before trying 223.

If you want to edit the file look for Nexuiz/Nexuiz.app/Contents/MacOS/nexuiz-osx-ppc-agl and edit it in some text editor.. add -notexturenonpoweroftwo to the end of the last line. And then PLEASE find out why you still have that old file

Hmm.. It's the SDL version I'm using, and it doesn't have any .agl files - that I can see...

it's called the same with -sdl then