<html> <head> <base href="https://bugs.freedesktop.org/" /> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - Borderlands 2: Constant frame rate drops while playing; really bad with additionl lighting" href="https://bugs.freedesktop.org/show_bug.cgi?id=84570#c21">Comment # 21</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - Borderlands 2: Constant frame rate drops while playing; really bad with additionl lighting" href="https://bugs.freedesktop.org/show_bug.cgi?id=84570">bug 84570</a> from <a class="email" href="mailto:kai@dev.carbon-project.org" title="Kai <kai@dev.carbon-project.org>"> Kai</a> <pre>(In reply to Andreas Hartmetz from <a href="show_bug.cgi?id=84570#c19">comment #19</a>) > I've noticed that disabling CPU frequency scaling makes a big difference in > the severity of micro-hangs (3.17, dynamic lights off). My explanation is > that, when threads are waiting for each other, the scheduler doesn't know > that the apparently "idle-blocked" threads would all run faster overall if > the CPU went faster. Doesn't matter if that's wrong, the difference is > there... > > At least on AMD (some Intel CPUs use a special frequency scaling driver), > you can effectively disable CPU frequency scaling like so: > echo performance | tee /sys/devices/system/cpu/cpu*/cpufreq/scaling_governor > > Maybe that also helps a bit with dynamic lights on? I have that Intel pstate driver for my CPU, but after feeding the performance setting to scaling_governor the amount of drops goes down, the drops aren't as severe (usually around 17 FPS and not single-digits; only exception: the first five to ten seconds after loading screens) and the overall FPS rate is up by ~5-8 FPS. Thanks a lot for that tip! (In reply to Ian C. Bullard from <a href="show_bug.cgi?id=84570#c20">comment #20</a>) > (In reply to Kai from <a href="show_bug.cgi?id=84570#c18">comment #18</a>) > > That's quite possible, though I can see drops (as shown in the attached > > screenshot), when I do nothing particularily intersting besides moving > > around in an area which I've been in for some time. The really bad drops > > (single-digit) indeed seem only to happen upon entering an area, ie. after a > > loading screen. > > The drops can occur even if you've been in an area for a while. Borderlands > is a heavily streamed game so new textures/shaders can cause a hiccup. > We're looking at ways to smooth this out. Thanks for clearing this up. Though I like to state that using the radeonsi driver with the stack detailed in <a href="show_bug.cgi?id=84570#c15">comment #15</a> gives you a very playable game (almost no drops) with "DynamicLights=false" and only the smaller drops I described in <a href="show_bug.cgi?id=84570#c18">comment #18</a> with DynamicLights=true. From my POV that sounds like "supporting" Radeons with the FLOSS driver should be ok or at least not worse than nVidia cards. Especially when combined with Andreas' suggestion. I've been playing for a few hours (alone and co-op) with this stack and DynamicLights=true and it works for me; if you keep DynamicLights off it should work for most, shouldn't it? > > Though I did hear from a friend – using a nVidia card with the proprietary > > driver and DynamicLights=false – that she's seeing occasional > > drops/micro-freezes as well. > > That fits with what I expected and matches what I said above. Oh, I thought your previous statements only related to Intel and AMD GPUs (especially since nVidia is the only officially supported GPU vendor).</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>