Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Bounty] Create a pcsx2 core #6867

Open
kenshen112 opened this issue Jun 6, 2018 · 12 comments

Comments

Projects
None yet
7 participants
@kenshen112
Copy link

commented Jun 6, 2018

What would be required?
rewrite PCSX2's plugin system to fit into Retroarch's core system
adjust config files and pcsx2 settings to work with Retroarch
adjust GUI config areas in pcsx2 to fit with Retroarch's quick menu

Note: Play! though not preferred would be an acceptable alt if someone wants to do that,

@i30817

This comment has been minimized.

Copy link
Contributor

commented Jun 7, 2018

I think it's far more likely that dobiestation or some other emulator gets a port than pcsx2. It would be a incredible burden to port and redesign the plugin system to retroarch and you wouldn't have the benefit of getting upstream commits. It would be the hardest of hard forks.

Granted dobiestation is a toy emulator, being a one man show, but i still consider it more likely. Maybe i'm exaggerating, mupen has a retroarch port and it's plugin based. Not sure though.

@kenshen112

This comment has been minimized.

Copy link
Author

commented Jun 7, 2018

@i30817 Actually dobiestation has several contributers at this point, and whilst yes it would be a chore and a half i still think pcsx2 would be our best bet for now to get a compatible working ps2 core in RetroArch aside from play! or in the future DobieStation

@i30817

This comment has been minimized.

Copy link
Contributor

commented Jun 7, 2018

Uh, interesting that refraction is contributing commits to dobiestation. One ps2 emulator was not enough.

@anothername99

This comment has been minimized.

Copy link

commented Jun 7, 2018

Perhaps look into Orbum:
https://github.com/marco9999/orbum

It's a rewrite of PCSX2. It should be more portable than mainline PCSX2.

Also, a hardware renderer is more of a nice thing to have than something actually necessary. PCSX2's software renderer provides perfectly playable speeds in most games and it's the most accurate option.

@orbea

This comment has been minimized.

Copy link
Collaborator

commented Jun 7, 2018

I think step 1 is to fix the 64-bit build upstream and make sure -fPIC is entirely supported.

@twinaphex twinaphex added the bounty label Oct 17, 2018

@orbea orbea referenced this issue Jan 12, 2019

Closed

Pcsx2 core #7993

@orbea orbea added the core issue label Jan 12, 2019

@natehaxx

This comment has been minimized.

Copy link

commented May 18, 2019

I think step 1 is to fix the 64-bit build upstream and make sure -fPIC is entirely supported.

its already fixed on the newest Play Forks ... Emulation runs now on the Nintendo Switch slow but it runs

@Zer0xFF

This comment has been minimized.

Copy link

commented May 30, 2019

I am considering looking into this bounty, however for Play!.

however, I want to confirm the validity of this, as the paragraph for Play! isn't encouraging.

Note: Play! though not preferred would be an acceptable alt if someone wants to do that,
@Zer0xFF

This comment has been minimized.

Copy link

commented Jun 1, 2019

@twinaphex thanks for the reply, but it didn't really address my question, the issue was original opened for PCSX2, but then Play! was added as an acceptable alternative, though the wording for that is somewhat discouraging, so I want to confirm if a core for Play! will indeed be accepted for the bounty? (as I believe the issue has to be closed for the bounty to be processed?)

as for your comments.

  • the code will be pushed out
    • and no CLA is in place at the moment (while I don't foresee a CLA in the future, (1) its does not apply retroactive, (2) so my work regarding the core remains true, (3) should Jean (emu owner) does purse it, its his choice, but I don't see it having a bearing on this bounty as per point (1) and taking that into account, this could apply to ALL current cores, so not really my issue in the future) ()
  • in the case of Play! license is MIT, and since there is no CLA in place, relicensing isn't a choice I even have (nor will I be able to obtain since I'm not the project owner XD)
@twinaphex

This comment has been minimized.

Copy link
Member

commented Jun 1, 2019

Hi @Zer0xFF, sorry for maybe confusing you. This was not related to Play!, more to somebody else who offered to fulfill this PCSX2 core bounty.

I'd also like to see a Play! core bounty, but ultimately the bounty backers decide. A vote could be done. Personally I'd still think it's best that Play! gets its own separate bounty, since I think we'd like to see both, but it's of course unreasonable to have that be part of the same bounty. But like I said, we can let bounty backers decide.

@Zer0xFF

This comment has been minimized.

Copy link

commented Jun 1, 2019

Thanks for the reply.

Well I presume, they only way backers can decide is after the bounty is fulfilled?
in such case, I'm afraid, I will not be taking this on, since my main reason for doing this is the financial compensation, if this can be done ahead of time that'd be great.

@twinaphex

This comment has been minimized.

Copy link
Member

commented Jun 1, 2019

I believe it might be best if we built up a separate core bounty for Play! and we bring that to the level of $300 and then make that grow from there. To reiterate, I'd like to see both get a libretro core, but I understand that can't be done with one single bounty.

@Zer0xFF

This comment has been minimized.

Copy link

commented Jun 1, 2019

I believe it might be best if we built up a separate core bounty for Play!

I agree, and I've foreseen the inevitable confusion in this case, which is why I decided to ask 1st.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.