How to caputure directX failure for bug report?

[kirkkorver]

Group,
I have a bicycle trainer (lets call it a game here) that is not functional under virtual box. I really want this to work, so I have a different virtual machine (VMwa.. on my computer and so my 'needs' are fulfilled. That said, I want to be a good cyber-citizen and want to provide feedback to Virtual Box that there is a problem. This game will ONLY work under 32-bit windows because they do not have a 64-bit USB driver.

I do not know the best way to capture the problem. Here are details:
Host OS: Windows 7 - 64 bit
Guest OS: Windows XP SP-3 (Clean install, straight from the CD)

What I see:
The game starts properly. When it comes time to display the video, the video is absent. Which is to say that I believe the programmer created a new window and displays the video on this new window. Overlaid if you will. The 'launcher' window is completely visible. The 'game' is actually playing. Sounds are coming and the system works normally, except that the window containing the 'movie' that would be seen at this point is not present.

What I expect:
When it comes time for the video to display, the screen changes to a 'movie'. The speed of the movie matches the speed of the bicycle. When I exit the 'movie' I would go back to the 'Launcher' screen.


Useful details:
The game requires DirectX to run. When DirectX is not not enabled, the game will not even start up. In this error condition dxdiag shows that Direct3D acceleration is not working.

I get exactly the same behavior if I use 'Guest Additions' installed in 'Safe Mode' or if I do NOT install the guest additions, but rather install WineD3D in 'Safe Mode'. In this condition dxdiag shows Direct3D acceleration as enabled. In the Test Direct3D completes normally.

I believe that the architecture is to use separate programs to actually control different aspects of the game. The primary interface (think game selection, or 'Launcher Window') uses DirectX 9.0c. The 'movie' is played using FDDShow, or is using FDDShow for the Codex. I know this because FDDShow is installed as part of the installation. It may be a separate executable that is actually showing the 'movie'.
I have tried multiple FDDShow installations, such as the ones as part of the install and the lastest FDDShow



All of this is a long winded way of saying that I believe that my setup is correct and that there is a bug in Virtual Box. How can I get information that is useful to the virtual box developers in fixing this problem? Saying, "My game is broken" is not useful.

Of course, I can try to tweak the installation and will gladly do so at your request. I know the USB driver is working properly. I know DirectX is installed, because the test button works inside of dxdiag and I know my game is broken.

What should I do next?

--Kirk