Taking the new model out for a spin
Yerli said that Crytek dedicated a pair of programmers to implementing the Shader Model 3.0 code path in Far Cry, and he said the entire retrofit took three to four weeks to complete. Obviously, implementing Shader Model 3.0 was more complicated than just ticking a checkbox for a new render target in a compiler, but it didn't require a rewrite of the game engine. Some of the changes Crytek made took only a few hours, while other elements of the retrofit took a week or two to complete. In fact, after the first two weeks of effort, Crytek had the initial version of the Shader Model 3.0 code path up and running.
Far Cry, of course, started out with a fairly sophisticated game engine that took advantage of Shader Model 2.0 to deliver per-pixel lighting. Yerli said Shader Model 3.0 doesn't bring any change in visual fidelity, just better performance. In fact, he emphasized the point repeatedly during our conversation. In the case of pixel shaders, lighting some objects covered with shader-based materials using Shader Model 2.0 required multiple passesone pass per light. If the object were affected by three lights, the pixel would have to take three passes through the rendering pipeline. With Shader Model 3.0, Crytek was able to consolidate its per-pixel lighting work so that up to four lights can be rendered in a single pass.
Crytek's revamped pixel shaders use branching and looping in order to calculate the effects of multiple lights in a single pass, but the instruction lengths of those shaders don't approach the 96-instruction limits of SM 2.0 pixel shaders. Instead, Yerli stated that the primary benefits of SM3.0 pixel shaders are more constants, tables, and the like, which lead to better performance. The effects you'll see in current games running on today's hardware, in his estimation, can be implemented within the 96-instruction limits of SM2.0; the longer instruction lengths in Shader Model 3.0 won't be practical until the next generation of graphics hardware arrives. For now, he said, SM2.0 will allow the creation of any effect developers want.
Beyond pixel shaders, Far Cry 1.2 uses another Shader Model 3.0 feature, geometry instancing, to accelerate game performance. With geometry instancing, the Far Cry engine can place multiple copies of the same 3D model onscreen at once, each with different attributes, using only one draw call. The game engine automatically uses geometry instancing whenever copies of the same static mesh appear at once. Although this capability primarily provides benefits in areas with lots of grass and foliage, the feature isn't linked to a single model type. In fact, like the pixel shader enhancements, geometry instancing is a game-wide enhancement that requires no change to the game content.
I asked Yerli about the image quality problems on GeForce 6800 cards in version 1.1 of Far Cry. He dismissed those as "just rendering issues" and said that the Shader Model 3.0 path cleaned up those problems. The SM3.0 path does include a mix of FP16 and FP32 datatypes on GeForce 6800 cards for the sake of performance, but Yerli said Crytek never sacrificed image quality for performance, a move that's "not an option" for them. Out of curiosity, I also asked whether he knew of any instances where the use of FP24 precision on ATI cards caused visual artifacts, and he said no.
The skinny on quick-save
As we wrapped things up, I veered off the path a bit to ask another question on everyone's mind: Will Far Cry 1.2 include a revamped save-game system? Yerli said there will be two versions of the 1.2 patch released. Crytek hopes to release the first version within the next week or so. That initial version of the 1.2 patch will not include a quick-save function. Some time later, Crytek plans to release a version 1.2 patch with quick-save enabled. Yerli said building quick-save into Far Cry has been a painful process, because the game wasn't designed with this feature in mind. However, Crytek is fixing bugs daily, and the quick-save patch will be released once all the bugs are squashed.
15 comments — Last by hmmm at 9:31 PM on 07/05/04
|Five GeForce GTX 960 cards overclockedHow do I compare thee? Dunno, really||189|
|The TR Podcast 169.5 bonus edition: Q&A intensifiesYou ask, we attempt to answer||5|
|Samsung's Galaxy Note 4 with the Exynos 5433 processorA Korean import gives us a look at ARM's latest tech||110|
|We discuss the GeForce GTX 970 memory controversyDissecting the issue||94|
|Nvidia: the GeForce GTX 970 works exactly as intendedA look inside the card's unusual memory config||204|
|Nvidia's GeForce GTX 960 graphics card reviewedThe green team brandishes a sawed-off shotgun||236|
|The TR Podcast 167.5 bonus edition: You guys ask us stuff!The chat channel hops into the driver's seat||6|
|Catalyst Omega driver adds more than 20 features, 400 bug fixes...and some performance improvements, to boot||162|
|Cherry Trail debuts as the Atom x5 and x7 series||36|
|End is in sight for Intel's contra-revenue efforts||12|
|Phanteks announces enthusiast-friendly Enthoo Evolv ITX case||16|
|SanDisk unveils microSD card with a whopping 200GB capacity||26|
|Unreal Engine 4 now free for everyone||23|
|Sony's waterproof Xperia Z4 takes on premium tablets||34|
|Samsung's Galaxy S6 is ready for battle at the high end||99|
|Atom x3 chips target cheap phones and tablets, feature ARM graphics||31|
|The TR Podcast 171: Nvidia takes heat, Carrizo runs cool, and Fractal stays quiet||1|
|God you're tiresome.||+60|