Jump to content

GM_Peka

Member
  • Posts

    823
  • Joined

  • Last visited

Everything posted by GM_Peka

  1. You should focus more on the boost clock, which is 4.1GHz, anyone can easily get the 6300 running at 4.1 with very simple/little bios tweaking.
  2. I dunno about that, maybe against an ivybridge i3 that'd be pretty spot on, but just look at this. And most of those games in the video actually work pretty well with large core counts, in some older games, the AMD chip would get slaughtered. Edit: oh someone already posted the video, I was that long rewriting my message.
  3. 6300 or go Intel i3. The 6100 would be mind numblingly silly, as it isn't even current, the Athlon series have less cores and no L3 cache; effectively stripped down versions of the FX line, even though they are based on newer architecture. i3 will generally give a more consistant performance, because while the 6300 will give a good performance on games that can use 6 cores, the i3 will destroy it in games that use 2 or even 4 cores. The new Intel i3 6100 is actually a bit faster than the previous i3s, gaining speed through performance per clock aswell as gaining a clock boost overall. Making them a pretty speedy 2 core/4 thread processor.
  4. I don't really even bother overclocking modern Intel stuff, the gains a smaller than they used to be. For instance, the 4790k came in at 4.4GHz stock, and most people got it to 4.6-4.7GHz on average. By comparision, I got my old q8300 to 2.8 from 2.5 stock with little effort. Alot of AAA games don't even see that much gain from a CPU overclock anyway, so that 10% cpu overclock turns into like 2.5% actual fps gain. On top of that CPU overclocks mean more power usage, heat and noise (albiet not much in alot of case) and things can still crash even though you thought everything was stable (I got a CPU prime 95 24 hour stable, only to crash 40 minutes into rendering a video) My stance on GPU overclocking is completely opposite though, GPU overclocking is hard to fuck up and very predictable, you can do a quick and dirty overclock in 10-15 minutes and be fairly certain nothing will fuck up, but at the same time, you almost get 1:1 fps gains with clock speed. Just my person views on stuff at least.
  5. The two times I've used Asus' auto overclocking stuff, it's used too little voltage somewhere on both counts.
  6. AISuite commonly has issues, bug and the sorts, my advice is to stay away from it, you even need a clean uninstall utility to remove it from yours system, cause the default uninstaller leaves a service or 2 running. You'll see alot of people on the internet having various issues and sometimes BSODS.
  7. That's not true, the lower input latency is very noticeable. And bhopping and long jumps can be easier at higher fps. For competitive FPS, you need all the frames you can get.
  8. 250 fps or so with that, yeah, abit more maybe, Post process and stuff off helps. Once you get past a gtx 950, It's all CPU, you want newer architectures and higher clocks for the highest fps. 2400mhz RAM will yield another 1-2% more fps. Finally, GET AN SSD, and SSD is far more important for CSGO than a 970. With in SSD, you'll never get any loading stutters, and generally get into the map first.
  9. On higher resolutions, CPU bottlenecking is less of an issue because higher resolution only really puts more stress on the GPUs, however, it is still worth putting a bit of money in a CPU, especially considering how much you've already put in everything else, a decent CPU isn't really asking much when you've already spent more than a thousand on everything else. An i5 will do, an i7 if you want to go big dick.
  10. I wish I knew how the stood right now, I know that earlier on freesync had some wierd ghosting issues, but I think those might've been fixed.
  11. gsync and freesync are really nice for games that are capped to low framerates, or don't work well above 60 fps, etc.
  12. Shadows can be generally quite CPU heavy too, I haven't played that game though.
  13. A decent encode takes time. When I set my settings high in handbrake, I can render as low at 5 FPS (but I only do short videos, so a slow/high quality encode doesn't take ages).
  14. Doesn't really matter, just anything that isn't rough, so pretty much any cloth. I sometimes use Tissues, because I'm to lazy to get a cloth :3. There isn't really any science behind cleaning a fookin monitor anyway. Appart from don't use chemicals as they can dissolve the matt coating etc.
  15. Water and clean cloth. (No chemicals)
  16. Yeah, disable resolution scaling in your GPU control panel and set the resolution lower. Alot of osu! players do this.
  17. It'll make a lot of noise :3. It's pretty quick though. Edit: Oops, I was thinking 6990, so it won't be as loud, but it'll hardly be silent :3. It's a cool card to own though IMO.
  18. Tell us a budget for the rest of the system, and we'll recommend stuff for you.
  19. Screen resolution>Advanced>monitor>Screen refresh rate.
  20. Very little, my ROG SWIFT uses 27 watts. Older, LCD monitors used about 40. LED monitors are around 20 or so usually. This is different if you have your monitor overly bright though. Setting the brightness down saves a bit of power.
  21. Just watch that through. Although one thing people often miss, is there's still input latency with gsync when you're running at the maximum 144fps. But the latency isn't there if you just cap to 138 FPS or something.
  22. Stuttering and tearing happens at any frame rate. Unless you have a perfect 144 fps that's also synced to your monitor.
  23. Why would time somehow make the game no good anymore? It's as fun as it was 6 years ago etc.
×