Homebrew Official Citra - New 3DS Emulator

[driverdis]

For once, this is not another *insert random 3ds emulator here* thread linking to a bunch of survey sites. granted this is long from running commercial games.

 

[Duo8]

Finally some real work on the scene, impressive work! This is the start of something much bigger!

Back I see
Anw yeah this is the start of a great debugger

 

[OldClassicGamer]

Finally, a real deal with no surveys

 

[loco365]

Good luck with that, I'm very excited with your emulator.
Since my 3DS is on v7.1 I coudn't develop for 3DS, but your emulator gives me the opportunity to do it.
I'll try developing simple homebrews, starting with a hello world and making more and more complex stuff to be able to contribute to the scene.

Pretty much this. Once I get access to input and whatnot, it'll be a nice place to start since I lack a 4.x 3DS. I'd love to make a homebrew for my Computer Science project, though.

 

[HuskyStrylight]

Finally after waiting so long just to play my favorite game when i cant afford a DS >.<
Please keep up the good work :3

 

[ulua]

thanks so much for your work!

 

[MegaAce™]

Finally after waiting so long just to play my favorite game when i cant afford a DS >.<
Please keep up the good work :3

Please don't misunderstand. This is nowhere near being able to play retail 3DS games.

 

[ChungnSeiker]

Hi Sir But There Is A Problem After I Download The Emulator Is Says he program can't start because MSVCP100.dll is missing from your computer . try reinstalling the program to fix this problem . I already Re-Install it many Times .. But It Still There .. How Can I Fix This Problem Sir

 

[Abcdfv]

Hi Sir But There Is A Problem After I Download The Emulator Is Says he program can't start because MSVCP100.dll is missing from your computer . try reinstalling the program to fix this problem . I already Re-Install it many Times .. But It Still There .. How Can I Fix This Problem Sir

Download that from dll-files.com and follow the instructions it comes with.

 

[dubbz82]

Download that from dll-files.com and follow the instructions it comes with.

or just grab up the visual c++ runtime and install it correctly instead of using some shady website where who knows if they messed with the dll at all or not.

 

[Bond697]

don't download the dll, download the whole runtime: http://www.microsoft.com/en-us/download/confirmation.aspx?id=5555

 

[Abcdfv]

or just grab up the visual c++ runtime and install it correctly instead of using some shady website where who knows if they messed with the dll at all or not.

Lol, it's a respected site.

 

[Arras]

Lol, it's a respected site.

Chances are fixing it that way will only cause more issues though, considering runtimes are more than just 1 DLL.

 

[dubbz82]

Runtime installs a lot more than just the single dll though, and it's stuff that even if it isn't relied on currently, could be in the future. Installing the dll's separate is effectively reinventing the wheel.

EDIT: Ninja'ed by Arras

 

[uyjulian]

just install dlls , when it ask you to install dll keep on doing it until it works.
that way you won't install what you don't need.

This isn't a 16 bit program, isn't it? then there should be no case of "Dll Hell"!

 

[neobrain]

just install dlls , when it ask you to install dll keep on doing it until it works.
that way you won't install what you don't need.

This isn't a 16 bit program, isn't it? then there should be no case of "Dll Hell"!

64 bit vs 32 bit is bad enough when people randomly place dll files in any of the system folders. That's what you get when giving that advice to people who have no clue what they're doing. Windows ends up trying to use 32 bit dlls for 64 bit programs (or vice-versa) and all you get as an error code is "0x0000007b", which is about as descriptive as nothing.

 

[uyjulian]

64 bit vs 32 bit is bad enough when people randomly place dll files in any of the system folders. That's what you get when giving that advice to people who have no clue what they're doing. Windows ends up trying to use 32 bit dlls for 64 bit programs (or vice-versa) and all you get as an error code is "0x0000007b", which is about as descriptive as nothing.

don't place em in the system folders then! put them in the same folder as the application!

 

[Bond697]

he should be installing the runtime, not piecemeal dlls. doing it that way is a bad idea.

 

[uyjulian]

he should be installing the runtime, not piecemeal dlls. doing it that way is a bad idea.

vs2013 runtime installer crashes for me.
just putting dlls in the same folder as application works for me.

let's not go off topic through.

 

[Bond697]

that's a problem on your end, not with the runtime installer. also it's vc++ 2010, not 2013.