Log in

View Full Version : [Everquest] 2nd Window Hanging/Freezing



Alge
02-16-2011, 03:03 AM
Hi Folks,

I've just started dual-boxing EQ. I'm running Inner Space, ISBoxer and WinEQ.

I'm using a window layout with regions on two monitors, one full size (1920x1200) on my main monitor and another smaller one with the same aspect ratio on a smaller monitor. On average every couple of hours the slave window just hangs (the graphics freeze) and it needs to be closed through Task Manager. Has anyone experienced anything similar or know of a solution?

Many Thanks,

Alge

moosejaw
02-18-2011, 03:02 AM
I had a good session tonight without any lockups. I box 6 on 2 monitors. If you check out the isboxer website forums there are a few tips for EQ users.

Make sure Innerspace is up to date. Get the Isboxer 38 update. Update your video drivers.

I have WinEq installed but I don't currently use it. I'll get in a longer session tomorrow and see if I have any problems. Previously I would crash all sessions except the main when logging to server select.

Good luck.

Alge
02-18-2011, 10:15 AM
Previously I would crash all sessions except the main when logging to server select.


I get that too.

I've now moved to a layout-free system in ISBoxer and have still had the freeze/lockup thing occur once or twice

Everything is up to date. Will start playing with settings and see if I have any joy.

Lax
02-18-2011, 12:05 PM
Previous reports of this issue have centered on using mouse broadcasting. I believe there may be a bug relating to rendering the fake cursor for EverQuest 1, but I haven't been able to track it down yet. You can try disabling that option in your Repeater Profile (the fake cursor check box at the top) and see if that helps.

Alge
02-18-2011, 11:03 PM
Thanks Lax, will try that.

moosejaw
02-19-2011, 01:34 AM
My crashes stopped when I updated IsBoxer and my video driver this week. I keep the pc on 24/7 and isboxer running so I didn't realize there was an update until I started searching for my crashes. If you use an Ati card only install the driver and not the catalyst control center. I have had nothing but problems with the ccc.

Five hour session tonight with some use of mouse broadcasting (with fake cursor on) and had a clean logout. I currently do not use repeater regions but I may set some up and see if I can crash it that way.

Either way, good luck and keep posting.

Alge
02-20-2011, 08:14 AM
Mine seems a lot more stable now too. Had a long session today without any lockups or crashes.

Alge

moosejaw
02-21-2011, 02:14 AM
Maybe the Thursday morning EQ patch had a silent fix in it.

Here are the patch notes from Thursday:





*** Emergency Update ***
- Corrected a bug that was causing framerate/lag and texture loading issues.
- Players on Progression servers should now be able to use automatically-granted AAs (such as Harm Touch and Lay on Hands) before Luclin is unlocked.

*** Progression Servers ***
- Translocators will no longer offer to send players to zones that have not been unlocked yet.

*** Quests & Events ***
- Terror in the Dark - The raid has been repaired and should function normally now. All tentacle terrors will need to be killed along with the final boss in order to complete the event.
- Ritual of Terror - General Grime's Glyph of the Horror will no longer be a possible requirement for defeating the auras of the Tae Ew leaders.

*** AA ***
- Shadowknight - Early ranks of the Harm Touch AA have been scaled back in damage on the Progression servers.


Perhaps the framerate bug was our issue?

Alge
03-01-2011, 12:22 AM
I'm still getting this issue occasionally. I'm still trying to catch it happening to see if I can find a way to reproduce it.

Sometimes it can be fixed by closing down that instance of EQ by right-clicking the icon on the taskbar and selecting close, then re-loading that character set in InnerSpace. Sometimes the window will come good and I can stand up to stop that character camping out.

moosejaw
03-01-2011, 11:28 AM
I had the lockup yesterday when I logged in. Shut it all down and rebooted. Not sure now what is causing it. It is strictly a display issue since we can issue commands to the slaves.

Alge
03-01-2011, 11:00 PM
Not sure now what is causing it. It is strictly a display issue since we can issue commands to the slaves.

I can also still issue commands to the slaves. Will keep investigating...