I have been trying to troubleshoot a problem with RB3D/Hell's Angels. After a mission in campaign or Fly Now mode, I get to the debriefing screen and there is no cursor. No cursor means I can't exit the debriefing screen, so I have to Ctrl-Alt-Delete to get out of the game, and my mission is lost. This happens EVERY mission without fail.

I thought at first it was a shell sound conflict, but now I'm pretty sure it's video related. I have tried disabling Anti-Virus, as that often causes a conflict, but it didn't help. I'm running under Win XP, Pentium 4, ATI graphics card, with DGVoodoo as my Glide emulator. Anybody else having a similar problem?

Tim

My first suggestion would be to drop the DGVoodoo and use Glidos. Generally, DGV and ATI cards don't seem to mix too well. Let's see what happens after that...

B.O.

Hmmm - ATI and DG Voodoo - no probs here.
Try http://www.polovski.com/
Best advice i got for RB.

Thanks for the replies. In a roundabout way, your suggestions seem to have solved my problem. I remembered trying various versions of Glidos/Openglide before and having a DTD problem trying to start a second mission after flying one. So I uninstalled dgvoodoo and tried running through various Openglide installs, and sure enough they all crashed on the second mission. Polovski's ATI driver doesn't solve the problem on my computer.

So I went back and re-installed dgvoodoo, but having blown out the old set-up file I had to reconfigure it. Now it works! Maybe it's just a good idea every once in a while to reinstall a few things and start over.

By the way, when I reinstalled I located a version 1.4 Beta of dgvoodoo online and tried installing that first. The program would not run, so I suggest that dgvoodoo users stick with the old version until the bugs are worked out on the newer one.

Tim

I'm not aware of a cursor being needed on the Debrief screen. SPACE, ENTER, and ESCAPE are the keys used to navigate the data or exit the Debrief.
The "Second Mission DTD" problem (only while using GLIDE mode) has been experienced by qiute a few users and has been unsolvable AFAWK. It has been present on varying vid cards and glide wrappers. If you can determine what exactly caused success in your case (some setting in the .ini file, probably)it would be very helpfull to the RB Community.