All eq2 sessions being placed on same core..

zatbox · Post by **zatbox** » Sat Apr 04, 2009 10:48 am

For some reason after the updates around gu51 in eq2 all sessions are being launched on the same core (last core, #7) the processes don't obey any affinity settings from isboxer nor do they listen to being manually set via taskman or process explorer.

Also, seems the windows don't reliably switch from a small view to main view if you click the window more then once.

xp64, eq2 (6 sessions) core i7.

zatbox · Post by **zatbox** » Sat Apr 04, 2009 10:56 am

just to add it worked fine previous to gu51, it would drop an instance on each core. and window switching had zero issues.

blackwinter · Post by **blackwinter** » Mon Apr 06, 2009 8:20 pm

Same here, crash a lot. One core can't do the job.

blackwinter · Post by **blackwinter** » Mon Apr 06, 2009 10:59 pm

Just after LavishScript Module API version 18.

Scooter · Post by **Scooter** » Tue Apr 07, 2009 9:02 am

I've been seeing the same issues. Dual core machine with 2 instances of EQ2 on it. I've tried loading up an ISBoxer profile as well as an older (pre-isboxer) profile and both will only allow the last core to be used.

Out of interest I loaded up two instance of the game without Innerspace and was able to confirm that I could put an instance onto each of the cores.

Also of interest (?)... Prior to using ISBoxer, I hadn't been trying to set my affinity in IS anyway and whether you can or not I don't know (though I suspect you can) Anyway, as I mentioned above even my old profiles were forcing the game onto the same core.

Hoping for it to be resolved soon

JamieW · Post by **JamieW** » Tue Apr 07, 2009 9:47 am

Scooter wrote:I've been seeing the same issues. Dual core machine with 2 instances of EQ2 on it. I've tried loading up an ISBoxer profile as well as an older (pre-isboxer) profile and both will only allow the last core to be used.

Out of interest I loaded up two instance of the game without Innerspace and was able to confirm that I could put an instance onto each of the cores.

Also of interest (?)... Prior to using ISBoxer, I hadn't been trying to set my affinity in IS anyway and whether you can or not I don't know (though I suspect you can) Anyway, as I mentioned above even my old profiles were forcing the game onto the same core.

Hoping for it to be resolved soon

You can set it in Inner Space by using the "proc" command:

Examples (from memory):

"proc 1 only" will set it to use only core 1
"proc 1 on 2 on 3 off 4 off" will give it affinity to cores 1 and 2 only.

wired203 · Post by **wired203** » Tue Apr 07, 2009 5:29 pm

I'm using dual core with no issues, goes to each core accordingly. I am using ISboxer build 29 as there is some wonkiness that build 30 has which is bad for my setup.

However I may have to check as I think I still have my proc 1 only and proc 2 only commands still embedded in my startup line.

Post by **Lax** » Tue Apr 07, 2009 5:53 pm

wired203 wrote:I am using ISboxer build 29 as there is some wonkiness that build 30 has which is bad for my setup.

Care to elaborate? I fixed all "wonkiness" issues as far as I am aware.

wired203 · Post by **wired203** » Tue Apr 07, 2009 6:54 pm

From my earlier post all proc settings are within ISBoxer.

Lax the wonkiness is how my PC goes is1 and then is3 for my 2nd account so the crash-relaunch part of ISBoxer acted wonky in my situation. I haven't seen anything about it in the patch notes.

Post by **Lax** » Tue Apr 07, 2009 10:43 pm

Ok back to the topic..

It does sound like EQ2 made some strange change to CPU affinity, I will check it out very soon -- I'm not ignoring the issue here, though it sounds very much like a bug with the game's CPU affinity related changes.

Post by **Lax** » Wed Apr 08, 2009 11:57 pm

Ok, to deal with this:
1. I added a new command "proclock" in IS build 4978 (current development build as of now). "proclock on" will lock the affinity so the game cannot adjust it (but it can still be adjusted through task manager)
2. If ISBoxer 31 is configured to set processor affinity, it will automatically lock it

That should do it. The new builds of IS and ISBoxer should be pushed live within a day or two.

Scooter · Post by **Scooter** » Thu Apr 09, 2009 5:12 am

Thanks Lax. Looking forward to trying it out.

asgradth · Post by **asgradth** » Thu Apr 09, 2009 11:42 pm

I hit this as well, came up with some funky workarounds (hotkeys that set /proc everytime i pull a mob), since the affinity does set for 20-30 seconds, before it goes back all instances on core0.

Btw, the far right bottom core in task mgr is core0, then count to the left and up. It has to do with the way windows enumerates procs, linux doesn't do this.

Thanks for fixing this!!!

Scooter · Post by **Scooter** » Fri Apr 10, 2009 12:32 am

asgradth wrote:Btw, the far right bottom core in task mgr is core0, then count to the left and up. It has to do with the way windows enumerates procs, linux doesn't do this.

Cool. I wasn't aware of that

jmoses · Post by **jmoses** » Fri Jul 24, 2009 4:06 pm

Lax wrote:Ok, to deal with this:
1. I added a new command "proclock" in IS build 4978 (current development build as of now). "proclock on" will lock the affinity so the game cannot adjust it (but it can still be adjusted through task manager)
2. If ISBoxer 31 is configured to set processor affinity, it will automatically lock it

That should do it. The new builds of IS and ISBoxer should be pushed live within a day or two.

How do you use this "proclock" fix? Could you explain how to do this?

I'm totally new to this toolset, I just bought Innerspace and downloaded ISBoxer to use with Everquest 2. the two work beautifully and do exactly what I need them to. Thanks so much devs! However I see both my everquest2 clients running on the same core on my computer.

I tried googling around and read there were Innerspace console commands like "proc 1 on 2 off 3 on 4 off", but "proclock on" didn't work for me... Also I don't see any way for ISBoxer to set processor affinity where you said it can, right?

About my setup:
Intel Core 2 Duo, Windows XP
Inner Space 1.09 Build 5018
ISBoxer Toolkit Build #33