Howdy, I'm afraid I've got another bug to report. There seem to be triangular, wedge shaped "peices" missing from the background. I played around with the background settings and nothing changed it. Here's a picture:

http://img.photobucket.com/albums/v236/A-Dawg/Random%203/dump0007.jpg

Hope its helpful and keep up the good work!

On linux this happens with the old client too, when you switch to a different desktop and back (or something like that).
I think under heavy load I've seen that too. (or I just got bored from the load times and switched to a different desktop <.<)

Did you minimize/hide whatever the game?

Bug: Weapon grouping - When playing around with the weapon grouping for my Centaur (three fireflies, one neut, FC battery, in case it matters), it sometimes crashes out to desktop (seems to happen when selecting weapons, not when clicking the 'Apply' button). This has happened twice so far.

Log (snipped off everything before the crash, sans a few lines of chat):
http://kabukiyasha.net/public/weapon_grouping.error.log

(Using Linux IA32, AMD 2100+, nVidia GF4 440MX.)

The Leviathan is still borked.



(MacOS 10.4.5, Radeon 9000 Mobility)

The character creation screen disconnects you if the name you try is already taken.
Weird thing is, it pops up two dialogues, one fancy one, saying "character creation failed: that character name is taken. [ok]" and another one, of the old ugly variety that says "connection failied That character name is taken [ok]"

The connection failed one comes out on top, and while you can move it to get a look at the one on the bottom, you can't actually click [ok] on that one. Only on the connection failed one, and that takes you back to the login screen. (with the character creation failed dialogue still underneath)

Ray: I think the key to reproducing KixKizzle's problem is that you have to die while holding down the trigger. Then buy back your ship, launch, hit 'u'.

On another note, here's some bugs with the HUD related to grouping:
- The white dots on radar are buggy: sometimes group-mates don't show up white, and once I had a white dot on radar, but none of my group-mates weren't in the sector.
- At least once, the hull status bar for a group-mate didn't show up until I opened and closed the sector list. This was in a station sector, so I don't know if my HUD didn't refresh when he undocked or when he jumped into the sector, but at the time I opened & closed the sector list, he was flying right in front of me.

I confirm the buggy group-behavior in beta 5 client that Klox mentioned. NPC bots regularly showed up as white dots during Obsidian's group mining event Friday night. Never other players for me, it was always other bots or NPC's.

Number Named NPCs:



This one happened before the last jump of my route. After reclicking my destination on the navmap this message went away. I've never seen it before.

http://www.tumblemonster.com/temps/ErrorWH.jpg

[Edited by Lemming, Please remember that not everyone has really large monitors.]

Ok, I think the group bugs are fixed for the next beta.

I docked, set the station as my home, reloaded, then tried to unequip a gauss and the client crashed. This message was printed in the xterm I launched beta5 from:

pure virtual method called
terminate called without an active exception

and here's what was in errors.log:

caught SIGSEGV; generating stack trace
fault address 3f800000, 00000000
ss 0x0000007b 123
uesp 0xbfffd1cc -1073753652
efl 0x00210296 2163350
cs 0x00000073 115
eip 0x3f800000 1065353216
err 0x00000004 4
trapno 0x0000000e 14
eax 0x0af55340 183849792
ecx 0x0b04e950 184871248
edx 0x0b2f3f70 187645808
ebx 0x0a146300 169108224
esp 0xbfffd1cc -1073753652
ebp 0xbfffd1f8 -1073753608
esi 0x08e728d0 149366992
edi 0x43250000 1126498304
ds 0x0000007b 123
es 0x0000007b 123
fs 0x00000000 0
gs 0x00000033 51
brk> 3f800000: 08e728d0 43870000 43250000 00000000
- 08118ac6: 43870000 43250000 00000000 08498538
- 08052299: 43870000 43250000 00000000 bfffd3a0
- 00149407: 082e9f58 00000000 00000000 00000000
- 08056195: 00000000 00000000 00000000 00000000
- 080564e4: 00000001 bffff894 00000000 00000000
- 0805c42f: 00000001 bffff894 bffff89c b7fec6f0
- 00721ad4: 0805c3b0 00000001 bffff894 08049e38

caught SIGABRT; generating stack trace
fault address 00004e8a, 00200286
ss 0x0000007b 123
uesp 0x0181d868 25286760
efl 0x00200202 2097666
cs 0x00000073 115
eip 0x006f07a2 7276450
err 0x00000000 0
trapno 0x00000000 0
eax 0x00000000 0
ecx 0x00004e8b 20107
edx 0x00000006 6
ebx 0x00004e8a 20106
esp 0x0181d868 25286760
ebp 0x0181d87c 25286780
esi 0x00004e8b 20107
edi 0x00824fdc 8540124
ds 0x0000007b 123
es 0x0000007b 123
fs 0x00000000 0
gs 0x00000033 51
brk> 006f07a2: 00000006 0181d890 00000000 00000020
- 00735882: 08249158 008257c0 00706670 b7fec700
- 0821448f: 009678f8 00122120 083a9810 00000100
- 08212ce9: 08214460 00970134 0181da28 08213009
- 08212d13: 00000002 0824880e 0000001b 00122120
- 08213009: 082a460c 083a9810 00000003 00000100
- 00115ec4: 082f6fc8 0181daec 006fb860 0181daa4
- 00115f3c: 082f6fc8 0181daa4 00000000 00000000
- 0096a98c: 0181dbb0 00000000 00000000 00000000

Something else to note in Tumble's sizable screenshot, at the top of the chat field there are a few black bubble-like thingies I see every now and then. They're rather weird, but not really a problem or anything... Just weird...

For igni ferroque's problem (the levi textures), turning off shaders 'solves' the problem.
http://www.vendetta-online.com/x/msgboard/2/12948

Strange issue appearing, when fps is on, the game simpley refuse's to jump or update chat, undoing fps solves the problem.

Shameless ploy: Replace that ad of the front page with mine! ^^

Something else to note in Tumble's sizable screenshot, at the top of the chat field there are a few black bubble-like thingies I see every now and then.

Wow, sure enough. I'm not hallucinating after all!

For igni ferroque's problem (the levi textures), turning off shaders 'solves' the problem.
Sure enough, it did. The auto-config should probably be tweaked accordingly.

The last thing we need in this thread are advertisement images. Go make your own thread so we can get on with reporting bugs without having to scroll past any banners/eyesores.

Regarding the bug I posted earlier about weapon grouping screen - it appears the problem is common to the Ship Equipment screen as well (I tried to equip a NeutMk2 to the left port on my hornet).

When crashing out, I get the following errors on the console:

[rhoward@cerberus vendetta_beta5]$ ./vendetta3.linux.ia32
Xlib: extension "XFree86-DRI" missing on display ":0.0". <-- Normal for me.
pure virtual method called
terminate called without an active exception
[rhoward@cerberus vendetta_beta5]$

My error log (snipped to the crash, let me know if you need the full thing):

[Mon Feb 20 00:09:04 2006] ^?ff0000*IRC* Thank you.
[Mon Feb 20 00:09:08 2006] ^?28b4f0[100] <Tol Kerhys> :D
[Mon Feb 20 00:09:09 2006] ^?28b4f0[100] <Eternas> My game svcreen went black :( so i reduced all graphs to medium...
[Mon Feb 20 00:09:11 2006] ^?28b4f0[100] <Tol Kerhys> :S
[Mon Feb 20 00:09:29 2006] ^?28b4f0[100] <Eternas> But, wraith MK2 (cargorunner) or normal wraith?

caught SIGSEGV; generating stack trace
fault address 0000006c, 00000000
ss 0x0000002b 43
uesp 0xbfffbce0 -1073759008
efl 0x00010296 66198
cs 0x00000023 35
eip 0x081187f6 135366646
err 0x00000004 4
trapno 0x0000000e 14
eax 0x00000000 0
ecx 0x09568360 156664672
edx 0x0950c368 156287848
ebx 0x09567f00 156663552
esp 0xbfffbce0 -1073759008
ebp 0xbfffbd08 -1073758968
esi 0x08d92820 148449312
edi 0x431f0000 1126105088
ds 0x0000002b 43
es 0x0000002b 43
fs 0x00000000 0
gs 0x00000033 51
brk> 081187f6: 08d92820 43890000 431f0000 00000000
- 08118ac6: 43890000 431f0000 00000000 08417a48
- 08052299: 43890000 431f0000 00000000 bfffbeb0
- 401c3407: 082e9490 00000000 00000000 00000000
- 08056195: 00000000 00000000 00000000 00000000
- 080564e4: 00000001 bfffe364 00000000 00000000
- 0805c42f: 00000001 bfffe364 bfffe36c 400154f0
- 42015704: 0805c3b0 00000001 bfffe364 08049e38

caught SIGABRT; generating stack trace
fault address 00000815, 08249158
ss 0x0000002b 43
uesp 0x40d58868 1087735912
efl 0x00000202 514
cs 0x00000023 35
eip 0xffffe002 -8190
err 0x00000000 0
trapno 0x00000000 0
eax 0x00000000 0
ecx 0x00000006 6
edx 0x421328d4 1108551892
ebx 0x00000815 2069
esp 0x40d58868 1087735912
ebp 0x40d58870 1087735920
esi 0x00000000 0
edi 0x00000100 256
ds 0x0000002b 43
es 0x0000002b 43
fs 0x00000000 0
gs 0x00000033 51
brk> ffffe002: 00000006 40d58888 00000000 4006f750
- 42028c55: 08249158 42130e60 40d58a00 0813d954
- 0821448f: 4016285c 40335120 4016907b 00000100
- 08212ce9: 08214460 40169424 40d58a20 08213009
- 08212d13: 00000002 0824880e 0000001b 00000004
- 08213009: 082a460c 082f5e10 00000003 00000100
- 40328ec4: 082ed5f0 40d58a94 4000c2c0 00002198
- 40328f3c: 082ed5f0 40d58d20 00000000 40d58b30
- 40165484: 40d58b30 00000000 00000000 00000000

Hope that helps,
Tol Kerhys

karol@omoikane vendetta_beta5% ./vendetta3.linux.ia32
pure virtual method called
terminate called without an active exception
*** glibc detected *** double free or corruption (!prev): 0x082e2118 ***
zsh: abort ./vendetta3.linux.ia32

caught SIGSEGV; generating stack trace
fault address 3f800000, 00000000
ss 0x0000007b 123
uesp 0xbfec3e9c -1075036516
efl 0x00010292 66194
cs 0x00000073 115
eip 0x3f800000 1065353216
err 0x00000004 4
trapno 0x0000000e 14
eax 0x0a69a360 174695264
ecx 0x0b81cff0 193056752
edx 0x0b795e28 192503336
ebx 0x0ae94508 183059720
esp 0xbfec3e9c -1075036516
ebp 0xbfec3ec8 -1075036472
esi 0x08ee9c48 149855304
edi 0x434f0000 1129250816
ds 0x0000007b 123
es 0x0000007b 123
fs 0x00000000 0
gs 0x00000033 51
brk> 3f800000: 08ee9c48 43978000 434f0000 00000000
- 08118ac6: 43978000 434f0000 00000000 0850e908
- 08052299: 43978000 434f0000 00000000 bfec4070
- b7350407: 082ebd48 00000000 00000000 00000000
- 08056195: 00000000 00000000 00000000 00000000
- 080564e4: 00000001 bfec6554 00000000 00000000
- 0805c42f: 00000001 bfec6554 bfec655c 00000001
- b7cdeeb0: 0805c3b0 00000001 bfec6554 08049e38

Tried to unequip a newly bought iceflare launcher from my hornet. I remember seeing it red on the equipement screen.

Freak bug. I was warping from Latos H-2 to Azek, when I got stuck in the loading screen. I clicked Cancel and got nothing, though error.log showed this:

[Sun Feb 19 19:51:28 2006] ffffff10 seconds to logoff
[Sun Feb 19 19:51:29 2006] ffffffLogoff aborted.
[Sun Feb 19 19:51:30 2006] ffffff10 seconds to logoff
[Sun Feb 19 19:51:30 2006] ffffffLogoff aborted.
[Sun Feb 19 19:51:32 2006] ffffff10 seconds to logoff
[Sun Feb 19 19:51:32 2006] ffffffLogoff aborted.
[Sun Feb 19 19:51:33 2006] ffffff10 seconds to logoff
[Sun Feb 19 19:51:33 2006] ffffffLogoff aborted.
[Sun Feb 19 19:51:33 2006] ffffff10 seconds to logoff
[Sun Feb 19 19:51:33 2006] ffffffLogoff aborted.

There was no way to get a screenie. Even if there was, you'd see nothing but the "speeding through space..." box

If you type a number in the amount box when selling an item that is greater than the amount you have, the report in chat upon clicking 'sell' will say you have sold x number of the item for a total amount of x*price, even if x is not the number you had or actually sold (you do not actually *recieve* the amount of cash it specifies)

for example, if I have 1 empty Behemoth, and I type 144 in the amount box and click sell with the Behemoth selected, it will say that 144 of Behemoth has been sold for a total amount of 1669700c (or some equally profane number)

Also, when loading/unloading cargo, the selection remains on the place in the list where the cargo was after moving it. The selection *should* go away once you move it, to prevent confusion and minimize mouse-clicks (i.e., you shouldn't have to first deselect the item that moved up in the list before selecting a new item to load)

I've also been getting these, seemably at random... this last one was while I was AFK in a station:
"Error! trying to update object(4:531)

[02/20/06 13:46:41] 28b4f0Error! trying to update object(4:531)"

Oh yeah .. wanted to report that for a while already

related to this. if you enter a negative amount you'll sell all you have of the item in the station.