Homebrew Official Citra - New 3DS Emulator

  • Thread starter Thread starter bunnei
  • Start date Start date
  • Views Views 3,856,108
  • Replies Replies 7,211
  • Likes Likes 175
Congratulations on taking it this far, that's awesome!
Though as you mentioned, poor citra team will get even more pokemon bugs soon :)
 
  • Like
Reactions: legend80
@Kirtai: The hardware tests we currently have aren't event automated. I wouldn't call it a test suite. Though, you are absolutly right and if you are a developer you can help by working on this (categorizing and refactoring existing tests, so that they can be automated). Merry recently added CATCH to the repo, but we are still lacking test cases for it.

@KillzXGaming: Remember that this is still an inofficial WIP branch. It's not merged yet.

@breel: If you are a developer you should just hop on irc. (I was mainly speaking about what non-devs can help with, but obviously devs are also very important. There are always open tasks).

Also, we'll obviously drop the "no support for Pokemon" once we have a stable base to run Pokemon.
The original "no support for Pokemon" stems from the fact that it's a mix of hacks to make it work in the first place - problems could just be due to incompleteness of certain hacks. Once these features are in master they are considered working (and reviewed). It will be easier to verify issues and bisect stuff, so we can accept bug reports then.
So as soon as CRO is merged and Pokemon is working in master we'll also be able to fix other bugs in Pokemon (and "support" Pokemon in the nightly builds).
 
@breel: If you are a developer you should just hop on irc. (I was mainly speaking about what non-devs can help with, but obviously devs are also very important. There are always open tasks).

Oh I know you were, I just looking at helping with the easier stuff :)
I was in IRC Wednesday for the Qt5.7 issue, I'll come back this week to look for open tasks then.
 
Last edited by breel,
If they merge this "cro++" for example it won't crush on petalburg woods? And in any place before it crashed? Excuse me for my english but i'm italian
 
Given you dislike Open Source, I'm not sure if I should even tell you, that the post you linked *literally* has a link to the source of a workaround (hack = not in master)..

It is not about like or dislike, I just tested 2 games on unofficial build & that was it.
unofficial builds are temporary, sooner or later these will disappear.
 
@Kirtai: The hardware tests we currently have aren't event automated. I wouldn't call it a test suite. Though, you are absolutly right and if you are a developer you can help by working on this (categorizing and refactoring existing tests, so that they can be automated). Merry recently added CATCH to the repo, but we are still lacking test cases for it.
I'm afraid I'm not much of a dev, though I do know a bit about hardware. Though I've noticed that emulators really need two test suites. One set of unit tests to test the emulator itself (using CATCH here) and one to run on the real hardware/emulator (as homebrew) to check behaviour. From looking over the available tests for Citra it seems that only the latter type exists?
 
how easy would it be to port citra to something like this, and how well do you think it would run?
http://www.hardkernel.com/main/products/prdt_info.php?g_code=G143452239825
not easy at all.that is an arm device, and there have not been any progress on the android side to think of a proper ARM port of the emu.also if a port of an emulator is planned for a specific arch, if it was not included in the original plan and started concurrently with the other ports, it will be difficult to port it later. the last gen console to have an android emu was purei, the ps2 emu for X86 and Arm, and before that ppsspp, the psp emu following the same aim.they were planned to be on android from the beginning, so they are quite successful.dolphin is also on android, but that started 2 years ago.dolphin already existed for over 8 years, and the android port start when most code has been polished well that it became easy to port. there have not been any other emulator that was not planned to work on x86 and Arm, but had an android port when it was young that was comparable to the pc port.they all started with android on mind or waited till there code became good enough that they did not need to rewrite a lot of things for the port.
by the way, this is just my opinion.
 
not easy at all.that is an arm device, and there have not been any progress on the android side to think of a proper ARM port of the emu.also if a port of an emulator is planned for a specific arch, if it was not included in the original plan and started concurrently with the other ports, it will be difficult to port it later. the last gen console to have an android emu was purei, the ps2 emu for X86 and Arm, and before that ppsspp, the psp emu following the same aim.they were planned to be on android from the beginning, so they are quite successful.dolphin is also on android, but that started 2 years ago.dolphin already existed for over 8 years, and the android port start when most code has been polished well that it became easy to port. there have not been any other emulator that was not planned to work on x86 and Arm, but had an android port when it was young that was comparable to the pc port.they all started with android on mind or waited till there code became good enough that they did not need to rewrite a lot of things for the port.
by the way, this is just my opinion.
I couldn't be bothered to read that due to lack of punctuation
but from what I have read:
a) when did I say android? I was more thinking of linux
b) code has to be polished well to be easy to port? I thought it was just a case of changing some platform specific code (like I think opengl is different on x86 and arm), and then recompiling it
 
Last edited by Nyap,

Site & Scene News

Popular threads in this forum