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?I'm using a DS4 and I don't feel any lag.
Core i5 2500K @ 4.5GHz, 8GB RAM, 680GTX SLiHmm, strange. What specs you running?
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 3840x2160Core i5 2500K @ 4.5GHz, 8GB RAM, 680GTX SLi
I use my motherboards Bluetooth with the DS4.
That's what I'm running. What kind of delay are you experiencing? Movement? Button input?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
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
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?
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.
No I'm not currently using gedosato at the moment.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.
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.
To answer the questions of multiple people at once: if you use an effect in GeDoSaTo (e.g. DoF, AO) then you should disable the corresponding effect in-game. The only exception is AA, because GeDoSaTo replaces the AA pass.
Yes, right.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?
I can't really help you with that, with my DS3 I don't get input lag :/Hey Durante whenever you get a chance, would you be able to answer this question?a
I'm being hurt by it as well, using a DS4 controller and anytime I actually enable downsampling it just makes input lag severely.
Run the game as admin
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 gedosatoShould I be disabling the SweetFX profile that Durante posted on PCGamer or run it with GeDoSaTo?
Version 0.3 now up:
http://blog.metaclassofnil.com/?p=510
That is entirely possible, I was rather surprised that it was still running that well in the first place to be honest.
Anyway, dropping the old VSSAO.fx file back in place restores performance back to what it was previously with no other changes.
[Asmodean];109781146 said:I've only just tried out the new version there, but it seems like the AO output is much lighter visually 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. It will need some readjusting.
How would i go about strengthening it, though? (aside from putting it @ 3 in the main .ini)
#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]#endif
[Asmodean];109782328 said: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.
Yup, with GeDoSaTo 0.2, it works fine:
(strength at 5.0, to test it out)
Damn, will just have to fiddle around with it then.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.
Its the camera and movement that feels almost floaty, the buttons work fine but just looks...strange.That's what I'm running. What kind of delay are you experiencing? Movement? Button input?
[Asmodean];109783129 said:That doesn't look like its working as intended either. Sure it's 'on' now, but it's not outputting correctly : /
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];109784191 said:That's odd. Those settings should work. What drivers/gpu are you using?
I'm on an EVGA 780 ACX 3GB and i'm using the latest beta drivers.
[Asmodean];109784920 said: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.
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?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).
This is normal with the "cheap" DoF. The bokeh dof (selectable in the ini) doesn't suffer from this issue, but is more expensive.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):
The only thing I could think of is a messed up installation :/Durante, I literally cannot get anything after Alpha 1a working, that's the only version that will work for me, newer releases just crash on startup, what could be causing this?
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 :/
DISABLED
ENABLED
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:
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?
Of Gedo? Is there a registry entry I can delete by any chance?
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:
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?
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?
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.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.
[Asmodean];109793986 said: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.
[Asmodean];109793986 said:Edit: I wonder if it's the sli compatibility bits. Try reverting that to normal, and see. Just in case.
yeah, since I've used GeDoSaTo 0.3, I can't get AO to work through the program OR through DS2 itself. It's like it turned AO off for the entire system somehow.