4/27/2023 0 Comments Afterburner benchmark![]() ![]() I know there are people here that know how to use it. I’m not going to explain step-by-step how to setup/use MSI Afterburner. This is what I would expect from people running the benchmark track when posting their results. The tracks have 5 parts that hit system resources hard in DCS-ġ.) Large number of static aircraft on carrier deckĢ.) Flying low over heavily forested areaĥ.) Helicopters launching flares over the city I made two tracks, one with clouds and one without. If you want to test the in-game performance of your overclocks or graphics settings, you can use Afterburner’s built-in benchmarking tool. I created a couple of replay tracks that purposely stress the gpu. I’d like to see that other people are having the same issues as me so I can be confident it’s not just some hardware or settings issue on my end. The one thing that would be nice about this is it would help to confirm some issues like frametime spikes and stutters. People have to post screenshots of their settings, capture results in something like Afterburner, state their system specs, and then post it all on the forum. If we try to do it on our own then we have to get everyone who runs it to follow very specific instructions which is well… difficult. ![]() ![]() If DCS had a built-in benchmarking tool that would be one thing. With all the new features there are new impacts pretty much nailed it. ![]() But it is not the same engine as 1.5.8, and the Caucasus map is certainly not Nevada even if you are coming from 2.2. So 2.5 is here, in beta anyway, and everyone wants to jump in and blow stuff up. A decent way to track performance is through guides like this: ED Forums 2.5 Settings Comparisons and GPU Impact I don’t want to be discouraging as this is a good idea, but it is currently just a really large moving target to make good comparisons in this way. It’s hard to get that baseline hardware profile down.ĭCS is still under pretty active development in terms of performance and VR. The hardware and the hardware drivers evolve regularly, often in combinations that cause impacts to performance. The configurations and settings to compare are numerous, in that shadows from medium to high vs anti aliasing vs etc. That means manual testing, which needs to be long to average results out (to stop changes in human input etc). Like mentioned, the tracks aren’t deterministic of outcome. It’s a noble endeavor, but there’s a lot of variables, and they change quite a lot as well: ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |