I also changed the entries to show equivalent functions instead of my bad descriptions of what the parameters do.

iOS4 Vector and Matrix Math

iOS4 Vector and Matrix Math: Part 2

So I ran through each version of GLES on a 1st Generate iPod Touch (MBX), an iPhone 4 (SGX) and an iPad 2 (A5), printing the returned string from glGetString( GL_EXTENSIONS ) for each device.

There are a some new extensions in iOS5, some of which are iPad2 specific. But you can see from the image, each newer device supports all the previous extensions.

I haven't had chance to run it on an iPad1 yet, so it will be interesting to see if there is any difference. I've only wrote a rough idea of what version of what SDK is required to use them.

Anything with '***' does not need the extension to work and has an implementation for that version of OpenGL ES.

Source code

GL_OES_depth_texture
GL_OES_blend_equation_separate
GL_OES_blend_func_separate
GL_OES_blend_subtract
GL_OES_compressed_paletted_texture
GL_OES_depth24
GL_OES_draw_texture
GL_OES_element_index_uint
GL_OES_fbo_render_mipmap
GL_OES_framebuffer_object
GL_OES_mapbuffer
GL_OES_matrix_palette
GL_OES_packed_depth_stencil
GL_OES_point_size_array
GL_OES_point_sprite
GL_OES_read_format
GL_OES_rgb8_rgba8
GL_OES_stencil_wrap
GL_OES_stencil8
GL_OES_texture_mirrored_repeat
GL_OES_vertex_array_object
GL_OES_standard_derivatives
GL_OES_texture_float
GL_OES_texture_half_float
GL_OES_texture_half_float_linear
 
GL_EXT_blend_minmax
GL_EXT_color_buffer_half_float
GL_EXT_debug_label
GL_EXT_debug_marker
GL_EXT_discard_framebuffer
GL_EXT_occlusion_query_boolean
GL_EXT_read_format_bgra
GL_EXT_separate_shader_objects
GL_EXT_shader_texture_lod
GL_EXT_shadow_samplers
GL_EXT_texture_filter_anisotropic
GL_EXT_texture_lod_bias
GL_EXT_texture_rg				
 
GL_APPLE_framebuffer_multisample
GL_APPLE_rgb_422
GL_APPLE_texture_2D_limited_npot
GL_APPLE_texture_format_BGRA8888
GL_APPLE_texture_max_level	
 
GL_IMG_read_format
GL_IMG_texture_compression_pvrtc

For more information on each extension, most of them can be viewed here. Some of the newer ones in the EXT namespace are viewable on the what's new page of the beta for iOS5, though the page calls them by the APPLE namespace still.

This is easily fixed, all I needed to do was log into the developer portal and add the device UDID, however the screen telling me this was preventing me from getting the UDID.

Eventually I managed to retrieve it from the Organiser in XCode. Glad I didn't brick it in less than 8 hours, I can now play around with airplay once I've flashed my AppleTV.

Vector Transform

Transforms a vector by a matrix

Source code

float matrix[16] =
{
	1.0f, 2.0f, 3.0f, 4.0f,
	7.0f, 6.0f, 9.0f, 10.0f,
	11.0f, 12.0f, 13.0f, 14.0f,
	15.0f, 16.0f, 17.0f, 18.0f
};
float vectorIn[4] = { 1.0f, 1.0f, 0.0f, 1.0f };
float vectorOut[4];
 
vDSP_mmul( &vectorIn[0], 1, &matrix[0], 1, &vectorOut[0], 1, 1, 4, 4 );

For the past week or two I've been trying to reproduce the water effect of PixelJunk Shooter on the iPhone, however I seem to have reached a bottleneck with the collision detection used for repulsion when compressing.

I tried changing from Length to Length Squared, to Manhattan Distance, but it still grinded my framerate to 1FPS.

I decided to see if the Accelerate Framework in the iOS SDK had the vector math added to it yet, and to my surprise it had. It may have been added a while ago and I missed it. So I began to replace my math functions with the vector ones.

The strides are for the single precision functions are the number of floats. So for a stride of 8 bytes, you need to use 2.

Source code

float vec[2];
 
vDSP_vclr( &vec[0], 1, 2 );

This function sets the contents of a vector to zero. The equivalent function would be this

Source code

void vDSP_vclr( float * inVec, const int inStride, const unsigned int inCount )
{
	for( unsigned int idx = 0; idx < inCount; ++idx )
	{
		*inVec = 0.0f;
		inVec += inStride;
	}
}

I haven't used the double precision version of the vector library yet so I don't know if the stride is the count of doubles, or of floats.

I have managed to go from 17 FPS for 650 particles to 30 FPS (I originally had it at 300 particles at 30FPS but it turned out I was profiling in debug). A definite improvement from using the Accelerate library functions for 2d vector math. One of my main issues for getting 1FPS originally was I was island producer was hit testing each particle with itself so it always had the maximum number of particles on each island.

The next couple of pages on this post cover some of the functions (vector and matrix) and their equivalent C++ function.

Whilst working on animation support for Athena for Courage, I began working on a game for the iPhone called Catalyst last weekend.

I was thinking about a game I had played about a month or two before called Polygonal Fury, and realised it would port nicely onto the iPhone.

So I started a OpenGL ES project (and discovered the new version of the iPhone supports shaders), and started with just making some circles bounce around.

Since the collision of a circle is easy, they seems the easiest to setup for interaction with touching the screen.

Initially I just made them "die" if tapped, but later I added the ability of shapes to spawn reactions.

All sprites within the game are triangle fans, but I will probably change them to quads with a texture due to the break that occasionally appears in the geometry, and alpha glow around the edge.

It is not much, but it is a start, I plan to add some more particle types, and maybe a few different upgrades than the ones giving in the Flash version.

The background needs changing, I was thinking of something going on in the background like in another Flash game I played, Spewer, with maybe cut scenes like the Nintendo DS game Contact had.

So a few days ago I started with the Wiimote, I had planned to try to the PS3 controller but I didn't have one, so borrowing one of my housemates Wiimotes I set to work.

There is quite a lot of documentation on the Wiimote at the moment, whether it is the correct way to do things is questionable, since there are cases like "1? - it is set to 1 by the Wii" and "set this to 0x55 at memory address X and set to 0x00 at memory address Y to enable it".

I started with website called The Wiimote Project, but as their documentation grew scarce I found a better site (which it seemed to copy it all from anyways) called WiiBrew. The WiiBrew wiki is quite comprehensive and within a few minutes I already had the LEDs flashing.

I won't go into a lot of detail, I'll just show the basics that I've got to grips with from the documentation on WiiBrew - LEDs + Motor, Buttons, and Battery.

Connecting the Wiimote

Connecting the Wiimote to a Mac is far simpler than it is for XBox 360, for a start its a Bluetooth device that operates using the normal protocols and it doesn't require a key to activate. To connect, first turn on Bluetooth on your Mac, and then select "Set up Bluetooth Device...".

Follow on the onscreen instructions, and when it gets to the point where it is searching for nearby Bluetooth devices, press 1 + 2 to soft synchronize if the Wiimote isn't bound to another device, or the sync button to hard synchronize (unbinds the Wiimote from anything it remembers).

When it appears, select it and click the "Passkey Options..." button. Select the "Do not use a passkey with this device" option and then OK. Continue on and the device will be setup and connected. You can't actually tell since the LEDs are still blinking, but if you have done it correctly, the Bluetooth icon should be different, or the menu will have a disconnect option for the device just setup.

One annoyance I had was with getting rumbling working on the XBox 360 pad, eventually after essentially pinging all messages, I found and worked out the format for the rumble message, which was annoyingly nothing like the others listed.

Well after that I got kinda bored with the 360 and decided to turn towards another console controller, the Wiimote. And I thought I'd write my own driver.

Long story short, when I was having trouble getting my driver working, I looked at the code for the driver for Tattiebogle's XBox 360 pad driver, only to find out that it has redefined the rumble message to it's own format, namely the 4 byte one, only to forward on the settings to the 360 pad.

Well I'm glad I figured out why the message was different, kinda annoying that wasn't in his FAQ. Hopefully others will find this post and go "ohhhhhhhh" like I did when seeing the code.

As for the Wiimote, writing a driver for a Bluetooth device I've decided doesn't make sense, the device is already designed to communicate with another bluetooth device, so I made a class instead, using a Bluetooth API and documentation I found on WiiBrew.

I'll hopefully post my Xcode project for testing the 360 pad in a few days. And I'll probably write up my Wiimote stuff once I get it working the way I want. I'm really tempted to buy lots of cheap USB and Bluetooth devices on eBay now just to see if I can write drivers for them.

I had no trouble with getting the LEDs flashing, but for some reason the rumble actuators just would not respond to my message with success.

I had searched at all other documentation on the pad on the internet, but although I found two variations of rumbling, neither worked.

It has taken my a week or two, but then I got the inspiration to just fire all possible messages to the pad, nullified apart from the header, and see responds with success. So I wrote some code to send 255 different type ids, with 255 different lengths.

Source code

//
//
void HIDInput::TestDevice( IOHIDDeviceRef inDeviceRef )
{
	unsigned char reportData[255];
 
	// Nullify Report
	memset( reportData, 0, sizeof( unsigned char ) * 255 );
 
	// Loop through most possible messages
	for( unsigned char reportType = 0; reportType < 255; ++reportType )
	{
		for( unsigned char reportLength = 0; reportLength < 255; ++reportLength )
		{
			// Setup Header
			reportData[0] = reportType;
			reportData[1] = reportLength;
 
			// Send Report to Pad
			if( DeviceSendReport( inDeviceRef, reportType, reportData, reportLength ) )
			{
				printf( "Success - Type(%u), Length(%u)\n", reportType, reportLength );
			}
			else
			{
				printf( "Failed - Type(%u), Length(%u)\n", reportType, reportLength );
			}
		}
	}
 
	//
	printf( "Finished\n" );
}

I'll explain show the function body for DeviceSendReport in a minute. After running this, only two reports returned with success, one was the LED report, and the other was of Type 0 with length 4.

Since the header take two bytes, I guessed the last two must be Actuator A and Actuator B. And after setting one of them to 0xff, I successfully managed to get one of the actuators rumbling, and then the other actuator with the other byte.

Now for the code for sending reports to the pad.

Source code

//
//
bool HIDInput::DeviceSendReport( IOHIDDeviceRef inDeviceRef, const unsigned char inType, const unsigned char * inReportData, const unsigned char inReportSize )
{
	return IOHIDDeviceSetReport( inDeviceRef, kIOHIDReportTypeOutput, inType, inReportData, inReportSize ) == kIOReturnSuccess;
}

As you can see it takes a parameter called inDeviceRef, this is the value that was passed to DeviceMatchingCallback in the previous entry. And now here is the code to get the LED flashing, there are a few status values for it, so I've created an enum with some comments explaining what each do.

Source code

//
//
enum LEDStatus
{
	kLED_AllOff = 0x00, // All LEDs are turned off
	kLED_AllBlink = 0x01, // All LEDs repeatedly blink on and off
	kLED_P1_FlashOn = 0x02, // Player 1 LED flashes then stays on
	kLED_P2_FlashOn = 0x03, // Player 2 LED flashes then stays on
	kLED_P3_FlashOn = 0x04, // Player 3 LED flashes then stays on
	kLED_P4_FlashOn = 0x05, // Player 4 LED flashes then stays on
	kLED_P1_On = 0x06, // Player 1 LED turns on
	kLED_P2_On = 0x07, // Player 2 LED turns on
	kLED_P3_On = 0x08, // Player 3 LED turns on
	kLED_P4_On = 0x09, // Player 4 LED turns on
	kLED_Rotating = 0x0a, // LEDs flash on in sequence
	kLED_CurrentBlink = 0x0b, // Currently active LED blinks
	kLED_SlowBlink = 0x0c, // All LEDs blink slowly
	kLED_Alternating = 0x0d, // Player 1 & 4 alternate blink with Player 2 & 3
};
 
//
//
void HIDInput::FlashLED( IOHIDDeviceRef inDeviceRef, const LEDStatus inStatus )
{
	//
	const unsigned char kReportType = 0x01;
	const unsigned char kReportSize = 0x03;
	const unsigned char kReportData[kReportSize] =
	{
		kReportType, kReportSize, static_cast<Core::byte>( inStatus )
	};
 
	//
	DeviceSendReport( inDeviceRef, kReportType, kReportData, kReportSize );
}

As you can see, it is fairly simple to send a message, all you have to remember is that the first two bytes contain a header (one byte for type, and one type for the size of the report including the header size). And finally for rumbling the motors.

Source code

//
//
void HIDInput::SetRumble( IOHIDDeviceRef inDeviceRef, const unsigned char inBigSpeed, const unsigned char inLittleSpeed )
{
	//
	const unsigned char kReportType = 0x00;
	const unsigned char kReportSize = 0x04;
	const unsigned char kReportData[kReportSize] =
	{
		kReportType, kReportSize, inBigSpeed, inLittleSpeed
	};
 
	//
	DeviceSendReport( inDeviceRef, kReportType, kReportData, kReportSize );
}

I had some minor problems with the rumble not changing after the first call to SetRumble originally, however it turned out that I had just accidently set the report data variable to be static, so the initialisation was only setup with the first values passed.

Other Rumble Reports

As I mentioned before, I've found other message formats for rumbling the motors, I don't know if its a version thing, or something, but here are the other two I've found if you have trouble with mine.

Version 1 (Tattiebogle)

Source code

//
//
void HIDInput::SetRumble( IOHIDDeviceRef inDeviceRef, const unsigned char inBigSpeed, const unsigned char inLittleSpeed )
{
	//
	const unsigned char kReportType = 0x00;
	const unsigned char kReportSize = 0x08;
	const unsigned char kReportData[kReportSize] =
	{
		kReportType, kReportSize, 0x00, inBigSpeed, inLittleSpeed, 0x00, 0x00, 0x00
	};
 
	//
	DeviceSendReport( inDeviceRef, kReportType, kReportData, kReportSize );
}

Version 2 (http://euc.jp/periphs/xbox-controller.ja.html)

Source code

//
//
void HIDInput::SetRumble( IOHIDDeviceRef inDeviceRef, const unsigned char inBigSpeed, const unsigned char inLittleSpeed )
{
	//
	const unsigned char kReportType = 0x00;
	const unsigned char kReportSize = 0x06;
	const unsigned char kReportData[kReportSize] =
	{
		kReportType, kReportSize, 0x00, inBigSpeed, 0x00, inLittleSpeed
	};
 
	//
	DeviceSendReport( inDeviceRef, kReportType, kReportData, kReportSize );
}

As usual, my Courage game played host to testing this new method of control.

First of all, the XBox 360 pad uses a 0xff device class (Vendor specific), so normal HID drivers (they use a device class of 0x03) will not attach to it, so I needed to download a driver for MacOSX that could handle this. Also I didn't have a Microsoft Wireless Gaming Receiver so I bought a wired pad instead.

I tried the Tattiebogle driver, and at first it worked, but after I logged into VMWare Fusion and used by pad in Vista it stopped working on MacOSX. Or it could have been that I got the Wacom Bamboo pad installed recently.

So after a bit of searching I found another driver, which although didn't work, sparked Tattiebogle's to life. This one is known as XBox HID Driver for Mac OS X.

Once it was all up and running, getting code to listen for the 360 pad was a breeze, and Apple has a nice section on your website for it Technical Note TN2187: New HID Manager APIs for Mac OS X version 10. I'll summarise the basics needed to connect to the pad.

None of this code cleans up properly, like I said I only just started with the HID manager, so I'll probably post an example App at some point that does clean up properly when shutting down.

Setting up HID Manager

The following code is quite straight forward, it just sets up two callbacks, one for when a device matches what we are looking for, and one for when a device is removed.

The IOKit.framework is required.

I also have two global variables, one for the HID manager, and another the device we going to be reading (this code can only do one device since we only have one buffer variable).

Source code

//
//
#include <IOKit/hid/IOHIDLib.h>
#include <IOKit/hid/IOHIDUsageTables.h>
 
//
//
namespace HIDInput
{
	//
	void DeviceMatchingCallback( void * inContext, IOReturn inResult, void * inSender, IOHIDDeviceRef inIOHIDDeviceRef );
	void DeviceRemovalCallback( void * inContext, IOReturn inResult, void * inSender, IOHIDDeviceRef inIOHIDDeviceRef );
	void DeviceIOHIDReportCallback( void * inContext, IOReturn inResult, void * inSender, IOHIDReportType inType, uint32_t inReportID, uint8_t * inReport, CFIndex inReportLength );
	Boolean Device_GetLongProperty( IOHIDDeviceRef inDeviceRef, CFStringRef inKey, long * outValue );
	long Device_GetVendorID( IOHIDDeviceRef inIOHIDDeviceRef );
	long Device_GetProductID( IOHIDDeviceRef inIOHIDDeviceRef );
 
	//
	IOHIDManagerRef l_IOHIDManagerRef;
	uint8_t * l_pReportBuf = 0;
}
 
//
//
int main( int argc, char * argv[] )
{
	// Create a HID manager with a default allocator
	l_IOHIDManagerRef = IOHIDManagerCreate( kCFAllocatorDefault, kIOHIDOptionsTypeNone );
	assert( IOHIDManagerRef );
 
	// Look for all device and open the manager
	IOHIDManagerSetDeviceMatching( l_IOHIDManagerRef, NULL );
	IOHIDManagerOpen( l_IOHIDManagerRef, kIOHIDOptionsTypeNone );
 
	// Register Callbacks to be run with application loop
	IOHIDManagerRegisterDeviceMatchingCallback( l_IOHIDManagerRef, HIDInput::DeviceMatchingCallback, NULL );
	IOHIDManagerRegisterDeviceRemovalCallback( l_IOHIDManagerRef, HIDInput::DeviceRemovalCallback, NULL );
	IOHIDManagerScheduleWithRunLoop( l_IOHIDManagerRef, CFRunLoopGetCurrent(), kCFRunLoopDefaultMode );
 
	//
	while( true )
	{
		// loop application
	}
 
	return 0;
}

The call to IOHIDManagerSetDeviceMatching() can have a dictionary passed to it to look only for devices matching certain criteria, but for simplicity, I'll just be checking all devices in this example, so I passed NULL as a second argument.

Checking for XBox360 Pad

With the code setup for calling back when a device is found that matches (or all devices in our case), we now need to check the device vendor id and product id to be sure they are what we are looking for.

Source code

//
//
Boolean HIDInput::Device_GetLongProperty( IOHIDDeviceRef inDeviceRef, CFStringRef inKey, long * outValue )
{
	CFTypeRef tCFTypeRef = IOHIDDeviceGetProperty( inDeviceRef, inKey );
	Boolean result = FALSE;
 
	if( tCFTypeRef )
	{
		// If this is a number get its value
		if( CFNumberGetTypeID( ) == CFGetTypeID( tCFTypeRef ) )
		{
			result = CFNumberGetValue( ( CFNumberRef ) tCFTypeRef, kCFNumberSInt32Type, outValue );
		}
	}
 
	return result;
}
 
//
//
long HIDInput::Device_GetVendorID( IOHIDDeviceRef inIOHIDDeviceRef )
{
	long result = 0;
	Device_GetLongProperty( inIOHIDDeviceRef, CFSTR( kIOHIDVendorIDKey ), &result );
	return result;
}
 
//
//
long HIDInput::Device_GetProductID( IOHIDDeviceRef inIOHIDDeviceRef )
{
	long result = 0;
	Device_GetLongProperty( inIOHIDDeviceRef, CFSTR( kIOHIDProductIDKey ), &result );
	return result;
}
 
//
//
void HIDInput::DeviceMatchingCallback( void * inContext, IOReturn inResult, void * inSender, IOHIDDeviceRef inIOHIDDeviceRef )
{
	if( !inIOHIDDeviceRef )
	{
		return;
	}
 
	const long kVendor_Microsoft = 0x045e;
	const long kProduct_XBox360Pad = 0x028e;
 
	const long kVendorID = Device_GetVendorID( inIOHIDDeviceRef );
	const long kProductID = Device_GetProductID( inIOHIDDeviceRef );
 
	if( kVendorID == kVendor_Microsoft && kProductID == kProduct_XBox360Pad )
	{
		// Assert if we're trying to create a second XBox 360 pad device
		assert( l_pReportBuf );
 
		// Get the size of the report for the device and allocate a buffer. The
		// report size property should be right, however the packet header
		// seems to want 20 bytes, so I'm allocating 20 bytes to be safe.
		CFIndex reportSize = 20;
		//IOHIDDevice_GetLongProperty( inIOHIDDeviceRef, CFSTR( kIOHIDMaxInputReportSizeKey ), &reportSize );
		l_pReportBuf = static_cast<uint8_t *>( malloc( reportSize ) );
 
		// Register a report callback for this device
		IOHIDDeviceRegisterInputReportCallback( inIOHIDDeviceRef, l_pReportBuf, reportSize, DeviceIOHIDReportCallback, 0 );
 
		printf( "XBox Pad Connected.\n" );
	}
}
 
//
//
void HIDInput::DeviceRemovalCallback( void * inContext, IOReturn inResult, void * inSender, IOHIDDeviceRef inIOHIDDeviceRef )
{
	// Deallocate report buffer
	free( l_pReportBuf );
	l_pReportBuf = 0;
 
	//
	printf( "XBox Pad Disconnected.\n" );
}

We have two constants in the device matching callback, one that is the vendor id for Microsoft, and the other which is the product id for the XBox 360 pad.

Since this code only supports the one pad, I've added an assert which will be triggered if a second pad is attempted to be matched that is a 360 pad (it checks to see if the report buffer has already been allocated).

Once a device has been removed, I free the memory for the report buffer. I think I'm suppose to unregister the input report callback by passing null as the callback, but I'm not 100% sure yet.

All the other helper functions were found on the Apple website technical note.

Reading Pad Status

XBox 360 pad updates come through on a report type of 0x00 and are 14 bytes long (though I have read on other sites of people getting reports of 20 bytes, this just seems to be padding).

I have skipped the checking of the report type in this code, but it should probably be checked, as well as the report length.

Source code

//
//
void HIDInput::DeviceIOHIDReportCallback( void * inContext, IOReturn inResult, void * inSender, IOHIDReportType inType, uint32_t inReportID, uint8_t * inReport, CFIndex inReportLength )
{
	// Output hex for each byte in the report (always 2 characters long, making up the rest with 0)
	for( int i = 0; inReportLength; ++i )
	{
		printf( "%02x", inReport[i] );
	}
 
	//
	printf( "\n" );
}

That sourcecode allows you to read just the actual reports being sent from the pad, however if you want to be able to use it as a 360 pad. You'll get a message something like this...

0014000000002efcc70792ff9a06

The 0014 at the beginning is a packet header, first byte being the command, second being the size of the packet. The other sections are split up as follows...

0014aaaabbccddddeeeeffffgggg

a is an unsigned short of button flags

b is an unsigned char representing the left trigger (LT)

c is an unsigned char representing the right trigger (RT)

d is a signed short representing the Left Axis X

e is a signed short representing the Left Axis Y

f is a signed short representing the Right Axis X

g is a signed short representing the Right Axis Y

This can be put into a function like so...

Source code

//
//
void HIDInput::DeviceIOHIDReportCallback( void * inContext, IOReturn inResult, void * inSender, IOHIDReportType inType, uint32_t inReportID, uint8_t * inReport, CFIndex inReportLength )
{
	unsigned char leftTrigger, rightTrigger;
	short rightAxisX, rightAxisY;
	short leftAxisX, leftAxisY;
	unsigned short buttonFlags;
 
	// Copy bytes to their respective variables (incase they are not aligned correctly)
	memcpy( &buttonFlags, &inReport[2], sizeof( unsigned short ) );
	memcpy( &leftTrigger, &inReport[4], sizeof( unsigned char ) );
	memcpy( &rightTrigger, &inReport[5], sizeof( unsigned char ) );
	memcpy( &leftAxisX, &inReport[6], sizeof( short ) );
	memcpy( &leftAxisY, &inReport[8], sizeof( short ) );
	memcpy( &rightAxisX, &inReport[10], sizeof( short ) );
	memcpy( &rightAxisY, &inReport[12], sizeof( short ) );
 
	// Output pad stats
	printf( "Buttons %u\n", buttonFlags );
	printf( "LTrigger: %u\n", leftTrigger );
	printf( "RTrigger: %u\n", rightTrigger );
	printf( "LAxis: %d, %d\n", leftAxisX, leftAxisY );
	printf( "RAxis: %d, %d\n", rightAxisX, rightAxisY );
	printf("\n");
}

I don't know what the 2048 button flag is, it is possibly the synchronization button that is on the wireless controller. So here is a list of all the other button flags and their bit number.

Source code

//
//
enum XBox360_ButtonFlags
{
	XBOX360PAD_DPAD_UP = 1,
	XBOX360PAD_DPAD_DOWN = 2,
	XBOX360PAD_DPAD_LEFT = 4,
	XBOX360PAD_DPAD_RIGHT = 8,
	XBOX360PAD_START = 16,
	XBOX360PAD_BACK = 32,
	XBOX360PAD_LAXIS = 64,
	XBOX360PAD_RAXIS = 128,
	XBOX360PAD_LB = 256,
	XBOX360PAD_RB = 512,
	XBOX360PAD_XBOX = 1024,
	XBOX360PAD_A = 4096,
	XBOX360PAD_B = 8192,
	XBOX360PAD_X = 16384,
	XBOX360PAD_Y = 32768,
};

There is still a lot more to cover, so I'll probably make a follow up entry tomorrow or the day after for sending messages to the pad to make it vibrate, and how to clean up after you're finished properly. As well as post an example application.

I also found a few new variables to add to my list of debugging preprocessor. I'll explain on the next page since this one is getting rather long.