The "next" Macroquest and Frame Limiters galore!

[B_I_G__D_A_D_D_Y]

Edit 2/26/2022 to note that as of January the old CPUAffinity setting has been replaced by a new setting called ClientCore.



The update notes https://forums.daybreakgames.com/eq...te-notes-january-19-2022.280388/#post-4098095

=============================

*** Disclaimer! The following settings seem to work well on my Windows 10 Pro (21H1) -- Dell G315 laptop -- quad-core, hyperthreaded Core I5-8300H CPU -- 16GB RAM -- Adata NVMe SSD -- integrated Nvidia GeForce GTX 1050Ti. Your mileage may vary on different hardware!

And don't take my advice if you frequently play without Macroquest loaded and still need frame limiting!***


I use ISBoxer and will continue since I appreciate it's monitor management and virtualized EQClient.ini files. ISBoxer also had frame limiting and CPU management as a standard feature long before Sony or Macroquest.

But after implementing the newest RedGuide's Macroquest it makes sense to ensure you're using just one frame limiter and RedGuide's really seems to work the best! And you no longer need to use the EQWire plugin!

Even if you're not using ISBoxer there are still the embedded settings in the EQ client itself. My recommendation is that you disable all frame limiters except for RedGuide's! In game you'd go the Display > Advanced Options and slide the levers to the far right.



!

If you use ISBoxer you should also disable the CPU and Frame Management in the Performance Tab for each character in your team. Make sure you save your changes and Export All to Innerspace!



!


Now I did have some issues with ISBoxer's Key Repeater not working on my Background boxes, but after some trial and error I found the following "Next" settings work well on my laptop...

(Editing the ..\Config\MacroQuest.ini file




!

Finally, make sure you're letting Windows manage your CPU cores by ensuring your EQClient.ini files are set to:



!

As I created this post my 6 character team was running KissAssist 12.002.006 and pulling and killing mobs and my hardware was:

 

[Sic]

why are you telling isboxer to lock to all cores if you're telling eqclient.ini to use -1?

 

[dreamflux]

Disclaimer - I assume this is only if you are using thumbnail views in isboxer. If you are stacked there is 0 reason to render BG.

 

[B_I_G__D_A_D_D_Y]

why are you telling isboxer to lock to all cores if you're telling eqclient.ini to use -1?

Because then the Windows OS scheduler itself makes all the core and thread decisions.

 

[B_I_G__D_A_D_D_Y]

Disclaimer - I assume this is only if you are using thumbnail views in isboxer. If you are stacked there is 0 reason to render BG.

No! If you do not render backgrounds then commands you type manually using ISBoxer's Key Repeater will not function correctly on the background boxes.

 

[Sic]

Because then the Windows OS scheduler itself makes all the core and thread decisions.

that's what i mean. you shouldn't tell isboxer to do anything

 

[B_I_G__D_A_D_D_Y]

that's what i mean. you shouldn't tell isboxer to do anything

It's sort of counterintuitive. Selecting ALL cores in the ISBoxer config program actually results in ISBoxer not attempting to do any CPU core management.

 

[Sic]

It's sort of counterintuitive. Selecting ALL cores in the ISBoxer config program actually results in ISBoxer not attempting to do any CPU core management.

or, you can just deselect everywhere where "nothing is nothing" and there's no confusion.

 

[B_I_G__D_A_D_D_Y]

or, you can just deselect everywhere where "nothing is nothing" and there's no confusion.

I tried it your way and it still works exactly the same. But I can understand how it makes more sense to show all cores completely deselected in ISBoxer!

 

[Sic]

I tried it your way and it still works exactly the same. But I can understand how it makes more sense to show all cores completely deselected in ISBoxer!

I've used isboxer a long time and i don't trust it to do absolutely anything lol

 

[B_I_G__D_A_D_D_Y]

I've used isboxer a long time and i don't trust it to do absolutely anything lol

I've had very good luck with it and Joe was very responsive when I had questions and issues. I absolutely love the nearly instantaneous screen switching I get when I'm using emulated full screen modes. To me that's worth the price of admission alone.

 

[allandallis235]

Thank you for the write-up. Could you share what you did do to reduce your memory usage to that extent?

 

[Cannonballdex]

I took a suggestion to set cpuaffinity to -1, after a couple of hours I would get toons freezing and not responding. I deleted all instances of cpuaffinity and restarted the game and let it do its thing. I ended up with this and no more freezing. Not really sure how this works but cpuaffinity -1 didn't work for me.

CPUAffinity1=1
CPUAffinity2=2
CPUAffinity3=3
CPUAffinity4=4
CPUAffinity5=5
CPUAffinity6=6
CPUAffinity7=7
CPUAffinity8=8
CPUAffinity9=9
CPUAffinity10=10
CPUAffinity11=11
CPUAffinity12=12

 

[Sarkam]

i have been using next since i could and love the frame limiter functions have worked out amazing for me in comparison to cpu management through isboxer and eqwire.

Since the 64bit release i have been encountering some weird behavior from isboxer, when window swaping they freeze or dont render and dont swap as should be expected.

i have tried the settings recommended in this post, as well as the ones Sic shows in his Next migration and feature video. Wondering if anybody else has encountered behavior like this, as i am not sure if its a framelimiter problem or isboxer issue atm.

 

[JerkChicken]

Have you tried updating IsBoxr to the latest development version?
The current general release has some known issues with EQ