Hyllian, we all want more from you. And Tino. And the whole motley crew that call themselves Dolphin developers/contributors.
But seriously, and I don't mean to put words in anyones mouth but we do appreciate the effort you (and Tino/Devs too) spend during valuable "free time" and most importantly the willingness to share the fruits of this effort. Even if some of us don't express it plainly. In my line of work (Land Surveying) you can tell how much someone appreciates ones effort because they will be more critical of said effort because they care.
That said, you say shader development?
Can't wait till Christmas/Festivus to see what it is
Since I'm thinking of it, what kind of performance hit does one these have amongst another? I mean, you know exactly how each works so could you take a ballpark guesstimate based on their function on whether or not if one is noticeably faster or slower than another?
I've got a very beefy machine, but if you could provide this relative performance question it could help those with less powerful computers.
I just check myself, since everyone's different hardware combinations will behave differently, but I'm sure you know there are some people who just can't be bothered to check themselves (and fewer that even know how to compare them without direction--no offense).
*EDIT*
It's a pain in buttocks to easily compare the shaders due to what I tried to describe earlier about shaders locking themselves and crap.
If I'm using the "xbr-lvl2" resize shader and change to--for example lets say "super_xbr", it looks exactly the same.
Since they look the same I now change from "super_xbr" to "crt-hyllian". Well now I don't see the scanlines, but something something changes (very slight difference in alpha textures like leaves way off in the distance).
To look at the changes again, I now go from "crt-hyllian" back to "xbr-lvl2". Now there is scanlines!
I says to myself: "Self, wtf?" and change to (default)/passthrough/nearest-neighbor. Well hell, now I'm confuzzled because I know (default)/passthrough/nearest-neighbor does NOT look like that.
Note: I'm not saying Hyllian's shaders are screwed, but something is happening with Ishiiruka 568 (and earlier if this experience is the same I tried to describe a few posts ago) that makes changing shader settings a tedious process because you need to completely close and restart the game to see current settings' results (i.e. restart the rendering thread(s).
But seriously, and I don't mean to put words in anyones mouth but we do appreciate the effort you (and Tino/Devs too) spend during valuable "free time" and most importantly the willingness to share the fruits of this effort. Even if some of us don't express it plainly. In my line of work (Land Surveying) you can tell how much someone appreciates ones effort because they will be more critical of said effort because they care.
That said, you say shader development?
Can't wait till Christmas/Festivus to see what it is
Since I'm thinking of it, what kind of performance hit does one these have amongst another? I mean, you know exactly how each works so could you take a ballpark guesstimate based on their function on whether or not if one is noticeably faster or slower than another?
I've got a very beefy machine, but if you could provide this relative performance question it could help those with less powerful computers.
I just check myself, since everyone's different hardware combinations will behave differently, but I'm sure you know there are some people who just can't be bothered to check themselves (and fewer that even know how to compare them without direction--no offense).
*EDIT*
It's a pain in buttocks to easily compare the shaders due to what I tried to describe earlier about shaders locking themselves and crap.
If I'm using the "xbr-lvl2" resize shader and change to--for example lets say "super_xbr", it looks exactly the same.
Since they look the same I now change from "super_xbr" to "crt-hyllian". Well now I don't see the scanlines, but something something changes (very slight difference in alpha textures like leaves way off in the distance).
To look at the changes again, I now go from "crt-hyllian" back to "xbr-lvl2". Now there is scanlines!
I says to myself: "Self, wtf?" and change to (default)/passthrough/nearest-neighbor. Well hell, now I'm confuzzled because I know (default)/passthrough/nearest-neighbor does NOT look like that.
Note: I'm not saying Hyllian's shaders are screwed, but something is happening with Ishiiruka 568 (and earlier if this experience is the same I tried to describe a few posts ago) that makes changing shader settings a tedious process because you need to completely close and restart the game to see current settings' results (i.e. restart the rendering thread(s).
what do you think about local contrast enhancement? (there an explenation 