Definitely unoptimised.
It came out in 2008 and I still can't max it at 60fps on a 980Ti/3570 combo (with only 2xMSAA at 1080p). There have been games since that run and look better, and since that's my basis I'll say definitely yes.
Crysis had a zillion trees and was open world, both things that decimate framerate
Because for a game that released nearly EIGHT years ago, it's still a bitch to run. It'll humble most modern PCs. It just doesn't seem like there is any way to maintain a solid 60fps without frequent dips and stutters into the 20s/30s/40s. It's really bizarre and not something I've encountered with any other game.
Crysis 2, by comparison, performs much better.
Can you find those quotes? Because direct documentation regarding how they changed up things in C2 points to the fact that their were multiple paradigm shifts regarding settings and hardware and not the fact that the game was coded poorly.
His quote is talking about scaling, making it so that all settings look great. To quote their Cryengine 3 tech presentation:A quick search turned up this:
http://www.dsogaming.com/news/cryte...ysis-2-didnt-implement-tessellation-properly/
But I also remember a different article going into more detail on how the artists had no restrictions on how to build the levels, so when they put everything together it turned out to be a huge mess.
A long time ago I was also kinda involved with Crytek, so I know a little bit about how hectic and rushed the development got towards the end.
Edit: As you say above, the single threaded nature can even push top notch CPUs to its knees today.
A quick search turned up this:
http://www.dsogaming.com/news/cryte...ysis-2-didnt-implement-tessellation-properly/
But I also remember a different article going into more detail on how the artists had no restrictions on how to build the levels, so when they put everything together it turned out to be a huge mess.
A long time ago I was also kinda involved with Crytek, so I know a little bit about how hectic and rushed the development got towards the end.
Edit: As you say above, the single threaded nature can even push top notch CPUs to its knees today.
In Crysis 1, a relatively brute force approach was used, where all features on lowest settings would be completely turned off, including HDR rendering, shadowsand all post processes.
Users were also forced to use lower resolutions for improving performance, which meant a lot of our low end hardware owners would not be able to achieve a decent visual experience of our game at good frame rates. Running Crysis 1 at HD resolutions on highest end hardware in 2007 was simply not possible
This time around, throughout the entire project,we dedicated a lot of effort to optimization. All features are present across all system specs, including HDR rendering, shadows, motion blur, SSAO, Depth of field and post MSAA. Anisotropic filtering is also used on every system spec
This effort made our lowest specification equal in many aspects and even superior to CryENGINE2 High specs
Crysis still today does things with its AI that few if any other games do. Especially Crysis 2 and 3, which were massively simplified.
Yes and no.
Yes in a sense that most of its features were optimized to hell in CE 3 and CPU scaling was bad due to being locked to two threads.
No, because it tried some completely new tech which we know is not always completely optimized when pioneered and it actually had decent lower quality settings.
It definitely used bruteforce approach for some of the stuff though.
---
No, it didnt.
subject: it's all over the place
body: No matter how nicely I asked it, Crysis refused to be gentle with my computer.
![]()
![]()
![]()
![]()
![]()
![]()
![]()
![]()
![]()
![]()
![]()
![]()
![]()
![]()
![]()
![]()
![]()
![]()
![]()
re: how did it run!? AHHH!! TEll me everything, all the specs, the details, the etc!!!re: It runs as nicely as a really fat girl. An incredibly good looking fat girl. That doesn't make any sense.
It wasnt. Open an editor and put C2 and C3 NPCs to similar map to Crysis 1 and see how they behave.
It did not run great on the 8800 series of cards, unless you played at very low resolutions, even then, you could not play this on ultra. Even at medium settings it was constantly below 30fps on such a card. Tbh, even sli 8800gt's averaged around 35fps at med settings at 1900*1200.Ran pretty well in my 8800gt (and previously 8600gt) + Athlon x2 at medium/high (mostly high) settings, around 30fps, back in 2008.
Played it a couple of years ago on a 7850 and Phenom II, everything Ultra, 60fps with very few drops.
Haven't tried it with my new i7, but if a Phenom II ran it so well at Ultra...
Never experienced problems running it. So I'd say no.
If only Crysis 2 and Crysis 3 did everything else I mentioned about dynamic and persistent environment destruction....
Well, it looked better. At least vs vanilla 2. Also, IIRC, Crytek scrapped a lot of effects from Cryengine 3 to make it run on consoles.
But regardless of the context, it's strange to see a game from 2007 fail to run smoothly on hardware from 6+ years after it was released. It suggests that they overreached, putting more detail into the game than machines could reasonably display, incorrectly assuming that hardware would scale in a certain way over the coming years. The result is a bottleneck that is so obvious and prevalent that people are still talking about it in 2015. It's an understandable mistake to make, but lets not fool ourselves into thinking it wasn't a mistake. There's a reason they built CryEngine 3 from the ground up after Crysis shipped. Major changes were needed if the engine was going to stay relevant.
But regardless of the context, it's strange to see a game from 2007 fail to run smoothly on hardware from 6+ years after it was released. It suggests that they overreached, putting more detail into the game than machines could reasonably display, incorrectly assuming that hardware would scale in a certain way over the coming years. The result is a bottleneck that is so obvious and prevalent that people are still talking about it in 2015. It's an understandable mistake to make, but lets not fool ourselves into thinking it wasn't a mistake. There's a reason they built CryEngine 3 from the ground up after Crysis shipped. Major changes were needed if the engine was going to stay relevant.
I told You, open editor and make a map with dynamic destruction. You can do that easily.
http://www.crytek.com/news/the-crysis-2-mod-sdk-is-here
---
No, they didnt. They actually added a lot.
Stop throwing those assumption as facts, they are not true. There a lot of tech publications on Crytek's site to prove You wrong.
http://crytek.com/cryengine/presentations&page=2
It doesnt take advantage of current multi core CPUs right now, it could use a patch for that. (they wont I know)
Far Cry 3 hardly ever was a "graphical" beast imo, it looked good for the time but has aged rather poorly.
On topic : the game is extremely CPU bound in some places, my framerate does drop below 60 on occasion.
Wonder how much it'd cost to port over the PS360 version, which was done with CE3 (with the missing stuff included even?).
He is former modder who has been part of the team since 2011. Wtf are you on about?Have You even read the article, which is stupid btw? Its a modder, not a dev.
He is former modder who has been part of the team since 2011. Wtf are you on about?
Metro 2033 was as demanding as Crysis 1
He said that xzero wasn't a dev which is bs. I say anything else about their post.He is mainly talking about optimizing for lower systems through scaling visuals though, and not saying "it was coded poorly".
Which, due to the nebulous phrasing of the term "unoptimized" in general, confuddles this thread.
We should probably reference optimization in three ways.
1. Changing some process paradagmitically to achieve the same result but with better performance
2. Reducing the hardware strain of some process so that it runs better
3. In the way Xzero and Cryengine documentation mentions it, "making the process scale visually on multiple configs"
He said that xzero wasn't a dev which is bs. I say anything else about their post.
I still wish Crytek would port the CryEngine 3 version of Crysis 1 to PC.
This one?edit: Durante, if you read this. Could you per chance post that one graph displaying single threaded performance over time vs. total multi-core performance?
This one?
![]()
2007 actually, 2008 had it's expansion.Definitely unoptimised.
It came out in 2008 and I still can't max it at 60fps on a 980Ti/3570 combo (with only 2xMSAA at 1080p). There have been games since that run and look better, and since that's my basis I'll say definitely yes.
Yes! Thanks for posting it.
That orange line is the main reason why Crysis runs the way it does today. I really am not sure if any CPU can play a level like the Harbor or Assault @ 60fps, even today.
I'm assuming you mean at stock clocks. Surely a heavily OC'd high end CPU can do it?
This one?
![]()
Have You even read the article, which is stupid btw? Its a modder, not a dev.
They never said it was unoptimized mess, though they said it wasnt optimized as it should in some CE3 presentations. I cant point which, because i dont have PowerPoint installed.
Check: CE3: Reaching the speed of light, Secrets of CryEngine 3 technology,
---
Also this quote - http://crytek.com/assets/Crysis-2-Key-Rendering-Features.pdf
You'd be amazed by how bad C1 is in terms of optimizations. You'd also be amazed by how much merging shaders can help speed up the engine. CE2 was a huge waste of resources, it really was. Just.... trust me on that.