WinEQ2

[Man0warr]

Do you have CPU Affinity set to 1 in your executable for P99?

The built in Windowed mode for the P99/Titanium client works well enough for me, WinEQ2 was always best for boxing which isn't allowed.

[Toodles]

Hi Man0 do you mean when playing without WinEQ?
No I do not set the affinity manually.

I also use windowed mode though have mismatched behavior. I set antialiasing and anisotropic filtering in my graphics panel, which works in EverQuest, but then sometimes after restarting the client, the top border of my window is pushed down a bit, forcing the chat windows and other GUI elements off the bottom of the scree. The anti-aliasing and anisotropic filtering stop working.

I have to then drag the window up a little to where it should be (however it automatically snaps back to it's previous position). I then set the game to full screen and restart the client. It then has the window in the right spot and the aa/af is working again.

I do not know what causes this.

[Iklossis]

This really isn't helpful at all because it doesn't show you how to point it to the Titanium launcher bat file. Options in wineq2 menu only shows folders and when I try to cut and paste the path from the "launch titanium.bat" file it says it doesn't exist...

[Whoop]

Originally Posted by Iklossis [You must be logged in to view images. Log in or Register.]

This really isn't helpful at all because it doesn't show you how to point it to the Titanium launcher bat file. Options in wineq2 menu only shows folders and when I try to cut and paste the path from the "launch titanium.bat" file it says it doesn't exist...

I don't get this either, how do you point it to the launcher?

[nyclin]

In your WinEQ2 profile, set "Everquest Path" to the directory where EQ is installed. You don't have to point it directly at a batch file or an executable.

[Hyperbase-1999]

I win key plus up cursor key sould maximise the window, left/right to shift positions/monitors. Then alt plus enter to full screen eq.

Make sure refresh isnt 59.9 eq loves to select that for me. Set to native 60 if that's what you have.

[Hyperbase-1999]

The slow movement is RDTSC (i believe) and a multi proc/core timing issue.

Fix by using a SingleProcAffinity shim.

Or set affinity manually, or WinEQ2 etc.

To minimise this make sure you are running a full power management plan, running power management on the cpu will manifest this issue more frequently.

[Marmoset]

Originally Posted by Hyperbase-1999 [You must be logged in to view images. Log in or Register.]

The slow movement is RDTSC (i believe) and a multi proc/core timing issue.

Fix by using a SingleProcAffinity shim.

Or set affinity manually, or WinEQ2 etc.

To minimise this make sure you are running a full power management plan, running power management on the cpu will manifest this issue more frequently.

Hello Hyper,

I have followed all of the guides and FAQs and I still get the memory reference error. I have set the affinity manually as per the guides, I have modified my EQClient.ini to include WindowedMode=TRUE, I have run as Administrator, I have included the patchme in the EQgame.exe Shortcut path, and I have attempted to run in Windows XP Compatibility mode. I am running a Sony VAIO Laptop with Windows 10 64bit.

[saren42]

I'm gonna post this here, since maybe more people will see it, and I might actually be able to get some help. This is a copy-paste from my thread I made the other day.

Hey all, but of an issue here, I launched the game through wineq, discovered needed a new spellfile, downloaded it, unpacked it, then tried to re-launch the game through WinEQ, now I get this error. It doesn't get the error when I launch without WinEQ, but... without WinEQ, my computer goes ape sh*t trying to play.

FYI, yes I've looked at the FAQ, and it's not resolution. It's causing some issues between the new spell file (v42) and WinEQ.

[You must be logged in to view images. Log in or Register.]

[clacbec]

win eq2 asking me to update directx however i m on windows10 , no DX to update when i check Windows update . Bug ?