The first one worked for me. Dunno what the diff is.

Strange, I havent had any issues with connecting on my mac. O.o secret ghost code this is. ^^ lol

while in 800x600 in XP, if you fly faster than 200, the 2 gets clipped

Great update, thanks for putting back the old colors, they are really much more easy on the eyes.

Hittin ESC during warps no longer brings up the option screen. I use this a lot when in window mode so I can free up the mouse pointer to move into another window (dual monitor setup).

The "window" widget's sharp blue titlebar with the box and the "x" button doesn't match the overall in-game-embedded, translucent feel of the UI. To be honest, it's butt ugly.

Options menu keyboard shortcuts are missing.

/fps and /ping not working (haven't checked all /commands, but at least these were missing)

"MouseLook on/off" messages have an extra newline. Same for the output of for example "/print 0". Maybe not so serious, but it takes up precious vertical space in the chat window.

"Speeding through space..." better replaced by something (warp animation, chat window, anything...). When I was a n00b I liked the tips displayed during jumps. They add a lot of atmosphere and the information is actually useful to new players.

Got some errors when entering the game:
Error! trying to remove object(2:1141)
Error! trying to remove object(4:25958)
Current Location: Geira Rutilus O-4
Current ship: SVG

Suggestion: In menus with shortcuts and a text input box, Alt+Key should be equivalent to hitting Key when focus is not in the text input.

Suggestion: leave chat boxes open when returning to station or warping. Those are situations where people often get an urge to talk :-)

NOoooooo!!! How dare you insult the loading scren!!! I love that loading screen!!!! I wish I had really SLOW internet just so I could stare at "Speeding through space..." all day!!! When you make all the changes, at least leave "Speeding through space..." as an option or something, :D

-Calder

Leber, nuthou5e:
try my fix in the original thread...
turn shaders off (config.ini... "doshaders=0")! or if that doesn't work, try setting all fields in your config.ini that are 1 to 0 and turn texture resolution to 8 (may default to 32 or 64) this worked for me on the original beta. Incarnate walked me through this and said (since mine then worked) to restore each 0 value (that was changed) back to 1 to repeat the error. One at a time, then launch the client!
I was never able to repeat the error, I am thinking that it was the config.ini always setting "doshaders=0" even though I'd set them to 1, which led me to believe that it was the shaders...

Person: I think you prolly have an ATI Radeon 7500 in that G4800mhz, it's the same as the one I have at work.

minor annoyances:
dont' know if these are from the first client or not.

Newsposts are very difficult to read with the transparent pop-up window. Nice effect, but they are a bit too transparent, and should not cover up the chat window so much, if at all.

since we are getting a new UI, I noticed the nav-map window has a very small map, but with a larger than normal chat window. Could we get the map a bit larger? mine's kinda small it seems. Also, the right window used for sector info could be split into sector info and a screen that lists the nav route you've selected. (just a thought)

I'm getting the same Valk targeting bug as mentioned a few times before.

Lastly (so far) I have 4 Valks in Jallik. Listed in "Commerce" are two with 3 Gauss Mk2, then a Valk with 3 Fletchettes Mk2, then another Gauss Valk. When I go to the SHIP tab, then to the YOUR SHIPS sub-tab, The Fletchette Valk is listed 2nd instead of 3rd. This can get confusing when trying to pick a certain loadout. Perhaps a simple display of the loadout on the YOUR SHIPS tab would solve this.

heres an interesting bug i was using the new client.. jumped into a new sector.. got the "speeding through space" box then.. the desktop.. the program just closed.

heres the last part of the error log with the exception in it, I edited out the full name of the location the game is in just because its in a folder with my real name.

[01/23/06 12:51:21] 28b4f0[100] <RelayeR> sry, couldn't resist
[01/23/06 12:51:21] 28b4f0[100] <Spellcast> ahh
00400000h 2002944 vendetta3.exe C:\<blahblahblah>\test client install\vendetta_beta2\vendetta3.exe
00D30000h 507904 directx8.dll C:\<blahblahblah>\test client install\vendetta_beta2\drivers\directx8.dll
00DD0000h 659456 directx9.dll C:\<blahblahblah>\test client install\vendetta_beta2\drivers\directx9.dll
00EA0000h 249856 refgl.dll C:<blahblahblah>\test client install\vendetta_beta2\drivers\refgl.dll
011A0000h 102400 McVSSkt.dll c:\progra~1\mcafee.com\vso\McVSSkt.dll
01390000h 65536 ctagent.dll C:\WINDOWS\system32\ctagent.dll
10000000h 110592 cwavsound.dll C:\<blahblahblah>\test client install\vendetta_beta2\drivers\cwavsound.dll
4FDD0000h 1728512 d3d9.dll C:\WINDOWS\system32\d3d9.dll
59A60000h 659456 dbghelp.dll C:\WINDOWS\system32\dbghelp.dll
5AD70000h 229376 uxtheme.dll C:\WINDOWS\system32\uxtheme.dll
5ED00000h 835584 OPENGL32.dll C:\WINDOWS\system32\OPENGL32.dll
662B0000h 360448 hnetcfg.dll C:\WINDOWS\system32\hnetcfg.dll
688F0000h 36864 HID.DLL C:\WINDOWS\system32\HID.DLL
68B20000h 131072 GLU32.dll C:\WINDOWS\system32\GLU32.dll
6D990000h 24576 d3d8thk.dll C:\WINDOWS\system32\d3d8thk.dll
6D9A0000h 1212416 d3d8.dll C:\WINDOWS\system32\d3d8.dll
71A50000h 258048 mswsock.dll C:\WINDOWS\system32\mswsock.dll
71A90000h 32768 wshtcpip.dll C:\WINDOWS\System32\wshtcpip.dll
71AA0000h 32768 WS2HELP.dll C:\WINDOWS\system32\WS2HELP.dll
71AB0000h 94208 WS2_32.dll C:\WINDOWS\system32\WS2_32.dll
71AD0000h 36864 WSOCK32.dll C:\WINDOWS\system32\WSOCK32.dll
72280000h 172032 DINPUT.dll C:\WINDOWS\system32\DINPUT.dll
72D10000h 32768 msacm32.drv C:\WINDOWS\system32\msacm32.drv
72D20000h 36864 wdmaud.drv C:\WINDOWS\system32\wdmaud.drv
73760000h 299008 DDRAW.dll C:\WINDOWS\system32\DDRAW.dll
73BC0000h 24576 DCIMAN32.dll C:\WINDOWS\system32\DCIMAN32.dll
76B40000h 184320 WINMM.dll C:\WINDOWS\system32\WINMM.dll
76C30000h 188416 WINTRUST.dll C:\WINDOWS\system32\WINTRUST.dll
76C90000h 163840 IMAGEHLP.dll C:\WINDOWS\system32\IMAGEHLP.dll
76F20000h 159744 DNSAPI.dll C:\WINDOWS\system32\DNSAPI.dll
76F60000h 180224 WLDAP32.dll C:\WINDOWS\system32\WLDAP32.dll
76FB0000h 32768 winrnr.dll C:\WINDOWS\System32\winrnr.dll
76FC0000h 24576 rasadhlp.dll C:\WINDOWS\system32\rasadhlp.dll
774E0000h 1298432 ole32.dll C:\WINDOWS\system32\ole32.dll
77920000h 995328 SETUPAPI.DLL C:\WINDOWS\system32\SETUPAPI.DLL
77A80000h 606208 CRYPT32.dll C:\WINDOWS\system32\CRYPT32.dll
77B20000h 73728 MSASN1.dll C:\WINDOWS\system32\MSASN1.dll
77BD0000h 28672 midimap.dll C:\WINDOWS\system32\midimap.dll
77BE0000h 86016 MSACM32.dll C:\WINDOWS\system32\MSACM32.dll
77C00000h 32768 VERSION.dll C:\WINDOWS\system32\VERSION.dll
77C10000h 360448 msvcrt.dll C:\WINDOWS\system32\msvcrt.dll
77D40000h 589824 USER32.dll C:\WINDOWS\system32\USER32.dll
77DD0000h 634880 ADVAPI32.dll C:\WINDOWS\system32\ADVAPI32.dll
77E70000h 593920 RPCRT4.dll C:\WINDOWS\system32\RPCRT4.dll
77F10000h 290816 GDI32.dll C:\WINDOWS\system32\GDI32.dll
7C800000h 999424 kernel32.dll C:\WINDOWS\system32\kernel32.dll
7C900000h 720896 ntdll.dll C:\WINDOWS\system32\ntdll.dll


Windows 5.01.2600 (platform 2) Service Pack 2
ExceptionCode: 0xc0000005 Access Violation
ExceptionFlags: 0x00000000
ExceptionRecord: 0x00000000
ExceptionAddress: 0x004C76E2
NumberParameters: 2
0x00000000
0x00000000



ContextFlags: 0x0001003f
EFlags: 0x00010246
ds 0x00000023 35
es 0x00000023 35
fs 0x0000003b 59
gs 0x00000000 0
cs 0x0000001b 27
ss 0x00000023 35
eax 0x038e2b90 59648912
ecx 0x038e2b90 59648912
edx 0x00000000 0
ebx 0x03928900 59934976
esi 0x038b7f20 59473696
edi 0x0390c0e8 59818216
ebp 0x0012c92c 1231148
eip 0x004c76e2 5011170
esp 0x0012c8ec 1231084
brk> 004c76e2: 03bcd528 02225930 022258d8 00000000
- 004222a1: 022258d8 8da8dfab 0012dd50 02225998
- 004f4a7f: 022259a0 8da8df87 02225998 03322228
- 004edbc2: 00584360 0012d004 004a83d8 0012d01c
- 004a82a2: 0012d01c 036f92a8 0012d06c 0040ed01
- 004a83d8: 0012d01c 00000076 036f92a8 00000185
- 0040ed01: 00000076 00000185 00008153 037180f0
- 00457b1c: 036f92a8 8da8c1fb 02156761 0012d1f4
- 00459d91: 000000c9 8da8c1b7 02156761 00ce36bc
- 004579b4: 0012d1f4 8da8c40f 0000007e 021556b0
- 0045aad0: 021556b0 00000005 02156761 0000007e
- 0049a48a: 0012d468 8da8c48f 021556c0 021556b0
- 0049a769: 020c19c8 0012f678 00000010 00000088
- 0049a970: 00000001 00e93a28 005b122c 7c910738
- 0049816f: 000001c0 00000002 0012d5c8 00416c01
- 004981ed: 001e0222 000001c0 00000001 00000000
- 00416c01: 001e0222 00001412 000001c0 00000001
- 77d48734: 00416aa0 001e0222 00001412 000001c0
- 77d48816: 00000000 00416aa0 001e0222 00001412
- 77d4c63f: 00416aa0 001e0222 00001412 000001c0
- 77d4e905: 00416aa0 001e0222 00001412 000001c0
- 4fdf6407: 00416aa0 00001412 000001c0 00000001
- 77d48734: 4fdf6040 001e0222 00001412 000001c0
- 77d48816: 00000000 4fdf6040 001e0222 00001412
- 77d4c63f: ffff0119 001e0222 00001412 000001c0
- 77d4c665: ffff0119 001e0222 00001412 000001c0
- 7229601d: 001e0222 00001412 000001c0 00000001
- 72296343: 002404d8 001e0222 00001412 000001c0
- 722963b2: 001e0222 00001412 000001c0 00000001
- 7228ff09: 001e0222 00001412 000001c0 00000001
- 72296343: 002404d8 001e0222 00001412 000001c0
- 72296422: 001e0222 00001412 000001c0 00000001
- 77d48734: 722963d0 001e0222 00001412 000001c0
- 77d48816: 00000000 722963d0 001e0222 00001412
- 77d489cd: 0012d9d4 00000001 0012d9f0 0049843c
- 77d496c7: 0012d9d4 00c02b90 00c184f8 001e0222
- 0049843c: 00000000 0009001f 0012fd10 00409551
- 004092f6: 8da8ed7f 00000000 00000000 001e0222
- 00409551: 00000001 00c02b90 8da8ed27 00c02b90
- 0040de0d: 00000001 00c02b90 00010000 00030000
- 004178e3: 00400000 00000000 0015239e 00000001
- 004d1ed0: 0171dd60 7c90e1fe 7ffd8000 805502fa
- 7c816d4f: 004d1f39 00000000 78746341 00000020

It dies when trying to load all the initial files. I tried running the binary in the package in terminal, and it couldn't find the bugreport.app, dunno if that has anything to do with it. Either way, it dies pretty quickly.

dimpfinator$ /Users/dimpfinator/Desktop/vendetta_beta2/vendettaclient.app/Contents/MacOS/vendettaclient; exit
2006-01-23 11:40:55.241 open[1895] No such file: /Users/dimpfinator/Desktop/vendetta_beta2/BugReport.app

Harry Seldon,
You have to be in the directory when you run the exe:

cd /Users/dimpfinator/Desktop/vendetta_beta2
./vendettaclient.app/Contents/MacOS/vendettaclient

Err. I copied in what happened in terminal when double-clicking the exe. However, "properly" executing it in terminal using the following resulted in a crash as well:

dimpfinator$ cd /Users/dimpfinator/Desktop/vendetta_beta2/vendettaclient.app/Contents/MacOS/
~/Desktop/vendetta_beta2/vendettaclient.app/Contents/MacOS dimpfinator$ ./vendettaclient
2006-01-23 12:38:59.724 open[1948] No such file: /Users/dimpfinator/Desktop/vendetta_beta2/BugReport.app

The program makes it into the loading screen, loads some stuff, and I see the screen resolution changing back to 1024*768 from 800*600. That's about it. I'll try to see how far it gets in loading now...

Oh, and before I forget:
10.4.2, Powerbook 12", 1.33ghz with 1280mb RAM.

I've posted the error log here: http://www.vendetta-online.com/x/msgboard/2/12747

Let's try to keep our error logs there, and link to them...that way this stays clean-ish and readable.

I saw this bug last night:

In Sedina, I killed a queen and followed the remaining bots to the Leviathan's sector. (I killed very few bots, so most of the bastion jumped.) When I jumped in, over half of the dots on radar were green, but I could visually determine that they were all hive bots. I'm guessing that the green dots were the dead queen's bastion, just arriving in the sector.

A few seconds after arriving, a small lua error message box appeared in the middle of the screen. I didn't try to resize it to read the text (the text didn't fit in the message box), since I was rather vulnerable amongst all those bots. Instead, I tried openning the console and /logoff, but I was kicked back to the login screen before I finished typing.

I logged back in with the released client and everything was fine (red dots on radar).

Don't know if this is a bug or "feature"...
I loaded DX9 with the new client, which works better than it did with the old client (for me, anyway). What I noticed, however, in certain sectors (I was in Verasi), there are dozens of red glowing dots(fixed points in 3d space) sprinkled throughout various areas. They don't do anything but glow, and they weren't always present. Did I just not see them with DX8?

Setting everything to zero worked kernel.panic. thanks.

I get Lua errors everytime i try to duel in the new client.

Will: Did the red lights apear in station sectors? If so, did they resemble the red lights on the station antenni...only not blinking?

Relayer, they looked a lot like the antenna lights, like you said, but there were a lot of them. I never saw them in a station sector, but I saw them in Verasi H-6 (empty sector) and a couple other bot sectors among the asteroids.

Ahhhh thought i was seeing things, saw one of the 'lights' in Latos O-12 just floating there. Agreed i does look like an antenna light in the 'on' pulse.
I thought it was a left over shot from some weapons fire.

Maybe the're the souls of dead NPC cargo pilots.......

Waylon did something that resulted in those lights appearing in Sedina a long time ago.

I'll look for the thread...

http://www.vendetta-online.com/x/msgboard/2/6849#84326

Seems the error was repeated with the new client?

Ok, I think I found the crashing problem on macosx.
As a test, edit the config.ini file and set tc=0 and see if everyone who was crashing on the mac can run again.

Also, anyone who is interested in helping me privately test a mac intel version email me and hope it doesn't get filtered out as spam ;)

(edit: changed do_vertexshaders to tc)