Install Steam
login
|
language
简体中文 (Simplified Chinese)
繁體中文 (Traditional Chinese)
日本語 (Japanese)
한국어 (Korean)
ไทย (Thai)
Български (Bulgarian)
Čeština (Czech)
Dansk (Danish)
Deutsch (German)
Español - España (Spanish - Spain)
Español - Latinoamérica (Spanish - Latin America)
Ελληνικά (Greek)
Français (French)
Italiano (Italian)
Bahasa Indonesia (Indonesian)
Magyar (Hungarian)
Nederlands (Dutch)
Norsk (Norwegian)
Polski (Polish)
Português (Portuguese - Portugal)
Português - Brasil (Portuguese - Brazil)
Română (Romanian)
Русский (Russian)
Suomi (Finnish)
Svenska (Swedish)
Türkçe (Turkish)
Tiếng Việt (Vietnamese)
Українська (Ukrainian)
Report a translation problem
Might peak out above 1024MB and climb for hours of play on win10 64bit
crysis x64 starts at 886MB of ram using r_displayinfo 1
First cutscene even before dropping out and parachuting 4200MB!!!! WTFFFFF is up with the 64bit version of this game crewing threw so much ram??????!!!!?!?!??!?!?!
once it hits that i just turn it off because its either going to crash to desktop crysis has stopped working windows is trying to find a way to solve the problem witch doesnt do ♥♥♥♥♥♥♥♥♥♥♥♥♥♥♥ or it restarts my computer... SOMEONE please comment
it has use only for mapeditor
64-bit is usually worse for every game
[GameProfiles]: Successfully activated profile 'default' for user '295x2'
$3r_FSAA = $60 $5[DUMPTODISK, REQUIRE_APP_RESTART]$4
$3r_FSAA_samples = $60 $5[DUMPTODISK, REQUIRE_APP_RESTART]$4
$3r_FSAA_quality = $60 $5[DUMPTODISK, REQUIRE_APP_RESTART]$4
Best way to start the game thru commands is the following:
con _ restricted 0
map island
r _ displayinfo = 1
or
com _ showfps 3
This will start you dropping out of the plane in the first mission and you will have you FPS meter in the right corner of the screen. I'm very excited about the remaster I believe it will be alot better of a game and run hopefully on VULKAN!!!!!
Thanks!