Close
Page 3 of 3 FirstFirst 1 2 3
Showing results 21 to 24 of 24
  1. #21

    Default

    Quote Originally Posted by Ughmahedhurtz View Post
    It's not gonna be a Keyclone problem.
    Wow... It IS a Keyclone problem, probably the same problems ISBoxer had back in the days (don't know what Lax had to change)...

  2. #22
    Member Ughmahedhurtz's Avatar
    Join Date
    Jul 2007
    Location
    North of The Wall, South of The Line
    Posts
    7169

    Default

    Quote Originally Posted by cmeche View Post
    No, on a normal pc. I finally figured out the basics of hkn and got that working fine. At least now, if a rift window closes unexpectedly, I get a rift error message. It only completely disappears with no explanation with keyclone.
    Quote Originally Posted by Klesh View Post
    Wow... It IS a Keyclone problem, probably the same problems ISBoxer had back in the days (don't know what Lax had to change)...
    I read that as it's failing with keyclone and HKN, the only difference is that due to the differences in UI hooking between the two, the crash either displays an error or does not. The root cause of the problem is not keyclone or HKN. I'd bet money on it.
    Now playing: WoW (Garona)

  3. #23

    Default

    If you'd read the complete thread, you'd see I've had random clients crashing every couple minute. Switching to HKN stopped my crashes completely.
    Ya, the reason for the crashes is probably the way Keyclone is sending the keystrokes to each window. As mentioned before, ISBoxer had such crashing problems too back in 2011 or so (which got fixed by Lax).

  4. #24
    Member Ughmahedhurtz's Avatar
    Join Date
    Jul 2007
    Location
    North of The Wall, South of The Line
    Posts
    7169

    Default

    Quote Originally Posted by Klesh View Post
    If you'd read the complete thread, you'd see I've had random clients crashing every couple minute. Switching to HKN stopped my crashes completely.
    Ya, the reason for the crashes is probably the way Keyclone is sending the keystrokes to each window. As mentioned before, ISBoxer had such crashing problems too back in 2011 or so (which got fixed by Lax).
    Doh. Missed the one post that had the relevant info in it. :P Correction acknowledged. In that case, yes, you're probably on the right track with regards to root cause.
    Now playing: WoW (Garona)

Posting Rules

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •