The new SDK, and thus that document, uses the HID standard axis nomenclature. HID/USB/Raw Input labels the Y and Z axis like an extension of the 2D mouse. The old 3Dx SDK had yet another orientation, and TDxInput had a third. We are sticking with the new standard from now on...until something else changes.
TDxInput is completely unsupported now.
You are probably correct in assuming that the Raw Input events are going to the main window. This is always an issue with plugins. Sometimes the API gives you a spot to take a look at the events. Sometimes you have to use Windows API functions to peek at them. Sometimes you have to create your own window (with its own WndProc) and tell Raw Input to just send the events to your window. I'd suggest doing that latter.
Confused: What API to use to add 3D Mouse support to our app
Moderator: Moderators