- Joined
- Jul 5, 2013
- Messages
- 25,572 (6.47/day)
While this is possible, it seems more likely that it's the way Windows 10 handles code. I had the same problem with Farcry1 on a Windows 8.1 machine I worked on a few years ago. Moving the installation out of the "Program Files (x86)" folder instantly solved the problem. It could have also been the parenthesis in the same folder. Only the original devs would know for sure, though both theories would be easy to test. Could just as easily be the way that Windows itself handles programs running within the "Program Files (x86)" directory. I wonder what would happen if the game was placed in the proper "Program Files" folder? Farcry was written before 64bit was a thing, so it is possible that it could be looking for that folder when running from a default install.There's a good chance it doesn't like spaces in its install path. Many old games are like that.
EDIT; This made me curious so I'm testing it.
I'm copying Farcry into two directories, one named "ProgramFiles(x86)" which has the no spaces, but still has parenthesis and another folder named "Far Cry 1" which has spaces but not parenthesis. Give me a minute..
EDIT2; Both scenario's tested, both times the game ran perfectly. Now let's try moving the game into the "Program Files (x86)" folder and see what happens..
EDIT3; That did not work. The game starts to run, screen goes black and the only way out is to Ctrl+Alt+Del out. So it seems Windows 10 does indeed handle programs running within the "Program Files (x86)" directory differently, which seems to be a problem for FarCry.
Solution is simple; Install Farcry to a folder other than the default, for example C:\Games\FarCry1. If it's already installed and having problems, simply move it to a new folder like the one in the example.
Last edited: