most of the issues introduced by my latest commit should be fixed now. download link updated in the main post
Thread Rating:
|
[UNOFFICIAL] Ishiiruka-Dolphin Custom Version
|
|
So i have some question:
I noticed that dx9 in this version is more fast than the dx9 in 4.0.2, its is because of the revision outdated or is really and improvement you made? Metroid snow area: get 52 fps in 4.0.2 get 64 fps in this build Zelda Hyrule field: 28 fps 4.0.2 33 fps this build Mario kart Double Dash 130-150 fps 4.0.2 40-50 fps this build Another thing this dx9 version was a little bit stutter than 4.0.2, one thing i need to know, the stuttering issues is related only to sound backend? and there is any way to record the fps or lag ingame to run a more solid test? Issue i found: Metroid Prime: In metroid prime samus randonly and rarely turn darker or black some times. but only some parts of the body and then turn to normal again. I will try to take a screenshot next time.
OS: Windows 7 Ultimate, 64-Bits
CPU: Intel Core I5-4670 @ 3.4 Ghz GPU: SAPPHIRE AMD HD 7770 GHz Edition OC 1GB GDDR5 VAPOR-X RAM: Kingston 4GB DDR3-1333 DOLPHIN: 4.0.2 x64 04-24-2014, 06:39 PM
(04-22-2014, 11:31 AM)Hyorus Wrote: I fixed it, so the only game i have right now for testing is the zelda tp for wii, i will get the others in the list and test it. Hm, the super-strong bloom-offset in ZTP seems to be gone (with DX11) but there still is an issue with bloom. Here is an old picture of mine that shows it pretty well (though I don't know if it would still be this bad in recent Dolphin versions): http://img577.imageshack.us/img577/7093/ro3exj1.png
Intel i5-4690k (Devil's Canyon) @ 3.5 GHz (+Scythe Mugen) / Gainward GTX 1070 Phoenix (OC'd) / ASUS Z97 PRO GAMER / 16GB G.Skill DDR3-2400 CL10 TridentX / X-Fi XtremeMusic / Win10 Pro 64bit / Dell S2716DG Monitor / 3x original WiiMote+MotionPlus+Nunchuk
04-24-2014, 07:25 PM
I think the bloom offset is priority since it is displayed wrongly on the screen, the high amount of bloom is a resolution scale problem, i dont know if it can be fixed with a filter or something.
OS: Windows 7 Ultimate, 64-Bits
CPU: Intel Core I5-4670 @ 3.4 Ghz GPU: SAPPHIRE AMD HD 7770 GHz Edition OC 1GB GDDR5 VAPOR-X RAM: Kingston 4GB DDR3-1333 DOLPHIN: 4.0.2 x64 04-24-2014, 08:24 PM
@ Tino: Did your last version change something in the cache? I'm suddenly having some strong hiccups. However, it might just be because after every new version the game seems to need to cache stuff that it sees for the first time, so I can't say for sure if something actually got worse.
Intel i5-4690k (Devil's Canyon) @ 3.5 GHz (+Scythe Mugen) / Gainward GTX 1070 Phoenix (OC'd) / ASUS Z97 PRO GAMER / 16GB G.Skill DDR3-2400 CL10 TridentX / X-Fi XtremeMusic / Win10 Pro 64bit / Dell S2716DG Monitor / 3x original WiiMote+MotionPlus+Nunchuk
Fixed the stuttering partly, i remenber that the game ini force some games that i was having some problems to use efb copy to ram, changing to texture fixed 90% at least on metroid prime, and i manage to get 43 fps on hyrule field in last dx9 build, i think devs should give info about the configs and not force it, its up to us to use or not, anyway i will keep using normal game.ini since it is for debug purposes.
But slowdowns on mario kart double dash stills, since game.ini dont use any special configuration.
OS: Windows 7 Ultimate, 64-Bits
CPU: Intel Core I5-4670 @ 3.4 Ghz GPU: SAPPHIRE AMD HD 7770 GHz Edition OC 1GB GDDR5 VAPOR-X RAM: Kingston 4GB DDR3-1333 DOLPHIN: 4.0.2 x64 04-24-2014, 09:50 PM
Oh yes, because having tons of people complaining how the game doesn't work at all (Metroid Prime, for instance, has half the visors not working in EFB2Texture) is a much better solution than just letting the users edit default settings. You do realize you can change the inis, right? Or would you rather they weren't included, so you could deal with all the issues on your own? Imagine starting a game, it crashing, so then you have to go to the wiki and figure out what settings are needed, and then set them every time you want to play that game because they weren't included.
More seriously though, I think your suggestion would cause a lot more problems than solutions. 04-24-2014, 10:33 PM
StripTheSoul: every new version clears the shader cache so is normal to have stuter after a new release. i will change that to the old way, and only clear the cache when something is changed in the shader generators to avoid this problem
(04-24-2014, 09:50 PM)JMC47 Wrote: Oh yes, because having tons of people complaining how the game doesn't work at all (Metroid Prime, for instance, has half the visors not working in EFB2Texture) is a much better solution than just letting the users edit default settings. You do realize you can change the inis, right? Or would you rather they weren't included, so you could deal with all the issues on your own? Imagine starting a game, it crashing, so then you have to go to the wiki and figure out what settings are needed, and then set them every time you want to play that game because they weren't included. I understand. So what issues are left anyway?Because issue list need an update.
OS: Windows 7 Ultimate, 64-Bits
CPU: Intel Core I5-4670 @ 3.4 Ghz GPU: SAPPHIRE AMD HD 7770 GHz Edition OC 1GB GDDR5 VAPOR-X RAM: Kingston 4GB DDR3-1333 DOLPHIN: 4.0.2 x64 04-25-2014, 06:23 AM
lets start clean, any issue you see in the current version please postit so i can add it to my issue tracker
|
|
« Next Oldest | Next Newest »
|
Users browsing this thread: 3 Guest(s)


![[Image: yzkbcne8.png]](http://s14.directupload.net/images/140422/temp/yzkbcne8.png)
![[Image: gewp7m5w.png]](http://s1.directupload.net/images/140422/temp/gewp7m5w.png)
![[Image: luyulg6k.png]](http://s1.directupload.net/images/140422/temp/luyulg6k.png)
![[Image: tv98s33w.png]](http://s1.directupload.net/images/140422/temp/tv98s33w.png)
