-
Hey, guest user. Hope you're enjoying NeoGAF! Have you considered registering for an account? Come join us and add your take to the daily discourse.
GeDoSaTo - Downsampling from Infinity and Beyond!
- Thread starter Alo81
- Start date
Cannon Goose
Member
Getting this error as soon as I click the play button for DS2 in Steam:
Using version 0.3.
Using version 0.3.
Run the game as adminGetting this error as soon as I click the play button for DS2 in Steam:
Using version 0.3.
Hmm, strange. What specs you running?
Pocky4Th3Win
Member
Core i5 2500K @ 4.5GHz, 8GB RAM, 680GTX SLi
I use my motherboards Bluetooth with the DS4.
Very strange. I'm just using USB cable, running i5 3770k, 770 4GB and 8GB RAM. The lag only appears when I enable the resolution downsampling so might just be going a bit too high with 3840x2160
Pocky4Th3Win
Member
That's what I'm running. What kind of delay are you experiencing? Movement? Button input?
ThatsMytrunks
Member
Running an i7 4770K and a GTX 770 I'm getting 60fps at 4K with antialiasing, depth of field, and ssao on.
I wish I had a 4K TV. :O
I wish I had a 4K TV. :O
Huh. When I try 4k my framerate suffers (4770k and 780). I am having Inspector force a few things though..
Quick question, If I use the NVidia Inspector to force HBAO+ and sgssaa should I turn off the in-game AA settings(or anything else for that matter) or leave everything on?
Turning the AA on and off in-game does seem to have an effect so I was just wondering what I should be doing?
Turning the AA on and off in-game does seem to have an effect so I was just wondering what I should be doing?
Are you using GeDoSaTo?
If so you should turn on in game AA, then use 1, 2, 3, and 4 on the numpad to toggle AA, DoF, SSAO, and post processing respectively depending on how the game runs/how it looks.
If you're already using HBAO+ and SGSSAA then you should disable the GeDoSaTo AA and SSAO.
This answered some of my questions too, thanks.
No I'm not currently using gedosato at the moment.
I tried it to see if my 660 x51 could handle downsampling but my initial attempt hit the framerate pretty hard(just used durante's default settings but may go back and try some other settings if I hear anyone with a similar rig having good success) so now I just wanted to try the nvidia inspector tweak and then go from there.
So leave on in-game AA then? It does seem to clean up the edges a bit more I think. But I haven't left the first part of the game yet so my eyes may be deceiving me.
I have a 570 so it's pretty comprable.
I downsample from 1440p using GeDoSaTo, and just use the post processing effects and not the DoF, SSAO, or AA.
In game, I have everything set to max except SSAO turned off.
Pretty much 60fps everywhere except Earthen Peak.
I feel this should be in the op, and also the disable steam overlay warning shouldn't be there since Durante has fixed it, no?
Yes, right.
I can't really help you with that, with my DS3 I don't get input lag :/
I also can't think of anything that would cause it.
Cannon Goose
Member
Thanks, that fixed it.
brain_stew
Member
Hey Durante, excellent work on this. I'm sure you've already got your plate full with a set of features you want to add to future versions but have you thought about adding properly implemented triple buffering support à LA D3DOverrider to the genetic version of this in the future? As I understand it both tools work on a similar premise but with D3DOverrider not working nicely on W8 it would be nice to have a catch all solution in the future. I'm using RadeonPro with an Nvidia card ATM, but it's not the most elegant solution.
I haven't had time to dive into the tool yet but thanks again for your work.
I haven't had time to dive into the tool yet but thanks again for your work.
I think sweerfx is already included inside gedosato..so you can just remove sweerfx completely and edit the fx files that are inside the folders of gedosato
I downloaded the latest version 0.3.393, and i can't seem to notice any SSAO in game anymore.
I did leave it to "2" from the ini and tried with both the ingame SSAO activated and disabled, but i can't seem to notice anything.
enabling and disabling it with the NUMPAD also doesn't show any noticeable change, whereas it was very obvious in the past version.
The other effects seem to work, not sure about SMAA (honestly didn't try it).
Oh, another thing, is this "halo" around the character normal, when using DoF? (in this case, the high quality one pumped up to 1.1, to show what i mean):
I did leave it to "2" from the ini and tried with both the ingame SSAO activated and disabled, but i can't seem to notice anything.
enabling and disabling it with the NUMPAD also doesn't show any noticeable change, whereas it was very obvious in the past version.
The other effects seem to work, not sure about SMAA (honestly didn't try it).
Oh, another thing, is this "halo" around the character normal, when using DoF? (in this case, the high quality one pumped up to 1.1, to show what i mean):
![[Asmodean]](/data/avatars/m/123/123312.jpg?1526393694){kind=avatar}
[Asmodean]
Member
Nice one, thanks. I just noticed that I forgot to remove a few things from the shader before uploading it last. I was half asleep lol. Good thing that you spotted them.
The difference in performance from the previous vssao, and this, should be a few frames at most, because it's using higher coverage samples for half of it. Plus, it has 3 sampling method options - of which option 2 is literally an optimized version of the previous method used. So it should be faster than previously when the using samplingType 2. (it's defaulted to 1).
----
I've only just tried out the new version there, but it seems like the AO output is visually lighter than before. This is fine for those who are willing to change a few options etc, but it will probably be a problem for people using default settings, it could be too light to even see visually, especially if they're using a strength under 3. The new method looks really nice, the vssao shader will just need some readjusting.
[Asmodean]
Member
If you open VSSAO2.fx with a text editor, there are some options at the top of it you can play around with. You can try raising the aoStrengthMultipliers as well. Just set it to something ridiculous at first, just to see if it even displays for you. eg: 5.00 or something.
Ideally, you'd want to be tabbing in and out of the game, and editing the shader while it's running to easily see shader changes made.
Edit:
Regarding the strength multipliers. Make sure you're raising the correct one for the ssaoStrength(1,2,3) you're using. Or, just raise all of them.
Code:
#ifdef SSAO_STRENGTH_LOW
extern float aoStrengthMultiplier = 0.60; [I]<-- This is ssaoStrength 1's multiplier.
[/I]#endif
#ifdef SSAO_STRENGTH_MEDIUM
extern float aoStrengthMultiplier = 0.75[I];<-- This is ssaoStrength 2's multiplier.
[/I]#endif
#ifdef SSAO_STRENGTH_HIGH
extern float aoStrengthMultiplier = 1.00[I];<-- This is ssaoStrength 3's multiplier.
[/I]#endifMickeyKnox
Member
I'm getting some strange artifacting with AO on distant and midrange objects where there's a strong white outline that I can't seem to get rid of.
i'll try to mess with the .fx then.
for now i took two screens with SSAO activated and deactivated, using NUMPAD3 (i'm using VSSAO2.fx from 0.2 version, btw, but with the 0.3 version is the same) at .ini strength "3".
I personally can't see any difference.
EDIT: Tried with SSAO multiplyer set to 5.0, in the .fx settings, nothing changes, so the problem must be somewhere else, i guess.
Am i the only one with this problem? I'll try to put GeDoSaTo version 0.2 and see if i get SSAO back that way, just to test it out.
for now i took two screens with SSAO activated and deactivated, using NUMPAD3 (i'm using VSSAO2.fx from 0.2 version, btw, but with the 0.3 version is the same) at .ini strength "3".
I personally can't see any difference.
EDIT: Tried with SSAO multiplyer set to 5.0, in the .fx settings, nothing changes, so the problem must be somewhere else, i guess.
Am i the only one with this problem? I'll try to put GeDoSaTo version 0.2 and see if i get SSAO back that way, just to test it out.
[Asmodean]
Member
That's not even remotely on. I doubt changing settings will do anything for you. Doesn't seem to be outputting at all, according to those screens.
Cannon Goose
Member
The AO in the new version is definitely lighter, but it still works on my end. I did have to bump it up from 2 to 3 though.
Also, the bokeh looks absolutely gorgeous when there's stuff floating in the air.
Also, the bokeh looks absolutely gorgeous when there's stuff floating in the air.
[Asmodean]
Member
That doesn't look like its working as intended either. Sure it's 'on' now, but it's not outputting correctly : /
Damn, will just have to fiddle around with it then.
Its the camera and movement that feels almost floaty, the buttons work fine but just looks...strange.
[Asmodean];109783129 said:
I think i'll just put back 0.3, disable GedoSaTo's SSAO and just force HBAO+ from inspector.
See how that goes.
EDIT:
Ok, now i'm wondering if i have a problem with drivers or something... HBAO+ doesn't seem to output, either:
Inspector settings, in case i'm missing something obvious:
[Asmodean]
Member
Here's an example of it off/on from my end. Note that the gamma/brightness got screwed up when I uploaded them to Imgur. It's not normally washed out looking.
Edit:
That's odd. Those settings should work. What drivers/gpu are you using?
OFF
ON
Edit:
That's odd. Those settings should work. What drivers/gpu are you using?
[Asmodean]
Member
I'm using a 680 with the same drivers, so I've no idea tbh. Are you running NV inspector as administrator?. Try setting the AO to off then back to quality from inside the nv control panel itself and see.
Vow of Silence
Banned
I'm another for whom SSAO doesn't work at all with alpha 3. I'm on a 6950 with 13.35 drivers.
Some people seem to have this issue, no idea why for now. Do you have all in-game settings maximized and AO and DoF off?
This is normal with the "cheap" DoF. The bokeh dof (selectable in the ini) doesn't suffer from this issue, but is more expensive.
The only thing I could think of is a messed up installation :/
That screen is actually with bokeh DoF set to 1.1, though at 1.0 that "halo" is not really noticeable, and i think it looks pretty damn good!
Also performance are still acceptable, so i think i'll keep bokeh DoF.
Oh also, yes i have all maxed out and AO and DoF ingame set to Off.
--
As for the AO, since i seem to have problem forcing HBAO+ too, i have to consider the problem lying elsewhere in my system.
I'll try to tinker with inspector some more, though.
EDIT:
So, here's the screens for the HBAO+ test, with relative Inspector settings:
DISABLED
ENABLED
Again, i see no difference.
Unfortunately i have no idea where to even look for a solution, i guess i could try some run of the mill generic solutions, like reinstalling the drivers.
Also, does Inspector override the Nvidia Control Panel? Cause i haven't even touched that one, but i noticed that AO is set to "Off" by default:
Could this be it?
[Asmodean]
Member
That NV control panel screenshot is of your global settings, not application settings.
Just as a test to establish if you're inspector settings are actually taking effect. Try the below;
Open NV inspector, and open your Dark Souls 2 profile. Keep antialiasing on app controlled, but change 'Antialiasing - Transparency Supersampling' to '2x Sparce Grid Supersampling' (this won't enable it, as you still have the AA flag on application controlled. This will only enable you to change texture lod bias). Now look for 'Texture Filtering - Negative LOD bias (DX)' and change it to +2.0000 and hit apply. Then launch the game and see if all the in-game textures are blurry looking.
You can just change them back to normal when you're done.
Edit: I wonder if it's the sli compatibility bits. Try reverting that to normal, and see. Just in case.
On a 64-bit OS it should be under: HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Durante\GeDoSaTo
Cannon Goose
Member
I'm using version 0.3 with version 0.2's vssao2.fx file and I'm seeing the AO flicker off and on when I move through doorways. It's reproducible and I took video of it which I'll upload in a bit.
I'm having the same problem as you.
And with SSAO not working with 0.3. Really weird...
I believe inspector and control panel override each other. I was testing it last night and that seemed to be the case. It remembers the last one you changed.
Just in the control panel, have to make sure to go to the program settings and at not just applying the specific game configuration as your global setting (ie, make sure you are on the second tab before making a selection in the drop down.)
Anyways, my question is that if I want to use AO and SGSSAA from inspector, I need to disable AA and AO from gedosato, what about in game? Keep AA on but disable AO?
Just in the control panel, have to make sure to go to the program settings and at not just applying the specific game configuration as your global setting (ie, make sure you are on the second tab before making a selection in the drop down.)
Anyways, my question is that if I want to use AO and SGSSAA from inspector, I need to disable AA and AO from gedosato, what about in game? Keep AA on but disable AO?
Yep, that should be right.
Yeah, this is an issue when the game changes the tone mapping, since the AO is now applied pre-tonemapping. It shouldn't really flicker on and off, just be applied with different strength. Sadly I don't have an idea of how to fix that yet.
[Asmodean];109793986 said:
Not sure what it was supposed to do, but it definitely did something to the textures:
So yeah, i guess the Inspector does work, just not AO, for some reason.
[Asmodean];109793986 said:
I don't even use SLI (i'm on a single 780) so i'm not sure i ever touched that one.
What should the "normal" be, for it?
I actually can use the regular, ingame AO, though i don't love it.