Yo, that SMG issue isn't going to get sorted out anytime soon unless someone bothers to find out which revision specifically caused the issue. The devs generally don't do any testing like this, so one of our end users will likely have to take care of it. Since end users generally don't bother about any but their own problems, it's probably you who'll have to do the boring work, slax65
Chances are it's like it looks on real hardware, anyway.
The pixel depth field in your config isn't an read by dolphin anymore, you might as well just remove it because it has no effect.
(05-05-2013, 04:45 AM)neobrain Wrote: [ -> ].. it's probably you who'll have to do the boring work, slax65 Chances are it's like it looks on real hardware, anyway.
I will find the revision, trust me that!
Why isn't PixelDepht supported anymore .. That's bad ..
It's r6777 that caused this issue
(05-05-2013, 07:43 PM)neobrain Wrote: [ -> ]Could you file an issue report on our google code page then, please? Make sure to properly fill out the issue template etc. Also, please include a link to a 2-frame fifo log showing the issue.
http://wiki.dolphin-emu.org/index.php?title=FifoPlayer
Do you mean this site for reporting the issue?
http://code.google.com/p/dolphin-emu/issues/list
And I don't actually understand how that whole Fifo-Player log thing is suppose to work ..
Isn't it enough to post that picture I made?
I mean this color gradient issue can be seen in any game, not just Mario Party 9; especially with dark colors ..
Yes, I mean that site for reporting the issue.
Did you read the "How to record a fifo log?" section of the wiki page that I linked to? Is there anything specifically that is unclear to you? When writing that wiki page I tried to make it as straightforward as possible, but maybe I'm missing something.
Having a fifo log available saves me a really good chunk of work on my side. In fact, screenshots are pretty much useless compared to fifo logs*. I can verify your issue report within less than a minute and debug it more efficiently when I have a fifo log at hand. I usually don't bother checking any issues without fifo logs because it'd be a huge waste of time in most cases otherwise. If you don't believe me, take a look at
http://code.google.com/p/dolphin-emu/issues/detail?id=6080 . I pushed a fix for that issue to the source tree within 10 minutes after I got a fifo log. While I own the game, I don't have it dumped currently, so just verifying this issue would've taken me several hours!
* I usually ask people to provide a reference screenshot anyway for various reasons.
(05-06-2013, 12:14 AM)neobrain Wrote: [ -> ]Yes, I mean that site for reporting the issue.
Did you read the "How to record a fifo log?" section of the wiki page that I linked to? Is there anything specifically that is unclear to you? When writing that wiki page I tried to make it as straightforward as possible, but maybe I'm missing something.
Having a fifo log available saves me a really good chunk of work on my side. In fact, screenshots are pretty much useless compared to fifo logs*. I can verify your issue report within less than a minute and debug it more efficiently when I have a fifo log at hand. I usually don't bother checking any issues without fifo logs because it'd be a huge waste of time in most cases otherwise. If you don't believe me, take a look at http://code.google.com/p/dolphin-emu/issues/detail?id=6080 . I pushed a fix for that issue to the source tree within 10 minutes after I got a fifo log. While I own the game, I don't have it dumped currently, so just verifying this issue would've taken me several hours!
* I usually ask people to provide a reference screenshot anyway for various reasons.
Well but this is an issue, that is everywhere, anytime and in any game, not at specific parts .. Or should I just record this part of Mario Party 9 which is on the picture of me with that Fifo Player, one time with r7666 (where the issue occurs) and then with the previous revision (where it's fine)?
Anyway, if I start reporting issues, you'll get some more work to do in future ;P
Just record that part of Mario Party 9 that you showed in this screenshot:
http://img833.imageshack.us/img833/4601/mustergg.jpg
Record it with the latest development build available (no need to record it multiple times with different builds) and make sure to follow the instructions on the wiki closely. In particular this includes (but isn't limited to) disabling XFB and using efb copies to texture.
(05-06-2013, 03:18 AM)slax65 Wrote: [ -> ]Anyway, if I start reporting issues, you'll get some more work to do in future ;P
I'm more than fine with that as long as the reports are of good quality. Take a (close!) look at the issue reports by JMC and MaJoR, for example. Well done issue report = higher chance of getting stuff fixed.