Daniel Hryzbil

Let's check crash logs to figure out what's going on. Crash log is dumped at the end of `Game.log`, which is stored either in Crysis main directory or in `Documents/My...

No crash in the first log. The game started and exited normally. The second log contains a crash. It crashed in CrySoundSystem inside FMOD memory allocation callback. That's interesting. I've...

> What about those "Error: CallMethod" lines in the first one? Are those in some way important? Those are just harmless Flash errors. The game actually contains quite many hidden...

That's strange. Is it the same if you rename the EXE?

Looks like some global thing related to a specific system-wide path. I suspect GOG installer adds this to make sure the 64-bit version works, but strangely it doesn't affect its...

By the way, as stated in the readme, you can rename c1-launcher EXEs to whatever you want and they will work fine. The only problem might be that modern graphics...

The first one is a crash inside CryMemoryManager. Its `CryMalloc` function to be precise. You can try to play via [CryMP-Client](https://github.com/crymp-net/client-server), which currently uses standard malloc as global allocator instead...

Nice and thanks for sharing it. Crysis uses only FSAA as far as i know and yes, it wasn't tested much back in the days probably.

There's an integrated crash logger in c1-launcher. It dumps crash details into Game.log (Server.log, Editor.log). Info from Event Viewer is very limited and not very useful usually. I've recently discovered...

Requires #28