[UNOFFICIAL] Ishiiruka-Dolphin Custom Version

[AschAurion]

in MGS:The Twin Snakes theres an issue where the screen flashes pink right before you use the codec, in regular dolphin its fixed by disabling XFB to Texture, I dont see that option in Ishiiruka, any way to fix the screen pink flash issue here?

[PCenthusiasmx58]

Hello any tip to help my friend from Colombia to improve her emulation on ishiiruka dolphin? she is using the last stable version 777, shes is trying to play New Mario bros wii but shes is having audio stuttering

she has a Lenovo Flex 2-14 model:
Specs:

CPU i5 4210u
Integrated Intel® HD Graphics 4400
SSD: 128 GB
OS: Windows 10 pro 64 bits fully updated

I already tried remove all bloatwares from her windows 10, mitigation security patch to speed cpu, meltdown, spectre, graphic tweaks, high event precision timer, and it improve the speed and smooth

But i wanted to know what settings may be great to test in the Emulator, i didn't tweak that much Ishiruka cause i was via Teamviewer helping my friend and actually my internet here in Venezuela sucks

So was wondering what can i do to keep her on good track? like smooth gaming experience no that much audio stuttering? thanks.

[DJBarry004]

While NSMBW is fairly easy to emulate, the ULV processor is likely the culprit here. Don´t expect reasonable performance during long sessions (unless the laptop uses an adequate cooling solution).

[PCenthusiasmx58]

So i'm guessing the ULV processor technology stands for running fast for a short period time because of getting heat? And when that happens the clock speed will drop notorius? uhmm
Well I configured her laptop to be running 99-100% cpu when using electrcity A/C directly. but she don't play that much time too.

but yup it sucks :/ shes running her graphics on the minimal resolution 630 and 0 antialising, anistropic 1, fullscreen, and time treching audio, and some CPu overriding, and is doing 60fps no drops at all.

[DJBarry004]

(04-11-2019, 07:19 AM)PCenthusiasmx58 Wrote: So i'm guessing the ULV processor technology stands for running fast for a short period time because of getting heat?  And when that happens  the clock speed will drop notorius? 

Yep. And to consume as less energy as possible (you know, to keep longer battery life).

Quote:And when that happens  the clock speed will drop notorius? 

That would depend. In this case, maybe. The base clock is 1.7 GHz, and it can TurboBoost to 2.7. The hit might be noticeable in certain cases.

[Tayyo]

(04-11-2019, 07:19 AM)PCenthusiasmx58 Wrote: If you're on Intel, you can use ThrottleStop to reduce throttling effect.

When your CPU hits turbo levels, it revs ups the voltage, in which turn creates more heat.

Say, if you're on a 2.0 ghz base, 2.6 ghz turbo clock cpu, you can limit that to 2.0, 2.1 or anything between to see if your CPU hits heat limits. You can also change the temp throttling limit but I would advise against it.

[Plavil]

Hi! Big thanks for your hard work, with your help we spent a lot of fun time with niece, playing with higher fps/ less lags.
Can you update your build, using new master backend changes for even more smooth ride?

[Tino]

(04-17-2019, 07:40 AM)Plavil Wrote: Hi! Big thanks for your hard work, with your help we spent a lot of fun time with niece, playing with higher fps/ less lags.
Can you update your build, using new master backend changes for even more smooth ride?

will try but it will take some time

[Tayyo]

Hello Tino, is there a problem with Vulkan/OGL with shaders? D3Dx shaders work fine.

I'm getting an error showing dump.bad ps.txt or something on Windows 10 19H1 + Nivida 430 drivers.

The usual toxic etc shaders work but advanced ones like Ishiiruka don't on OGL/Vulkan.

[Tino]

(04-19-2019, 07:44 PM)Tayyo Wrote: Hello Tino, is there a problem with Vulkan/OGL with shaders? D3Dx shaders work fine.

I'm getting an error showing dump.bad ps.txt or something on Windows 10 19H1 + Nivida 430 drivers.

The usual toxic etc shaders work but advanced ones like Ishiiruka don't on OGL/Vulkan.

can you share your dump file to debug the error?