Dunno. I just wrote it from XC2 perspective.You say the red_auto=on setting doesn't work, are you sure it's not just scene.conf's AutoReduction enabled="true" now?
Dunno. I just wrote it from XC2 perspective.You say the red_auto=on setting doesn't work, are you sure it's not just scene.conf's AutoReduction enabled="true" now?
So this is my lib_nx.ini. The logic here is that humans are actually more sensitive to horizontal resolution than we are vertical, so I've prioritized horizontal resolution at the expense of vertical. In other words, this config file will reduce resolution down to a minimum of 576 x 432 compared to the default 672 x 378. Not only is the subjective image quality better at the minimum resolution, but an added bonus of my file is that the amount of pixels is also reduced over default (248,832 pixels vs 254,016 pixels). This means you can actually get a playable framerate with a downclocked GPU (230mhz) - all while looking better than the unmodified game. This is especially useful if you're away from a charger for longer than expected and want to squeeze out more gametime without sacrificing performance.
Another setting that was changed is red_AtRate. Reducing this to 85.0 is the threshold where resolution transitions no longer result in stuttering (this also applies to XC2). The upper bound (max resolution) was changed to 1280 x 720 so that you can take full advantage of the native screen resolution when plugged into a charger. TMAA is turned on here (but, critically, the sharpening is disabled) and can be turned off and/or substituted for FXAA depending on your preference. Give it a try and let me know what you think. Enjoy!
Code:red_hdsclX=1.0 red_hdsclY=1.0 red_Auto=on red_AtMinX=0.45 red_AtMinY=0.60 red_AtRate=85.0 AntiAliasing=off AA_Sharpness=8.0 tmaa=on tmaaNewUpScale=off
To reduce framedrops by giving higher resolution jumps in heavy areas.Thanks for this!
A question: you say you want to prioritize horizontal resolution over vertical, but your settings show the opposite (your vertical res is 432, higher than the default 378). Did I get something wrong?
Also, could you clarify the reason for setting red_AtRate at 0.85?
so wo should "autoredution enabled=false? and red-auto=off” to close Dr resloution.You say the red_auto=on setting doesn't work, are you sure it's not just scene.conf's AutoReduction enabled="true" now?
But tesla dont work with sxos? Im right?So after some hours in the game, playing in portable mode with the official charger, with native 720p (so no dynamic resolution) ReverseNX set to docked mode, and some overclock (1428MHz CPU, 844MHz GPU and 1600MHz RAM), I can tell you it's very smooth and functionnal. (So if you play docked, it'll be the same)
With those settings, the game looks stunning, it's incredible what we can do on this game, the difference is huge. And there's headroom if in the game there's more demanding area, I can still overclock the CPU and GPU more.
Yeah it's a bit hot, but it doesn't get past 50°C or 323,15K, so it's fine if you think it could damage the console.
In a day or two, I'll record a short video (with no spoilers) demonstrating how it behaves, I can't right now.
Oh and I really recommand you the sysclk module for the Telsa Overlay, it's way more easy to tune clocks that way.
Wrong. It works from 2.9.5.But tesla dont work with sxos? Im right?
So after some hours in the game, playing in portable mode with the official charger, with native 720p (so no dynamic resolution) ReverseNX set to docked mode, and some overclock (1428MHz CPU, 844MHz GPU and 1600MHz RAM), I can tell you it's very smooth and functionnal. (So if you play docked, it'll be the same)
With those settings, the game looks stunning, it's incredible what we can do on this game, the difference is huge. And there's headroom if in the game there's more demanding area, I can still overclock the CPU and GPU more.
Yeah it's a bit hot, but it doesn't get past 50°C or 323,15K, so it's fine if you think it could damage the console.
In a day or two, I'll record a short video (with no spoilers) demonstrating how it behaves, I can't right now.
Oh and I really recommand you the sysclk module for the Telsa Overlay, it's way more easy to tune clocks that way.
I cant get it to work. Where to put the files?Wrong. It works from 2.9.5.
What FW are you using? You need to be on 9.0.0+I cant get it to work. Where to put the files?
Root of SD or in the switch folder?
Hello there. I mainly play on docked and I get the feeling that there can't be much changed to increase the fidelity. I know of overclocking for more headroom as well as improving the adaptive resolution, either upping the minimum resolution or getting rid of it. When editing the config, handheld definitely sees improvements but I am wondering for docked. Any suggestions for further improvement or are we at a limit?
Can you share your config settings. Thanks
Got a couple of screenshots. Both as 720p with no dynamic resolution. One has no AA at all and no bloom, the other only has TMAA on as well as bloom. TMAA does soften the image but cleans up those harsh edges quite a bit.
So the soft one is with all enabled? I think if we could achieve something a bit more sharpened than that, it would be the perfect spot.
So comparing the soft one to the original config file, they're practically the same. Some settings are different but the difference isn't big enough. I decided to settle on native 720p with no TMAA, the shimmering is quite bad though which is one of the reasons why I tried to avoid it. However, the sharpness and clarity are probably the best you can get. With TMAA on, the shimmering is greatly reduced but the whole image is softer. TMAA may still be interesting to explore though, I'll have to find the sweet spot for sharpening with TMAA on during docked mode. I have ordered a mCable alternative, which would give me upscaling as well as anti-aliasing. I'll see how things go.
EDIT: Finally reached Gaur Plain and found quite severe jaggies on the plains at the distance (improving draw distance would really help) with no TMAA and "AntiAliasing=on". This led me to do some testing on sharpness settings with TMAA on. Sharpness is adjusted by changing the value below "tmaa=on/off", counting for all 5 settings.
tmaa=off and AntiAliasing=on, best sharpness but bad jaggies
View attachment 211347 View attachment 211348
tmaa=on and sharpness set to 0.0, the best improvement in jaggies and shimmering but very soft image
View attachment 211349 View attachment 211350
tmaa=on and sharpness set to 0.5, probably the sweet spot: reduces the jaggies and shimmering and being not too soft, has slight artefacts when moving camera or character
View attachment 211352 View attachment 211351
tmaa=on and sharpness set to 1.0, improvement in jaggies and shimmering but has bad artefacts, quite noticeable when moving the camera or character
View attachment 211345 View attachment 211346