[Bug 34011] New: Path of Exile stutters constantly
http://bugs.winehq.org/show_bug.cgi?id=34011 Bug #: 34011 Summary: Path of Exile stutters constantly Product: Wine Version: 1.6-rc4 Platform: x86 OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: michael.blumenkrantz(a)gmail.com Classification: Unclassified When playing the game, any time a new resource is loaded from disk, the game freezes completely for some time while it waits for the load. Given that the game is constantly loading things from disk, it makes the game nearly unplayable in many cases. -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email Do not reply to this email, post in Bugzilla using the above URL to reply. ------- You are receiving this mail because: ------- You are watching all bug changes.
http://bugs.winehq.org/show_bug.cgi?id=34011 FeepingCreature <default_357-line(a)yahoo.de> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |default_357-line(a)yahoo.de --- Comment #1 from FeepingCreature <default_357-line(a)yahoo.de> 2013-07-25 19:26:25 CDT --- I have this problem as well. -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email Do not reply to this email, post in Bugzilla using the above URL to reply. ------- You are receiving this mail because: ------- You are watching all bug changes.
http://bugs.winehq.org/show_bug.cgi?id=34011 --- Comment #2 from FeepingCreature <default_357-line(a)yahoo.de> 2013-07-25 21:23:18 CDT --- Setting UseGLSL to disabled seems to mitigate this. -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email Do not reply to this email, post in Bugzilla using the above URL to reply. ------- You are receiving this mail because: ------- You are watching all bug changes.
http://bugs.winehq.org/show_bug.cgi?id=34011 --- Comment #3 from Mike Blumenkrantz <michael.blumenkrantz(a)gmail.com> 2013-07-26 01:02:16 CDT --- (In reply to comment #2)
Setting UseGLSL to disabled seems to mitigate this.
Mitigate, but not eliminate. -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email Do not reply to this email, post in Bugzilla using the above URL to reply. ------- You are receiving this mail because: ------- You are watching all bug changes.
http://bugs.winehq.org/show_bug.cgi?id=34011 Justin Soulia <rockinup1231(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |rockinup1231(a)gmail.com --- Comment #4 from Justin Soulia <rockinup1231(a)gmail.com> 2013-10-26 03:54:25 CDT --- I can confirm this is a significant problem, as it can render the game unplayable if you don't have a buddy with to cover you while recovering from a lag spike. I will say, however, I loaded the 'Content.ggpk' file from the PoE installation directory to a tmpfs ramdisk, and symlinked it to the PoE install directory where it was and this helped, albeit only a little bit. The stuttering was still an issue. That single file is about 4.5GB in size and would have contained most of the game's content data. -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email Do not reply to this email, post in Bugzilla using the above URL to reply. ------- You are receiving this mail because: ------- You are watching all bug changes.
http://bugs.winehq.org/show_bug.cgi?id=34011 Xavier Vachon <xvachon(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |xvachon(a)gmail.com -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email Do not reply to this email, post in Bugzilla using the above URL to reply. ------- You are receiving this mail because: ------- You are watching all bug changes.
http://bugs.winehq.org/show_bug.cgi?id=34011 --- Comment #5 from Xavier Vachon <xvachon(a)gmail.com> 2013-11-14 02:43:32 CST --- Confirming in latest wine (1.7.6). What kind of log could help to expose the problem? -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email Do not reply to this email, post in Bugzilla using the above URL to reply. ------- You are receiving this mail because: ------- You are watching all bug changes.
http://bugs.winehq.org/show_bug.cgi?id=34011 --- Comment #6 from Justin Soulia <rockinup1231(a)gmail.com> 2013-11-15 18:07:18 CST --- As I've been looking for more information regarding the issue and potential workarounds, there seems to be a consensus that this is only an issue for users with AMD/ATi graphics cards. If that is so, that would make this not a wine issue, unfortunately. What graphics card do you guys have? I have a Radeon HD 7870 (PCIe). -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email Do not reply to this email, post in Bugzilla using the above URL to reply. ------- You are receiving this mail because: ------- You are watching all bug changes.
http://bugs.winehq.org/show_bug.cgi?id=34011 --- Comment #7 from Xavier Vachon <xvachon(a)gmail.com> 2013-11-15 18:16:30 CST --- (In reply to comment #6)
As I've been looking for more information regarding the issue and potential workarounds, there seems to be a consensus that this is only an issue for users with AMD/ATi graphics cards.
If that is so, that would make this not a wine issue, unfortunately.
What graphics card do you guys have? I have a Radeon HD 7870 (PCIe).
I have an NVIDIA 550 TI, so it affects NVIDIA too. Setting UseGLSL to disabled makes the game playable, but even then I often die because of the lag when I face unique bosses or large group of creatures. -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email Do not reply to this email, post in Bugzilla using the above URL to reply. ------- You are receiving this mail because: ------- You are watching all bug changes.
http://bugs.winehq.org/show_bug.cgi?id=34011 Karlson Pfannschmidt <quietdeath(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |quietdeath(a)gmail.com -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email Do not reply to this email, post in Bugzilla using the above URL to reply. ------- You are receiving this mail because: ------- You are watching all bug changes.
http://bugs.winehq.org/show_bug.cgi?id=34011 Evan Goers <megatog615(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |megatog615(a)gmail.com -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email Do not reply to this email, post in Bugzilla using the above URL to reply. ------- You are receiving this mail because: ------- You are watching all bug changes.
http://bugs.winehq.org/show_bug.cgi?id=34011 Kai Hiller <V02460(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |V02460(a)gmail.com -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email Do not reply to this email, post in Bugzilla using the above URL to reply. ------- You are receiving this mail because: ------- You are watching all bug changes.
http://bugs.winehq.org/show_bug.cgi?id=34011 Tanweth Imarato <tanweth(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |tanweth(a)gmail.com --- Comment #8 from Tanweth Imarato <tanweth(a)gmail.com> --- I likewise experienced this issue on a Radeon 7850, using the 13.11 proprietary drivers. Disabling GLSL made the game unable to open until I deleted my old production_Config.ini so it would reset my settings. Then the game would load, but the main menu background was black, and any attempt to change any of the display settings made it freeze. So I was unable to test if it mitigated the issue for me. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
http://bugs.winehq.org/show_bug.cgi?id=34011 Screwtape <thristian(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |thristian(a)gmail.com --- Comment #9 from Screwtape <thristian(a)gmail.com> --- My understanding is that this isn't "when a new resource is loaded from disk", but rather "when a new effect is drawn, and the game suddenly goes off and compiles a new shader script to HLSL, which Wine then has to compile to GLSL, which the driver then has to compile to its own internal representation." Why that's such an issue, I have no idea. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
http://bugs.winehq.org/show_bug.cgi?id=34011 none2366811(a)mailismagic.com changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |none2366811(a)mailismagic.com --- Comment #10 from none2366811(a)mailismagic.com --- Created attachment 48260 --> http://bugs.winehq.org/attachment.cgi?id=48260 In game screen shot of the frame drop. First I thought it’s micro stuttering. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
http://bugs.winehq.org/show_bug.cgi?id=34011 --- Comment #11 from Screwtape <thristian(a)gmail.com> --- Earlier this year at FOSDEM, one of the Mesa developers gave a talk called "Three Years' Experience with a Tree-Like Shader IR": http://video.fosdem.org/2014/H1301_Cornil/Saturday/ ...in it, he talks about how terrible Mesa's GLSL compiler and optimizer are, and explicitly mentions that it tends to cause problems for games run under Wine. Apparently, Direct3D treats vertex and fragment shaders separately, and you can swap them in and out any time you like, so games tend to do that a lot. In GL, vertex and fragment shaders are considered part of the same shader program, so when a game swaps out one fragment shader for another, Wine has to recompile the new combination of vertex and fragment shaders, which is more expensive than what Windows does. On top of that, Mesa's GLSL compiler is very slow and inefficient, and the speaker actually mentioned stuttering-while-approaching-a-boss as a common symptom. So I suspect there's nothing Wine can do about this particular behaviour. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
http://bugs.winehq.org/show_bug.cgi?id=34011 Roland Haeder <roland(a)mxchange.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |roland(a)mxchange.org --- Comment #12 from Roland Haeder <roland(a)mxchange.org> --- Happens with propritary nvidia drivers. Flickering and freezes and latest wine (GIT/master). -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=34011 Sovyn <teddy5978(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |teddy5978(a)gmail.com --- Comment #13 from Sovyn <teddy5978(a)gmail.com> --- This bug is even more important than in the past. Why? Because prior to Path of Exile 1.2.2, users could disable GLSL and experience relatively smooth, glitch-free gameplay. After the Path of Exile 1.2.2 patch, users with GLSL disabled still experience smooth gameplay, however, Path of Exile now has a slowdown issue on mana use alleviated only by using a very recent wine version (I'm running 1.7.27, the latest version available as of this writing). The consequence of using a recent version of Wine is that we get some unacceptable GUI glitches that essentially blank out large portions of game screen. Here is an example screenshot: http://i204.photobucket.com/albums/bb130/7h645764n57/poe-issue_zps12561cf6.j... The only way things would be perfect is to fix the stuttering bug that this page is about, so that users could run Path of Exile as intended, with GLSL *enabled* without undue FPS drops when new graphics resources (e.g., spell effects) are rendered. I know it will be a lot of work to optimize GLSL under wine. Hopefully someone is working on it. Consistently reproduced on different systems. Example: Ubuntu Linux 14.04 LTS 64-bit Intel G3258 (2x 4.1 Ghz), Also Core i3-4360 3.7 Ghz 8 GB DDR3 RAM Video Card: Nvidia GeForce GTX 750 Ti with 2GB memory Nvidia proprietary driver 337.25 (all versions including latest beta tested, no difference) Screen Resolution: 1920x1080 (1080p), Path of Exile runs in full screen mode Fast SSD hard drive -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=34011 Andrey K <silencex(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |silencex(a)gmail.com --- Comment #14 from Andrey K <silencex(a)gmail.com> --- Constantly happened on my PC: ArchLinux x86_64 Intel Core 2 Quad Q6600 @ 2.4GHz 4GB RAM Kingston SSDnow V300 Radeon HD 6850 1GB Catalyst 14.9 proprietary driver I start PoE via PlayOnLinux (wine versions 1.7.27-PathOfExile-1.7.27 and 1.7.19-WGL_WINE_surface2) -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=34011 --- Comment #15 from Sovyn <teddy5978(a)gmail.com> --- (In reply to Andrey K from comment #14)
Constantly happened on my PC: ArchLinux x86_64 Intel Core 2 Quad Q6600 @ 2.4GHz 4GB RAM Kingston SSDnow V300 Radeon HD 6850 1GB Catalyst 14.9 proprietary driver
I start PoE via PlayOnLinux (wine versions 1.7.27-PathOfExile-1.7.27 and 1.7.19-WGL_WINE_surface2)
Hi Andrey, Path of Exile is now perfect (except the fonts) with 1.7.27-PathOfExile-1.7.27 via PlayOnLinux and an Nvidia card with GLSL disabled. ATI just does not work with GLSL disabled. Must be something with their drivers, been that way forever. Looks like you will have to spend $50 like I did for an Nvidia card to play Path of Exile properly. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=34011 Ken Sharp <imwellcushtymelike(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Keywords| |Abandoned? --- Comment #16 from Ken Sharp <imwellcushtymelike(a)gmail.com> --- Please retry in vanilla Wine, version 1.7.44 or later. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=34011 --- Comment #17 from Xavier Vachon <xvachon(a)gmail.com> --- (In reply to Ken Sharp from comment #16)
Please retry in vanilla Wine, version 1.7.44 or later.
This bug could be a duplicate of http://bugs.winehq.org/show_bug.cgi?id=35718 -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=34011 Matteo Bruni <matteo.mystral(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |matteo.mystral(a)gmail.com --- Comment #18 from Matteo Bruni <matteo.mystral(a)gmail.com> --- (In reply to Xavier Vachon from comment #17)
(In reply to Ken Sharp from comment #16)
Please retry in vanilla Wine, version 1.7.44 or later.
This bug could be a duplicate of http://bugs.winehq.org/show_bug.cgi?id=35718
Hardly so, that bug was introduced in 1.7.13, this is reported against 1.6-rc4. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=34011 super_man(a)post.com changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |super_man(a)post.com --- Comment #19 from super_man(a)post.com --- There was some addition into wine code recently that fixed a regression bug which had Path of Exile game mentioned. It would be worth to retest against 1.8.rc1 -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=34011 --- Comment #20 from Justin Soulia <rockinup1231(a)gmail.com> --- (In reply to super_man from comment #19)
There was some addition into wine code recently that fixed a regression bug which had Path of Exile game mentioned.
It would be worth to retest against 1.8.rc1
I gave it a test, but performance did not fix the stuttering. It did improve any flickering/corruption issues that were coming up per that bug, though. Should add that if I switch over to wine-staging and use CSMT performance comes way up overall but the stuttering is still a major problem. Current relevant specs: Nvidia GTX 260 w/proprietary driver v. 358.16 AMD Phenom II x4 965 3.8 Ghz 12GB DDR3 1600 RAM Arch Linux x86_64 wine 1.8-rc1 (and wine-1.8-rc1 (Staging) tested, too) -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=34011 --- Comment #21 from super_man(a)post.com ---
Should add that if I switch over to wine-staging and use CSMT performance comes way up overall but the stuttering is still a major problem.
How about CSMT off with staging? Does it change anything? -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=34011 --- Comment #22 from Justin Soulia <rockinup1231(a)gmail.com> --- (In reply to super_man from comment #21)
Should add that if I switch over to wine-staging and use CSMT performance comes way up overall but the stuttering is still a major problem.
How about CSMT off with staging? Does it change anything?
With CSMT turned off, performance is identical to vanilla wine. In both cases, the stuttering behavior reported here is frequent. The only difference is the average frame rate with CSMT on improves significantly but frequent frame time spikes are still common. It is still always a problem when effects/shaders need to be rendered for the first time entering a map. I imagine this still an issue related to Comment 11 of this bugzilla report. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=34011 David <dd31879(a)yahoo.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |dd31879(a)yahoo.com --- Comment #23 from David <dd31879(a)yahoo.com> --- (In reply to Justin Soulia from comment #22)
(In reply to super_man from comment #21)
Should add that if I switch over to wine-staging and use CSMT performance comes way up overall but the stuttering is still a major problem.
How about CSMT off with staging? Does it change anything?
With CSMT turned off, performance is identical to vanilla wine.
In both cases, the stuttering behavior reported here is frequent. The only difference is the average frame rate with CSMT on improves significantly but frequent frame time spikes are still common. It is still always a problem when effects/shaders need to be rendered for the first time entering a map.
I imagine this still an issue related to Comment 11 of this bugzilla report.
Just installed POE myself after not playing for a while. Wanted to play in the the newer 2.x version a bit. I get the stuttering on default settings as well. Something that helps is to turn off the GLSL. However, if you press F1 in game you can see the frame time/latency/fps graphs. Look at the fps graph and frame time graph if you are having this issue. You will notice spiking occuring a lot in the fps graph where it seems like the card cuts out performance for some reason and drops down to like 10fps, then resumes as normal. if your GLSL is enabled all sorts of crazy lag can occur. I have noticed this in town especially. I turned off my GLSL and it helped mitigated the effects of all this stuttering substantially. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=34011 kutajydam-5795(a)yopmail.com changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |kutajydam-5795(a)yopmail.com --- Comment #24 from kutajydam-5795(a)yopmail.com --- I've experienced similar issues while playing Path of Exile and the combination of disabling GLSL and using the following commandline switches for Path of Exile: -ns -gc 1 completely removed any and all stuttering. -ns will completely disable sound and with it, its sound engine and with that, its need to load sound assets. -gc 1 will make its internal garbage collector more aggressive, putting less memory pressure on the machine it is played on. I also did experiment with nopreload, waitforpreload and combinations of either of those in conjunction with ns, gc 1 but I found the preload commandline options to be of no constructive use. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=34011 henk_roemer(a)web.de changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |henk_roemer(a)web.de --- Comment #25 from henk_roemer(a)web.de --- (In reply to kutajydam-5795 from comment #24)
I've experienced similar issues while playing Path of Exile and the combination of disabling GLSL and using the following commandline switches for Path of Exile:
-ns -gc 1
completely removed any and all stuttering.
-ns will completely disable sound and with it, its sound engine and with that, its need to load sound assets. -gc 1 will make its internal garbage collector more aggressive, putting less memory pressure on the machine it is played on.
I also did experiment with nopreload, waitforpreload and combinations of either of those in conjunction with ns, gc 1 but I found the preload commandline options to be of no constructive use.
This seems to be the way to go But i have no idea how to use these commandlines or where to insert them. Could you explain real quick how you did that? I am using the Non-Steam version of the game. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=34011 Eric <naisanza(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |naisanza(a)gmail.com --- Comment #26 from Eric <naisanza(a)gmail.com> --- Have you tried disabling Multi-core processing in the options? -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=34011 jeppe winther <jeppewinther(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jeppewinther(a)gmail.com --- Comment #27 from jeppe winther <jeppewinther(a)gmail.com> --- (In reply to henk_roemer from comment #25)
(In reply to kutajydam-5795 from comment #24)
I've experienced similar issues while playing Path of Exile and the combination of disabling GLSL and using the following commandline switches for Path of Exile:
-ns -gc 1
completely removed any and all stuttering.
-ns will completely disable sound and with it, its sound engine and with that, its need to load sound assets. -gc 1 will make its internal garbage collector more aggressive, putting less memory pressure on the machine it is played on.
I also did experiment with nopreload, waitforpreload and combinations of either of those in conjunction with ns, gc 1 but I found the preload commandline options to be of no constructive use.
This seems to be the way to go But i have no idea how to use these commandlines or where to insert them. Could you explain real quick how you did that? I am using the Non-Steam version of the game.
You append them to the command you use to launch the game. So, if you run the game from a terminal, you just tack it on the end, like so: wine PathOfExile.exe -gc 1 -ns If you run it using a shortcut, you'd need to edit that shortcut and append it there. I'd like to note that -ns seems unnecessary at this point. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=34011 jeppe winther <jeppewinther(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC|jeppewinther(a)gmail.com | -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=34011 jeppe winther <jeppewinther(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jeppewinther(a)gmail.com --- Comment #28 from jeppe winther <jeppewinther(a)gmail.com> --- The severity of this bug is somewhat overstated, at least in my experience. Running on: Intel i3 4170 @ 3.7GHz 8GB Ram NVIDIA GeForce GTX 750Ti and with -gc 100, the "constantly" from the bug report is surely wrong. It will stutter occasionally, drop from 60 fps to 25-30 (Vsync on), and very occasionally drop all the way to sub 1 fps. This stuttering is more prevalent in groups, in higher level content, and in areas with patches of burning/shocking/chilling ground. Basically, the more effects are happening, the more work has to be done, and the less fps you get. -gc 100 seems to keep these assets around in memory, though, so the stuttering is much less noticeable, at the cost of eventually crashing the game due to running into the 32bit memory limit. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=34011 --- Comment #29 from henk_roemer(a)web.de --- i cant figure out where to put these gc 1 and ns. i am running PoE from my playonlinux. when i run the game via a shortcut '/usr/share/playonlinux/playonlinux --run "PathOfExile" %F' i cant fit them in anywhere without getting errors. same goes if i run this in a shell -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=34011 --- Comment #30 from jeppe winther <jeppewinther(a)gmail.com> --- Well. What you're trying to add to the execution of the program is called an Argument. Normally you append them after the instruction to execute said program, in order to give additional instructions on how the program should run and behave. The easiest way to see them in action is to open up a terminal and comparing the following commands invoking the ls program (no quotation marks): "ls" "ls -l" "ls --help" With playonlinux, you have to Configure your shortcuts to add arguments to them. http://wiki.playonlinux.com/index.php/The_Configuration_Window#The_Main_Conf... Have a look at the second image on this page, the one with all the red boxes and numbers. You'll want to add the arguments in the "Arguments" box, here number 16. So, in there write "-gc 100", again no quotation marks. I still don't think -ns is necessary, but experiment away. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=34011 Bruno Jesus <00cpxxx(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Ever confirmed|0 |1 URL| |https://www.pathofexile.com | |/ Keywords|Abandoned? |download Status|UNCONFIRMED |NEW --- Comment #31 from Bruno Jesus <00cpxxx(a)gmail.com> --- I can confirm this in Wine 2.9 with both Intel and NVIDIA graphics drivers. The game client has changed a lot since the bug was opened but the problem described in comment 0 is still present. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=34011 Zakk <zakk(a)rsdio.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |zakk(a)rsdio.com --- Comment #32 from Zakk <zakk(a)rsdio.com> --- Wine 2.9, MacOS: same freeze/stuttering issue. It is much much better on Nvidia+GLSL disabled, but in that case some effects aren't rendered. I put some crude timing/debugging into glsl_shader.c: I'm pretty sure this issue is shader generation related. One particular attack effect always stutters for me on first load; triggering it causes the generation of about 10-15 shaders, most of which take around 8ms to load, with one or two taking around 12-15ms. I'm not sure if they're all generated on a single frame, but it's probably enough to tank the frame rate no matter what. The game is frequently loading new shaders. You can mitigate it a bit by forcing some preloading via the command line options, but it still doesn't preload all monster shaders. Those seem to be deferred until they're actually needed. I suspect this is likely going to be an issue until either 1) the PoE devs change how shaders are loaded in the game or 2) the wine generation of hlsl->glsl gets significantly faster. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=34011 Robert Xiao <nneonneo(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |nneonneo(a)gmail.com --- Comment #33 from Robert Xiao <nneonneo(a)gmail.com> --- (In reply to Zakk from comment #32)
Wine 2.9, MacOS: same freeze/stuttering issue. It is much much better on Nvidia+GLSL disabled, but in that case some effects aren't rendered.
I put some crude timing/debugging into glsl_shader.c: I'm pretty sure this issue is shader generation related.
Out of curiousity, did your timing reveal if the main delay was due to HLSL->GLSL translation or due to OpenGL Compile/Link time? The former we can probably cache to disk (at least, it would be a potential solution); the latter we can do nothing about unless glProgramBinary is available (it isn't on my laptop). -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=34011 --- Comment #34 from Zakk <zakk(a)rsdio.com> --- It was mostly in OpenGL compile/link if I'm remembering correctly. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=34011 talchas(a)gmail.com changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |talchas(a)gmail.com --- Comment #35 from talchas(a)gmail.com --- With NVIDIA and glsl=disabled, as said the resource loads are not an issue. The eventual massive slowdowns during lots of spell effects are (at least with the spell effects created by my character's build) caused by massive heap fragmentation in RtlAllocateHeap. Adding HEAP_freeListSizes entries of 0x198, 0x8c8 and 0xbc8 nearly entirely fixes this for me, though after a few hours it started lagging again and then crashed shortly afterwards, so it's still leaking somewhere (which might be a partial cause of the fragmentation). -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=34011 --- Comment #36 from Robert Xiao <nneonneo(a)gmail.com> --- Previously I was getting crash-on-startup from glsl=disabled. I patched wined3d to increase the number of float constants (my gfx driver reported only supporting 128 constants, but some PoE shaders use up to 140): diff --git a/dlls/wined3d/arb_program_shader.c b/dlls/wined3d/arb_program_shader.c index fa72b4f..da8b10b 100644 --- a/dlls/wined3d/arb_program_shader.c +++ b/dlls/wined3d/arb_program_shader.c @@ -4942,7 +4942,7 @@ static void shader_arb_get_caps(const struct wined3d_gl_info *gl_info, struct sh if (gl_info->limits.arb_ps_native_constants < 24) ps_consts = gl_info->limits.arb_ps_float_constants; else - ps_consts = min(gl_info->limits.arb_ps_float_constants, gl_info->limits.arb_ps_native_constants); + ps_consts = max(gl_info->limits.arb_ps_float_constants, gl_info->limits.arb_ps_native_constants); if (gl_info->supported[NV_FRAGMENT_PROGRAM2]) { After this change, glsl=disabled works. I also had to add the game options "--noasync --nopreload" to prevent an outbreak of black/missing textures. A few effects are missing due presumably to my horrible patch and the limited HLSL shader support, but it works well enough to be usable. It still crashes after a while due to memory exhaustion; this is tracked in bug #43545. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=34011 Fincer <fincer89(a)hotmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |fincer89(a)hotmail.com -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=34011 Robert Olofsson <winehq(a)khelekore.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |winehq(a)khelekore.org -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=34011 David Brooks <skade88(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |skade88(a)gmail.com --- Comment #37 from David Brooks <skade88(a)gmail.com> --- Disabling GLSL in WINE fixed the stutter for me completely. I have played my newest character for 17 hours with no stutter. I am on Wine-staging 2.17. Ubuntu 17.04. 4.10.0-35-generic #39-Ubuntu SMP Wed Sep 13 07:46:59 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux NVIDIA binary driver - Version 375.66 from nvidia-375 (proprietary, tested) -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=34011 cypherznenigmas(a)gmail.com changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |cypherznenigmas(a)gmail.com --- Comment #38 from cypherznenigmas(a)gmail.com --- For Users Running with an AMD GPU this setup worked for me Build Core i5 kaby lake RX480 Wine 2.21, using winetricks and playonlinux Set on Windows 8 use winetricks and get vcrun2015 riched20 usp10 corefonts do not disable glsl it will crash immediately at this point the game should run but have massive screen flickering issues. the only thing that solved this for me was to disable engine multithreading in the in game settings. it doesnt completely remove the stuttering, but it makes the game playable without the need to discover if you're epileptic or not I also have the arguements -gc 1 -ns set up but I'm usure as to how well they're helping -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=34011 joaopa <jeremielapuree(a)yahoo.fr> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jeremielapuree(a)yahoo.fr --- Comment #39 from joaopa <jeremielapuree(a)yahoo.fr> --- Does the bug still occur with wine-5.17? -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=34011 Rémi Bernon <rbernon(a)codeweavers.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |rbernon(a)codeweavers.com Resolution|--- |FIXED Status|NEW |RESOLVED Fixed by SHA1| |40b7c3e89a95d6ccb190b234d4a | |d13b3a8304495 --- Comment #40 from Rémi Bernon <rbernon(a)codeweavers.com> ---
From the comments and other reports I believe this is fixed with heap performance improvements. Please re-open with more details if not.
-- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=34011 Alexandre Julliard <julliard(a)winehq.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED --- Comment #41 from Alexandre Julliard <julliard(a)winehq.org> --- Closing bugs fixed in 8.3. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
participants (2)
-
wine-bugs＠winehq.org -
WineHQ Bugzilla