Jump to content

Ready

Members
 View Profile  See their activity

  • Posts

    651

  • Joined

  • Last visited

3 Followers

Personal Information

  • Flight Simulators
    DCS, MSFS, X-Plane.
  • Location
    Netherlands
  • Interests
    Aviation (DCS, GA), Pool (1-pocket), Sailing
  • Website
    https://www.youtube.com/channel/UCm1MRJcn9K-89F6qnK0DVIQ

Recent Profile Visitors

2994 profile views
  1. Ready
    Good you ask. tbh the results are from what I remember. I just checked my change log in my thread on this forum for the numbers (you can find the link in my sig), I found the MSI-util tests I ran back in december before I did a complete reinstall, but... I see the results themselves were not written down in the log. I think I also ran some tests with the MSI change after my reinstall a couple of months later, but those tests are no mentioned in the screenshots of my log. I see some files dissapeared from the thread, only filenames remain. When I am back at my rig I will see if I can pull them straight from my original excel. With regards to how I measured; I have used various tools and methods for the testing, mostly focusing on frametimes, latency and reducing those irritating microstutters that sometimes tend to appear out of nowhere. In my thread you can read about most of the ups and downs with the various tools. iirc I was focusing on input latency towards the end of the thread.
  2. Ready
    Yup I have had good results with it too.
  3. Ready started following VR benchmarking methods , Completed A10CII Outpost , Completed A10CII Outpost official campaign and 1 other
  4. Ready
    Interesting! Might give it a spin after returning from vacation.
  5. Ready
    Yep that's weird, never saw that before. Was this only after the latest update?
  6. Ready
    Nice!
  7. Ready
    For DCS in-game settings I found it to work the best by just turning everything down and one by one check what each setting does for your performance and your personal visual experience when you play around with it. Imho some things are just too taxing for very limited gain and some I can even hardly spot. When I am in the middle of the action I also don't really look at how nice reflections are etc. It is still immersive when everything is at low because I get used to it. But I do get irritated by trees popping up, unclear instruments, lags or microstutters and things like that, those things for me break the immersion. Some settings can be played with while in the game. For example the sliders for trees etc. I turn them down when I know we will fly low in green fjords. Best to try each change for yourself. Just run a test before/after and also see what your experience is within the headset. I sometimes had good numbers but strange things happening visually. I sometimes tried a couple of settings at the same time, trying to save some time, but to be honest it does happen that I still have to go back and check them one by one because the effect was counterproductive and I was not sure which one was the cause. So I would recommend to just take them one at a time. The current experience is pretty stable and I still have quite a backlog of things to check and further work on. But I am not in a hurry and sometimes just like to fly as well
  8. Ready
    Yes I think our objectives have quite some overlap. I aim at getting the best performance out of my own hardware, which to me translates in a stable/stutter-free experience, which for me began when I first got my G2 and was fighting to get a decent picture in my headset. So I try to get as close as possible to 90fps without microstutters (1% lows), which I try to realize by stripping and silencing Windows (which is a pretty big chunk of it) and optimizing all the hardware, DCS and the additional software my rig is running. Your checklist is fine; it points to items for people to look at. Some of the things that work differently for me (and are sometimes contrary to popular belief or recommendations that are given here and there); game mode, full screen, HAGS, HPET, overclock on my CPU and GPU, limiting FPS. So my main point would be to check the recommendations, but not blindly follow everything and test things for yourself (if you have the time and interest to do so). Look at the numbers and the experience in the headset (sometimes for me they did not match). Write down the changes and their impact in a log to track and compare and use various tools to do so.
  9. Ready
    Nice helpful list! Some of the items work the other way around for me though. Recommend running baseline tests before and after each change and keep a log of all the changes with their impact on your performance. I have also spend months aiming to get the best out of my system. Did you take a look at my list of changes? There might be some items in there you might like to add.
  10. Ready
    Nice! Have you considered/looked into CapFrameX? I used to perform the Excel calculations before as well using various tools to record, export and analyze. I found that https://www.capframex.com/ is way easier to quickly get to useable visual data and to quickly compare settings. No more exporting, importing, manual stuff, no more Excel wizardry needed. Just run the game and use hotkeys to start/end the log recordings, add titles/descriptions to the recording tracks and voila. I think it will save you a lot of time going forward and I assume it will have most of what you are looking for. I have used it 500+ times in my quest to silence Windows, stabilize my rig and get the most performance out of the hardware, testing all setttings and scenario's I could imagine and stuff I found online, I still use it to test the effects of updates or setting changes. You can find some decent examples of this tool in the postings of my thread (don't want to self plug). I also use XRFrameTools, but mostly to get realtime visualization of stability and get direct feedback of things I change on the fly. I now only use Excel to keep track of all the changes I make (either by for example DCS updates, driver updates or me tweaking something); with each change I create a log entry and log the frametimes etc. This ends up in one chart to show historically how my frametimes are improving or degrading with changes. It also is great to lookup stuff I have tested. Hope it is of any help!
  11. Ready
    Thanks for sharing!
  12. Ready
    Walk back the update? I frequently also have updates messing things up. If it works don't touch it if you don't have to
  13. Ready
    Hi I try to keep the first posting in this thread updated, I also added graphs where you can see the items that gave my system the biggest improvements. Of course your miles may vary. I did not use Atlas or any other preconfigured/debloated install because I wanted to decide for myself which functionality I disable and I wanted to stay in control. The end-result may be similar, I am not sure. I have seen some videos on comparing installs like Atlas and tbh was not regretting I went the long route. Whenever there are new thoughts or things to try I will add them to this thread and once in a while I will update the original posting with a list of my most recent changes.
  14. Ready
    Thanks I will check it out. Maybe it will be the solution to a weird issue I see in latencymon.
  15. Ready
    Nice one! Looking forward to the pilot body for a long time! Would be great to get additional visual improvements from within the helmet like moveable visor, the overlay of the visor and maybe some additional symbology.
  16. Ready
    I killed the process and the speed stayed the same, but haven't restarted yet. Not sure yet how it behaves.
×
×
  • Create New...