ModMan CTD when first using with BS!

[Snacko]

I had ModMan working fine with Blackshark on my computer several months ago. I was using an older version of Modman (6.?? I think). I have reinstalled BS and also have FC and FC2 installed. ModMan works fine with FC and FC2, but when I tell it where the BS game folder is it gets this error while it is 'Checking its Files Index (FID)'?

 

I have just disabled all mods in all games and uninstalled, then reinstalled ModMan and still get the same error....

 

 

I guess the next step is to uninstall Blackshark? I just flew BS and it runs just fine! What exactly is Modman doing when it is checking it's files index (FID)???

 

Has anyone had this problem before?

 

Thanks,

Snacko

[Booger]

Wasn't there a problem with ModMan when BS was installed in the default directory? I honestly don't remember the details, but I read something like that. Win 7 issue or something?

 

Anyway, it prompted me to install BS in C:\Ka-50\ and I have no problems with it personally.

 

Maybe try that?

[Snacko]

Yea, I have always installed it in C:\My Programs\Eagle Dynamics\Ka-50, so it is not in the Program Files.

 

I now have it working with Modman, but the cross cursor has disappeared. I think it disappeared when I Loaded my controller backup profiles.

[Snacko]

Great, I rebooted to see if that would fix my mouse cursor not showing up, and it did fix it. I can see and use it now...

 

But now ModMan is back to that same old problem. I am getting the same exact CTD as in the screenshot above!

 

Any help would be greatly appreciated. This is weird.... :cry:

[Snacko]

Followup to document what fixed it.. Basically, I don't know..

 

Ok, the mouse not showing up was due to the one Mod that I really wanted to install in BS, and that was the Cockpit Tooltips Keycommands. The game's Key commands show up on the Tooltips when you move your mouse over clickable controls. That is real handy. Unfortunately I had the first (and only one I know about) of that mod, and the patch has changed some code in that file that displays the cursor. Since that code was not in the old mod file the cursor disappeared. But adding it to the old file at the top did fix the cursor problem, and now that mod works.

 

But ModMan still crashed. So, I uninstalled Modman and tried all the previous versions up to 7.0.0.1 where BS became supported. They all CTD at the same point. So, I uninstalled BS for the second time and also Modman and deleted all folders for those. And reinstalled BS and patched up to 1.0.1c and installed the latest Modman. I made sure not to touch Blackshark, not even to run it at all. And I tried ModMan again and this time it worked!!?? But it had worked once before and then failed. But this time something totally new happened when I first selected the game folder.

 

ModMan displayed this screen about backing up the player logbook, and network config. I had never seen this screen before. And I have loaded Modman 5 times last night and twice today and it works each time with BS. So, I have backed up my entire BS folder just in case. I am not sure what fixed what here...

 

 

Before this it also did display the list of critical game files that it had backed up as well. I have seen that screen before, but not during this crashing problem. But I have not seen this one before. I am wondering if something about this was the problem. If this reinstall of everything had not fixed it, I was planning on turning off my firewall and av, and even making sure none of the game files were read-only. Because I could not think of anything else. I had already tried running it as Administrator and I have UAC totally off and both BS and ModMan installed outside my Program Files folders. Hmm...

Edited April 7, 2010 by Snacko

[Booger]

Enigma.