It's not atmos, I update it later.
Py script is for version released with it if I remember well.
i reported at github the problem with RAM OC, will report when KazushiMe answer me
Homebrew Homebrew app Switch-OC-Suite
- Thread starter ChanseyIsTheBest
- Start date
- Views 82,021
- Replies 300
- Likes 13
- Status
Py script is for version released with it if I remember well.
i reported at github the problem with RAM OC, will report when KazushiMe answer me
It depends on the game really, you do get more generally benefit with at higher CPU/GPU values but you still get benefit at lower ones as well just not as much. Mario Rabbids Sparks of Hope is capped at 30FPS and usually maintains that with some drops so max RAM should decrease FPS drops somewhat.
Last edited by ChanseyIsTheBest,
I used InfoNX, couldn't find it compiled anywhere and was tired of asking too for a way to check voltages...
I got it from the all-in-one 4IFIR mod from @Cooler3D
https://github.com/renA21/InfoNX/network/members (despite this being a link from renA21 github, I have 0 clue who made it at all though seems to come from masagrator but from his description I have no clue if it even had voltage function)
View attachment 348955
(It has other stuff which I hope doesn't change like power settings for the battery or something as it has 2 options you can press, you can check at the bottom of InfoNX in my screenshot).
ps: anyone with a github account I'd be pleased if you can contact KazushiMe if he can add InfoNX to OC suite which I think it's a cool addition (though I think he is planning to make his own voltage information)...
Wanted to know what all the fuss was about so I compiled the version of InfoNX located here:
https://github.com/renA21/InfoNX/
it’s also version 1.0.1 but there are some slight changes so I figured it would be worth uploading this version here:
https://gbatemp.net/download/infonx-overlay.37844/
I’m curious about the >80% statement at the bottom, soooo
a couple pics while at around 75% charge.
with reduce battery aging OFF
with reduce battery aging ON
*charging happens*
wait! I see it.
Disable Charging >80% now turns On/Off along with the Reduce Battery Aging toggle at the top.
(in short they simplified the L stick R stick choices)
What about the ram OC making things a bit stuttery on some games, is it to do with voltages too??
I'm now using 1996mhz on Erista with Samsung memories it seem to be working fine like 1862mhz both stock voltages and on memtest 1996 does give a slight increase in performance over 1862 thought it's minimal.
Also I tested before more than 4hours on memtest with 1862mhz perfectly fine.
On Resident Evil 6 for example wether it's 1862 or 1996 after some time it start to give small stuttering, if I change to 1600 and back to the max frequency it gets rid of it, but eventually the stuttering is back.
Did anyone found a fix for that on mem OC?
Also did memtests with same exact score (within margin of error) as last stable version and played for like 1h resident evil 6 with no issues.
I'm now using 1996mhz on Erista with Samsung memories it seem to be working fine like 1862mhz both stock voltages and on memtest 1996 does give a slight increase in performance over 1862 thought it's minimal.
Also I tested before more than 4hours on memtest with 1862mhz perfectly fine.
On Resident Evil 6 for example wether it's 1862 or 1996 after some time it start to give small stuttering, if I change to 1600 and back to the max frequency it gets rid of it, but eventually the stuttering is back.
Did anyone found a fix for that on mem OC?
Seem to be working fine here and voltage reading is back but it's not right giving wrong values (InfoNX keep showing the voltage properly though).
Also did memtests with same exact score (within margin of error) as last stable version and played for like 1h resident evil 6 with no issues.
Last edited by guily6669,
IMO the stuttering is one of two things, the game engine doesn't like 1862, my RAM is stable at that but for some reason Persona 5 Royal had some music stutters very occasionally (a couple times an hour) What was interesting was this happened at stock RAM as well just much less frequently. The other thing is that you undervolted too much maybe but I doubt that because stress test benchmark is fine and you haven't been having crashing or hanging problems.
EDIT: The latest version of sys-clk OC crashes my Switch because of the Loader.kip and I updated AMS to the latest as well. Hope I can fix this lol
Last edited by ChanseyIsTheBest,
I was just about to drop the shitz in too. I just upgraded AMS to 1.4.1 and was feeling froggy enough to check out OCS.
You can just remove the loader.kip and reboot back to normal, right?
Do I have to switch to boot w/ fss0 to use OCS or can I keep fusee.bin?
You can just remove the loader.kip and reboot back to normal, right?
Do I have to switch to boot w/ fss0 to use OCS or can I keep fusee.bin?
Latest version of OC suite is working pretty fine for me also on latest atmosphere, both are version 1.4.1 and hekate 6.0.1
Maybe you are not using the sys-clk included in it?
I already tested some older version and OC was working fine without the loader.kip but the ram OC was gone.
I'm not sure about the payload I'm anoob\rookie, but I think I'm only using fusee.bin from hekate without autoboot and latest OC suite is working good for me.
Maybe you are not using the sys-clk included in it?
I always reboot to hekate and manually launch emunand when I change or delete the .kip...
I already tested some older version and OC was working fine without the loader.kip but the ram OC was gone.
I'm not sure about the payload I'm a
Last edited by guily6669,
Comment out the line kip1 line in hekate_ipl.ini and you can reboot back to normal.
The second part I'm not sure. I personally don't use fusee.bin and use SysNAND.
I got mine to work I just had to update atmosphere a second time because it didn't copy the files across the first time kind of weird.
Appreciate the hints. I’ll move forward.
I don’t believe other variables in a helate_ipl.ini stanza are considered when you use fusee.bin so I’ll switch to match your working model.
I don't know if that does anything cause I never added the line to my hekate, from what I understood after some update with full Erista support I think they said it didn't need to modify hekate settings but I'm not sure.
Anyway I know my "loader.kip" is definitely working, it automatically lunches with atmosphere because deleting it the mem OC doesn't work so maybe don't even need it to be added on hekate.
I'm talking about this: "kip1=atmosphere/kips/loader.kip"
Ps: but I have 0 clue if it makes any difference adding it to hekate...
In the readme, it say you must add this line to hekate, so better do it, when say no need to modify hekate, it's about minerva, older versions you must compile it with te values of the RAM OC or delete it, but now it's not needed
Well but it's working fine for me without it and applies whatever settings I add in the .kip wether it's voltages or ram frequency...
I think atmosphere also for a while says anything in \kip will be loaded automatically...
Ps: I might try adding the line when I get home but I'm thinking it won't change anything because my loader.kip is definitely loaded and working fine.
I think no change, because fusee.bin is supposed to execute all kips al the kip folder, but if KazushiMe say add it... Better do it, you will lost nothing, haha
New silent update.
Last updated @ 2023-01-27T02:49:20ZZ
Last updated @ 2023-01-27T02:49:20ZZ
Thanks for this.
What would be the most noob-friendly way of setting this up?
What I want to do is a kind of set-and-forget but maybe now and then have a setting or two that I might change depending on the game.
From what I understand, having the RAM always on 1862 (whether docked or not) is safe? if so, is there a way to always have it on?
Another question - I have sys-clk installed, I would assume I need to replace sys-clk with this as I don't need both?
What would be the most noob-friendly way of setting this up?
What I want to do is a kind of set-and-forget but maybe now and then have a setting or two that I might change depending on the game.
From what I understand, having the RAM always on 1862 (whether docked or not) is safe? if so, is there a way to always have it on?
Another question - I have sys-clk installed, I would assume I need to replace sys-clk with this as I don't need both?
Yeah you replace the old sys-clk with this sys-clk. Setting ram to 1862 to always on is safe if its stable for your Switch. You can set universal ram frequency by using global profiles in the sys-clk overlay.
Thanks for your response, I would love some help though, this is a bit scary for me.
I have an erista.
By following above instructions, am I getting the default setting or what exactly? I dont want to mess with it to much, just get optimized RAM and whatever is safe for handheld/docked, nothing crazy.
Step #2 says to copy all files from SDOUT which are these:
Do I move all of them and just extract the other files from the 2nd sdout to the Root? not sure what to do with system_settings.
Step #3, Since I dont have a folder named kips, do i just make one and put the file there?
Step #4 is scary to me, what would be the optimized way as mentioned above?
I have an erista.
By following above instructions, am I getting the default setting or what exactly? I dont want to mess with it to much, just get optimized RAM and whatever is safe for handheld/docked, nothing crazy.
Step #2 says to copy all files from SDOUT which are these:
Do I move all of them and just extract the other files from the 2nd sdout to the Root? not sure what to do with system_settings.
Step #3, Since I dont have a folder named kips, do i just make one and put the file there?
Step #4 is scary to me, what would be the optimized way as mentioned above?
Just extract what's inside that 2nd SdOut to the root of your mSD, it will have Switch and atmosphere folder, just copy paste...
Don't worry, by default you will have very stock like settings including default or very similar to stock voltages... And in terms of clocks you chose on-the-fly at any moment you want from switch Tesla menu and can be configured per game or general profiles and has different choices of clocks for handheld, docked, handheld with official charger and so on...
The clocks will automatically change to whatever your choice, like for me I can be on whatever high OC, if I remove the official charger I set default clocks with default ram frequency...
Note: You also need the following:
Tesla-Menu:
saltyNX:
nx-ovlloader:
ReverseNX (not mandatory but if you want to use the included option to change between docked\handheld mode you need it);
StatusMonitor (not mandatory but it gives you the CPU\GPU usage and other extras);
NX-FPS (not mandatory but I think it's needed for statusMonitor to show current game FPS);
- Status
Similar threads
He/them/IT does