|
#1
|
|||
|
horrible frame rates on one character, but not others
The Issue:
While attending a raid on Filbus, I suffered terrible, laggy frame rates. We're talking like 1 frame per 3 seconds. I have also noticed this reduction in FPS while on Filbus in other, non-raid environments, such as going into Chardok vs going into Chardok on another toon. -I'm playing EQ on a fairly powerful gaming PC. It's not spiffy by 2018 standards, but I used to play EQ on a far worse machine without this issue. -I'm not downloading elf porn or running any intensive programs. -I adjusted in game frames and other stuff during the raid event, to no avail Has anyone had this issue? My EQ is installed on a separate HD than the operating system, but all my games are installed this way and its never caused performance issues. I just don't understand why raiding would destroy my FPS, when I was able to do it for years on worse computers. Thanks for your thoughts prayers and hoping to help | ||
#2
|
|||
|
p99 anti cheat bs and kunark zones do not mix well on some pcs
__________________
Current Games:
Naw | ||
#3
|
||||
|
Quote:
PS it was around 15mb which isn't huge | |||
#4
|
|||
|
Also happened to me. Clearing out logs to another folder fixed it
| ||
#5
|
||||
|
Quote:
I would be surprised if this was the cause of your problems.
__________________
Tungh Lashor - 60 Grandmaster
Ortnit Bloodthirst - 60 Warlock <Europa> | |||
#6
|
|||
|
UI files maybe? Worth a shot to at least move both out and see if the default gives you problems.
| ||
#7
|
|||
|
Moving logs has so far made things less choppy. I have yet to be able to attend another high pop raid so we will soon see. I'll try moving out all logs if it'd not better then try temporarily removing ui
| ||
#8
|
|||
|
I had that happening for one of my character, the log size wasn't the issue since it was lower than my other characters that were unaffected. Deleting that specific log file resolved my problem, it made a new file and now I have a normal framerate on all my characters. May be you're experiencing the same thing.
| ||
#9
|
|||
|
Making a new logfile solved it!
| ||
|
|