Dolphin, the GameCube and Wii emulator - Forums

Full Version: Build Variation and Benchmark
You're currently viewing a stripped down version of our content. View the full version with proper formatting.
Pages: 1 2

mrpj

Thanks for clarification - I was more assuming bricking the device by trying to overclock it ;-).

Mind me also asking - how you control the clockspeed? Any specific adb commands, or do I need a different kernel?

(with my phone I use a custom kernel and fauxclock app - but so far I haven`t found anything about the tegra x1). Would be glad if you could help out
(12-12-2015, 12:36 PM)mrpj Wrote: [ -> ]Thanks for clarification - I was more assuming bricking the device by trying to overclock it ;-).

Mind me also asking - how you control the clockspeed? Any specific adb commands, or do I need a different kernel?

(with my phone I use a custom kernel and fauxclock app - but so far I haven`t found anything about the tegra x1). Would be glad if you could help out

You need root for controlling the CPU speed, I'm sure of that.

A few questions:

Did the emulator hit bottleneck with current hardware?

Is there documentation to this emulator? I'm not a high level programmer (robotics is my profile), but I'd like to learn more about how various chunks of Wii hardware were emulated (and timed) together.
(09-17-2015, 02:52 AM)Sonicadvance1 Wrote: [ -> ]That is a persistent setting that sticks around even after reboot. This enables the Nvidia driver to run on a secondary thread, as similar to what it does in Windows.
Linux/Android this has to be enabled manually since it may cause issues randomly.
Setting the option of high performance mode in the settings isn't enough to force the GPU in to a high performance rendering mode. You've actually got to manually disable GPU clock scaling, otherwise the GPU will only run ~200Mhz instead of its full 1Ghz.

And how exactly do you actually "disable GPU clock scaling"? This information seems quite elusive. I appreciate the help
(09-17-2015, 02:52 AM)Sonicadvance1 Wrote: [ -> ]That is a persistent setting that sticks around even after reboot. This enables the Nvidia driver to run on a secondary thread, as similar to what it does in Windows.
Linux/Android this has to be enabled manually since it may cause issues randomly.
Setting the option of high performance mode in the settings isn't enough to force the GPU in to a high performance rendering mode. You've actually got to manually disable GPU clock scaling, otherwise the GPU will only run ~200Mhz instead of its full 1Ghz.

I came a post where you gave us the setting to disable 3D Scaling on the Tegra K1 but I don't know if they are the same on the X1?
Pages: 1 2