c1-launcher icon indicating copy to clipboard operation
c1-launcher copied to clipboard

Open-source Crysis executables.

Results 20 c1-launcher issues
Sort by recently updated
recently updated
newest added

## Motivation People who report crashes and provide crash details for analysis are very likely only a small fraction. Therefore, we need to make crash reporting as easy as possible...

enhancement

There isn't a way to run the Warhead launcher via Steam without changing the target executable somehow. Steam always runs `Bin64/Crysis64.exe`, which is required by the Warhead launcher.

Editor cannot save any changes when Crysis directory is not writable. And it even crashes during level export. Without showing any error message. Unbelievable.

I sometimes am able to play Warhead for a few minutes with no issues. However it seems to crash often very soon after reloading of a savegame (either made with...

Subj. Renaming folder Bin64 to Bin32 is needed to run the game wia Steam. Gives game time tracking, online game status, maybe some other steam-related goodies. There is a mention...

Here's the log file: [Game.log](https://github.com/ccomrade/c1-launcher/files/14312441/Game.log)

bug

First of all, thank you so much for updating this game for everyone. I started playing from the beginning on a fresh install (Steam version, v4 of your launcher) and...

I'm using the latest GOG version of Crysis and I also have put both the Bin32 and Bin64 EXE files from **c1-launcher-v3-build** into the corresponding folders. The game is running...

I don't know if this is just a bug with the GOG version or a unwanted side effect of using the c1-launcher but sometimes this happened: ![CrysisStuckTPose](https://user-images.githubusercontent.com/60928292/224331088-24546bd5-5d0a-481e-9c65-fb5d87e8b7b0.png)

Add CI/CD pipeline for creating releases. Including code signing of resulting executables.

enhancement