Artifacting in certain games

**admin89** · (This post was last modified: 05-13-2016, 02:16 AM by admin89.)

Good thing that I did not wipe out my user\download folder for more space .
I still have the Ishiiruka.637 Dx9 build (661 is the latest atm)
So here if anyone need it (I don't Big Grin

)

Spoiler: (Show Spoiler)

Edit : Jumped to conclusions too soon ...

Aaronius Leonius · 05-13-2016, 03:20 AM **#12**

I found TurboK's unofficial build on GitHub. I did read the forum rules and it said I can only link custom builds if they solve an issue that other builds don't but I will still wait to post it. Someone let me know if I am allowed to in this case but it works and it ran faster for me. It might be that the artifacting was causing lag because I think artifacts are rendering issues and it may have been falling behind because of that. did also try the Ishiiruka Dolphin last night because it still had Direct3D9 support even though I prefer Direct3D11 because of its speed, and Direct3D9 is slow. The artifacts still were there on that build so I just decided to go to bed because I knew I would be refreshed in the morning. If I am allowed to link to the github page with the unofficial build that worked, please let me know. I know a bunch of the views this thread got were from people with the same problem and I want them to get what they came for.

TurboK · 05-13-2016, 04:29 AM **#13**

Good to hear that you got better performance with the "custom" build!
You're right about the line "it can specifically solve an issue that the official builds cannot", this does exactly that, and there is nothing wrong in helping other people with the same problem. The best way is to tell them how to fix it themselves (by compiling Dolphin on their own), and the second best is to provide the build.
I don't know why I wanted to point out the "custom build"-rule in this case, anyway. You're free to link to github about the fix, of course.
Maybe if you or someone else wanted to keep the Intel HD 4000-branch more visible he/she should create a thread in the Development section of the forums and provide the builds (and the link to the source) there.

Aaronius Leonius · 05-13-2016, 07:26 AM **#14**

Anyone else who is having this problem should compile this unnoficial version from GitHub. Use visual studio 2013 because the latest version doesn't have some of the older libraries that it relies on. Also, since you are compiling the source, you can change it however you want. That is how this version was made. You could in theory compile it on Mac/Linux but I don't know why you would need to because this issue doesn't exist on Mac/Linux.