Homebrew Homebrew app Switch-OC-Suite
- Thread starter ChanseyIsTheBest
- Start date
- Views 80,972
- Replies 300
- Likes 13
- Status
Gladly I never had that happening to me... Make sure you really have all the required stuff.
Also I have atmosphere 1.4.1 and Hekate 6.0.1 and I use Hekate to boot atmosphere with fusee.bin. My Nintendo FW is 15.0.0...
Ps: also make sure you have latest sigpatches. Don't know if any of this info helps
For some reason I had to copy over the atmosphere files twice to get the new OC Suite to work. Something is a bit wacky with it.
Humm, that's odd...
Cause I also updated a friend switch Hekate and Atmosphere and added all OC stuff and other stuff, but I did a clean Hekate and Atmosphere install by deleting the old...
Everything was setup exactly like before updating but somehow not a single sysmodule were working not related to OC suite and hell even tinfoil was broken but all installed games were fine...
I rebooted like 4 times to Hekate and back to atmosphere and at 4th reboot without doing nothing everything was working perfectly fine, tinfoil was back in business and all sysmodules were finally loaded without doing anything...
Ps: could it be some odd bug with atmosphere 1.4.1 compared to 1.4.0? Though I think it's just his crap slow integral 500GB A1 mSD (it has never been tested)...
There is no need to update if all is working good, I think it's only a cleanup code, but I always like all updated, I only report because sometimes are silent updates, if you want to know what's new, click at code with last update
Attachments
Also we could use 0 values on some other options before which would probably instantly mean use stock value but now it's mandatory to put a value or it also throws a error, thought it's not important cause they have the default value listed but still a bit annoying to have to copy paste all default values if we want to change anything on the loader.kip...
Ps: but using ram timings option 1 instead of 0 at least doesn't seem to affect Erista, I'm getting pretty much same speeds\latency as before within margin of error...
EDIT: What the heck, the online configurator page seems to have just been fixed...
Last edited by guily6669,
Yes, I reported it yesterday and KazushiMe fixed it 6 hours ago, there was two values with problems
Changed this in the first post. I misunderstood something some I'm fixing it because I got confused.
DO NOT GO ABOVE 537 GPU UNPLUGGED ON V2 SWITCHES - going any higher is bad and will damage the Charger IC.
Yep this is wrong. Keeping this up for a while so people who have read this read this. As a general rule of thumb on V2 unplugged make sure you have at least 1 hour of battery life while OCing preferably 1.5 hours for battery health.
Edit: Ignore all the strikethrough I got stuff wrong again.
This is the rule you should be obeying while unplugged.
Avoid going close to 18W on Mariko/OLED/v1 and 12W on Switch Lite. You can check approximate power draw in the Misc. section of Switch OC Suite (don't know how close the accuracy is, but if you Switch turns off while OCed while you still have above 1% you are drawing too much power.
Also the reason why you can't go above 460mHz GPU on v1 is because of power draw. Going higher on the CPU draws a lot less power then even going moderate with GPU. If the CPU could go past 1785 on v1 you would get the emergency shutoffs as well. Thanks for CTCaer again for clearing this up.
Yep this is wrong. Keeping this up for a while so people who have read this read this.
Edit: Ignore all the strikethrough I got stuff wrong again.
This is the rule you should be obeying while unplugged.
Avoid going close to 18W on Mariko/OLED/v1 and 12W on Switch Lite. You can check approximate power draw in the Misc. section of Switch OC Suite (don't know how close the accuracy is, but if you Switch turns off while OCed while you still have above 1% you are drawing too much power.
Also the reason why you can't go above 460mHz GPU on v1 is because of power draw. Going higher on the CPU draws a lot less power then even going moderate with GPU. If the CPU could go past 1785 on v1 you would get the emergency shutoffs as well. Thanks for CTCaer again for clearing this up.
Last edited by ChanseyIsTheBest,
Tempted to test some of the safe vaules on a v1. If I do i'll check back in a few days.
I believe technically you might be able to get away with 537 GPU but its borderline and risky and could still cause shutouffs.
But without charger its not possible, is limited to 460, months ago I was using a sys-clk version with an option to unlock it, and I used 1020/768 without problems, I wish someday KazushiMe give us the option to do it too
Pd. I'm testing now some UV, only can do a little, 1100 at CPU (1125 default) and 1100000 at Samsung RAM (1125000) using always 1862,4, will try these days same voltage with 1996,8
Last edited by Medel87,
If PD not exceed 18W shouldn't be a problem
Pd. KazushiMe said will try to add an option to do, only if PD not exceed it
https://kazushime.github.io/Switch-OC-Suite/
This is on the project homepage. They aren't going to add it.
These were 'fake' clocks, I believe voltages weren't set right. Not all Mariko Switches could handle those clocks because they have varying CPU and GPU speedos. It's basically a gacha. Those high didn't exactly boost performance all that much and had crazy high power draw.
Here's a performance comparison that should be useful showing GPU clocks over 998 offer diminishing returns (plus they have unsafe power draw). GPU performance at high unsafe clocks does depend on GPU speedo (gacha) I'm going to add this to the main post later. RAM performance on Mariko is a gacha as well.
Mariko w/ auto adjusted RAM (1996) timings #1
Mariko w/ non-auto adjust RAM (2099) timings #2
Mariko w/ auto adjusted RAM (1996) timings #3
v1 Switch 1862 RAM and 1600 RAM
Idk what you mean i downloaded official package and i have those clock frequncies. It seems they changed the freqencies in later version.
I know, but at issues said this and it's not closed
Maybe someday KazushiMe will take a look
KazushiMe got rid of those later frequencies because they aren't real and don't work right. They are 'fake' and can give lower performance. You'd set your Switch to one of those clocks using status monitor but it wouldn't actually be set at that clock and would be set lower and you'd get worse performance. You could literally set the clock to 10000mhz it would show that in Status Monitor but it wouldn't actually be running at that and would drop lower and have errors (worse performance).
If you still have those higher clocks and want to do test do a performance comparison in Crash Trilogy on the first level of Crash 1 and compare your FPS to the FPS in the images I sent on each GPU clock increase. That should show the problems with those clocks.
Post automatically merged:
The project page was added less than week ago and it says 'never'. That issue post response is from December. I think they have made up their mind. It's a shame if you want to use it those but you would have to edit out the restriction and compile it yourself.
- Status
Similar threads
- No one is chatting at the moment.
-
-
-
@
Sonic Angel Knight:
Or, I also heard that if you use flash memory, it can act as more "RAM" at least windows tell me when I stick a flash drive into it. -
-
-
-
-
-
-
-
-
-
-
-
-
-
-
@
K3Nv2:
I can think of the design teams process another joystick and no audio or a joystick and mono audio -
-
-
-
-
-
-
