Recent Change broke DaoC?

WinEQ 2.0 Pro discussion and support

Moderators: Lavish Software Team, Moderators

Post Reply
JamieW
Non-Subscriber
Posts: 78
Joined: Fri Jul 15, 2005 3:27 pm

Recent Change broke DaoC?

Post by JamieW » Fri Sep 16, 2005 6:30 pm

DaoC had been working just fine for me, and with whatever the recent change that went in (patched today, and probably haven't patched in about 2 or 3 days), whenever I switch out of my DaoC window, it turns completely black to me when I go back, and moving around or resizing does nothing.

JamieW
Non-Subscriber
Posts: 78
Joined: Fri Jul 15, 2005 3:27 pm

Re: Recent Change broke DaoC?

Post by JamieW » Sun Sep 18, 2005 2:14 pm

JamieW wrote:DaoC had been working just fine for me, and with whatever the recent change that went in (patched today, and probably haven't patched in about 2 or 3 days), whenever I switch out of my DaoC window, it turns completely black to me when I go back, and moving around or resizing does nothing.
I should clarify, the character select screen appears to work fine, as well as loading screens. But whilst inside an actual game session, if I make my web-browser my foreground window, when I switch back to my DaoC session, the window is completely black. I can see on my other computer, my character still reacting to my inputs, so I know that it's just a display problem. Zoning or returning to the character select screen does not fix the problem (as I said those particular graphical screens will display, but upon returning to the actual game, it's all black).

It makes the product completely un-usable.

Lax
Owner
Posts: 6634
Joined: Fri Jun 18, 2004 6:08 pm

Post by Lax » Sun Sep 18, 2005 2:22 pm

I'm about to work on this. Are you using /clientsleep at all?

JamieW
Non-Subscriber
Posts: 78
Joined: Fri Jul 15, 2005 3:27 pm

Post by JamieW » Sun Sep 18, 2005 5:35 pm

Lax wrote:I'm about to work on this. Are you using /clientsleep at all?
Was set as background, I think it's been that way for as long as I've had WinEQ2 running, without problems.

Tried it with /clientsleep off, and it worked without a hitch.

Seen the note in the patch notes, about /clientsleep, so it appears that whatever change was made broke this for me.

Still running cats client.

BTW, thanks for quick response/help. Still loving the service from you. :D

Lax
Owner
Posts: 6634
Joined: Fri Jun 18, 2004 6:08 pm

Post by Lax » Sun Sep 18, 2005 7:53 pm

:roll: I was fixing a problem reported by a WinEQ Lite user, and I guess this must be another difference between Catacombs and Atlantis. I'll get this fixed up.

Lax
Owner
Posts: 6634
Joined: Fri Jun 18, 2004 6:08 pm

Post by Lax » Wed Sep 21, 2005 1:52 am

This should be fixed as of today's WinEQ 2 patch, please let me know

JamieW
Non-Subscriber
Posts: 78
Joined: Fri Jul 15, 2005 3:27 pm

Post by JamieW » Fri Sep 23, 2005 4:39 pm

Lax wrote:This should be fixed as of today's WinEQ 2 patch, please let me know
Haven't tried to set it to /clientsleep background again yet, with Catacombs client (although I tried it with ToA client, and I still have the black-screen problem with that client), but I have noticed the same problem described on the Win EQ2 Lite forum:

http://www.lavishsoft.com/forum/viewtopic.php?t=2121

I don't quite understand what your suggested fix was. I run Catacombs client, and the setting is still for Catacombs.

I tried going in and switching it to Atlantis, applying it, and then switching it back to Catacombs, and applying it, and the problem still persists.

I think whomever the OP for the problem was is getting around it by running TOA client, 'cause I tried that, and it worked for me also.

JamieW
Non-Subscriber
Posts: 78
Joined: Fri Jul 15, 2005 3:27 pm

Post by JamieW » Sun Sep 25, 2005 2:02 pm

Anything on this yet? I hate running ToA client.

Lax
Owner
Posts: 6634
Joined: Fri Jun 18, 2004 6:08 pm

Post by Lax » Mon Sep 26, 2005 11:47 am

This should be solved by today's WinEQ 2 patch.

JamieW
Non-Subscriber
Posts: 78
Joined: Fri Jul 15, 2005 3:27 pm

Post by JamieW » Thu Sep 29, 2005 6:43 pm

Lax wrote:This should be solved by today's WinEQ 2 patch.
Yup, looks to be working fine for me. Thanks again!

Post Reply