Any graphics mods or fixes?

[~🐣Venvetta🐣~]

I'm new to the DQ series and I just played the demo for a couple of hours. I really like the artstyle of this game and the intro cinematic looked absolutely amazing, but something about the ingame graphics looks a bit....console-ish? There seems to be barely any anti-aliasing, especially in the distance (or is something wrong with the resolution? idk) and there are no shadows on stuff like grass etc. Is there a way to fix this? Or is it just because it's a demo? In my opinion it kinda dampens the otherwise great visuals of the game.

[Mist]

Ryuzaki Morgoth の投稿を引用：

So, I did it but I got some weird shadow silouhette around me, what is causing this?

Kinda hard to tell. I know it's a pain but adding each part one at a time and checking for the culprit is the best way to deal with it.

[The Ultimate Despair]

r.DefaultFeature.AntiAliasing=2

r.PostProcessAAQuality=6

r.TemporalAASamples=16

r.TemporalAACurrentFrameWeight=0.45

r.TemporalAAFilterSize=0.5

r.Tonemapper.Sharpen=1

The culprit is something between or a combo of those, i can now confirm as much

[Mist]

I use all of them and don't have the same issue. That's really weird.

[The Ultimate Despair]

Alright, after final testing, it appears that the motion blur setting tweak completely fixes it, for some reason. Its weird because you could see this artifact without moving the camera, but then again I will assume that its caused by the camera's movement not syncing with the character's silouhette. Maybe the modder in this thread can confirm this?

[Mist]

Ah, so it was an issue of missing settings instead? Interesting.

[The Ultimate Despair]

Mist の投稿を引用：

Ah, so it was an issue of missing settings instead? Interesting.

I do think so, I'm no modder, but I think i understand enough of the basics to tell its probably an issue with the engine not being able to sync with the silouhette or something similar.

[Evangela]

Bleh... SE can't do anything right nowadays.

[Mohal]

Which one to use? [/script/engine.renderersettings] or [SystemSettings]
Is there a difference? Because on PCGamingWiki they use both.

[Ghigi]

Mohal の投稿を引用：

Which one to use?

I would put what's already in the usersettings file under systemsettings. What I mean is that couple of settings are not added but tweaked over their default values. Example: the only way to actually remove the FXAA (using the postprocessingsAA =0) and increase the screen percentage is putting those lines under [SystemSettings], at least on my end.

[the_randomizer1889]

Current specs:

Core i7 9700K
MSI RTX 2060 Super
32 GB DDR4 SDRAM
2560 x 1440 Asus IPS monitor

Which settings would be the best for this setup? Obviously, I don't want to fry my CPU or GPU.

[Ghigi]

Ok, I almost completely fixed my "flickering" issues. As I mentioned in my previous post, there are some settings that are NOT recognized if you do not put them under the [SystemSettings].

The fix was putting "PostProcessingAA=6" in the right place and the TAA started working as intended, not only that: if I now select in-game any AA level, they do not affect the screen at all and the overall look of the game is way better than before.

[marcus]

Ghigi の投稿を引用：

Ok, I almost completely fixed my "flickering" issues. As I mentioned in my previous post, there are some settings that are NOT recognized if you do not put them under the [SystemSettings].

The fix was putting "PostProcessingAA=6" in the right place and the TAA started working as intended, not only that: if I now select in-game any AA level, they do not affect the screen at all and the overall look of the game is way better than before.

i've the same problem, can u post your ini?

it seems that those tweaks only works if i put then under [SystemSettings] instead of [/script/engine.renderersettings]

[Ghigi]

I posted a "fixed" ini here: https://steamcommunity.com/app/1295510/discussions/0/2974028351342437724/#c2974028351344153670

[Orang Asli]

thank you for the pinned mod,btw anyone have fix for ultrawide 21:9 3440 x 1440 mod?

[Tim Allahn SnAckbarr]

So obviously there are plenty of good resources on tweaks at this point https://steamcommunity.com/sharedfiles/filedetails/?id=2312807086

I did want to add a couple things I have noticed since downloading the full release (from the Demo version).

1. I encountered an issue where my Engine.ini was being overwritten (with the same settings as the last time I had played the Demo) every time I launched the game. Even going back into the Demo config and changing the ini there did not change this. I have no idea what caused this (other than simply upgrading from the Demo), but for anyone else who encounters the same issue this is how I "fixed" it:

-Make the changes in Engine.ini and save it
-Right click the file -> Properties -> Advanced
-Auditing tab -> Continue (elevates you to Admin permissions)
-Permissions tab -> Disable inheritance
-A new dialogue opens -> "Keep inherited permissions"
-Change permissions for SYSTEM (and maybe even your own user account if you're paranoid like me) to "Read & execute"
-Apply

This makes it so that the file is read-only and hence won't be overwritten by the game at launch.

2. I have noticed some discrepancies (omissions, etc) with different posted configs/guides/etc, particularly with 2 things that really seem to boil down to personal choice.

-Depth of Field: I prefer having Depth of Field effects off, similar to OG's default. Hence I recommend

r.DepthOfFieldQuality=0

However, I know some people like having Depth of Field on. If you do, please note that the default DepthOfFieldQuality is 2, not 1. I have seen a couple posted configs that have this set wrong, 1 is for very low-end systems (2 is barely a performance hit on any modern hardware configuration anyway). And really, if you want DepthOfField on, you should just eliminate this line from your config. 2 is the highest value for that cvar

-Tonemapper: I really like having the sharpen tone mapper on as well. On my setup, it makes the game look far crisper than it does by default, and actually makes the textures look much higher definition. The ideal value also seems to vary wildly. I've heard some people say that r.Tonemapper.Sharpen=1 is way too strong, and recommend r.Tonemapper.Sharpen=0.3 instead. On my configuration however, 0.3 makes almost no difference. In the Demo, r.Tonemapper.Sharpen=1 was perfect, however when I started playing the full release, I ended up having to turn it up to 4 in order to get the same definition. So

r.Tonemapper.Sharpen=4

is what I recommend now, but what value is "ideal" will depend entirely on you. Some people say it looks "fried" or "way too crispy" with that setting, but I encourage anyone to test with it, as it (combined with r.ScreenPercentage=150) made my game look 10x better (like 1.5 generations ahead).