3DS Emulator Citra Boots First Commercial Game
- Thread starter PGamer
- Start date
AcademicSaucer
Member
http://citra-emu.org/ said:
I can wait.
Fantastical
Death Prophet
Me too! I'm just really happy it's happening.
I'll take what I can get.
TheCongressman1
Member
Animal Crossing: New Leaf can now get in-game.
Oooh, nice. I'd love to play AC on my computer eventually, well, if I can import my save. I don't think I could start over at this point.
Allnamestakenlol
Member
This is really exciting stuff. 
Grylvak
Member
This is so exciting!
orthodoxy1095
Banned
Fantastic!
SomedayTheFire
Member
Unbelievable progress.
What specs do you have? Did you use software rendering or OpenGL?
Difference from my last pull:
151 files changed, 1625 insertions(+), 2448 deletions(-)
Seems they did some good changes although more deletions than insertions
I think the builds from the homepage don't have OpenGL, do they? Anyway, didn't change anything in the config so I assume it's software. I have a i5 4570 @ stock (and a GTX 970 but I don't think it matters huh). By useable I didn't mean to say playable tho
it's sufficient to navigate through menus with a reasonable amount of lag.I think the builds from the homepage don't have OpenGL, do they? Anyway, didn't change anything in the config so I assume it's software. I have a i5 4570 @ stock (and a GTX 970 but I don't think it matters huh). By useable I didn't mean to say playable tho
Oh, I understood what you meant
I remember "playing" Tekken 2 on a P2 266 MHz with pcsx... 
Still amazing progress and I think they currently really should consider to implement as much as possible and concentrate on performance later.thequickandthedead
Member
Will playing online multiplayer with other 3DSs ever be possible?
I guess it is possible but this is a feature which is far, far off in the timeline for this project.
Again, the project is in early stages. Go to youtube, you will find games that are rendered with an external opengl renderer but the main code is currently software only.
Why not try it yourself?
Improved home menu emulation:
I love those kind of screens .... tells a lot about how the console works
So I know this is asking something crazy, but the emulator currently only outputs at native resolution correct?
I really want to jump into Animal Crossing and just grab a full 4K screenshot, letting it render however the hell long it needs because I'd love to see the art style in high res.
I really want to jump into Animal Crossing and just grab a full 4K screenshot, letting it render however the hell long it needs because I'd love to see the art style in high res.
Chû Totoro
Member
I know it may have been asked many times but I don't think it's a stupid question so I'll ask here
I understand homebrew and emulation. This is awesome things we have the chance to use for free thanks to talented developers. Still in specific cases like 3DS I don't understand how emulation (not homebrew) can be perceived as something exciting since no 3D on the upper screen, no touch screen etc.
Is it mostly for the technical challenge?
Also how do we back up our games? I don't find the information and I might try this just to see
I understand homebrew and emulation. This is awesome things we have the chance to use for free thanks to talented developers. Still in specific cases like 3DS I don't understand how emulation (not homebrew) can be perceived as something exciting since no 3D on the upper screen, no touch screen etc.
Is it mostly for the technical challenge?
Also how do we back up our games? I don't find the information and I might try this just to see
Chû Totoro;163659274 said:I know it may have been asked many times but I don't think it's a stupid question so I'll ask here
I understand homebrew and emulation. This is awesome things we have the chance to use for free thanks to talented developers. Still in specific cases like 3DS I don't understand how emulation (not homebrew) can be perceived as something exciting since no 3D on the upper screen, no touch screen etc.
Is it mostly for the technical challenge?
Also how do we back up our games? I don't find the information and I might try this just to see
DS emulation has been possible for years. Typically, Mouse emulates touch. If you've got a touchscreen (like a tablet PC, or just a touchscreen monitor) you could simply make physical touch emulate touch. If you've got a drawing tablet, you can use something like that as well.
3D monitors and televisions have been perfectly usable for years on PC. I use my 3D monitor all the time and 3D on PC where you aren't limited in depth looks incredible.
On top of that, for many 3DS games 3D isn't really essential, though it adds a great effect. The 3DS first and foremost is a game console, and plenty of the games play great in both 2D and 3D.
To back up games, you need something like the Gateway 3DS flashcart, which lets you rip ROMs of your 3DS games to backup on your PC.
Chû Totoro;163659274 said:I know it may have been asked many times but I don't think it's a stupid question so I'll ask here
I think it's a good place as the thread is not going that fast currently.
Well, although 3d is nice for 3ds, there are people who don't like the effect and turn it off even on the real hardware and you can easily emulate the touch screen via a mouse input.
Also keep in mind not every game needs touch input so you can still play a lot of games without having to use a mouse at all.
Also this, yes, but it also enables you to play these games in, let's say, 20 years (if cpus at that time still can execute x86-code
).Also how do we back up our games? I don't find the information and I might try this just to see
I don't think this is the appropriate place for this but I guess gba temp is a better place for your interests.
Basileus777
Member
Chû Totoro;163659274 said:I know it may have been asked many times but I don't think it's a stupid question so I'll ask here
I understand homebrew and emulation. This is awesome things we have the chance to use for free thanks to talented developers. Still in specific cases like 3DS I don't understand how emulation (not homebrew) can be perceived as something exciting since no 3D on the upper screen, no touch screen etc.
Is it mostly for the technical challenge?
Also how do we back up our games? I don't find the information and I might try this just to see
A mouse can emulate touchscreen controls pretty easily. Having dual displays isn't an issue given the size and resolution of PC monitors, you can easily render both. Many people don't care for 3D on the 3DS, so they aren't bothered if that is never emulated, though 3D is possible on the PC too.
I don't think it is. There is a pull request for an OpenGL hardware renderer from just yesterday but is hasn't been merged.
I was just browsing through the source and found this folder (https://github.com/citra-emu/citra/tree/master/src/video_core/renderer_opengl). Might just be a placeholder or sth, no idea if it's actually implemented; just figured it was worth asking
Chû Totoro
Member
Thank you all for the answers. Sorry to notice them only now. As always homebrew and emulation community is always very patient and it's so pleasant to discuss with you all.
Now go back to work for region free for everyone and make nice homebrew apps for my New 3DS
Oh and having a software to rip 3D movies on my 3DS would be sooooo awesome... I'm making a lit here, am I?
Anyway, I'll try this emulator at least for curiosity since I'm keeping almost every Nintendo system when there is a sort of BC "gap"
Now go back to work for region free for everyone and make nice homebrew apps for my New 3DS
Oh and having a software to rip 3D movies on my 3DS would be sooooo awesome... I'm making a lit here, am I?
Anyway, I'll try this emulator at least for curiosity since I'm keeping almost every Nintendo system when there is a sort of BC "gap"
KatamariOnTheRocks
Member
Hi, I've always been fascinated by people's ability to rework tech and understand hardware that has no basis for comparison or documentation. I just had a question about the general process of developing the software and hardware involved with emulation.
How do you go about development on a day to day basis? I know I won't understand the very technical aspects but just in simple terms, is it alot of experimentation that you'll make small changes to code, test it out and rinse and repeat? And how do you know what changes to make, is it experimentation or following the digital architecture you're attempting to emulate through access to internal code on said system?
I guess I'm unsure of how someone knows where to start in such a large endeavor. I know if I was provided all the hardware necessary to figure out some tech I had never seen that I'd have no idea what to do/where to begin.
How did people develop the hardware to either read code from the system itself or to even read games? My mind is blown by the fact that people are able to create hardware capable of interfacing with these closed systems that I can't even imagine how they would know where to start in terms of creating software capable of interacting with tech that's previously undocumented.
To put it in the simplest terms, I have no idea how someone begins a project like this, do they begin by attempting to recreate the O.S. from scratch? Do they find a way to read processes as they are running and then change values, comparing what happens to find out what function affects what?
I apologize for this wall of text and so many questions, it's entirely passion driven as it amazes me what some people can do with tech that didn't exist before the console manufacturers made it.
I remember being shocked about initial D.S. emulation as I had assumed that DS carts are manufactured using proprietary hardware that "readers" didn't exist for, in the way that SD cards used for save files were an existent tech beforehand.
Thanks for bearing with me, and a big thanks for all the hard work put in by the people working on this emulator and explaining it to people like me, I can't wait to see how it turns out down the road
How do you go about development on a day to day basis? I know I won't understand the very technical aspects but just in simple terms, is it alot of experimentation that you'll make small changes to code, test it out and rinse and repeat? And how do you know what changes to make, is it experimentation or following the digital architecture you're attempting to emulate through access to internal code on said system?
I guess I'm unsure of how someone knows where to start in such a large endeavor. I know if I was provided all the hardware necessary to figure out some tech I had never seen that I'd have no idea what to do/where to begin.
How did people develop the hardware to either read code from the system itself or to even read games? My mind is blown by the fact that people are able to create hardware capable of interfacing with these closed systems that I can't even imagine how they would know where to start in terms of creating software capable of interacting with tech that's previously undocumented.
To put it in the simplest terms, I have no idea how someone begins a project like this, do they begin by attempting to recreate the O.S. from scratch? Do they find a way to read processes as they are running and then change values, comparing what happens to find out what function affects what?
I apologize for this wall of text and so many questions, it's entirely passion driven as it amazes me what some people can do with tech that didn't exist before the console manufacturers made it.
I remember being shocked about initial D.S. emulation as I had assumed that DS carts are manufactured using proprietary hardware that "readers" didn't exist for, in the way that SD cards used for save files were an existent tech beforehand.
Thanks for bearing with me, and a big thanks for all the hard work put in by the people working on this emulator and explaining it to people like me, I can't wait to see how it turns out down the road
Hi, I've always been fascinated by people's ability to rework tech and understand hardware that has no basis for comparison or documentation. I just had a question about the general process of developing the software and hardware involved with emulation.
How do you go about development on a day to day basis? I know I won't understand the very technical aspects but just in simple terms, is it alot of experimentation that you'll make small changes to code, test it out and rinse and repeat? And how do you know what changes to make, is it experimentation or following the digital architecture you're attempting to emulate through access to internal code on said system?
I guess I'm unsure of how someone knows where to start in such a large endeavor. I know if I was provided all the hardware necessary to figure out some tech I had never seen that I'd have no idea what to do/where to begin.
How did people develop the hardware to either read code from the system itself or to even read games? My mind is blown by the fact that people are able to create hardware capable of interfacing with these closed systems that I can't even imagine how they would know where to start in terms of creating software capable of interacting with tech that's previously undocumented.
To put it in the simplest terms, I have no idea how someone begins a project like this, do they begin by attempting to recreate the O.S. from scratch? Do they find a way to read processes as they are running and then change values, comparing what happens to find out what function affects what?
I apologize for this wall of text and so many questions, it's entirely passion driven as it amazes me what some people can do with tech that didn't exist before the console manufacturers made it.
I remember being shocked about initial D.S. emulation as I had assumed that DS carts are manufactured using proprietary hardware that "readers" didn't exist for, in the way that SD cards used for save files were an existent tech beforehand.
Thanks for bearing with me, and a big thanks for all the hard work put in by the people working on this emulator and explaining it to people like me, I can't wait to see how it turns out down the road
Well, in the beginning you want to write a debugger, combined with opcode emulation. That is where you start "executing" the code from the emulated machine on your machine. Documentation for the system is very helpful, of course, like ISA manuals and stuff like that. Other things include "inner workings" of the emulated machine as you don't want to only emulate the CPU but the whole system so you get to know memory mappings, encrypt and decrypt, you have to reverse engineer file types, API calls, other chips like sound and so on. It is often a story of redoing work, trying out things, finding out things and quite often you rewrite code you have written before because of recent findings make you better understand what is really going on.
KatamariOnTheRocks
Member
Thanks for the reply, that's really interesting. It puts things in perspective of just how big of an endeavor proper emulation is. I have a ton of respect for the people that figure this stuff out.
lol yeah, I keep trying to boot up 3G and 4G whenever I download the latest nightly but so far no luck
