This study is about a device which is probably the best joypad of all times: the Dual Shock. It has many variants and we can expect it to keep evolving in the coming years, however, we will focus here on the current version, the Dual Shock 3.
In this article, we will go through the history of the game controller in general and then focus on the history of the Dual Shock itself, so that we understand in which context and how it was built. In a next part, we will then analyse the controller by studying its specifications and comparing it to its most direct competitor, the Xbox 360 controller.
There are many categories of game controllers, among which we will retain the most popular one, the gamepad, as that’s exactly what the Dual Shock is. Gamepads, also known as joypads, can have many action buttons combined with one or more omnidirectional control sticks or buttons. They are held using both hands with fingers (typically thumbs) used to provide input; as mentioned on Wikipedia, most modern game controllers are a variation of a standard gamepad. Common additions include shoulder buttons placed along the edges of the pad, joysticks, centrally placed buttons and internal motors that provide haptic feedback (as in, they typically vibrate).
In his article intituled “History of the game controller”, Catalin Ivan stated “Ever since the very beginning of video gaming, the controller has been the best (and usually the only) way of man-machine interaction.” That’s actually an interesting fact, and it would be good to follow the evolution from that “very beginning” to see how we reached the current gamepad technologies. There had actually been many, many gamepads released throughout the history, we are not going to study all of them, we are just going to review those who appear like important milestones that we observed from a study by John Honnibal and that we are summing up in the following table:...
In this post I will show you two methods to configure your .NET applications so that they would launch as soon as Windows starts. These two methods do not require any change to the registry, hence you don't need to worry about cleaning up that database if the user uninstalls your application.
The first method:
From the Windows Installer Deployment Project, follow these steps:...