Regarding the "client not in focus" bug that Cunjo mentioned, I reported that with the old client here: http://www.vendetta-online.com/x/msgboard/4/6047

On another note: If you dock with a cap ship in a storm, when you launch you won't have an exit point anymore, but you can just fly to 3000m and jump as though you aren't in a storm (but the storm animation is still present).

The whole 'client not in focus' has been an issue for years. I have never tracked it down and don't understand why or how it happens, since full-screen directx apps can't not have focus.

I'll have to check out the capship problem.

I also tracked down the problems with group-mates no longer showing up as white radar blips and Doukutsu's lua errors.
I haven't had any problems with flashing the Options window and the HUD, though.

Rygel, if VO crashes again email me your errors.log file.

Odd bug, in Windoze. I was doing a timed Guild trade mission, died to the SF (stupid thing warped right on top of me as I was about to exit Azek), and respawned somewhere in Latos. I then tried to log off to set up my pad and I got the error in the screenie below but not in VO, but in Windows (you can see the VO site on the background). When I clicked OK, VO crashed to the ground. Odd.

http://paganserver.no-ip.org/joyce/VO_errors/lua_error.jpg

UPDATE: I restarted VO< and aborted the mission, but the timer remained running, and staid even when it ran out:

http://paganserver.no-ip.org/joyce/VO_errors/mission_error.jpg

And when I finally logged out, the same lua screen, same crash, same everything.

I want to repeat my issues with the navigation map, because I didn't see any acknowledgement that they had been seen:

- After logging into the new client, if I had used a manual navroute to where I currently am located on my previous login, one or more jumps of that navroute are put back into the navmap as if I hadn't arrived at my destination, even if I did.

- Setting a navroute, then doing something (I think it's something in the Options menus) will insert a navroute to the place where your navroute started from before the rest of the navroute, making you backtrack to where you started unless you clear the whole navroute and set it up again. Nasty, and bloody annoying.

A bug with speed while switching flight-assist on:

- turn flight-assist on
- set some speed
- turn flight-assist off
- change your speed
- turn flight-assist on and the speed changes back to what it last was with flight-assist on.

Maybe it was supposed to be a feature, not a bug ;) But if so, I personally prefer keeping my speed from when I have flight-assist off, especially when I'm surrounded by bots and turning flight-assist on drops me to 0.

Bug with character creation.

I was disconnected from the server when the name i tried to create was already taken.
2 windows popped up
1: "Conection failed: that character name is taken" in the new blue top with grey body style
2: "Character Creation failed that character name is taken" in the plain light blue pop up

the 2nd window stayed up after i clicked "ok" on the 1st, and prevented me from reconnecting.

I had to try and reconnect, cancel it, then the 2nd window became interactive and i was able to close it and connect normally.

info incase it's relevant...
Beta 7 os x macbook

Something I'd noticed while trying to message 0 was that instead of messaging 0, the thing would instead try to message someone named "ab" or "af" or just "a" or, in one case, "[". Quite curious. As best as I can tell, it's pretty much arbitrary. On the other hand, could be related to the message, since the two times I sent the same messate, the same pair of letters showed up as the intended recipient.

Mildly related: trying to hail a piece of cargo sends that hail to "sector." Thankfully, such a character does not exist, BUT WHAT IF IT DID!?!?!

"sector" exists... she just wasn't online. I had the same problem trying to /msg "0".

Ray, it seems radartoggle is no longer a command. How do we alias/bind to get objects off our radar in Beta 7?

It seems the problem is related to the truncated (") as it will not recognize radartoggle 9 (with the space)

Not acknowledging something on this thread doesn't mean I don't see it. Usually, it means that I am unable to duplicate the problem or that there's not enough info to duplicate the problem.

Relayer: I fixed the radartoggle problem., but don't understand why you say that's related to the " truncation issue.

jexkerome: Ok. I forgot to clear out the mission timer when you log out.

MSKanaka: I don't quite understand. I tried what you said earlier and didn't have any problems.

misiorysio: Do you have a joystick plugged in? That's the main reason the flight-assist speed reverts. Most joysticks have a throttle that is bound to the flight-assist speed and the speed always tries to be what the joystick setting is.

Cam: I tried that and didn't have any problems.

genka: Ok, I'll test that.

raybondo: no, I don't have a joystick or any kind of controllers except for keyboard and mouse...

I have an interesting background problem. This happends in every sector and any alt too.

http://i48.photobucket.com/albums/f214/TDStranger/Vendetta/dump0000.jpg
http://i48.photobucket.com/albums/f214/TDStranger/Vendetta/dump0001.jpg
http://i48.photobucket.com/albums/f214/TDStranger/Vendetta/dump0002.jpg
http://i48.photobucket.com/albums/f214/TDStranger/Vendetta/dump0003.jpg
http://i48.photobucket.com/albums/f214/TDStranger/Vendetta/dump0004.jpg
http://i48.photobucket.com/albums/f214/TDStranger/Vendetta/dump0005.jpg

Ray, the following is from a virgin wgaf.cfg file for beta 7:

alias toggleobjects "radartoggle 9"

When I tried to change the bind by typing /bind O toggleobjects, it returned 'no such command as toggleobjects'.
When I tried to re-write the alias as written (with a preceding /), it returned 'no such command as 'radartoggle' (without the 9) leading me to believe it truncated the "s and didn't recognize "radartoggle 9" as a command.

Okay. Here's more info on my first bug, or rather, another occurance.

Earlier today (this morning) I had been using the beta7 client. The last thing I did was fly to Odia M-14 (presumably from Sedina). When I fly from B-13 to M-14, I always stop in an empty sector on the way to avoid storms. In this case, the sector was I-16. I arrived at and docked at the station when I got to M-14. The nav map (when I entered the sector) did not show any navroute jumps.

I exited the game normally.

I came back to the beta7 client later tonight and when I went to enter a navroute to Verasi, there already was a navroute loaded on the map--from M-14 to I-16 and back. Dunno if that is helpful at all. I'll fiddle around a bit and see what causes the second one.

I'm having the same problem as Miharu, except I'm using Beta 6. (I'd love to test Beta 7, but it hardlocks the machine when trying to load the textures, etc.)

I've had he same problem as Miharu, on both beta6 and beta7(when I used it. That flashing green is painful).

Same here... it always seems to do that when I load beta 7

Ok. I'll try to duplicate that navmap thing.

relayer: radartoggle didn't exist, and that's why those aliases didn't get created. Aliases don't execute their code until they are called, so the alias definition didn't know that radartoggle didn't exist at that time. Anyways, It's fixed.

Been having a little bit of a problem with storage in stations. So I'm on a trade route, a bring some stuff over to another station and inload it, and when I come back with another load, the stuff is gone!
This does only happen occasionally, but its still really annoying. And...*tear*...my poor newbie characters wallet!

darn space rats!