Hook can only override accessible-after-runtime cvars, such antialiasing or screen percentage. Anything manifest or blue print coded setting is permanent unless overidden in a pak file.
Try turning off per-object blur or DoF or flashback/cutscene film grain. You can't. That's because cutscenes have a prebuilt cvar manifest in their initial blueprint, and the only way to override this is with a pak that loads before anything hits the screen. Same for per-object motion blur.
The only way to 100% enforce Manifest settings is to make a .pak, not an ini, a pak that overrides DefaultEngine.ini while keeping the control and accessibility functions intact and pristine.
I've been playing with it for over 16 hours of game time and have gotten many achievements. So empirically, I'm confident that it does not affect achievements via Steam. Enjoy!
Will this help with stuttering on dx12? I've tried dx11 but it still stutters. It's so bad in all of the NPC hubs. Sucks because the mods are so cool for this game.
I downloaded FFVIIHook and wrote the line down in the Engine file. Console is enabled and I can open it with my tilt key, but the game still looks exactly the same. Am I missing a step? Shouldn't the lines in the Engine file apply the changes automatically? Or do I need to run a line in the console?
Hi, I have a question regarding the new patch for the pc version.
It said in the patch notes “-The resolution is now stabilised for framerates of 90 and above.”
Does this mean dynamic resolution is disabled for all FPS options like 30fps and 60fps or that dynamic resolution is still in place if you chose 60fps and it switches on when you pc doesn’t hit 60fps? Does that imply that in the pre-patch version dynamic resolution only applied when you chose 90fps and 120?
I find the patch notes a bit confusing.
Also when I have the resolution disabler mod installed there are certain cutscenes (esp. character close ups where the FPS dips a little from 60fps to 50fps). However, this isn't the case WITHOUT the mod on the latest 1.001 version. This leads to me to believe either there is still some sort of dynamic resolution in place for the 60fps target or that the resolution disable mod causes these dips.
When installing the mod, should I put in the mods folder or just the Pak file in the directory? Also if I should copy the mod folder in, should I move the Pak file out to the mod folder for it to work?
222 comments
At all.
Hook can only override accessible-after-runtime cvars, such antialiasing or screen percentage. Anything manifest or blue print coded setting is permanent unless overidden in a pak file.
Try turning off per-object blur or DoF or flashback/cutscene film grain. You can't. That's because cutscenes have a prebuilt cvar manifest in their initial blueprint, and the only way to override this is with a pak that loads before anything hits the screen. Same for per-object motion blur.
The only way to 100% enforce Manifest settings is to make a .pak, not an ini, a pak that overrides DefaultEngine.ini while keeping the control and accessibility functions intact and pristine.
Get yourself the program 7 zip and extract that boi its comprimated
It said in the patch notes “-The resolution is now stabilised for framerates of 90 and above.”
Does this mean dynamic resolution is disabled for all FPS options like 30fps and 60fps or that dynamic resolution is still in place if you chose 60fps and it switches on when you pc doesn’t hit 60fps? Does that imply that in the pre-patch version dynamic resolution only applied when you chose 90fps and 120?
I find the patch notes a bit confusing.
Also when I have the resolution disabler mod installed there are certain cutscenes (esp. character close ups where the FPS dips a little from 60fps to 50fps). However, this isn't the case WITHOUT the mod on the latest 1.001 version. This leads to me to believe either there is still some sort of dynamic resolution in place for the 60fps target or that the resolution disable mod causes these dips.