CBJ wrote: ↑Wed, 22. Sep 21, 15:40
Didn't we already establish in your case, that part of the problem was that you were using remote file storage? This would almost certainly have a detrimental effect on the game's ability to verify files.
No we did not. As the entire X4 program files are not touched by OneDrive as I have mentioned previously. X4 is installed on a NVMe drive attached to the motherboard chipset (should not make a difference, like it has not in the past, it is as "remote" as SATA drives which also run through the chipset) with the install folder neither being backed up by cloud storage or being touched by antivirus. Only the documents folder is backed up by cloud storage, and again that has not caused any issues in the past, and if it can now then an explanation would be nice.
The problem still happens very frequently, having happened twice in the course of 3 hours. I have started logging and noticed the following has a correlation with X4 becoming modified.
Code: Select all
Log when first time X4 became modified today.
[General] 264013.00 ======================================
[General] 264015.31 ======================================
[=ERROR=] 264015.31 CheckGzipHeader() not a gzip source buffer, magic bytes don't match!
[General] 264015.31 ======================================
[General] 264016.68 ======================================
Log when second time X4 became modified today.
[General] 264800.70 ======================================
[General] 265135.19 ======================================
[=ERROR=] 265135.19 CheckGzipHeader() not a gzip source buffer, magic bytes don't match!
[General] 265135.19 ======================================
[General] 265135.19 ======================================
It seems as if it is trying to decompress data that is not compressed by gzip or is corrupt? I do not know where these bytes are being sourced or what they are intended for as the logs do not seem to mention it.
I will try to delete the entire X4 install folder and redownload it completely. This will rule out that steam verify is not verifying all the files correctly.
EDIT:
So far it seems to be just a specific file causing the problem.
Code: Select all
[FileIO ] 271361.55 File I/O: Failed to verify the file signature for file '.\extensions\ego_dlc_terran\assets\textures\environments\planets\jupiter_4k_diffhq.gz' (error: 13)
[General] 271361.55 ======================================
[=ERROR=] 271361.55 CheckGzipHeader() not a gzip source buffer, magic bytes don't match!
[General] 271361.55 ======================================
Last 2 times X4 turned modified seem to be due to this file. Although steam verification found no issues I have deleted the entire terran DLC folder and had steam verify redownload it just in case and will be trying to recreate again.
This should mean that OneDrive can be completely ruled out since it is not touching the X4 program files. Neither is antivirus.
It seems the trigger is me doing something in either station or ship editor while on a L ship in combat. If it triggers is still seemingly random with not all uses of those tools causing it. A possible reason why this is so rare is that the player has to explicitly build in Jupiter for it to occur.
Since this is a texture it is sometimes failing on, could it be related to VRAM utilisation changes made by 4.10? My GPU only has 4 GB VRAM which used to be above the minimum requirements but is on the low end by modern GPU standards. Would updating graphic drivers maybe help?