Jump to content

sslechta

Members
  • Posts

    508
  • Joined

  • Last visited

Everything posted by sslechta

  1. I've had good luck just having NVIDIA Control Panel set to have VSYNC set to ON. It made a big difference from the OFF option and VSYNC enabled in game. I haven't tried Adaptive yet since ON is working fine.
  2. Several topics on this one already: https://forums.eagle.ru/showthread.php?t=162111 https://forums.eagle.ru/showthread.php?t=204393 https://forums.eagle.ru/showthread.php?t=200977 Looks like it has not been updated for 2.5 yet.
  3. Another thing to check is if you have a NVIDIA card/drivers if you had application specific settings for the Open Beta, maybe those need to be set for the Release version. Of course if you customized anything on the NVIDIA control panel universally, that wouldn't matter. Good luck hunting!
  4. When you installed OA and OB, you volunteered to do that. ED didn't make you do it. There should be no confusion on the versions if you look at what you download and install on your own computer. The install folders clearly say DCS World, DCS World Open Beta, etc..... You not having a firm grasp on the way they classify their installs is not their fault. At this point wipe your whole machine of DCS stuff and just install the release candidate and stick with that only. Don't download alpha or beta versions if you get confused on so many of them.
  5. 2.5 open beta and 2.5 release version are currently identical. If you are having issues on one and not the other, I would compare your settings and configs. If open beta ran better for you then copy over your settings to release.
  6. When you upgrade 1.5.8 release to 2.5, it automatically copies files from the open beta install. There is no need to force it to.
  7. Yes, if you read this forum and some of the open beta forums, you'll see several posts about this same topic. It is a known issue at the moment without a fix.
  8. Release version is identical code to open beta so that is why the problem is the same. Once open beta does another update then the two versions will be different.
  9. Bipper, your specs are a little low for 2.5. The graphic drain on the system has increased several times over.
  10. Launch the DCS 1.5.8 version on your machine. It will prompt you to update.
  11. Hey Weld, I see the same thing happen and wrote a post a while ago where you can just wait out your time on the F10 map. I've found that once you can freely move about the map, you can jump into a cockpit with no delays or rendering to worry about: https://forums.eagle.ru/showthread.php?t=203376 :book:
  12. Yes, when you upgrade release version 1.5.8, it will copy needed files from open beta so you have minimal download of files.
  13. Johnny_Rico & 100KIAP_Falcon, thanks for your testing, I love to see hard data. When I had a 32 GB RAM rig, I typically used 20-25 GB at the most during those early load times on a multiplayer server. I picked up a new rig (see signature) with 128 GB and the usage stays about the same, 20-25 GB. Also, with all the cores I have, DCS maxes out only one core and uses half of another. All the rest just hum along at 0-1%.
  14. The black cockpit looks similar to what is caused from the memory issues. Sometimes it takes a few minutes for the cockpit to render. I use a GTX970 as well and I experience the same thing.
  15. Glad that worked! Please post the line of code so others may do it that have the same issue. Thanks!
  16. From what I've seen so far today since I was curious is that they both seem to point to the same multiplayer instance. So I guess it doesn't matter until one of the versions change. Please correct me if I'm wrong.
  17. If you have not done a previous edit to the file, there won't be one. Just create one from a Notepad file or something and rename to autoexec.cfg. The system should pick it up on start. The folder you listed is the correct location.
  18. DanielNL, until now I was having issues with P-51D and the NEVADA map with activation on every launch. I got a new PC a few weeks ago but used the same C:\ drive (DCS Install) from the old PC. I just tried this Activation page instructions for the registry: https://www.digitalcombatsimulator.com/en/support/faq/564/#1780273 I ran the REG key for the 2 modules I had an issue with. Essentially, it just removed all related license keys to those modules. The next time I launched DCS I pasted in my key for each module and I've been golden ever since. So bottom line is my hardware looked different to what was stored in the registry and wiping it out cleared the issue and used another activation on my allotted activations.
  19. Not sure why it's not set correctly by default for you. Some folks use a tool called Process Lasso to force apps to the correct affinity by default. I couldn't find a quick answer on a tweak of your system to do this without an external app. You can also write a .BAT process to set it as well when your game launches. Lots of stuff on the Google. :)
  20. Check for updates on your 1.5.8 Release candidate. That's what was updated. That will update to 2.5. The open beta was not updated.
  21. I agree. Affinity set to all cores by default here too.
  22. Yes, I believe the "Print Screen" key on your keyboard always takes a picture regardless of the settings you show.
  23. Turns out my video rendering workstation makes a good flight sim machine.
×
×
  • Create New...