Contributor bounties / feature requests

[skmp]

Issues for bounty hunters

Issues that have asked for bounties

BountySource Issues view

BountySource Team View

---

Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.

[skmp]

@twinaphex do you have any links handy?

[inactive123]

Sure thing.

https://www.bountysource.com/issues/43656021-make-libretro-reicast-work-on-arm-ios-android-and-32bit-pc

I'm completely willing to throw more bounty funds behind specific Reicast milestones. Some bounties I can think of that I would be completely OK with throwing some money behind -

• Fog table emulation in the GL renderer. This can be an optional feature, it can even require certain GLES 3 and/or GL3 extensions, as long as it's something that can be toggled on/off.

• An optional order independent transparency codepath for the most accurate transparency handling (can be DX11/GL 4.5-specific, it can be slower, as long as it is optional it doesn't matter to me personally at what performance cost it comes. It would be nice to have an accurate but slow codepath for this)

• Depth buffer solutions - this can still be a pretty big problem right now. Some game still need near/far Z tweaking in order for the depth rendering to appear correctly, and worse, this seems to be GPU-specific. I hear that 'depth peeling' could be a potential solution there?

• Bounties for fixing some of the self modifying code bugs such as the crashes in Shenmue.

• Improved Naomi / Windows CE emulation.

Let me know if any of this is stuff that would be interesting to you and other Reicast members, I can start allocating some funds behind it then. I am sure a lot of users would be willing to throw their weight behind such things too if we created enough coverage for it.

[JoeMatt]

Why is the bounty for 3 different platforms though? I can definitely make it run on iOS (does it need to be jailbreak free?) but wouldn't know to start with the others.

[AbandonedCart]

@JoeMatt That is exactly why it is a bounty, though. The idea is to provide enough motivation to have it fixed for every platform, not just one.

[JoeMatt]

Yeah but who has enough experience in all those disciplines in some of the most niche and difficult aspects of each. CoreAudio alone is a major pain, I've written about 5 commercial core audio based apps and it still gives me nightmares.

[AbandonedCart]

I don't know what to tell you, honestly. It (being a pain) is the same reason I don't bother with it lol

[JoeMatt]

I agree, hate to get the people’s hope up that such an enigma exists though. Maybe set some realistic expectations would be more engaging for the community.

Who knows, maybe there is such a person lurking in the shadows

[inactive123]

You dont have to touch Coreaudio at all in a libretro core, which is what the bounty is for. Honestly, a lot of the codebase doesnt cater to platform specific APIs when making a libretro core.

[blackman91]

I would definitely contribute to a bounty to make cannon spike playable on reicast:
#898

It works on nulldc.

[skmp]

@twinaphex can people submit bounties somehow?

On Thu, 17 May 2018 at 02:46, blackman91 ***@***.***> wrote: I would definitely contribute to a bounty to make cannon spike playable on reicast: #898 <#898> It works on nulldc. — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#1144 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAYAMukh1EdjXBW3rAklJySKE3H_t3jnks5tzLpugaJpZM4TzhXN> .

-- ~skmp

[inactive123]

Sure, I just made one for the Cannon Spike compatibility. I will be asking @hunterk to drop some money into it just to get the ball rolling, hoping for others to chip in too.

Users can create a Github issue here -

https://github.com/libretro/reicast-emulator/issues

I can later attach the bounty label to it then. Users can then go to Bountysource, input the URL of the Github issue, and then attach money to it.

[inactive123]

A question before I start creating bounties and adding some initial seed money -

Since a lot of the visual problems with these games come down to unemulated GPU features, what should be the nature of these bounties?

Enduser-oriented where the main subject is game-specific and trying to basically get it to render correctly which could be part of a much larger problem? This could bring unrealistic expectations with each and every bounty though and a moving target.

Or technically oriented ones, more vague stuff that an enduser would not necessarily understand that are nevertheless approachable and could be managed in bite sized chunks by contributors.

For instance, individual bounties for -

• implement volume shadows
• implement clipping
• implement fog tables
• etc.

Etc. You guys let me know which one you prefer. I could start creating separate bounties then for these individual elements where the GL renderer is currently lacking.

Requirements for these advanced features could be - optional features that require a GL featureset beyond GLES 2.0. Fog table could be implemented through an UBO for instance.

Once it's decided which direction we are going to go in, I'm going to start allocating $50 to a $100 worths on initial seed money on some of these bounties.