Jump to content

Groove_C

Member
  • Content Count

    940
  • Joined

  • Last visited

  • Medals

Everything posted by Groove_C

  1. And you say that 9700K is better than 3700X, because average and max FPS are better, which is also completely wrong, since Intel dips to 33 and AMD to only 38, which is more important, obviously. What brings me 110 FPS peak if I have just little above 30 FPS in heavy situations, whereas the other system delivers almost 40 FPS in same heavy situation.
  2. You say you tested each change in video quality and CPU/RAM settings 5x, but in your live videos I could see you run 1x and then directly upload to imgur with titles for screens, so... And also making average of all 5 runs is not the way I would do, if in some runs min or/and high are more than 2 FPS off. I'm not a fanboy, and if Intel or AMD sucks -> they suck. I can bash on Intel for known for years vulnerabilities, even if I myself have more than 1 Intel. I don't care. I don't "protect" something, because I'm the owner of. Would have be stupid if I did so. I know other people that have benched Intel vs. AMD and Intel was not behind AMD @ min FPS. They did it with RAM at +- same settings and with CMA AVX2 x64.
  3. Well, as I could see, you benched only 1x per setting, which is really wrong, because of great discrepancy there can be between each run, thus resulting in wrong results for AMD and Intel and you also couldn't manage to OC your RAM on Intel. So for me, the results can't be concidered at all. One needs to run at least 3x per quality setting and per CPU and/or RAM setting, to make and average of 3 runs, for min, avg and max. And if the discrepancy between runs is high (2 FPS or more), continue to bench (more than 3x) and completely drop anomal runs. If min is too low or max is too high. Also closing all known/unnecessary background tasks, like antivirus, firefox, discord, monitoring software (MSI Afterburner/EVGA Precision X/ HWiNFO64), nVidia Shadowplay, Discord, Skype... that can influence the results. @ standard I can have like 36, 43, 39 FPS min, 68-70 FPS avg and 95, 108, 103 FPS max. So I have to understand what is anomal, too low 36 FPS or too high 43 FPS, too low 95 FPS or too high 108 FPS. To clarify this, I have to run more at same settings, to see what is closer to the reality, in the way, what comes as result more often, so I can exclude, 36 or 43, 95 or 108. To have a clear picture.
  4. And not even released 10th gen Comet Lake CPUs are affected as well, since same architecture ))) So they will have a lot of vulnerabilities right on the release ))) And new vulnerabilities on the way. Just not publicly disclosed yet, since no solution for them, yet. Cristiano Giuffrida, Vrije Universiteit, Amsterdam Security engineering at Intel (or rather lack thereof) is still business as usual. These issues aren't trivial to fix. But after eighteen months, they're still waiting for researchers to put together proofs-of-concept of every small variation of the attack for them? It’s amazing. We don’t know the inner workings of Intel's team. But it’s not a good look from the outside. If Intel isn’t looking and is making no effort, who knows how many vulnerabilities are left?
  5. Well, when BIOS and/or Windows updates to fix (partially) vulnerabilities, it costs performance, so...
  6. https://feedback.bistudio.com/T148556 - List of vehicles with wheels sinking into the ground (locally)
  7. RAM OC helps a lot, once in CPU limit. Proven! Sure, at higher res and video settings there is less of a difference, but still should be. If it's for free, why not use it.
  8. You can set SA and I/O analog/digital to 1.25 V both. So 3x 1.25 V.
  9. Download and install this and launch it after reboot: Asus TurboV Core 1.03.02
  10. Need to also increase SA (system agent / memory controller) and I/O analog/digital voltages when very low timings and/or very high frequency. Core voltage might need to be increased as well. ASRock Timing Configurator 4.0.4 for Z390 Secondary and tertiary timings are very important as well. If PC is not crashing, it doesn't mean, that everything is fine with RAM settings. Can result in lower FPS.
  11. It's really wrong to say, that Intel doesn't benefit as much from RAM OC as Ryzen.
  12. Increase cache frequency and if not stable -> increase core voltage, as core voltage is for core and for cache.
  13. Cache should also be OC'ed as much as possible. Depends on core voltage as well.
  14. The best RAM specs for Intel are also not above 3800 MHz 14-15-14, 15-14-14 or 15-15-14, since 4200-4266 MHz CL17 or 4000-4133 MHz CL16 is slightly worse than 3800 CL14/15. Only higher bandwidth, but worse timings. Even DDR3 2400 MHz <40 GB bandwidth is not restricting anything in anyways, DDR4 3800 MHz ~60 GB banwidth wouldn't as well. Should result in not more than 40 ns, if all secondary and tertiary timings tightened as well. I would say even <40 ns, whereas on AMD it's impossible to go <61-62 ns with same 3800 MHz CL14/15. Arma will 100% approve such low latancy! I'm also @ 39-41 ns (Aida64 results tend to fluctuate from run to run) with my DDR3 2400 CL10 and Arma likes it very much.
  15. If there is an option to select nVidia NVEC codec in OBS, then this is what I would choose. This way, even if you have only 4 cores i3, it doesn't matter, since it's the GPU that will take care of almost everything and CPU load will be minimal.
  16. I wouldn't go past 5.0 GHz, even if the CPU was capable of 5.1-5.2 GHz, since no FPS increase past 4.7-4.8 GHz in Arma. So no need to stress the CPU with a lot of voltage for just 100-200 MHz more if it won't improve your FPS in Arma or if it will by like 1 FPS, average, which is within margin of error.
  17. No need for water cooling. A high end air cooler is more than enough. A 240/280 mm AiO should be more than enough as well.
  18. 9600k will deliver exactly same FPS, in Arma, as client, at same frequency, provided you don't use OBS to stream/record. Server side happily uses more threads/cores than client.
  19. @razazel If you ever whish to add ticket numbers for fixes listed in changelog - here they are: https://forums.bohemia.net/forums/topic/140837-development-branch-changelog/?do=findComment&amp;comment=3389138 Fixed: Broken tooltip in object equipment storage in 3DEN - https://feedback.bistudio.com/T117193 Fixed: Script error in Splendid Camera when mouse or joystick were mapped to camera controls - https://feedback.bistudio.com/T146601 + https://feedback.bistudio.com/T117681 https://forums.bohemia.net/forums/topic/140837-development-branch-changelog/?do=findComment&amp;comment=3392238 Fixed: NATO Pacific Mk6 Mortar, HMG and GMG were assembled into Independent versions instead of NATO Pacific - https://feedback.bistudio.com/T145362 Fixed: Warlords - The inventory screen no longer remains open when opening Arsenal - https://feedback.bistudio.com/T147759 Fixed: Potential script error in the patrol module - https://feedback.bistudio.com/T117706
  20. https://feedback.bistudio.com/T148498 Not working incoming missile sound warning + M letter on radar (where radar available) Incoming missile sound warning + M letter on radar (where radar available) are all connected to driver only or available through driver only. 100% reproducible and problematic on any server, any mission and by/for any players.
  21. https://feedback.bistudio.com/T148491 List of helicopters/planes where it's impossible to get out when under armor fire, due to get out animation and DPS (damage per seconde) to the player Problematic on any server and any mission and 100% reproducible.
  22. https://feedback.bistudio.com/T148482 Commander smoke missing and/or not visible in interface (locality issue?) Concerns all ground vehicles, that have commander seat and where commader is the one, who has smoke. Problematic on any server and any mission and 100% reproducible.
×