Archive Thread of Screenshots of Ridunkulous Quality and Size [2007-2015]
- Thread starter Neb
- Start date
- Status
No but I get some slight barely noticable jittering "tint" on some surfaces shadows LOD. I'll check and also give you my custom config settings.
Some Crysis super sampled shots for wallpapper use with my TOD mod and personal config.
Perhaps it is a driver bug as well, or something exclusively related to the 5xxx series. Because sometimes for me, shadows are fine, but as soon as I'm moving can see shadows in the distance being very jittery, almost to a point of flickering (even for something as close as 10 meters). It would be great if you let me know what your cfg looks like. Even then the game is still playable, it is just beautiful to play with D3Doverrider on along with 16x AF (the dark tones look even better than how it is done in Crysis).
Those are some nice screens. I'm guessing oversampling must bring a huge performance hit. For HD movies, I oversample even the full 1080p material to 2x the resolution, even in film you can notice a difference that makes.
It works for me in DX10 64 bit mode just fine. Well, fine if you're cool with <20FPS.
Ouch, ran it at 3840 x 2400 16xAF and 4xAA and 1 gb vidram would cut it 
(ofcourse), but it's playable with two HD 5970's hahaha. But it appears to be deformed, everything is so strechted in should I change the values ie 2400 for width and 3840 for height ? Man would think 3840 x 2400 would be the right value for a 1920 x 1200 screen ?
Edit I made a type probably, running allright now
(ofcourse), but it's playable with two HD 5970's hahaha. But it appears to be deformed, everything is so strechted in should I change the values ie 2400 for width and 3840 for height ? Man would think 3840 x 2400 would be the right value for a 1920 x 1200 screen ?Edit I made a type probably, running allright now
Last edited by a moderator:
Hey Nebula, I've been playing around with triple buffering and vsync for Crysis. You said that D3Doverrider does not work for DX10 @ 64bit.... does it work for DX10 @ 32bit?
Since I'm not using DX10, will 64bit in DX9 have proper vsync and triple buffering through ONLY the console commands (override doesn't work in 64bit, regardless of DX level). Just wanted to know for sure I'm getting the "right" vsync. Otherwise I will just go with DX9 @ 32bit, which the override works with.
Since I'm not using DX10, will 64bit in DX9 have proper vsync and triple buffering through ONLY the console commands (override doesn't work in 64bit, regardless of DX level). Just wanted to know for sure I'm getting the "right" vsync. Otherwise I will just go with DX9 @ 32bit, which the override works with.
Not sure if D3DOverrider works well with 64bit exe. However with 32bit exe and DX10 it is alright. About vsync that can already be enabled ingame in the games settings menu.
Some ways to enable triple buffering.
Cheap solution to enable triple buffering is to press ingame CTRL + ALT + DEL and then go back to game and triple buffering will be activated.
For DX9 32/64bit all you need to do is in the autoexec file put this line,
d3d9_TripleBuffering=1
(..\Electronic Arts\Crytek\Crysis\autoexec.cfg)
This will be automatically be read and enabled every time you launch the game.
Sadly there is no similar command for DX10...
Some ways to enable triple buffering.
Cheap solution to enable triple buffering is to press ingame CTRL + ALT + DEL and then go back to game and triple buffering will be activated.
For DX9 32/64bit all you need to do is in the autoexec file put this line,
d3d9_TripleBuffering=1
(..\Electronic Arts\Crytek\Crysis\autoexec.cfg)
This will be automatically be read and enabled every time you launch the game.
Sadly there is no similar command for DX10...
Ouch, ran it at 3840 x 2400 16xAF and 4xAA and 1 gb vidram would cut it
Yeah 1.5-2GB VRAM would seem optimal. I hope ATI and Nvidia really pushes this for their cards.
But it appears to be deformed, everything is so strechted in should I change the values ie 2400 for width and 3840 for height ? Man would think 3840 x 2400 would be the right value for a 1920 x 1200 screen ?
Edit I made a type probably, running allright now
[strike]It should be 2400 for height and 3840 for width if your original res is 1920x1200. You can also test different FOV angle to correct view perspective with cl_fov where default value is 60 degrees (cl_fov 60).
[/strike]
EDIT: Just noticed your edit, great to hear it is running allright!
Yeah thanx for the heads up for this handy AA tip. I noticed you have to put the values for height and width seperate
Well 2400x1500 seems playable with 4x ingame AA, so I have a mixed mode of 1,5 SSAA+4 AA now?
3840x2400 with 4xAA needs to much vidmem, but after a while after the scene has loaded the perf is good, I just cann't move So 2 GB cards would do it
Well 2400x1500 seems playable with 4x ingame AA, so I have a mixed mode of 1,5 SSAA+4 AA now?
3840x2400 with 4xAA needs to much vidmem, but after a while after the scene has loaded the perf is good, I just cann't move
So 2 GB cards would do it
Last edited by a moderator:
What POM + AF utility ?
Timeshift
I'm just screwing with ya.
It's always worked for me
Picking up where I left in the first Mass Effect. Really enjoying it and the dialogs although the lines you get to choose are not really what he says.
For some reason the screenshots came out with bluriness less or more. Dunno if it is the grain filter in game or other that makes it blurry but onscreen it is far crisper. Anyway looking forward for ME2 when it is released!
For some reason the screenshots came out with bluriness less or more. Dunno if it is the grain filter in game or other that makes it blurry but onscreen it is far crisper. Anyway looking forward for ME2 when it is released!
- Status
Similar threads
