Forums » Bugs

Group creation bug for grouped missions

May 08, 2010 Aticephyr link
I was grouped with a 1/1/-/1/- and was showing him around greyspace, when I took a Hive skirmish. When I took the skirmish mission (which he certainly did not have the levels for), the newbie no longer showed up as in the group, but I could still hear him over group chat (though he no longer showed up as a white dot on my radar). I'm 99% sure he couldn't hear my group chat though (hard to tell since he's so newb).

I then left the group to create a new group, but I could still see his group chat (he still couldn't see mine). I was able to /group invite him while I was still seeing his group chat, and told him via pm to /leave group (which he did just fine) then re-joined the new non-mission group and everything was normal.

note: momerath, this is not the bug I PM'd you about. I haven't figured out how to repro that one yet.
May 14, 2010 socialSavant link
Similar group bug happened to me last night:
I was invited to join a group which had already begun a BP mission. Once it was completed the group leader got another BP mission. When the mission started it displayed some tags that I am certain are supposed to stay hidden to me: <hudtext>...</hudtext>. This happened twice in a row in exactly the same way. I got a screendump if you would like to see it.

Also, I think I started getting a memory leak (related? who knows?) and had the fastest/worst crashes in VO to date. The client Crashed To Desktop four times in only a matter of maybe an hour, each time my comp got slower and less responsive, and finally Vendetta would no longer load.

I am still reinstalling in an effort to get back ingame... will post later what I find out if I ever get it working again.
May 14, 2010 socialSavant link
Update:
Ignore the earlier part about getting the client to start at all. A bug yes, but completely unrelated. It had to do with an update that happened overnight on my comp which broke the GLX system causing me to reinstall my video driver. It works now and I will maybe post a seperate bug elsewhere when I have more details.