Skip to main content

On Sale: GamesAssetsToolsTabletopComics
Indie game storeFree gamesFun gamesHorror games
Game developmentAssetsComics
SalesBundles
Jobs
TagsGame Engines

Hi there.
Generally I don't use the same name and/or change any file's casing along the way.
That being said, I indeed didn't know about the case sensitivity in Unix-like systems, so naturally I never was too careful about file name casing, beyond my general inclination to keep things somewhat clean.

Could you tell me what files the error was about? Cause, when looking at the collection of files from last update, I don't see any that I have changed the casing of.

Assuming I'm not missing anything, there might be a different reason for said error - so, in the spirit of covering multiple bases at once: Did you use the update-only patch or the full update? And if it was the latter, did you unzip it into a new location or did you overwrite your previous installation of CH?

Hello Vertigo !

The first time I just downloaded the update file, extracted it and uploaded it to the game directory overwriting everything. Then after loading the last game state, it fired an error every now and then. 

Now I deleted everything and downloaded the full compilation image. The earlier errors no longer occur. Strange, I thought I had done everything right before. It also seems that the problem I suggested earlier was not the direct cause, but that does not mean that I wrote untruthfully about the importance of case in file names in the Linux file system ;)

Thanks for the update !

You're right, of course. No matter if it was the actual reason for the error messages you got, knowing about the case sensitivity stuff is an improvement. I'll definitely keep that in mind going forward and make doubly sure to not change any file name casing halfway through. So, thanks for teaching me about that. :)

About the error itself: Don't worry about it too much - these things happen. Maybe something got jumbled while unzipping the patch, who knows.
The important part is that it's fixed now and works. :)