Loading is faster, but in game performance are actualy worse?

"

MisterER wrote:

"

zupafundo wrote:

it wont get fixed and this will turn into another 50 page thread

I guarantee it.

GGG has a piss poor track record of fixing bugs affecting large portions of the community

Then let's make it reach 50 pages, because I don't want to give up PoE :(

And the most annoying thing, that Chris didnt even said anything about that, half of my mates have same problems. At least when a lot of ppls had troubles with sounds (not 100% of em), GGG made some posts and answers about that. And now what? - nothing! just a shiitty post about some guy(they call him "Administrator" - haha!) drank too much and fell asleep on keyboard. With the result of completely broken game for us.

Ran a few maps to test 2.3.0f.
No improvements were noticed. Wait it out until 2.3.0g.

i fixed it with task manager -> Processes tab -> Path of exile -> set priority 'above normal' instead of 'normal'
only tested it for a few mins and was fine, no fps issues.

hope it works for u too! ^___^

At least we finaly got a thread made by Chris, we can try to cry a bit more about our problems there :)
https://www.pathofexile.com/forum/view-thread/1678815

I too have encountered major issues with FPS drops and stuttering since the 2.3x hotfixes. Been playing since Closed Beta with no issues at all.

My rig:

GTX 780
i7 2600k
8BG RAM
Windows 10
Dedicated soundcard: Asus Xonar Essence STX

The LagSpikes Is Killing me, literally =(


Die and Die...

Im also having issues with my fps that i never had before in previous versions, now my fps drops like a spike which really sucks.....not sure if disability vsync would solve it because using more than 60fps on a 60fps monitor would be pointless and would work your gpu more for nothing...let me know if im correct...

I can not play the game, this too bad, so started Porphecy league all got bad. And I have all the problems shown by all.
My PC: Win 7 - 64, 12 GB Ram, Amd x6 (3.8GHz), MB Asrock 980 and GTX 680 - 2GB.

--noasync fixed the problem for me.