Running 24/7 for weeks already on max clock and full loadTo be honest I kind off do think so. Please educate me if I am wrong.
Running 24/7 for weeks already on max clock and full loadTo be honest I kind off do think so. Please educate me if I am wrong.
While these values are in the nvidia's spec. and everything is underclocked to begin with, we will only know in a few years.Sorry about the switch, which is screwed for testing the oc
Overclocking has been publicly available information for months. It's literally 3 lines of code. You're not only off base in your characterization of the issue, but you've totally ignored the part about us actuallycaring whether or not we ruin users consoles.
It is and always will be "use at your own risk."Is the code that's been released safe? Or is it a use at your own risk thing
Did not expect this. Respect.Running 24/7 for weeks already on max clock and full load
It is and always will be "use at your own risk."
But if the code has been released is it safe enough?
If I told you yes, what would you do? Take my word for it?
would you compile it and run it on your machine?
I'll say it a little louder for those still confused:But if the code has been released is it safe enough?
Actually, if they can't understand what critical code like this does, they should NOT overclock.
It really is that simple as that.
You don't give a baby a knife
If it was released by the developers after they had tested it and there was no clear warning, I'd assume it was okay
There you go, Just wait for that to happen(Trust me you will know when it happens, it will probably be like the biggest news that week)
I mean if the code was released for people to compile themselves you'd assume that it's at a point where it isn't that dangerous
I mean if the code was released for people to compile themselves you'd assume that it's at a point where it isn't that dangerous
The code has been publicly available for months. There is and never will be a scenario where Overclocking a device beyond its manufacturer chosen power constraints is "risk free." There are no equivocations to be had.
The SoC's stock clock is 1.9 Ghz, yet we run at 1020 mhzWell, thats debatable, Companies usually underclock their devices abit more than they really have to in order to stay on the safe side..
They don't like lawsuits. And if they can say "Hey we can not be held responsible for your Switch overheating because we are meeting all the requirements for this Nvidia chip, in fact we are not even running it at full speed" then they will do that. It's all about keeping their ass out of trouble.
I would argue that overclocking the switch a bit is probably perfectly safe.
How much, I don't know..
Did u ever looked at the dynarec code?
It's months and months of work. Half knowledge? that wont get you far.
Here is a bounty we put up for n64 https://www.bountysource.com/issues/63766562-bounty-write-an-arm64-dynarec
Feel free to create one for PSX too
Well, thats debatable, Companies usually underclock their devices abit more than they really have to in order to stay on the safe side..
They don't like lawsuits. And if they can say "Hey we can not be held responsible for your Switch overheating because we are meeting all the requirements for this Nvidia chip, in fact we are not even running it at full speed" then they will do that. It's all about keeping their ass out of trouble.
I would argue that overclocking the switch a bit is probably perfectly safe.
How much, I don't know..


