Please report Beta3 issues here. Again, focus is primarily on the bugs and crashes.

There's a torrent here for anyone who might be interested
http://www.vendetta-online.com/vo3_beta3.zip.torrent

Downloading. Will seed all night and all day tomorrow.

first off here is what I've got.

amd64 custom box
GeForce 6200 128mb
1gig ram

don't know what else you need. Please ask if you need more.

I had this problem with Beta2 but thought it was just because it was a 32bit binary and didn't like my 32bit libs.

Basicly it a video problem. On the login screen the station is very jurky in its spin. It acts like the video processing is taking a lot of cpu time. The audio actually suffers and has lots of rapid taps and pauses. I've got the "Visual Quality" setting on Low, haven't changed anything else and I still have the same problem. Never had this with the old client and I've got the settings on it cranked.

I've been messing with settings and no matter what I do the nothing changes. I have noticed that the audio only gets weird when there is a lot of vid stuff to do.

Does the production version have any problems at all? Or just the Beta(s)?

Just the betas. Only time I had problems with the production client was my fault.

Beta seems overall much more stable and final. Chat behaves as it should, but there is one...

BUG: The valk's lead indicators are still borked.

The valks indicators are borked, but other than that minot hiccup everything runs fine, now a few pages need to be completed, but thats already know and isnt really a bug now is it? ^^

Anyway this one is basically a production version.

Lua error when targeting a cargo crate left by a dead queen (IIRC): http://kolos.math.uni.lodz.pl/~grzywacz/lua1.jpg

Also, taking cargo makes the container disappear, but the glow is still there: http://kolos.math.uni.lodz.pl/~grzywacz/glow.jpg

HUD scaling doesn't work: http://kolos.math.uni.lodz.pl/~grzywacz/lua2.jpg

Question: how do I remove a key I've assigned to some action in preferences?

Credits still list some random names. :P

Loaded up the new client, logged into the character screen. Chose the alt and clicked Play. It sarted to load but then quit the application.

<blockquote>Lua error when targeting a cargo crate left by a dead queen (IIRC): http://kolos.math.uni.lodz.pl/~grzywacz/lua1.jpg </blockquote>

I get that with any cargo.

vo/vo_gamefuncs.lua:191: calling `TypeToObjectName' on bad self (number expected, got table)

ok, you can now group in the new UI... you cant switch sectors once grouped but you can group. :P

was able to create a group and invite another member, but my health bar dissapeared when he joined (or it might have just gone completely empty)

When i jumped through a wormhole to get to the BP mission I got the following

lua/iup/label.lua:16: parameter title has wrong value or is not initialized in label
stack traceback:
vo/error.lua:31: in function `logerror'
vo/vo_event.lua:52: in function <vo/vo_event.lua:46>
vo/vo_event.lua:68: in function `ProcessEvent'
vo/vo_gameevent.lua:513: in function <vo/vo_gameevent.lua:504>

Incidentally sometimes when i get a lua error in flight it brings a mousepointer up as well, when i close the LUA window all my keypresses go to chat, but i dont get any sort of chat prompt, and cant get control of my ship back without doing a /logoff and logging back in. (other times i have to open the console to get a mouse pointer, but thats not the problem)

Seeding...

Initial feedback: The "new" textures still look worse on Linux than on Windows; the HUD scaling is much worse at 1280x1024 than it was in beta2; amd64 feels smoother, but I can't tell without /fps

Im getting a lot of weird Lua error windows. Id love to 'report them back' but I see no button labeled 'report bug'

When my ship is smoking, I'm seeing smoke in my HUD. Theoretically this is cool; actually it just looks weird.

the new ship loading/buying UI appears to require more mouse clicks and time to accomplish the same task as in the old UI.

when you sell the first item in the list of items, the cursor does not reappear; you have to reclick an item on the list.

the station UI is sluggish; this can lead to accidentally selling the wrong things.

there is no 'undo' button on the 'sell' menu.

when you click on 'my ships', the 'current ship' is not automatically selected. this leads to confusion with, for example, the 'set preset' buttons.

the actual type of ship you are currently equipping is not listed in an obvious place; this leads to confusion.

the ship equip UI sometimes makes the square boxes on your ship picture turn red, and sometimes not red, for no apparent reason. the intuitive meaning of red is 'disabled' or 'malfunctioning', and it is confusing.

sometimes the square slot pictures 'bounce' when you unequip or equip an item. this is very confusing and annoying.

the ship equip UI screen is not intuitive; clicking on 'fast charge battery' for example prompts no change in the ship picture; a newbie would have a hard time understanding that you are supposed to click on the square picture on the lower portion of the ship picture, and then go back and click 'equip', in order to actually equip a battery.

these are bugs, since they prevent newbies from playing.

Same lua bug as everyone else when clicking on cargo OR trying to target a station.

Mac OSX 10.4.4

An add to my previous post with the vid problems.

I'm running gentoo and just sync and updated every possible thing I could. So I now have the newest nvidia drivers and what not but there is no change. Any way that /fps could be working on the next beta so I could get more info for you?

Hey Stranger, have you tried turning the shaders off? Cuz on the beta test client the shaders are on my default, and those'll really make your computer scream, especially if you've got a station in the backround.

If you re-setup your weapon groups, the leadoff indicator should work again.
It's a bug with the way the new client reacts to the data from the server.

moldyman, what OS and can you email me your errors.log file that is generated by VO to me and I can try to figure out why it's crashing.

roguelazer: what 'new' textures are you talking about? No textures changed between beta2 and beta3 except some asteroid textures. The HUD scaling didn't change either, so if you have some major problem, try to get me a screenshot and I can try to figure out what's causing the problem.

Don't worry if I didn't respond to any other bugs. I am reading all of them.

I'm seeding as well, about to try the new B3 client. That why we were down this AM?

The client crashed after I clicked "yes" in the "Would you like to buy back you last config" dialog. Here's the full error log for the session:

http://www.dualitymedia.com/~jonm/vendetta_test/errors.8G32.01.log

update: I haven't been able to reproduce this.