Q: Apparently, the handy Crysis tweakers were able to get most of the old DX 10 effects, whereas in DX 9 mode.
More info here:
Screenshoots excellent (http://www.crysis-online.com/forum / index. php? topic = 11837.0)
The modded cfgs here:
Crysis DX10 effects on DX9 mode pack (http://rapidshare.com/files/65472180/Crysis_Pack_High_to_VeryHigh__NoFrag_.zip.html)
Alternative link (http://www. megaupload. com /? d = PPVQWWZ3)
Can everyone who plays in DX 9 mode and try to report with screen shots?
: Live D
Long XP/DX9
Additional Info: Link to the unlock
Official (http://maxcrysis.com/dx10unlock. Php)
Screenshoots: 10
DX mode (http://www.uploadgeek.com/uploads456/1/Vista% 20DX % 2010% 20Very 20High.JPG%)
Versus
DX 9 mode with the tweaks applied: No big diffrerence in Visuals (http: / / 20DX www.uploadgeek.com/uploads456/1/XP%%% 209% 20Very 20High.JPG)
More info:
The screen shoot pack (http://files.filefront.com/crysis+XP+vs+Vistarar/, 8912087; / fileinfo.html/1/1)
Re:Yeah it seems far more likely that very high detail is just reserved for the purchased product, as a way of upping the tease factor. Can someone testing with Vista prove this wrong? Is there a straight up DX10 setting in the Vista install?
Re:Originally posted by: guy
Wait I thought DX10 effects were only possible under Vista …
Is that some sort of emulated DX10 ?
I don't think using very high detail has anything to do with dx10 in Crysis.
Re:I tried in Vista on my X1950pro, went from medium settings @ 1024×768 to those settings at the same res…framerates went from 45fps to about 15-20fps
Was nice, but not enough for me to warrant playing a game at unplayable settings. Gotta get me one of those 8800GTs, or an RV670.
Re:this just goes to show the reason crysis is so slow is due to the way the engine is written.
Re:Of course you don't get every effect DX10 does, for example no fps slowdown
I'm happy with the "DX10" sunrays and terrain/model normal/parallax occlusion mapping turned on. The stones and all the other parallax mapped stuff on the ground looks fabulous.
btw you can add this with little effort.
Just paste this into a txt file and name it autoexec.cfg, make it writeprotected and place it inside your config folder:
r_GeomInstancing = 1
r_sunshafts = 1
r_UsePom = 1
e_terrain_normal_map = 1
r_UseNormals = 1
r_shownormals = 1
This is the only stuff that's needed and doesn't add too much strain to the fps. If you have 35fps on everything high, you have maybe 32 with this on.
With this turned on, the only difference left between slow very high DX10 and pimped high DX9 are the ridiculous high waves (which look stupid in shallow water, and more accurate shadows, which are useless.)
Re:Originally posted by: guy
You're not getting all the DX10 things. Just what is possible in DX9 but turned off except for DX10. There is still more things that DX10 does and can do that DX9 (even with tweaks) does not.
thank you for stating the obvious
Re:DX9 and DX 10 are both Turing complete.
Re:You're not getting all the DX10 things. Just what is possible in DX9 but turned off except for DX10. There is still more things that DX10 does and can do that DX9 (even with tweaks) does not.
Re:damn crysis looks good with very high settings… damn my rig crys with this even at 800×600 =(
Re:Last bump…
Any chance for benchmarks WITH the DX10 effect tweaks applied?
Re:Originally posted by: guy
Cevit Yarli never claimed that Crysis is a D3D10 game.. In fact he has stated numerous times the exact opposite.. That it is a D3D9 game..
Marketing is one thing, while the truth is another..
http://www.shacknews.com/featuredarticle.x?id=639
^^^this says otherwise^^^
and i missed this at the very end:
Cevat Yerli: Very, very well. Stay tuned for more on this. In mid November you will see the new NVidia cards. They are a blast for Crysis and really, really very good deals.
:Q
Re:Cevit Yarli never claimed that Crysis is a D3D10 game.. In fact he has stated numerous times the exact opposite.. That it is a D3D9 game..
Marketing is one thing, while the truth is another..
Re:DX10 is a software library from Microsoft that only runs under Vista.
What DX10 *DOES* is provide a set of functions that lets you write a program for
the PC running Vista to access many (but not all) of the hardware functions of
the graphics card. Most of the DX10 functions don't really do much except pass
the request for a certain function to occur to the graphics card hardware for the
graphics card to process. That's why there are "DX10 capable" card models and
others aren't. Only the newer cards have the drivers and hardware capabilities
that let them perform all the functions the DX10 software library is capable of
asking them to perform.
DX8, DX9, etc. are basically the similar situations. The DX library runs under
Windows XP or Windows2000 or Vista or whatever and it is like a layer on top
of the graphics card driver that lets the PC ask the compatible graphics card
to perform certain graphics functions. The DX library wouldn't do anything
if it wasn't for the hardware and driver of the graphics cards supporting those
functions, the DX library is just like a little layer on top of the graphics driver,
and the graphics driver is a more complex layer on top of the graphics board
chip hardware.
Other graphics libraries exist and for LINUX or UNIX or WINDOWS there's
also OPENGL and you can similarly use that library to ask a graphics driver and card
to do almost all kinds of graphics functions.
The interesting bit is that in OPENGL or in DX9 or other graphics libraries
there are ways to detect, and use, "capabilitty extensions" of the
driver / graphics hardware. Those extensions let you access functions of
a graphics driver/card that go beyond what is specified in the basic
DX9 or OPENGL libraries. If the chip can do it and the driver has some
"extension" code for letting PC software use that additional capability, it can be
done.
You can also use DX9 or OPENGL or DX10 to write all kinds of "custom shader"
routines which are like little software programs that you write but they don't
run on the PC's CPU, they run in the CPU inside the graphics card. So you
can program software defined effects like things to do with lighting, rays,
smoke, flames, fog, blurs, water waves, physics, whatever; if you can write
the program as shader code, you can use it to process the images of the
objects in the game and change the way those images/objects are rendered
just as you'd change a photograph with various effects/filters in PhotoShop.
So really DX10 graphics library (vista only) doesn't let you do much anything the
GPU card and driver don't already know how to do almost "all by themselves".
Many of those features of the newer graphics cards can be accessed through
using a program that calls DX9 plus custom extensions/capabilities plus
some custom shader code (which doesn't run on the PC anyway).
You can use the same kinds of added capabilities / extensions in OPENGL too
and then you don't use DX8, DX9, DX10, DX-anything, it's just a different way
to get the same end results with the same driver / graphics card but writing
your game / program in a different language or using a different library /
game engine / whatever.
So that's why it's possible to do almost anything that you can do in DX10
with using DX9 or OPENGL instead if you really want to go to the effort to write
the code to work that way. DX10 just tries to make it "easier" by changing
the default programming choices and framework to talk to advanced GPU cards
to more closely match the actual capabilities and architectures of the
drivers and GPUs, but really you could have written the same special effects
or game engines to use a different way of accessing the card driver and card
and not ever use DX9 or DX10 at all.
Originally posted by: guy
And Halo 2 is supposed to be Vista only.
*cough*
Stuff like this makes me wonder how much of this "DX10" and "Vista" only stuff is truly inhibited by programming. Is it merely easier to perform under Vista, or truly impossible to perform under XP? Or, are they just being lazy and trying to save a few days of debugging by designing it for Vista specific stuff and simply not spending time on it for XP?
Re:And Halo 2 is supposed to be Vista only.
*cough*
Stuff like this makes me wonder how much of this "DX10" and "Vista" only stuff is truly inhibited by programming. Is it merely easier to perform under Vista, or truly impossible to perform under XP? Or, are they just being lazy and trying to save a few days of debugging by designing it for Vista specific stuff and simply not spending time on it for XP?
Re:Wait I thought DX10 effects were only possible under Vista …
Is that some sort of emulated DX10 ?
Re:If this is indeed possible, I wonder why EA/Crysis did not enable it by default.
This reminds me of DX9C vs. the ATI enhancements to DX9 when the X800 cards came out. It's not quite DX10, but close enough to not really matter.
DX10 mode has been very buggy and slow for me, so I might just give this a try.
0 Comments.