Jump to content

c0ff

ED Team
  • Posts

    3615
  • Joined

  • Last visited

  • Days Won

    4

Everything posted by c0ff

  1. Unzip the attached file to the root of your DCS install folder. It will create the autoupdate_dev.cfg file, with the contents: { "keep_torrents": true } This will tell the updater to keep all torrent-related files in the _downloads/ folder. You can seed directly from there. autoupdate_keep_torrents.zip
  2. We have a mailling list for those who want to seed. PM me with your email if you are interested. Another option is to keep torrent files after the update and seed from them directly. But this should be set up before the update. If you are interested, I can post the details.
  3. Yes, it is correct.
  4. It won't. Unless told so using dcs_local_source.txt file.
  5. It does not matter.
  6. Yes, it works as well.
  7. Hopefully, a week after.
  8. OpenAlpha in your case.
  9. Just in case, the updater seeks for the installed versions in the registry, the paths are expected to be in: "HKEY_CURRENT_USER\\Software\\Eagle Dynamics\\DCS World 2 OpenAlpha" "HKEY_CURRENT_USER\\Software\\Eagle Dynamics\\DCS World OpenBeta" "HKEY_CURRENT_USER\\Software\\Eagle Dynamics\\DCS World" string value "Path".
  10. The 2.5 will be rolled out in two stages: Stage 1: Openbeta 1.5 will be updated to OpenBeta 2.5. If OpenAlpha is installed the updater will pick up the installed modules from it and will suggest to remove it after the install. As usual, common files will be used from 2.2: if you selected to remove 2.2, the files will be moved. If you selected to keep 2.2, the files will be copied (actually, hardlinked). Stage 2: Release 1.5 will be updated to Release 2.5. Before the update the updater will suggest to keep 1.5 as a separate install. If you agree, it will download the special DCS 1.5 installer which will move the files (and download what's needed if any) from your existing 1.5 install to a new location of your choice. After that, if there's OpenAlpha 2.2 is present it will do the same as Stage 1. If no OpenAlpha found, but there's OpenBeta 2.5, the update will pick up the list of modules from OpenBeta 2.5. At the same time as Stage 2, those who only have OpenAlpha 2.2 installed will be prompted to automatically download and install Release 2.5 which will, as noted earlier, ask to remove 2.2. This is as detailed as it gets.
  11. It will pick up the installed modules from openalpha 2.2 or openbeta 2.5 depending on what's available on your machine.
  12. Yes, because you are on the 'openbeta' update channel.
  13. Wait as long as you can until our servers become not as busy ;)
  14. Removal of 2.2 is optional in either case.
  15. Refresh the MM. Should be fixed now.
  16. No! Your modules won't go away ever! It is authorization data which expires after 3 days, but each time you log in you get it fresh again.
  17. It works this way: Each time you log in, you get authorization data, which is valid for the next N days, currently 3. If you don't log in after that, authorization data expires and has to be renewed. That's it.
  18. Actually, it is 3 days right now.
  19. Most probably, that's your antivirus
  20. Remove the mod. For the textures IC is applied when they are being loaded by the sim. That's why it is green first and becomes red after entering a mission. Unfortunately, it is not practical to check the textures beforehand - they are too big.
  21. That's something on your machine. DCS never touches its files apart from explicit update/repair.
  22. c0ff

    Steam VR

    It should continue to work ok if enabled in the game settings. Does it?
  23. Gazelle is Polychop-Simulations's creation. Ask them.
  24. It's a known issue with the servers having many players. We'll fix this. No ETA, though.
×
×
  • Create New...