@JayFoxRox , so far how is the progression of Hardware Renderer's branch ? You are doing that part right?
@JayFoxRox , so far how is the progression of Hardware Renderer's branch ? You are doing that part right?
Does anybody know, how to create the nand structure (https://github.com/citra-emu/citra/wiki/Home-Folder) without a nand dump?
I have a 3DS, but I don't own a flashcard, to dump the files.
Is there any possibility to reconstruct the nand system. For example with NUS.
I have a 3DS, but I don't own a flashcard, to dump the files.
Is there any possibility to reconstruct the nand system. For example with NUS.
Hi, would anyone be able to point me in the direction of getting Pokemon X or Y running in Citra? I tried some stuff from a few months ago but Im getting stuck after making a name at a black screen. I know I was supposed to use a save file to get past this and supposedly had the files, but Citra simply stopped doing anything at the black screen, even in the command prompt.
If there's a better thread/area for this please direct me :]. Thank you in advance~
If there's a better thread/area for this please direct me :]. Thank you in advance~
currently Pokemon X & Y does not work on the latest official build so no but you can always take a look here https://gbatemp.net/threads/citra-unofficial-chinese-builds-discussion.431974/
OR use the existing thread where this non-official build is already being discussed?
Also your YouTube vid contains link to a GPL violation which you should remove. Complain to gdmk directly about violating the GPL and illegaly sharing roms on their baidu account. The Citra community shouldn't condone GPL violations and piracy or it will hurt Citra in the end.
The hardware renderer isn't a branch - it's a feature in master.
And no, I'm not. I'm mostly concerned with the reference renderer (which is the software rasterizer).
However, I didn't like how my code was being reviewed lately so I pause contributing code at the moment (I'll still moderate the Citra forums, maintain the compatibility list and occasionally review stuff etc.).
Also I felt that the community is lacking: just too many GPL violations, people only caring about Pokemon and performance hacks (but not actual emulation of the system, which is important for its preservation).
- I also worked on geometry shaders which yuriks might take over now. Maybe it simply won't be merged now though.
No.
Also your YouTube vid contains link to a GPL violation which you should remove. Complain to gdmk directly about violating the GPL and illegaly sharing roms on their baidu account. The Citra community shouldn't condone GPL violations and piracy or it will hurt Citra in the end.
The hardware renderer isn't a branch - it's a feature in master.
And no, I'm not. I'm mostly concerned with the reference renderer (which is the software rasterizer).
However, I didn't like how my code was being reviewed lately so I pause contributing code at the moment (I'll still moderate the Citra forums, maintain the compatibility list and occasionally review stuff etc.).
Also I felt that the community is lacking: just too many GPL violations, people only caring about Pokemon and performance hacks (but not actual emulation of the system, which is important for its preservation).
- I also worked on geometry shaders which yuriks might take over now. Maybe it simply won't be merged now though.
No.
Last edited by JayFoxRox,
This thread is for official build! ask for pokemon advice here : https://gbatemp.net/threads/citra-unofficial-chinese-builds-discussion.431974/
Last edited by raulpica,
, Reason: Removed quote -rp
@JayFoxRox I'm sad you decided that. but I can understand your mind, the thread is filled full of pokemon. and thank you.
by the way I have question, When I play super mario 3d land, it have graphical glitch, I think it appeared after geometry shader merged to unofficial build. Now, official build have this issue. Do you know why?
by the way I have question, When I play super mario 3d land, it have graphical glitch, I think it appeared after geometry shader merged to unofficial build. Now, official build have this issue. Do you know why?
That's bad. Especially considering the emulation, the firmware or at least the core file structure is an essential part of the emulated system.
Compared to other older systems, the emulation of newer hardware consoles have to consider the software stack as well to run properly.
This makes the emulation more complex.
Looking into NUS, all title files can be downloaded. Nevertheless the version is most likely not the correct one and must be defined to run Citra the correct way.
Means only two files (data/config and shared_font) are missing.
The data/config is already created by Citra. So the file itself is not 100% compatible with all games.
shared_front is therefore the only missing file, which is not handled in any way. A possible approach would be to create a generic font file according to a reverse engineered font table.
Last edited by papermanzero,
We were (and are) looking into generating a shared_font on the fly or in advance. However we'll have to write our own tools probably because the tools available don't work properly.
And it's too much stupid work for the long-time Citra contributors who know the codebase inside out to work on something that's mostly external code.
There are also more important issues at hand (missing features / performance).
We don't really expect anyone to actually play games uing Citra yet. We also expect anybody to be able to dump their shared_font currently as Citra is still aiming at a technical audience.
If you want to fix the shared-font situation (if you can code) you should hop on #citra / #citra dev (freenode) and offer help.
@clockymood: The Pokemon stuff was annoying but the review style was the nail in the coffin. But hey.. at least review policys are being discussed now.
Mario 3D Land doesn't use geometry shaders and they aren't merged either. The problem is most likely this one (and it exists for some months now, it was only masked before too).
If it's not that issue (particle effects broken), provide screenshots [of nightly build + commit id] (If it's an issue we don't know yet you should bisect it and create an issue on github)
And it's too much stupid work for the long-time Citra contributors who know the codebase inside out to work on something that's mostly external code.
There are also more important issues at hand (missing features / performance).
We don't really expect anyone to actually play games uing Citra yet. We also expect anybody to be able to dump their shared_font currently as Citra is still aiming at a technical audience.
If you want to fix the shared-font situation (if you can code) you should hop on #citra / #citra dev (freenode) and offer help.
@clockymood: The Pokemon stuff was annoying but the review style was the nail in the coffin. But hey.. at least review policys are being discussed now.
Mario 3D Land doesn't use geometry shaders and they aren't merged either. The problem is most likely this one (and it exists for some months now, it was only masked before too).
If it's not that issue (particle effects broken), provide screenshots [of nightly build + commit id] (If it's an issue we don't know yet you should bisect it and create an issue on github)
My friend, you do a great job! unfortunately people do not always do right . but it is not because there is evil that good will cease to exist . Thanks for the great emulator CITRA today . I hope you continue the great work and that in the future I can play Luigi is mansion 2. I'm not working now but as soon as possible will help with the project . Do not be discouraged . always forward. Thank you
@JayFoxRox , Lots of people are testing and not reporting, why don't you make a reporting guide for github on the Citra site, that includes the games you want to test, PRs etc, i think it would be helpful.
I see. It is in general hard to decide on which component to focus, because the software and hardware are working close together in the 3ds (as a system). Currently the emulator status is awesome and interessting to follow. Especially the approach to choose an available arm emulator was interessting, although this emulator had no optimisations and dynamic recompiler functions (which is now the biggest obstacle).
That citra is not in the state to play games should be obvious, although many cries about why this and that game is not working. For homebrew it would be great as well, but also here some essential parts of the system are missing in the emulation.
I would like to support but i don't have time left.
But maybe as recommendation. You could run very simple homebrew apps on the 3ds and on citra to compare the results of certain functions. But i guess you are already doing that. :-)
(Take what I say with a grain of salt please, personal opinion incoming. Not intending to offend anyone, but probably will)
Because it takes a lot of work to write these documents. As Leo just pointed out we already have some of those but people don't care.
Also average joe is not a good "Tester": The quality of bug reports is usually horrible with inexperienced (non-developer) users.
flamesage has been working on some compatibility testing feedback functionality (on the websites server) so you can report compatibility from within Citra.
However, I'm not sure who is going to write the code for the emulator to talk to said website. He contacted me but I still see some unresolved issues.
For the time being the unofficial compatibility lists are the best we have and you should contribute to that.
Unless you know what you are doing / reporting you shouldn't report crashes / compatibility issues on github (which is a tool for developers, not users; and it's certainly not a forum).
The amount of bad reports we get on github is insane (also note that I stopped adding the invalid tag lately and some other maintainers don't use it - for whatever reasons; we also get a ton of bad reports / questions on the forums). Moderations for these bad reports takes hours per week (which would otherwise be spend developing and doing proper bug reports).
Most of these issues are not issues in Citra and we'll be able to solve them with a proper release (with a version number) which would probably include some installer.
However, nightly builds are just that: nightly builds; not clean releases.
People should not expect support getting these to work. And they should at least google their issue or search the issue on the forum first.
So if you want to free the developers from wasting time you can also start moderating the forums (either the official forums, speaking up on reddit and here). However, you'll probably want to get on IRC for that so you can ask for the proper answer unless you know something for certain.
Similarily, I shouldn't have to explain the GPL here (which users agreed to when accessing Citra builds / source), but you must have noticed how long the discussion about it became.
- This takes up a contributors time despite being common sense.
So even if you can't code, you can still support Citra by trying to inform people about Citra (but making it clear that it's not a finished product = no support and certainly no Pokemon), not using piracy (and informing users that it hurts Citra), reminding them of the GPL (which will bring in more devs + avoid legal issues) etc.
We already do this.
That's how you write an emulator, you can't really avoid it. Ideally we'd test every function, but a lot of contributors just don't care unfortunately and if we stopped accepting their stuff we'd be way slower - more accurate though. (This is, in part, caused by all these Pokemon kids and non-official builds, pushing Citra in certain directions)
Also note that using a CPU core by someone else is common in the days of open source (and why we depend on the GPL I've talked so much about).
It's essentially how MAME works.
xqemu also uses qemu as a base. I think it won't be long until we see more widespread use of unicorn-engine or some other generic approach (for other emulators).
Because it takes a lot of work to write these documents. As Leo just pointed out we already have some of those but people don't care.
Also average joe is not a good "Tester": The quality of bug reports is usually horrible with inexperienced (non-developer) users.
flamesage has been working on some compatibility testing feedback functionality (on the websites server) so you can report compatibility from within Citra.
However, I'm not sure who is going to write the code for the emulator to talk to said website. He contacted me but I still see some unresolved issues.
For the time being the unofficial compatibility lists are the best we have and you should contribute to that.
Unless you know what you are doing / reporting you shouldn't report crashes / compatibility issues on github (which is a tool for developers, not users; and it's certainly not a forum).
The amount of bad reports we get on github is insane (also note that I stopped adding the invalid tag lately and some other maintainers don't use it - for whatever reasons; we also get a ton of bad reports / questions on the forums). Moderations for these bad reports takes hours per week (which would otherwise be spend developing and doing proper bug reports).
Most of these issues are not issues in Citra and we'll be able to solve them with a proper release (with a version number) which would probably include some installer.
However, nightly builds are just that: nightly builds; not clean releases.
People should not expect support getting these to work. And they should at least google their issue or search the issue on the forum first.
So if you want to free the developers from wasting time you can also start moderating the forums (either the official forums, speaking up on reddit and here). However, you'll probably want to get on IRC for that so you can ask for the proper answer unless you know something for certain.
Similarily, I shouldn't have to explain the GPL here (which users agreed to when accessing Citra builds / source), but you must have noticed how long the discussion about it became.
- This takes up a contributors time despite being common sense.
So even if you can't code, you can still support Citra by trying to inform people about Citra (but making it clear that it's not a finished product = no support and certainly no Pokemon), not using piracy (and informing users that it hurts Citra), reminding them of the GPL (which will bring in more devs + avoid legal issues) etc.
We already do this.
That's how you write an emulator, you can't really avoid it. Ideally we'd test every function, but a lot of contributors just don't care unfortunately and if we stopped accepting their stuff we'd be way slower - more accurate though. (This is, in part, caused by all these Pokemon kids and non-official builds, pushing Citra in certain directions)
Also note that using a CPU core by someone else is common in the days of open source (and why we depend on the GPL I've talked so much about).
It's essentially how MAME works.
xqemu also uses qemu as a base. I think it won't be long until we see more widespread use of unicorn-engine or some other generic approach (for other emulators).
That's really unfortunate. Test suites are godlike at spotting regressions and every system should have them.
Is the Gateway launcher the only way to get a suitable NAND dump for use with https://github.com/citra-emu/citra/wiki/Home-Folder? Isn't there a way to use the dumps from Decrypt9 or EmuNAND9 instead?
I did test a D9 dump but the NAND.fat16.bin doesn't seem to be readable.
Edit: Decrypt9 dumps do work perfectly with OSFMount. The problem seems to have been with my RPi not liking the dump for some reason.
I did test a D9 dump but the NAND.fat16.bin doesn't seem to be readable.
Edit: Decrypt9 dumps do work perfectly with OSFMount. The problem seems to have been with my RPi not liking the dump for some reason.
Last edited by Kirtai,
Similar threads
-
- Portal
- No one is chatting at the moment.
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
@
BigOnYa:
Caller -"Everytime I start a Pc game on my S24, playing on a external monitor, someone calls or texts me, n it kicks me out of the game." Customer Support - Click (hangs up)+1 -
-
-
-
-
-
-
@
BigOnYa:
I found it funny cause many many years ago, had a roommate in college that did this same dumbass branding of the school logo, but it didn't look anything like it after it healed. Just looked like a birthmark.
-
-
