Because devs are tied to SDK. And SDK Has clear limitations on what is possible.
- Thread starter DemetriusBlack
- Start date
- Views 155,159
- Replies 635
- Likes 36
They may use 460 mhz in handheld mode like BOTW and Witcher 3 developers. I think that nintendo must add option to SDK for higher clocks for Mariko consoles, cause it have lower TDP.
Last edited by Stepik,
They can't if Epic won't add option for it to UE4.
Iirc Unity still doesn't have option to enable 460 MHz.
NVN is not responsible for clocks. Only nnSDK.
And it's not about configs. It's about adding options.
Last edited by masagrator,
I tested your config on 460 Mhz and it's laggy but beatiful (cfg code also is more beatiful), lower or lowest cfgs is more comfortable to play.
Thanks! Tried it out, performance was fine in handheld at least, I almost never play docked. I've never noticed flickering issues, that's a shame. I like me some lens flare to distract me from the missing skyboxes lol. This game is looking more and more like borderlands thanks to the work you guys put in.
This might be my last update, I'm happy with it's performance now
- Reduced lowest dynamic res to 55%
- Reduced shadow quality in handheld mode (Shadow.MaxResolution=512, Shadow.CSM.MaxCascades=1)
- Reduced docked graphics profile (sg.TextureQuality, sg.FoliageQuality still remain higher than handheld)
- Add a version with SSR disabled in handheld mode (if you don't mind those bright white water ponds on ground, use this for better performance).
- Reduced lowest dynamic res to 55%
- Reduced shadow quality in handheld mode (Shadow.MaxResolution=512, Shadow.CSM.MaxCascades=1)
- Reduced docked graphics profile (sg.TextureQuality, sg.FoliageQuality still remain higher than handheld)
- Add a version with SSR disabled in handheld mode (if you don't mind those bright white water ponds on ground, use this for better performance).
Why you changed +CVars=r.GTSyncType= to 0 from 2? mode 2 is for reducing frame latency.
https://docs.unrealengine.com/en-US/Platforms/LowLatencyFrameSyncing/index.html
And in scalability options r.PostProcessAAQuality= is jumping from FXAA to TAA as you said earlier.
--------------------- MERGED ---------------------------
For making bigger interface and font change ApplicationScale to 1.100000 in section [/Script/Engine.UserInterfaceSettings] in DefaultEngine.ini
That GSyncType was in vanilla settings I didn't touch it. I don't know but when I put r.PostProcessAAQuality=2 in Default Enginee.ini it's FXAA
--------------------- MERGED ---------------------------
The ghosting may be is a penalty for sharper, less blurry TAA, you can increase sg.AntialiasingQuality to 3 - 6, r.TemporalAASamples to 4 or 6, increase TemporalAACurrentFrameWeight in BaseSwitchDeviceProfiles.ini and see if it still there.
Edit: sg.AntialiasingQuality=3 seem to fix that major ghosting trail (there's still minor ghosting around it especially when facing sea but I can just ignore it - and seem it can't be fixed completely anyway)
Last edited by NotACat,
try this, I added +CVars=r.Streaming.MaxTempMemoryAllowed=35 from default configs in 1st page, also increased sg.AntialiAliasingQuality to 3 to reduce ghosting trail
Last edited by NotACat,
this config is the same as ssr off.
I found good option for SSR
+CVars=r.SSR.Quality=1
+CVars=r.SSR.Temporal=0
+CVars=r.SSR.MaxRoughness 0.1
I have just tested this config, SSR ON, stock clocks, handheld mode: performance is a bit better, but not as visually striking as your config from top of page 19 (my preferred so far). Btw, DOF is missing (in conversations, for example) :/
I have just tried this too, do not see much difference with the latest .configs you have uploaded. DOF is noticeable lower (sorry, I'm a sucker for that effect, especially in a game with so many conversations.
I have set for "My Config" you have uploaded on page 21, still playing on stock clocks. It has a very good DOF and balance between performance and overall look, so I have replaced your previous .config on page 19 for this one.
Thx for your work!
Similar threads
