jojo, jojoba and clones: Missing 2P combo meter graphics.

[ghost]

Greetings:

The 2P side of the combo meter is never showed. It happen on any system, on any version of MAME since the CPS3 implementation, and in any way you try it, so I think it's an emulation bug. You can see here the comparison of the same attack on both sides:

http://i.imgur.com/VPQBdRX.png

As you can see, the combo meter on 2P side is missing.

I have try other CPS3 emulators and it happen always. On the original arcade this error is not showed.

You can check this tournament for example:

https://www.youtube.com/watch?v=q4e15P_hAOA

Another video with the cabinet:

https://www.youtube.com/watch?v=obglKCXwcUU

Other video where you can even see the PCB:

https://www.youtube.com/watch?v=oGwybo2U9gk

[Osso13]

Hi, I assume it's you that already reported it to MAMETesters: https://mametesters.org/view.php?id=6157, so this issue isn't really needed.
That said, keep in mind that the game is flagged as MACHINE_IMPERFECT_GRAPHICS, inaccuracies are to be expected.

[Tafoid]

Adding redundant issues to the Git system for bugs already acknowledged on MAMETESTERS (as linked above) is a waste of resources.
Closing.

[happppp]

It's attached to bountysource: https://www.bountysource.com/issues/63928588-jojo-jojoba-and-clones-missing-2p-combo-meter-graphics

[ghost]

The point was that I wanted to post it on bountysource, but it required a GitHub link, so I open it here. Can you please reopen this issue? Because it now appear like closed on Bountysource and that's wrong.

Thank you.

[Robbbert]

Looks like it won't need to be open for long, as good things are happening.

[ghost]

I have resolved this in #4035

[cuavas]

I'd really rather avoid BountySource altogether. The bounties are tiny compared to actual pay scales for skilled developers. Consider that the contract rate for a good C++ developer is at least $120/hour. A $60 bounty pays for a developer for a maximum of half an hour, not including piecework loading. As soon as you put money on the table, it completely changes the dynamic. If people want to go down the path of offering financial rewards for MAME functionality, they need to consider what developers' time is worth.

Also, as @Tafoid mentioned, duplicating bugs from MAME Testers is wasteful. The GitHub issues system is very lacking in functionality. It doesn't support components, custom fields, etc. It's not a viable replacement for MAME Testers.

[MooglyGuy]

Meanwhile, 60 bucks is going towards either the DU or EdHunter's dumping efforts. You're more than welcome to turn up your nose at free cash for something you would have done anyway, Vas, but in the meantime, if someone wants to throw some cash into a pot in an attempt to get a bug fixed, they're more than welcome to. If it's not a sufficiently large amount to balance out a lack of developer interest, then nobody will pick up the bounty: The free market at work.

In this case, it's a bug that Haze or I would have been more than happy to look into even without the bounty, so who are you to tell us what the going rate should be for our time?

[MooglyGuy]

And, for that matter, let's be real here: $120 is the going hourly rate for a skilled C++ developer? Great, then, because I probably spent all of 10 minutes isolating the issue before Haze started looking at it, and I would wager that it took him less than half an hour if you deduct the time spent throwing ideas around in the Shoutbox. So $60 was exactly the correct amount.

[Robbbert]

I'd wager that an unemployed person would think $60 is much better than nothing at all. Anyway, I assume that Haze has received his renumeration, so this can once again be closed.

[rb6502]

We want to avoid even the remote appearance of being one of those for-profit Patreon shitshows like RetroArch is turning into, so be very very careful about this stuff in the future.

Also, please keep Caps0ff in mind as a destination for random downfalls of cash.