Creating a NES emulator in C++11 (PART 2/2)

In this tool-assisted education video I compile and run the NES emulator that I created in the first part. I showcase a few TASes from http://tasvideos.org/ , some simultaneously.
The emulator is very accurate, and sort-of portable; it compiles on any architecture that support libSDL, but it outputs audio through an external program and reads joypad input from a file.
This video is part 2/2.
-- Part 1 ( http://youtu.be/y71lli8MS8s ): Creating the emulator.
-- Part 2 ( http://youtu.be/XZWw745wPXY ): Compiling and running.

Because of the 15 minute limit that YouTube still imposes on my account (I have no idea why; none of the restrictions mentioned on their help pages should apply to my account, and I have even sms-validated it); I had to develop many techniques to shorten the code dramatically. I also had to type it very quickly... And I had to split the actual demonstration into a second video, which is this video.

Category:

Gaming

Tags:

• linux
• C++0x
• NES
• emulator
• opcode
• dos
• gcc
• gnu
• Joel Yliluoma
• video game
• Nintendo
• Nintendo Entertainment System
• games
• memory
• debugging
• emulation
• Famicom
• FC
• ファミリーコンピューター
• 任天堂
• ＴＡＳさん
• Super Mario Bros.
• Battle of Olympus
• Mega Man
• ロックマン
• Wizards & Warriors
• RARE
• MMC

[darkzone4822]

Very impressive! How many years did you work with C++ language?

[Bisqwit]

@darkzone4822 I first learned about C++ in ~1995, using Borland C++ 3.1, which was pre-standard. However, I didn't truly begin using C++ until ~1999, when my friend (whose YouTube channel is WarpRulez) showed me a simple program that reads words of text, sorts them, and counts how many times each word appeared. It used STL. It impressed me greatly. The program had no hardcoded limits, and it was only about 10 lines long. After that, C++ has been my primary programming language. No regrets.

[BurnInHell7]

I meant OS



[Bisqwit]

@BurnInHell7 Linux. The graphical UI in this video was created in postprocess from the following sources: The DOSBox text output (I run a terminal emulator within DOSBox; within the terminal emulator, the Linux system is accessed); the emulator windows (SDL, as in the source code; though I used a special version of the emulator that outputs raw video into stdout instead); and all custom graphics (UI glue) added by a video processing program I created for this particular video.

[DamarSweetness]

@Bisqwit I am curious at what kind of knowledge you have? I am self-taught in c++ and at a uni learning Java but I have not gone through any development course. What maths do you know what kind of programming experience would i have to have in order to learn this? I could kind follow your code but the reasons for using certain numbers for memory seem arbitrary

[Bisqwit]

@DamarSweetness I used NES architecture documents extensively from e.g. nesdev. Knowledge of them is implied. Bit indexes for registers are part of the hardware's specification. It would have been a major inconvenience to try and explain those in the source code. Some, such as bitmasks, I could have reasonably put as consts/enums, I admit. In the rendering loop, things happen in a marching succession: step 1, do this. step 2, do this. steps 3 and 5, do this. All of this is applied documentation.

[NoobScratcher]

Hes a fucking genious lol I read the code and try to understand it and probably could with time but jesus fucking christ dude you are one in a million

[TheGoodChap]

@Bisqwit Wow I very much agree with you on that. I actually have a 500mhz 94meg box that I put arch linux on and used for a few years as one of my desktops. Did everything I wanted it too at the time, the main reason I have a new computer is for newer games but I still use the old machine.

[arenics]

finally I found a hacker on youtube

[BurnInHell7]

Which SO do yo use?