tangofan Posted January 17, 2022 Posted January 17, 2022 When I'm running the Open Beta DCS updater, I am prompted to from version 2.7.8.16140 to 2.7.9.18080. Every time I choose to update I am getting a data error (cyclic redundancy check) on file F-16C-CPT-TEXTURES.zip. I should note that Comcast is my ISP, but this also happens when I'm running a VPN client, so this apparently isn't related to Comcast. This is not a one-time occurrence, but has happened every time over the 5 or 6 times I've tried this (a couple of days apart). Please note that when the program prompts me that there are some residual files left, I always choose to delete them. I've copied the relevant snippet from the autoupdate_log.txt file into a separate file and attached it to this post. Does anyone know, if this is a general problem or something that I can fix on my side? autoupdate_log_snippet.txt
ED Team maximov Posted January 17, 2022 ED Team Posted January 17, 2022 Do I understand correctly, you have two folders with the game: D:\Games\Eagle Dynamics\DCS World OpenBeta\DCS World OpenBeta and D:\Games\Eagle Dynamics\DCS World OpenBeta?
tangofan Posted January 17, 2022 Author Posted January 17, 2022 (edited) 50 minutes ago, maximov said: Do I understand correctly, you have two folders with the game: D:\Games\Eagle Dynamics\DCS World OpenBeta\DCS World OpenBeta and D:\Games\Eagle Dynamics\DCS World OpenBeta? No, there is just one installation of the OpenBetaVersion, in D:\Games\Eagle Dynamics\DCS World OpenBeta\DCS World OpenBeta . There is nothing else in the parent folder D:\Games\Eagle Dynamics\DCS World OpenBeta . I'm not sure, how I got to this setup, perhaps I didn't pay attention during installation and thus had this additional sub directory. Once I have the update issue sorted out, can I just move the game to the parent folder or do I need to delete and reinstall? Edited January 17, 2022 by tangofan
ED Team maximov Posted January 17, 2022 ED Team Posted January 17, 2022 Move the secondary DCS Open Beta folder to the Eagle Dynamics folder (you may need to rename one of the DCS folders). Then you will have two DCS Open Beta folders in the Eagle Dynamics folder. Delete the empty folder and check the update process. If the error occurs again, we wait for you to autoapdate_log.
tangofan Posted January 17, 2022 Author Posted January 17, 2022 7 hours ago, maximov said: Move the secondary DCS Open Beta folder to the Eagle Dynamics folder (you may need to rename one of the DCS folders). Then you will have two DCS Open Beta folders in the Eagle Dynamics folder. Delete the empty folder and check the update process. If the error occurs again, we wait for you to autoapdate_log. Thanks so much for the quick response. I fixed the game directory directory situation as instructed. The game is now in "D:\Games\Eagle Dynamics\DCS World OpenBeta\" and the launcher points to "D:\Games\Eagle Dynamics\DCS World OpenBeta\bin\DCS_updater.exe" with the "Start in" directory adjusted as well. When running the update (and choosing to delete the residual files) the error still occurred. The relevant snippet of the autoupdate_log.txt file is once again attached to this post. If you need me to provide anything else, please let me know. Thanks so much in advance for any help you can provide. autoupdate_log_snippet2.txt
ED Team Solution maximov Posted January 17, 2022 ED Team Solution Posted January 17, 2022 Try deleting the file D:\Games\Eagle Dynamics\DCS World OpenBeta\Mods/aircraft/F-16C/Cockpit/Textures/F-16C-CPT-TEXTURES.zip and run the repair. If this does not help, temporarily disable antivirus and repeat the same steps.
tangofan Posted January 18, 2022 Author Posted January 18, 2022 (edited) 12 hours ago, maximov said: Try deleting the file D:\Games\Eagle Dynamics\DCS World OpenBeta\Mods/aircraft/F-16C/Cockpit/Textures/F-16C-CPT-TEXTURES.zip and run the repair. If this does not help, temporarily disable antivirus and repeat the same steps. Thank you so much for your response. It turned out - when I tried to copy the F-16C-CPT-TEXTURES.zip to a different drive before deleting it - that this file had read errors and a surface scan of my SSD showed a train wreck of bad sectors. But after copying everything that I could to a new SSD and then running the repair, the installation proceeded without any problems. Now it's time to RMA that SSD... Thanks so much for your help, maximov. Next time I'll know to check first, if the file can be read. Edited January 18, 2022 by tangofan
Recommended Posts