Black screen in 2.2.3 too

[Clueless Newbie]

Basically - 2.2.3 seems to have the same problems as 2.2.2: I get a black screen with sound. I can click around in the darkness to enter menus that are also dark, and if I'm lucky, I'll click the right combos that'll get me into a server, after which the game plays normally.

That's the SDL version.

The non-SDL version seems to work normally, except 1) The keypad isn't mapped, which is bad since that's where I've got my controls, and 2) some of the projectiles don't show (such as the bouncy blue balls). There are also some odd visual artifacts on the screen.

I tried using the OS X build that was uploaded here some time ago, but it just told me to go to use the console to locate the files needed to play - even though the engine was in the Nexuiz folder.

But 2.2.1 still seems to be compatile with the servers, so I'll just keep on playing that and all is well. But I do worry that there will be a future Nexuiz build that breaks that compatibility and does not work on the mac.

[divVerent]

The problem is that it works on my Mac, so we need a developer who can look into it and has an AFFECTED Mac...

Also, the fix from the build that was uploaded before is applied to 2.2.3, so that shouldn't help at all.

[kozak6]

When updated the Mac at school, I got a blank screen with no sound. I didn't try clicking around, though. Didn't try the SDL version either.

However, after I got a fresh install, it started working properly again.

[divVerent]

That's odd, maybe the updating instructions do NOT work right and the Finder does something weird?

Oh wait... Mac OS X, Finder... HOW did you update?

Wrong way: copy the files from the update into the previous version. That works fine on Windows, KDE and GNOME, but Mac is different. It will replace the previous data directory by the one from the update and not just copy its files, so the data.........pk3 file gets lost in the process and doesn't even appear in the trash bin.

A working way to update on OS X works the other way round: Copy/move the contents of the data directory (the contents, not the whole directory!) into the update's data directory and play from the extracted update.

Another working way to update is using the command-line unzip tool to extract the patch over the full release.

[Clueless Newbie]

That's odd, maybe the updating instructions do NOT work right and the Finder does something weird?

Oh wait... Mac OS X, Finder... HOW did you update?

I didn't update. What I did was download the full version of 2.2.3, unpack it, and then play it as it was. No files were moved around.

[divVerent]

"However, after I got a fresh install, it started working properly again."

What was that then? Fresh install of what? Did you erase your Nexuiz config.cfg or what do you mean?

(OS X users usually don't reinstall their OS after slight problems... )

[kozak6]

Ah. I attempted to update the "wrong way."

That shows how much of a Mac user I am . Really, I have no idea what I'm doing, but it's just close enough to what I'm used to so that I can just sort of stumble along.

I also meant I reinstalled Nexuiz, or at least I did to the best of my abilities (which isn't really saying much).

[divVerent]

I doubt this is your fault - I'd say it is Apple's fault. But we can't expect Apple to change this. So basically we need some ideas for a way to update that works on OS X too...

[esteel]

I'm not familiar with mac.. but maybe we can use some sort of self extracting zip file?

[torus]

It seems that the main problem is that when you just "drag and drop" the patch, it overwrites the folder data with every thing in it with the new one, because there is a similarly named one in the origional. Then the "data" and "config.cfg" are gone. A self extracting zip for the patch itself might solve that (which extracts into the data directory and then deletes itself, which can be done i believe). However, an easier and less time consuming thing to do would just to include a README.txt that would explain how to patch.

Personally I think for Mac nexuiz all the relevant parts would be contained within the application package, instead of in an external "data" one, but thats just me, and it is more or less unnecessary, aside from the "mac congruency" of it .

That shows how much of a Mac user I am . Really, I have no idea what I'm doing, but it's just close enough to what I'm used to so that I can just sort of stumble along.

arg stop perpetuating the stereotype! *sigh* I wish it werent true though.