Jump to content

Client and dedicated server attempt to load .gitkeep files as livery ZIP archives


Recommended Posts

Posted

Presumably with the recent F-14 update, two .gitkeep files made it into both client and server deployments. I highly doubt these files were put there intentionally, merely for lack of any logical reasons to do so. Both client and dedicated server attempt and fail to load these files as livery ZIP archives:

2025-10-24 18:26:03.326 ERROR   EDCORE (5320): Drivers errors while mounting coremods/aircraft/f14/liveries/f-14a-135-gr-early/.gitkeep:
2025-10-24 18:26:03.326 ERROR   EDCORE (5320): 	ZipDriver: Failed to open zip archive coremods/aircraft/f14/liveries/f-14a-135-gr-early/.gitkeep.
2025-10-24 18:26:03.347 ERROR   EDCORE (5320): Drivers errors while mounting coremods/aircraft/f14/liveries/f-14a-95-gr/.gitkeep:
2025-10-24 18:26:03.347 ERROR   EDCORE (5320): 	ZipDriver: Failed to open zip archive coremods/aircraft/f14/liveries/f-14a-95-gr/.gitkeep.

P.S.: Just me rambling about (unit) testing again. This could have been easily caught by checking the dcs.log for error messages (PowerShell: Select-String -Pattern ERROR dcs.log). Starting a vanilla DCS install shouldn't result in any error messages at all.

  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...