I lowered the resolution within the ini file to 160 x 200, but i can't see an obvious effect, does the ini read resolution directly?
Also the draw distance, would lowering this help at all? I don't mind certain things popping up a little closer than normal.
(01-10-2017, 12:28 AM)dlads Wrote: [ -> ]I lowered the resolution within the ini file to 160 x 200, but i can't see an obvious effect, does the ini read resolution directly?
Are you talking about the FullscreenResolution setting? It doesn't affect the performance, and it doesn't even do anything at all on Android. What matters for performance is that the internal resolution is set to 1x.
(01-10-2017, 12:28 AM)dlads Wrote: [ -> ]Also the draw distance, would lowering this help at all? I don't mind certain things popping up a little closer than normal.
Unlikely. If you want to, try running the game with the Null renderer. If it isn't fast enough then, there's no way that lowering the draw distance will help. If it is fast enough will Null renderer... well, it probably won't prove a lot.
Please just accept that not all hardware is fast enough to run Dolphin well. In case you really want to tweak the software to be as fast as possible, you need to optimize Dolphin's code (likely in the way degasus described), not fiddle around with settings. But it'll likely take some serious effort to make the code significantly faster.
(01-10-2017, 12:55 AM)JosJuice Wrote: [ -> ]If it is fast enough will Null renderer... well, it probably won't prove a lot.
It will give a hint that your GPU drivers are slow. On Nvidia, the null backend is usually up to 30% faster than OGL. But this depends a lot on the game.
(01-10-2017, 12:55 AM)JosJuice Wrote: [ -> ]But it'll likely take some serious effort to make the code significantly faster.
to make the code measurable faster. For a significant speedup, you likely need an expert working on it fulltime for a year.
(01-10-2017, 01:21 AM)degasus Wrote: [ -> ]to make the code measurable faster. For a significant speedup, you likely need an expert working on it fulltime for a year.
True. I should be more careful with which of those words I use in the future
(01-10-2017, 12:55 AM)JosJuice Wrote: [ -> ]Are you talking about the FullscreenResolution setting? It doesn't affect the performance, and it doesn't even do anything at all on Android. What matters for performance is that the internal resolution is set to 1x.
Unlikely. If you want to, try running the game with the Null renderer. If it isn't fast enough then, there's no way that lowering the draw distance will help. If it is fast enough will Null renderer... well, it probably won't prove a lot.
Please just accept that not all hardware is fast enough to run Dolphin well. In case you really want to tweak the software to be as fast as possible, you need to optimize Dolphin's code (likely in the way degasus described), not fiddle around with settings. But it'll likely take some serious effort to make the code significantly faster.
What would 1x signify?
I'll check out null when i'm home, wouldn't that mean that nothing is rendered on screen?? I've seen no difference even when setting it to 160x200
Have managed 20-25 on onset island with what we've done up til now, couple that with a small overclock and it'll be ok, 25 fps is definitely playable, it's quite smooth, 30 would be ideal but it's not the end of the world.
The main problem is the F.fortress and trying to get the same results, once that gets done we should be good unless there's a heavier part of the game, I can't remember there being one though.
(01-10-2017, 02:04 AM)dlads Wrote: [ -> ]What would 1x signify?
It's the option called "1x Native (640x528)" in the Android GUI.
(01-10-2017, 02:04 AM)dlads Wrote: [ -> ]I'll check out null when i'm home, wouldn't that mean that nothing is rendered on screen??
Exactly. It's not useful for actually playing the game, but it can give you some idea about how much of the slowdown is because of the GPU or GPU drivers.
(01-10-2017, 02:04 AM)dlads Wrote: [ -> ]I've seen no difference even when setting it to 160x200
It's not possible to set the internal resolution to that value, and like I said before, the FullscreenResolution setting doesn't affect the performance.
(01-10-2017, 02:08 AM)JosJuice Wrote: [ -> ]It's the option called "1x Native (640x528)" in the Android GUI.
Exactly. It's not useful for actually playing the game, but it can give you some idea about how much of the slowdown is because of the GPU or GPU drivers.
It's not possible to set the internal resolution to that value, and like I said before, the FullscreenResolution setting doesn't affect the performance.
i see that makes sense, i'll give null a whirl, I am fearing that one of the larger cores is closing down, I have a PNP thermal tweak which has been widely used on the HTC 10 which keeps it alive but within the boundaries of whats safe, plus for whatever reason there is a 50fps cap on gaming? It's HTC's way of saying "We still don't know what we're doing" I suppose.
The reason I mentioned resolution was because emulating at over the standard resolution obviously has an impact on performance as in it makes it a lot slower, so i was thinking going the other way would have had the opposite effect, shame
I know that all of these bits n bobs alone may not have an overall effect on the outcome of the fps but maybe all at once they may have a positive impact.
Will test when i finish work in a couple of hours.
Also to the chaps putting things to rest what we have been looking into I really appreciate your input, it's saved us a tonne of time, so thank you.
Also i'm not going to be going mental on the kernel and baking my phone, just wanted to see what was possible then if an overclock was needed, clocking back down until the sweet spot is met.
(01-09-2017, 10:45 AM)Snomelbelak Wrote: [ -> ]Version 5.0-1691
Try backing up your Dolphin.ini config and delete it from the dolphin-emu/config folder then install the latest version from Dolphin android's nightly builds. That's what I did anyways.
It's not DPS it's DSP, sorry was my typo.
It's under [DSP] in Dolphin.ini on the version of 5.0 that I used
Change
Backend = OpenSLES
To
Backend = No Audio Output
My full Dolphin.ini so far (some tweaks could be useless):
Code:
FifoPlayer]
LoopReplay = True
[Analytics]
ID = d3ea8264aaa4cd7fb2fb1d297b295b38
Enabled = False
PermissionAsked = False
[BluetoothPassthrough]
PID = -1
LinkKeys =
Enabled = False
VID = -1
[DSP]
DumpAudio = False
DumpUCode = False
CaptureLog = False
Volume = 100
EnableJIT = True
Backend = OpenSLES
[Interface]
MainWindowHeight = -1
AutoHideCursor = False
ExtendedFPSInfo = False
ThemeName = Clean
LanguageCode =
PauseOnFocusLost = False
OnScreenDisplayMessages = True
ShowToolbar = True
ShowLogWindow = False
ShowLogConfigWindow = False
HideCursor = False
ShowStatusbar = True
DisableTooltips = False
MainWindowWidth = -1
MainWindowPosY = -2147483648
ConfirmStop = True
UsePanicHandlers = True
MainWindowPosX = -2147483648
[Input]
BackgroundInput = False
[GameList]
ListSortSecondary = 0
ColorCompressed = True
ListWad = True
ListSpain = True
ListUnknown = True
ListGermany = True
ColumnFileName = False
ListGC = True
ColumnBanner = True
ListUsa = True
ColumnNotes = True
ListRussia = True
ColumnID = False
ColumnSize = True
ListItaly = True
ListDrives = False
ListWii = True
ListJap = True
ListWorld = True
ListElfDol = True
ColumnRegion = True
ListSort = 3
ListNetherlands = True
ListFrance = True
ColumnPlatform = True
ColumnState = True
ListAustralia = True
ListKorea = True
ListTaiwan = True
ListPal = True
[Core]
SerialPort1 = 255
WiiKeyboard = False
CustomRTCValue = 0x386d4380
SelectedLanguage = 0
AdapterRumble1 = True
SlotA = 1
SlotB = 255
EnableCheats = False
DSPHLE = True
SimulateKonga0 = False
EmulationSpeed = 1.0
AgpCartBPath =
SyncGPU = False
RunCompareClient = False
DPL2Decoder = False
GPUDeterminismMode = auto
OverrideGCLang = False
AdapterRumble3 = True
Fastmem = True
FPRF = False
Overclock = 0.60
CPUThread = True
SIDevice3 = 0
Apploader =
AgpCartAPath =
EnableCustomRTC = False
WiimoteContinuousScanning = False
MemcardBPath = //sdcard/dolphin-emu/GC/MemoryCardB.USA.raw
SimulateKonga2 = False
SyncOnSkipIdle = True
HLE_BS2 = True
Latency = 2
SIDevice0 = 6
OverclockEnable = True
DefaultISO =
GFXBackend = OGL
TimingVariance = 40
SimulateKonga1 = False
AdapterRumble2 = True
PerfMapDir =
BBA_MAC =
SyncGpuMinDistance = -200000
AccurateNaNs = False
RunCompareServer = False
FrameSkip = 0x00000004
SIDevice2 = 0
CPUCore = 4
DVDRoot =
MemcardAPath = //sdcard/dolphin-emu/GC/MemoryCardA.USA.raw
WiiSDCard = False
SimulateKonga3 = False
AdapterRumble0 = True
WiimoteEnableSpeaker = False
SyncGpuMaxDistance = 200000
SyncGpuOverclock = 1.0
SIDevice1 = 0
[Sysconf]
SensorBarSensitivity = 50331648
SpeakerVolume = 88
WiimoteMotor = True
SensorBarPosition = 1
Screensaver = 0
WiiLanguage = 1
AspectRatio = 1
[Display]
ForceNTSCJ = False
KeepWindowOnTop = False
Fullscreen = False
PAL60 = True
DisableScreenSaver = True
RenderWindowAutoSize = False
ProgressiveScan = False
FullscreenResolution = Auto
RenderWindowXPos = -1
RenderToMain = False
RenderWindowWidth = 640
RenderWindowYPos = -1
RenderWindowHeight = 480
[Movie]
ShowInputDisplay = False
Author =
ShowRTC = False
DumpFrames = False
DumpFramesSilent = False
PauseMovie = False
[Network]
SSLDumpWrite = False
SSLVerifyCert = False
SSLDumpPeerCert = False
SSLDumpRead = False
SSLDumpRootCA = False
[Android]
MainDown_0 = Device '72c161e9a8092be90382754281b0c513fbf98afc'-Button 47
DPadDown_0 = Device '72c161e9a8092be90382754281b0c513fbf98afc'-Button 30
InputA_0 = Device '72c161e9a8092be90382754281b0c513fbf98afc'-Button 39
InputX_0 = Device '72c161e9a8092be90382754281b0c513fbf98afc'-Button 40
InputL_0 = Device '72c161e9a8092be90382754281b0c513fbf98afc'-Button 59
CStickLeft_0 = Device '72c161e9a8092be90382754281b0c513fbf98afc'-Button 21
InputStart_0 = Device '72c161e9a8092be90382754281b0c513fbf98afc'-Button 66
MainRight_0 = Device '72c161e9a8092be90382754281b0c513fbf98afc'-Button 32
InputZ_0 = Device '72c161e9a8092be90382754281b0c513fbf98afc'-Button 76
CStickDown_0 = Device '72c161e9a8092be90382754281b0c513fbf98afc'-Button 20
DPadUp_0 = Device '72c161e9a8092be90382754281b0c513fbf98afc'-Button 53
CStickUp_0 = Device '72c161e9a8092be90382754281b0c513fbf98afc'-Button 19
DPadLeft_0 = Device '72c161e9a8092be90382754281b0c513fbf98afc'-Button 35
DPadRight_0 = Device '72c161e9a8092be90382754281b0c513fbf98afc'-Button 36
InputY_0 = Device '72c161e9a8092be90382754281b0c513fbf98afc'-Button 37
InputB_0 = Device '72c161e9a8092be90382754281b0c513fbf98afc'-Button 38
InputR_0 = Device '72c161e9a8092be90382754281b0c513fbf98afc'-Button 74
MainUp_0 = Device '72c161e9a8092be90382754281b0c513fbf98afc'-Button 51
CStickRight_0 = Device '72c161e9a8092be90382754281b0c513fbf98afc'-Button 22
MainLeft_0 = Device '72c161e9a8092be90382754281b0c513fbf98afc'-Button 29
[General]
ShowFrameCount = False
WiiSDCardPath = //sdcard/dolphin-emu/Wii/sd.raw
LastFilename =
RecursiveISOPaths = False
ISOPaths = 0
NANDRootPath =
ShowLag = False
DumpPath =
WirelessMac =
I added to the bottom:
SafeTextureCacheColorSamples = 128
HiresTextures = False
Update:
What I changed manually that helps:
EmulationSpeed = 1.2 (same as Overclock, might as well as boost overclock to 70%, raises fps above 30 causing audio issues)
FrameSkip = 0x00000004
Overclock = 0.60
Tested with no effect:
Backend = No Audio Output
SyncGpuOverclock = 1.5
SafeTextureCacheColorSamples = 128
HiresTextures = False
I'm only using stock marshmellow and it's playable speeds already so we should be able to get a bit more performance out of Wind Waker.
after use this dolphin config. all games have masive fps up for few seconds then back to normal speed like:
dragon ball z budokai tenkiachi 3 wii after apply this config reach 30fps stable for atleast 10seg. then back to 18-21fps
zelda wind waker after apply this config reach 21-22fps for atleast 10seg, then back to 12-14fps
zelda twilight princess in zora domain (very slow part) reach 16fps for atleast 10seg, then back 9fps
also checked cpu freq and thermal and both are ok. I think maybe sound is disabled for few seconds and then back to emulating sound again, that explain the speed up.
if there an way to Completely disable sound emulation would be great for mobile devices. (speed hack)
(01-12-2017, 03:22 AM)nonexist Wrote: [ -> ]if there an way to Completely disable sound emulation would be great for mobile devices. (speed hack)
No, it would be terrible, because the game wouldn't work right at all. The DSP emulation isn't only necessary for correct audio output, it's also necessary for avoiding incorrect behavior on the PPC CPU.
Besides, DSP HLE isn't especially demanding. DSP LLE is a lot worse, but luckily, that's generally unnecessary nowadays.
Another obvious thing you could do (other than freezer) is to tweak CPU override values to a lower ones and to run cpuburn on top of Dolphin (two threads should be enough) to trick DVFS (which doesn't allow CPU to use high frequencies in Dolphin) at least till it starts thermal throttling
SD820, LG G5:
https://youtu.be/wpL9WFt0jd4