INC:
when i download a new client, I erase the older and start the new client alone.
ATM I'm at work so can't tell you which videocard im using, but as soon as i reach my home I'll tell you...
my screen resolution is on 1440/990 or something (can't remember)

Make sure you have the drivers folder in the vendetta_beta5 folder and that it isn't empty. From your post of the first few lines of your errors.log, it looks like vob5 didn't find any drivers at all, which is very strange indeed.
Just for a test, see if you can take the drivers folder from beta4 and put it into the beta5 folder and see if that works. Your videl settings won't be right, but at least it should run. And if you couldn't even run beta4, try beta3 or whatever last beta that actually worked on your computer.

Also, check the Console output of OSX. There's a Console app somewhere in the Applications folder (may be in a folder in there).

I'm not sure if these really count as bugs but, just to make you aware of them...

Flight control is different, such that turning with the mouse is slightly more difficult. Was the default sensitivity changed, or the underlying code modified?

Perspective is different, much more of a fisheye effect. Was the default value of this changed as well?

Finally, not a bug, but more an observation on scaling (again). Scrollbars become tiny little slivers and are difficult to grab at 1600x1200. I feel the best way to handle this overall is to allow the users to actualy scale the UI to thier liking. I want mine to look as proportional as 800x600 no matter my resolution, others might not.

Zyl: flight control shouldn't have changed at all.
Perspective hasn't changed at all, either. The FOV is the same as it was.
Scaling is not finalized, yet.

@ INC:
My video card settings ( french :p )

ATI Radeon X600 Pro :

Modèle de jeu de puces : ATY,RV370
Type : Moniteur
Bus : PCI
Logement : PCI-E
VRAM (totale) : 128 Mo
Fournisseur : ATI (0x1002)
Identifiant du périphérique : 0x5b62
Identifiant de révision : 0x0000
Révision de la ROM : 113-xxxxx-113

My screen resolution is 1440x900

BTW 10.4.5 IS RELEASED!

@ RAY:
I dunno why I'm doing that but since I receive a new client; I erased the old one... Damnit!
There is my drivers folder contents, tell me what's wrong:
osssound.amd64.so
directx9.dll
macsound.i386.dylib
macsound.dylib
gkgl.so
directx8.dll
refgl.dll
osssound.so
refgl.i386.dylib
refgl.dylib
gkalsa.amd64.so
cwavsound.dll
gkgl.amd64.so
gkalsa.so

hope that will help.

Sometimes when you leave a station, bring up the U or K options, you'll start firing and it will lock.
You don't stop firing untill you press the fire button again.

GRAIG: can you tell me if the .dylib files (ones without i386) are set to executable? Go into Terminal and go into the drivers directory and type ls -l and see if they have something like rwxrwxrwx.

KixKizzle: That's very odd. U and K aren't bound to fire at all. SO you're launching, floating in space, then press U or K and then your ship starts firing? What weapon group is it firing? The Primary, Secondary, or Tertiary?

the button to close the console is hardcoded to ` I traditionally have bound it to a different button. Which means that I can currently open the console with my button but have to close it with `

You guys forget that everytime you add a new dialog >.<

In-station Cargo Menu: I loaded some cargo "A" onto the ship (not enough to fill the hold), then selected cargo "B" (of which there was more than my ships capacity) and pressed "load". I received the "cargo hold is full" message, but the ship and station inventory didn't update. When i left the station, both the correct amounts of both cargo "A" and "B" had been loaded onto the ship.

(personal peave: there is still no option to load a specific amount of cargo from the in-station stores. It's still max or nothing)

yeah kix i sometimes have the same problem :D

its annoying though, but i haven't figured out what is the lead to it.

I noticed something funny last night.
I had a couple of mines I wanted to sell to a station as I was replacing them with different mines. I selected one of the mines and told it to sell two. Only one of the mines disappeared from my inventory, but the chat box said something like "2 concussion mines sold for xxxxxxx credits" what ever the amount was.
The it let me sell the other mine and I got the message that I'd sold it for half the credits of selling 2.
Then I did some tests.
I bought one prox mine and told it to sell 1200 and even 2400 prox mines. The chat box reflected that I had actually sold 1200 and 2400 prox mines for 1200 or 2400 x the selling price of a mine.
This however did not turn out to be a massive gold mine or anything as the actual amount of money I had, reflected that I had only sold one mine.
So ultimately it wasn't as serious as I had feared, but it is a bit odd.

Also, when trying to switch my audio driver from OSS to ALSA it repeatedly crashed. Don't know if this is a known issue or not.

same issue with firing almost immediately after leaving the station, it happens just sometimes and i don't think i hit any key at all. i will try to reproduce it and come back with more details.

i don't remember if it hapenned in previous beta clients or not.

If you're currently at a sub-cruising speed and are flying in Flight-Assist mode with throttle set to full, and you press 'u' to view the sector list, when you return to the cockpit, your throttle has reset itself to match whatever your current speed was.

so if you're still accelerating out of a wormhole or dock, youu will cease to accelerate (unless you're turboing, in which case your throttle just gets reset, but you continue to accelerate beyond your throttle) Same sort of thing with deceleration - breaking from the main cockpit screen resets your throttle to your current speed level.

on another note...

>/ping
no such command, 'ping'

>/verbose 2
no such command, 'verbose'

Please tell me there's a plan to get this functionality back...

Try to create a character. If the name already exists, the error logs you out.

Ray,
Well I usually open the player list with U, click on some name.
Then I press u again and its like that click never stopped clicking.
But its not just U or K.
You have to click right after you leave the station.
Or right after you press U.
Or something.

It was working fine last night, and every other time before that... what happened?

EDIT: NOOOOOOOOO!!!!!!

It's doing it on the general client too now... I can't get the game to work ><

Dihelical Synthesis: check your errors.log and directx log files. See if they have anything useful in them. Post them if you can.

WIll Roberts: I tried it and it didn't log me out. Can other people try to confirm this?