I got a weird bug that i have not noticed before when i use F5 to change scales on hud my shiip moves like im pressing the arrow keys. i went and lookede to make sure i don't have any double binds, i don't. it's really kinda of irratating but not a critical issue.

Woodstock

I have been having speed/memory issues as well.

I'm having the same problem as Swithun (except with Red Hat 9) - it takes up so much RAM that it starts using swap, which effectively locks up the machine (I left it loading for half an hour, and it was still sitting there, harddisk light flickering). It usually happens when I switch graphics settings (loads the high-res ones, then has to load the low-res ones afterwards).

Miharu's navroute problem (navroutes being preset when you start the client) is present, except it seems to manifest itself (occasionally) when you undock from a station. I'll post a screenshot and more explanation when I get home.

Nav box doesn't close when you press escape - really annoying. :S

Thanks for putting the old loading screen back in (with some modifications), though. :)

- Tol Kerhys

terribleCabbage: no need to make a screenshot. It's fixed.

Thanks for the bug reports again, everyone.

I managed to fix almost all of the bugs here. I haven't fixed the one when a couple of you launched from the station and couldn't move your ship.
It's very surprising that the new client is using up that much memory. In the Windows version, sitting at the login menu takes up only about 180 megs. I wonder if the lack of texture compression for some of you is causing the huge numbers?
Basically, the beta8 client preloads all the textures and objects so jumping between sectors would be faster. I am disabling that, though, so memory usage should be back to beta7 sizes. It should also be mostly the same as the production client.

Requiring texture compression would be a bad thing, since Linux nvidia drivers have a tendency to randomly corrupt compressed textures...

Wonderful.

VO betas already default texture compression to on for low ram video cards that support texture compression.

Oh that's why it was on one day. I thought I had accidently enabled it myself.

Yeah texture compression looks really sucky on linux.

There's a trend I've noticed - I don't know if it will help at all... but there's a certain tendency for bugs to occur with lag issues - I'm pretty sure my previous wormhole jump bugs were all connected to lag spikes. I've had the 'not-being-able-to-move-after-leaving-the-station' bug happen to me when I was getting lag as well.

It's really hard for me to reproduce those bugs, sorry I can't be of more help.

Process ID Process Name %CPU # Threads Real Memory Virtual Memory
425 vendettaclient 31.10 3 166.46 MB 513.11 MB

Above stats from a Dual 2GHz PowerPC G5 Tower, 1 GB RAM, ATI Radeon 9600 Pro 64 MB VRAM.
VERY CHOPPY. I'm composing this in the browser and I have to wait for the text to catch up with my typing. So, this is bad methinks. I turned texture compression off and everything is only marginally better.

However, when I turn texture compression off, looks like vendettaclient uses up 42% of available CPU cycles. I was just chatting in-station. I got ~10 fps the entire time. However, when I left the station, I got a respectable 40 fps without a station in my field of view, but the processor usage graph stayed at around 40% to 45%, and TextEdit was slowed down to a crawl as I had the two windows side-by-side.

Cursor will still go "off-screen" if I move it out of the window I was playing VO in. This is VERY annoying.

Anyway, that's the report from my work machine. I'll test it out on my iMac at home, but I hope that this speed/RAM/processor issue gets resolved. I would deem VO unplayable if beta 8 is released as the new client as it stands now.

I would suggest that (at least on the mac client) that Texture Compression defaults to "OFF"? It seems to cause problems.

Hrms.. I used texture compression on my G4 iBook with no problems on the production client, and all the betas that i've used (I've yet to download beta8.

Not to detract, but, Leber, welcome to my computer. I hope you run away from your variant as fast as you can.

To add to the texture compression comments, I have a 128meg video card (6600GT AGP) and the default settings in Windows/DirectX9 (I understand the Linux version doesn't do any autodetecting) for that memory size without compression (the default) produces lots of texture thrashing around stations (1-2 fps in the station window). Texture compression solves this.

PS: OpenGL really needs to get the iceyo texture effects. I hadn't seen them in person before now.

We're not going to disable texture compression.

LeberMac: what texture res are you using? 64 meg video cards seem to have the most problems with texture thrashing. Either lower the texture res or run in full-screen. Enabling texture compression should stop the texture thrashing, though.
Your work computer is more than enough to run VO. There's probably some other app running on your computer than is sucking up resources. I discovered a dashboard applet that caused VO to do exactly what you are saying. very choppy.
Do a top and see what else has a CPU usage greater than 0. Top will show up but you can ignore that one. However, I don't know if VO should show up as 50% or 100% cpu usage on a dual machine. We don't have a dual machine to test with.

I just made some tests on both my macs to get the following numbers:
---------------------------------------------------------------
imac G5 1.9GHz 1.5GB ram, 128MB video
using 1440x900, texture compression off, all settings on highest available.
---------------------------------------------------------------
- current client:
real ram: 60MB
virtual: 361MB
(80-90fps in Sedina B8)

- beta 8:
real ram: 419MB
virtual: 1.07GB
(50-60fps in Sedina B9)

---------------------------------------------------------------
ibook G4 1.33GHz 768MB ram, 32MB video
using 1024x768, texture compression off, all settings on low or medium
---------------------------------------------------------------
- current client:
real ram: 39MB
virtual: 190MB
(this runs much faster fps: ca 80fps in Sedina B8)

- beta 8:
real ram: 172MB
virtual: 421MB
(I can SEE it take the ram as VO loads the textures btw.)
(ca 35fps in Sedina B8)

So looking at this I think you should not load any textures that eat up real ram for the mac version. Looks like It loaded and ran much faster before. Seems the Mac OS X VM can handle the loading when needed quite well and apparently beta 8 settings only slow down things alot, instead of making them faster.

M. Duncan

Here is another bug screenshot. Happened as I got logged out, because I had logged in on the other computer with the same account. But only after like a minute or two, leaving the screen in "you have been logged out" mode. Then this popped up.

http://www.visual--media.com/beta8.png

Also, beta 8 always crashes in mac os x when i Apple-Quit anywhere during playing. current client doesnt crash.

M. Duncan

raybondo: Was runnning solely vendettaclient beta 8 and textedit at work, no other apps running in background at all. I even quit the Suitcase X background app. I forgot to mention I'm at OS X 10.4.4 at work.

Home testing coming along... (I'll test with the current prod client as well)

I just tried it again on my 1.9ghz g5 imac. same super slow load and bad frame-rates. Still cant create a new char.

Even the mouse moves around very jumpy. Mac beta 8 is definitely unplayable for me.

beta 7 is smooth like butter.

Edit: made sure i had no other apps running as well, just VO.

switched to window mode, turned on texture compression and pulled up activity monitor.

while flying around vo is using about 90% of processor power 167 megs of real mem and 629 megs of virtual, in station only slightly less.

Switched compression back off and me usage went to 144megs real and 1.04 gigs virtual.

seems like framerates are a little better with compression off but still low compared to beta 7 (I don't have numbers cause im not sure how to check framerate in game) cpu usage is in similar range as with compression on.

let me re-iterate, texture compression doesnt cause me any problems, my system is
iBook G4 1.67ghz
1G RAM
32M ATI Radeon Mobility
so.. your 64M card should be even better than mine...

/fps

my machine wont do 640x480 for some reason. old client will.
win2000, nvidia riva TNT2 16MB vidram, + system RAM for textures, pentium 733mhz, 256MB ram.

this would help my FPS a whole lot.