Log in

View Full Version : Keyclone - Wow client crashing on zone



Nitro
04-22-2009, 03:12 PM
After patch 3.1 when i zone my borderless windows on my clients (keyclone maximizer) become bordered briefly and if I am doing something on one toon while another is in this state that client crashes. Makes wintergrasp very difficult.

Anyone else have this issue or a solution?


(5 boxing on a single pc)

Gurblash
04-22-2009, 03:28 PM
After patch 3.1 when i zone my borderless windows on my clients (keyclone maximizer) become bordered briefly

I noticed this while trying out HKN this weekend. I havn't experienced this while running Keyclone, last night worked great.

As to the crashing I typically load all 5 at the same time so I don't have the opportunity to do other things while other windows are loading.

Freddie
04-22-2009, 03:41 PM
I noticed this while trying out HKN this weekend.
Did WoW crash with HotkeyNet?

Gurblash
04-22-2009, 03:46 PM
I didn't have any issues with crashing. Just the borderless windows getting a border while loading screen, but they do go back to borderless once they are loaded again. /boggle.

Rin
04-22-2009, 04:04 PM
I've noticed this exact same thing, except my keyclone/wow won't actually crash. I do get the default keyclone disconnect sound (as if one of my wow sessions have ended), but it seems to restore itself within milliseconds... I should note that this is a rare occurance too, I've only had it happen about 2-3 times since 3.1 ... Since it hasn't actually interrupted my gameplay, I'm not sure what to make of this issue.

Nitro
04-23-2009, 01:25 PM
I've noticed this exact same thing, except my keyclone/wow won't actually crash. I do get the default keyclone disconnect sound (as if one of my wow sessions have ended), but it seems to restore itself within milliseconds... I should note that this is a rare occurance too, I've only had it happen about 2-3 times since 3.1 ... Since it hasn't actually interrupted my gameplay, I'm not sure what to make of this issue.

I get the default disconnected sound as well.

Nitro
04-23-2009, 01:27 PM
After patch 3.1 when i zone my borderless windows on my clients (keyclone maximizer) become bordered briefly

I noticed this while trying out HKN this weekend. I havn't experienced this while running Keyclone, last night worked great.

As to the crashing I typically load all 5 at the same time so I don't have the opportunity to do other things while other windows are loading.

The issue is if I am in wintergrasp fighting and one of my guys died the alliance can click release the body which sends that client to the loading screen. I would have to stop fighting on all clients to prevent a crash (and im sure my opponents would love that).

lans83
04-23-2009, 11:39 PM
put me on this list as well, except without the crashing (yet). i use Keyclone and get the same border/sounds and occasional white screen (where loadscreen should be) but that has only happened to me while porting to Dalaran so far. that actually only happened when i soloed my main for a bit with the screen maximized and Keyclone off. anyone experience that yet? all video effect settings are turned off btw, except for view distance and particle spell effects on main. those i keep up all the way so i can see AoEs being cast and of course see as far as possible.

Skaai
04-25-2009, 05:18 AM
If what is happening for you is the same thing that's been going on over here, it's not Keyclone. I've had these crashes happen when WoW is open in windowed mode, both maximized and not. The problem seems to happen when you tab out, or in my case, look at a few web pages on a 2nd screen while loading in areas. Sometimes it happens even when not looking at teh pron. I'm 94.553% sure it has something to do with WoW and not Keyclone.

ghonosyph and the moocrew
04-25-2009, 06:13 PM
im having the same problem! The wow clients when keyclone maximizes the clients, then when any client is zoning(even if you press alt tab) they get a little error that says "this program is not responding" giving you two options either end this process or cancel the action, problem is whenever you click or press any button while not focusing that wow window that parcticualr client crashes!

Not sure but i'm gonna try to Re-link my keyclone in command editor because i did a fresh reinstall after the patch destroyed my wow.

KEYCLONE! HELP US PLEEEEEEEZE!

keyclone
04-26-2009, 12:56 PM
?(

i haven't seen the issue yet, but i've spent my spare time with coding/testing and not playing... the only 'zoning' i'm doing is during login... not quite the same.

where is the most reliable place to go to reproduce this issue?

Senyens
04-27-2009, 02:39 AM
Does it everythime you zone so just zone and you will see it.

keyclone
04-27-2009, 02:09 PM
hmph. i'm not seeing this. what OS are you using? keyclone version? do you have any wow addons? which ones? have they been updated?

Senyens
04-27-2009, 08:44 PM
I am using 64bit Vista Ultimate on 1 and Home Premium on other macine, does it with or without addons and ones I am using are updated. I am not having the crash issue unless I click the window itself durning a zone or load then like anything else "not responding" it closes out. Using the newest keyclone that was on website v1.8k. It can be avoided the crashing part long as you dont click on the window when its happening. Only real annoying thing is the disconnect and reconnect sound from keyclone I hate to disable it just in case of a real disconnect in middle of something.



Also like somebody else stated I am not 100% sure this is even a keyclone issue as after some testing loading up 2 launcher clients and zoning clicking caused same thing a crash cause program was marked as "not responding"

ghonosyph and the moocrew
05-02-2009, 09:59 AM
found a fix that seems to be working for me on this issue... especially running vista**

right click your wow.exe shortcuts
click properties at the bottom
go to the compatibillity tab

then click the check box for run this program in compatibility mode for ... then go find and select the windows NT 4.0 setting

this seems to have been suggested on the wow forums and its solved my problem somewhat for now

14 pages on the blizzard forum on this problem and only 2 blue posts about it... ^ this is the only fix i found in those 14 pages