DescentBB

Krom wrote:Once you run the launcher, if you have Mercenary installed as well and it gives you an error about "guidebotred" email me and I'll send you the missing registry files you need to make it work, doesn't matter where it is installed.

I would be interested in those. The other day I noticed that there's no BP in my ship config and starting the Mercenary mission would come up w/ some bogus message about something missing. I do see BPs just fine in MP games. And yes, this D3 setup is copied from my previous comp

http://krom.sploitz.com/temp/Descent3registry.zip

It will overwrite a lot of your basic settings and also your video/audio renderer (it'll make your PC use directsound and opengl) so you might want to run the launcher once after you merge the registry entries. I have used this same set of registry files to make D3 work for the last 2-3 years through multiple formats and wholly different computers.

Thank you Krom, this should fix my Merc issues to.

Thanks, I will check it out.

Edit: nope, still the same.

Here's the situation: D3 & Mercenary installed on my old machine, copied over to this one about a year ago. Since I don't use the BP I have no clue if it was broken from the beginning

- BP doesn't show up in the pilot config
- I see BPs just fine in MP games
- if I start D3: Mercenary SP, it plays the movie but doesn't start it -- comes up w/ the following error: Unable to load level file merc.d3l

I checked the following files for corruption against the D3 install on my server:

dmfc.dll, main.exe, extra.hog, extra13.hog, merc.hog, merc.mn3

they check out fine. I also cleaned out my sounds, graphics & stats files. Nada.

Any ideas ?

Hmmm, seems to be doing the same thing on my server when I drag and drop D3+Merc on to it, I'll look into a solution and get back to you.

[Edit: Grendel, try this one: Descent3Fix.zip I hand edited this registry file so let me know if there are any problems.]

Did it work?

The suspense is killing me. ;)

Let me look the keys over 1st

Thank you, I got it fixed. It's the D3 Mercenary uninstall key that has to be there

Here's the one I used, for D3 installed in C:\\Games\\Descent3

d3mercun.reg wrote:Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\\SOFTWARE\\Microsoft\\Windows\\CurrentVersion\\Uninstall\\Descent3 Mercenary]
"UninstallString"=hex(2):43,00,3a,00,5c,00,47,00,61,00,6d,00,65,00,73,00,5c,00, 44,00,65,00,73,00,63,00,65,00,6e,00,74,00,33,00,5c,00,75,00,6e,00,6d,00,65, 00,72,00,63,00,2e,00,65,00,78,00,65,00,20,00,2d,00,63,00,20,00,43,00,3a,00, 5c,00,47,00,61,00,6d,00,65,00,73,00,5c,00,44,00,65,00,73,00,63,00,65,00,6e, 00,74,00,33,00,5c,00,00,00
"DisplayName"=hex(2):44,00,65,00,73,00,63,00,65,00,6e,00,74,00,20,00,33,00,3a, 00,20,00,4d,00,65,00,72,00,63,00,65,00,6e,00,61,00,72,00,79,00,00,00

Edit: forgot to mention -- I added the BaseDirectory key 1st since I didn't have it in the Outrage list, didn't fix it but may have to be there.

Yeah, I had a suspicion it was the merc uninstall string that needed to be there.

Just FYI, it seems it is completely irrelevant where D3 is actually installed, since I have an alternate version of D3 installed in a different folder that works just as well. If I copy my D3 install to the servers C:, or even launch D3 on the server off a network drive from my PC it still works once these registry keys are in place.

I have repaired broken registry settings in D3 by installing it and merc on a dummy drive and then deleting the folders once it was done leaving the registry settings behind, works perfectly fine so there is no need to worry about the base directory key being at all accurate.