BenQ ZOWIE XL2430 (not XL2430T) includes DisplayPort cable or only DVI-DL cable?
Account Details | |
---|---|
SteamID64 | 76561198057296106 |
SteamID3 | [U:1:97030378] |
SteamID32 | STEAM_0:0:48515189 |
Country | International |
Signed Up | November 18, 2016 |
Last Posted | January 27, 2017 at 12:14 PM |
Posts | 7 (0 per day) |
Game Settings | |
---|---|
In-game Sensitivity | |
Windows Sensitivity | |
Raw Input | |
DPI |
|
Resolution |
|
Refresh Rate |
Hardware Peripherals | |
---|---|
Mouse | |
Keyboard | |
Mousepad | |
Headphones | |
Monitor |
1. You should disable AMD Turbo Core feature in BIOS because it can cause overheat. If you want to overclock you really should do it manually (just change the multiplier).
2. If you're not going to overclock your CPU you should undervolt it (set lower CPU voltage without changing the frequency). This helped me a lot. Temperatures in TF2 dropped from 55-60 to 40-45, but performance stayed the same.
https://techreport.com/forums/viewtopic.php?t=95088
http://www.ronwoods.us/2013/08/the-fx-8320my-journey-into-under.html
AMD says 62C is the maximum allowed temperature for AMD FX CPUs. For me, anything higher than 60C for prolonged periods of time (over 15 minutes) causes memory parity errors and crashes.
https://steamcommunity.com/profiles/76561792132465273
this guy's so silly
FX-8320E is the same as FX-8320/8350, but underclocked to 3200 MHz. I have FX-8320 @ 4700 MHz and I get only ~142 fps with it (1080p, comanglia + very high textures), but when I underclock it to 3200 MHz I only get ~106 fps. I wouldn't recommend buying this CPU for TF2.
Shanky
Sensitivitity is 1:1 (6/11) by default. I think what you're talking about is mouse acceleration. If you're using Xfce or KDE, you can disable it in the GUI.
But if you're using Gnome 3 or you're not using Desktop Environment at all, you can try disabling mouse acceleration by using xinput (you need to have xinput package installed), but it might not work on the newest version of X.org. First, you need to get your mouse name or id:
user@localhost~$ xinput --list
⎡ Virtual core pointer id=2 [master pointer (3)]
⎜ ↳ Virtual core XTEST pointer id=4 [slave pointer (2)]
⎜ ↳ YOUR MOUSE NAME HERE id=8 [slave pointer (2)]
...
then you disable acceleration (with second command you can adjust your "real" mouse sensitivity, "1" is the equivalent of 6/11):
xinput --set-prop "YOUR MOUSE NAME HERE" "Device Accel Profile" -1
xinput --set-prop "YOUR MOUSE NAME HERE" "Device Accel Constant Deceleration" 1.000000
If that doesn't work, you can try using xset command, but it also might not work:
xset m 0 0
Finally, you can disable mouse acceleration completely in the X.org config as described in this guide.
P.S. Actually, my "gaming" mouse had acceleration disabled by default, but my cheap office mouse didn't.
P.P.S. Also there are guides for setting up mouse sensitivity if you want it:
https://bugs.freedesktop.org/attachment.cgi?id=17772
http://510x.se/notes/posts/Changing_mouse_acceleration_in_Debian_and_Linux_in_general/
sage78great tip ! this worked in my laptop making the average clockspeed higher on the "performance" mode but it still varies (480 MHz to 2.16 GHz on intel N3050)
do you know how to make it fixed?
Arch Wiki says that new Intel CPUs (like N3050) use intel_pstate driver which uses dynamic frequency scaling, so it should be fine (source):
Note: The intel_pstate driver supports only the performance and powersave governors, but they both provide dynamic scaling. The performance governor should give better power saving functionality than the old ondemand governor.
and also this article says that performance using intel_pstate shouldn't be an issue:
we are seeing very significant power/performance improvements with the 3.9/3.10rc code over using ondemand, and a much smaller performance gap with the "performance" governor in terms of performance.
Disabling CPU powersaving also might help (setting CPU frequency scaling governor to "performance" instead of default). I use cpufreq-set from cpufrequtils package:
for ((i=0;i<$(nproc);i++)); do cpufreq-set -c $i -r -g performance; done
I made benchmark using governor "ondemand", which is default for me:
2639 frames 21.300 seconds 123.90 fps ( 8.07 ms/f) 9.436 fps variability
2639 frames 21.197 seconds 124.50 fps ( 8.03 ms/f) 10.121 fps variability
2639 frames 21.456 seconds 122.99 fps ( 8.13 ms/f) 9.636 fps variability
and using governor "performance":
2639 frames 20.154 seconds 130.94 fps ( 7.64 ms/f) 8.499 fps variability
2639 frames 20.087 seconds 131.38 fps ( 7.61 ms/f) 8.380 fps variability
2639 frames 20.187 seconds 130.73 fps ( 7.65 ms/f) 8.477 fps variability