Curse client not working

My vanguard client crash a lot when use Curse client 0.10.5. Curse client removed : Fine.

Same here. Also when Curse client 0.10.5 running, Vanguard console window always opens. I tried to play with the option for console window in Curse client and restarting Vanguard client each time, but it had no effect. Only when I start Vanguard without Curse client in memory, console window doesn't open and Vanguard client works stable.

I'll look into this. I just released a new version of the extension to deal with the new update. It's possible I screwed up.

-edit- The console and log to file always being on was indeed a bug and has been fixed in my version. I haven't found a source of any crashes yet though.

asp,

vgdb.log shows the hash on several of the .dll files as being incorrect. whether or not you calculate the file hash or this is unreal's md5sum, i don't know.

also could you please fix the CurseClient so that if one exits CurseClient before they exit from Vanguard the game does not keep vgdb.log open ? (having to forcefully close the handle is a bit annoying :)

Hmm hashes should definitely not be wrong. You probably didn't get the new version yet but it should only take about 4 hours and there's about 8 between our posts.

The vgdb.log file is actually opened by Vanguard as I insert the extension into the memory of that process. So Windows will make the Vanguard process the owner. Closing the handle could probably cause weird stuff to happen ;P

I'll give the new version a try ;) Makes sense now, regarding vgdb.txt :)

Curse client 0.10.6 has same problem as 0.10.5. Always opens Vanguard console window. Option to turn it on/off seem to do nothing.

i know, it's fixed in 0.12 that we're releasing soon. 0.10.6 is a branch off of 0.10.5 and was a minor world of warcraft update.

49 carpentry :) 22 cleric

Oh! good to know. Thanks a lot.. I thought something that I'm doing wrong. Keep up a great work :)