FPS issues during combat/lots of mobs.

[Odann]

So since returning to the game I have noticed a huge issue with my FPS dropping when looking at large swaths of mobs or being in combat during a large pull.

Examples would be when running out in FoB and looking at the pit or being in CoM and pulling even just 5-6 mobs.

This didn't use to happen and since returning I have built a new monster of a PC. https://www.reddit.com/r/buildapc/comments/4xtm4d/repost_build_was_buried_first_time_build_for/

That is my build for anyone wondering. It runs other much higher quality games @ 60 FPS or higher without issue.

How can I fix this with EQ?

[paulgiamatti]

Bloated/corrupted log files can often cause this - go into your EverQuest\Logs folder and delete or move your logs out so that it generates a fresh file the next time you enter the game.

[Odann]

Bloated/corrupted log files can often cause this - go into your EverQuest\Logs folder and delete or move your logs out so that it generates a fresh file the next time you enter the game.


Awesome, thank you. I will try this when I get home and see if it works.

[Odann]

Bloated/corrupted log files can often cause this - go into your EverQuest\Logs folder and delete or move your logs out so that it generates a fresh file the next time you enter the game.

Removed all log files and the issue persists. FPS is rock solid but as soon as I look at a large corridor of mobs (like entrance to KC) it drops way down.

[paulgiamatti]

Seems strange - there definitely shouldn't be any reduction in FPS just from having a lot of mobs on screen. Even the worst systems can handle a full Chardok/Fear AoE pull graphically if logging and particles are turned off. Might just be some setting that disagrees with your graphics card - I'd just try messing around with graphics settings in game at that point.

Make sure Max Frames Per Second is set to 100 and try enabling/disabling Level of Detail in Options. Also go into the Advanced menu and try enabling/disabling Advanced Lighting, and try messing with the Actor Clip Plane & Shadows sliders and the vertex & pixel shader settings.

[thejester11]

You mentioned that you recently upgraded to a new computer. You may want to check out the multi-core solutions that can cause the issues you are describing: http://www.project1999.com/forums/showthread.php?t=3609

[Erica]

If your new computer downloaded the latest Windows 10 update, you could be experiencing this issue too: http://www.project1999.com/forums/showthread.php?t=254240

At least two of us fixed it by reverting the last windows 10 update. I went from getting at least 40+ fps while recording during a raid, to just 5 fps with a few mobs on screen.

[Odann]

You mentioned that you recently upgraded to a new computer. You may want to check out the multi-core solutions that can cause the issues you are describing: http://www.project1999.com/forums/showthread.php?t=3609

If your new computer downloaded the latest Windows 10 update, you could be experiencing this issue too: http://www.project1999.com/forums/showthread.php?t=254240

At least two of us fixed it by reverting the last windows 10 update. I went from getting at least 40+ fps while recording during a raid, to just 5 fps with a few mobs on screen.

Thanks for the replies pals!

Seems strange - there definitely shouldn't be any reduction in FPS just from having a lot of mobs on screen. Even the worst systems can handle a full Chardok/Fear AoE pull graphically if logging and particles are turned off. Might just be some setting that disagrees with your graphics card - I'd just try messing around with graphics settings in game at that point.

Make sure Max Frames Per Second is set to 100 and try enabling/disabling Level of Detail in Options. Also go into the Advanced menu and try enabling/disabling Advanced Lighting, and try messing with the Actor Clip Plane & Shadows sliders and the vertex & pixel shader settings.

But this is what finally fixed it. I had my FPS maxed out but hadn't changed any of the lighting or vertex settings. So I messed with those a bit and it fixed the issue! Thanks guys.