Homebrew RELEASE sys-clk under/overclocking sysmodule

[Instandhaltung]

Hey nice people, just a quick question. I am using sys-clk but I wondered about two things:
1. When I am starting the homebrew launcher to use an emulator, the overclock setting of the app I used to launch the homebrew launcher will transfer to the homebrew apps, correct? In short: To use overclock with homebrew, I have to launch it over a game with an overclock setting.
2. I think that I might have witnessed worse performance on an emulator after being in standby. Is it possible that the overclock resets during standby? Or was it just my imagination?

 

[p-sam]

DF never looked into going beyond what sys-clk allowed out of the box.

I'm not sure of your definition of "out of the box", you might see why after the next release

Hey nice people, just a quick question. I am using sys-clk but I wondered about two things:
1. When I am starting the homebrew launcher to use an emulator, the overclock setting of the app I used to launch the homebrew launcher will transfer to the homebrew apps, correct? In short: To use overclock with homebrew, I have to launch it over a game with an overclock setting.
2. I think that I might have witnessed worse performance on an emulator after being in standby. Is it possible that the overclock resets during standby? Or was it just my imagination?

1. Yes
2. No it should be okay

 

[Instandhaltung]

1. Yes
2. No it should be okay

Hm weird, I guess it was the emulator then

 

[p-sam]

It's time for a new sys-clk update ! Features temperature logging, CSV exports, more efficient logs, and a few fixes. Go get it here ⏱️ https://t.co/9hLqTRIMRt

— 🅿️ ＳＡＭ (@p__sam) September 20, 2019

 

[veekay]

Is it normal to actually lose battery charge when overclocked and on the dock? It isn't much, but maybe 1% an hour when clocks are maxed out.

 

[Raul8]

Thanks for the update! I think there is a minor bug, in one game (Xenoblade 2) I used 921 MHz, then reverted (while in game) to 768 MHz; after that, reading the .csv file, the maximum clocks were still been written in the file but I was using 768 MHz, only the last update of the .csv file reflected the real clocks. The frequency was set to write every 5 minutes. I played for about an hour with 768 MHz.

 

[Audioboxer]

Just found this, really cool.

Has anyone messed around with Zelda Links Awakening? Some rough framerate drops in handheld mode from time to time.

 

[hippy dave]

Just found this, really cool.

Has anyone messed around with Zelda Links Awakening? Some rough framerate drops in handheld mode from time to time.

Yep, set the higher mem clock, and as high GPU as you can depending if you're plugged in or not. Bumping the CPU clock up would probably help load times too.

 

[Audioboxer]

Yep, set the higher mem clock, and as high GPU as you can depending if you're plugged in or not. Bumping the CPU clock up would probably help load times too.

I'll have a play around with it. The framerate drops in the game really are pretty bad.

 

[Rahkeesh]

The trouble with link's awakening is that double-buffering, if you ever drop below 60 you're straight into 30 FPS ville, and raising the GPU from 700 to 900 doesn't do much to fix that. Its hard to see much difference in smoothness docked without doing something drastic like ReverseNX, which lets you run handheld resolution at docked clocks. You can probably also get good results with sys-clk and a charger running docked clocks in handheld mode.

 

[Audioboxer]

The trouble with link's awakening is that double-buffering, if you ever drop below 60 you're straight into 30 FPS ville, and raising the GPU from 700 to 900 doesn't do much to fix that. Its hard to see much difference in smoothness docked without doing something drastic like ReverseNX, which lets you run handheld resolution at docked clocks. You can probably also get good results with sys-clk and a charger running docked clocks in handheld mode.

Things are improved a little I think with messing around.

One quick question for anyone, I know handheld_gpu is limited to 460 max, but what about handheld_cpu? Will it go to 1785? Obviously that will eat battery though lol.

 

[Puremin0rez]

I'm new to sys-clk and I'm just trying to figure out if any of this is normal or not.

I currently have a blank config file (so no overclocks or anything like that), and sys-clk is running.

When I do title takeover (hold R while launching a game), and go into RetroArch, the clock is forcibly set to whatever the games clock is launching as. If i choose a higher (or lower) clock in Retroarch, it just immediately reverts back to whatever the titles clock was set as.

As an example, if I do title takeover on Super Mario Odyssey, of which I have no profile for, and open Retroarch - my clock is now maxed out to 1.7ghz (in handheld) and I can't change it.

If I launch Homebrew Menu via Album, in applet mode, and open RetroArch - my clock is then forcibly set to 800mhz and can't be changed.

Is this normal behavior when having sys-clk installed?

 

[p-sam]

I'm new to sys-clk and I'm just trying to figure out if any of this is normal or not.

I currently have a blank config file (so no overclocks or anything like that), and sys-clk is running.

When I do title takeover (hold R while launching a game), and go into RetroArch, the clock is forcibly set to whatever the games clock is launching as. If i choose a higher (or lower) clock in Retroarch, it just immediately reverts back to whatever the titles clock was set as.

As an example, if I do title takeover on Super Mario Odyssey, of which I have no profile for, and open Retroarch - my clock is now maxed out to 1.7ghz (in handheld) and I can't change it.

If I launch Homebrew Menu via Album, in applet mode, and open RetroArch - my clock is then forcibly set to 800mhz and can't be changed.

Is this normal behavior when having sys-clk installed?

yup

 

[swutch]

I have updated my firmware from 8.1 to 9.0.1 and Kosmos to 14.2 (emummc)
Now when sys-clk(0.13.0) plugin is activated, and I start Assassins Creed 3, the switch crashes after about 5sec after the Ubisoft logo.
I even don't have settings for assassins creed in the sys-clk config.
As soon as I deactivate sys-clk it won't crash any more.

everything worked fine with firmware 8.1

edit:
---------------------
also Crash Team Racing freezes in main menu, when the plugin is activated.
is sys-clk not yet compatible with 9.0.1?

Assassins Creed 3 crash log:

 

[Anonymousu]

May I ask what to do if I want to overclock and not get banned?

Which online games and applications can be played without being banned?

(What is The Witcher 3's ID anyway?)

 

[Username4321]

(What is The Witcher 3's ID anyway?)

Witcher 3 should be [01003D100E9C6000].

 

[Rahkeesh]

If you are using blawar's latest tinfoil/hbg it's going to cause issues, basically turning kosmos into an atmosphere fork. sysmodules like sys-clk then aren't going to function correctly out of the gate because atmosphere isn't preconfigured for them to work. I ended up reinstalling kosmos and using tinfoilmod to get around it.

 

[Florens]

Will charging with my 60W laptop charger unlock the overclocks only for the official charger? Is there anything special about the official charger except it being 40W.

 

[swutch]

If you are using blawar's latest tinfoil/hbg it's going to cause issues, basically turning kosmos into an atmosphere fork. sysmodules like sys-clk then aren't going to function correctly out of the gate because atmosphere isn't preconfigured for them to work. I ended up reinstalling kosmos and using tinfoilmod to get around it.

thanks for the hint, but i only use original kosmos and not the frok from blawar.
(always copied only the switch folder and now with mod)

does sys-clk work with version 9.0.1 and the mentioned games on your system?

 

[MonMonz]

am trying it with TW3 how to check if it worked or not?