Jump to content

AdrianL

Members
  • Posts

    507
  • Joined

  • Last visited

Everything posted by AdrianL

  1. The original version of Windows 11 (also known as version 21H2) was released in October 2021. It carries the build number 10.0.22000. So you are a few years out of date. It also went out of support in October of last year https://learn.microsoft.com/en-us/lifecycle/announcements/windows-11-21h2-end-of-servicing
  2. You have mods installed in 'saved games'. and a lot of sound related warnings.
  3. If you have any mods installed, you need to remove or update them. The UH-60, Grippen, SU-30, etc mods are all causing issues with the OB like ships not spawning
  4. You are likely exceeding the default Win 260 character path length. Either: Google "Enable Longer File Path Support" to increase this limit Move the download to a very short path before extracting i.e. c:\a
  5. Remove your mods. SU-30, Grippen, UH-60 and others are causing this. Some of the mods have already been updated to address
  6. I would recommend that you do not get your hopes up. This was Cobra's reply to that comment
  7. Stop assuming you speak on behalf of everyone. I care about plane directors.
  8. Specifically, you failing in the 'edterrainGraphics41.dll' and you have manifest failures in 'mods/terrains/caucasus/rastercharts/5m/256m_xab00.zip' Remove mods and then do a repair. Assuming that addresses the issue then you can slowly start adding back your mods.
  9. You now crashing in zlib library. Also a IN_PAGE_ERROR. You might have a corrupted memory stick or disk drive. Run a memory test and a disk hardware test to be sure. See
  10. You getting an IN_PAGE_ERROR, which means DCS cannot read a file. Do a slow repair. Also try with all your mods removed (You have a lot installed). See and
  11. See this Reddit post. The F-4E is NOT releasing this year https://www.reddit.com/r/hoggit/comments/185mhe3/for_those_that_missed_it_the_f4e_is_not_releasing/
  12. It is not available and will likely come with the next patch. I think he means to the ED source control for inclusion with next patch
  13. See following post for possible cause. Tacview might not have permissions anymore to write to your documents folder. For example, Windows Security → Protection History is enabled
  14. You have a very small page file, considering you only have 16 Gig of ram. From your log: APP (Main): CPU cores: 4, threads: 8, System RAM: 16323 MB, Pagefile: 2560 MB Try increasing your page file to 32 gig i.e min and max set to 32768 Your logs ends with ERROR ASYNCNET (7540): HTTP request dcs:stats failed with error 6: Couldn't resolve host name See
  15. From your log: APP (Main): CPU cores: 6, threads: 12, System RAM: 32668 MB, Pagefile: 1024 MB Try increasing the size of your page file to 32 gig. So min = 32768 max = 32768.. Do not let windows manage See
  16. Please do not link to this video as it does not state that you have to apply it to your currently active power plan. Finding the first key does not guarantee it is your active power plan so you might not actually have disabled parking. See
  17. If you on a laptop then settings might have been hidden from the power plan by your manufacturer, or maybe was not run under an admin cmd line. Also max sure it is the high performance plan. Use a app like CPU Unpark or Park Control. They just setting the value in the registry (which is what the power plan is reading). Note it is for the selected power plan and then if on batcher or plugged in. In the app, set parking off. You should not need to reboot but do recommend you switch the active power plan to something else and then back again. It also seems that CPU parking is not the answer for everyone's stuttering issue.
  18. Once you press Apply, it is applied to the current power plan. So app can be closed and will not be needed again, unless the power plan changes. If you reboot and then look Unpark CPU, it should show 100% for the selected power plan. Otherwise the setting has not been applied, for whatever reason
  19. DCS is using DLSS 3.5 but without Frame Generation See
  20. Not the correct settings. The CPU Parking setting is hidden by default To show it see But I recommend CPU Unpark.
  21. You would need to open a new thread and post the logs to see what is causing that. 1 of those threads is the render thread so will generally be maxed out.
  22. Still check if you have CPU parking off. The ultimate perf plan does not switch it off by default
  23. The problem with the video is that it says to search once. The setting needs to be applied to your active power plan, which might not be the first one found in the registry. Download CPU Unpark (Does not need to be installed) and see what the parking index is. You want it to be 100 for the active power plan. You might need to reboot. See
×
×
  • Create New...