
This process starts with the prostitutes. It does so by allowing most NPC’s to be propositioned for sex. Sorry about the slip up over your writing this fork, with so many names attached to it I wrongly assumed.Animated Prostitution adds fully animated prostitutes to the Capital Wasteland. If anything I would've thought the opposite since Fallout3 is away from the Program Files folder which is usually a problem. When FOMM tries to install its folders under my Fallout3 game folder, it bugs out whereas they are fine under the FalloutNV folder. Even the nfig is in a non-system folder so I have not the foggiest what is happening.īut there you have it. I don't know why that makes a difference, no folders on my system are under UAC and at any rate I have full administrator rights. Now I placed those folders as sub-folders under the install directory of FOMM like this:Ĭ:\Games\Utils\FOMM\FalloutNV\Install InfoĬ:\Games\Utils\FOMM\Fallout3\Install Info **C:\Games\Fallouts** & **C:\Program Files (x86)\Steam\SteamApps\common\Fallout New Vegas**

Previously both those locations were sub-folders to my games: So retry number 2, complete uninstall again and this time I decided to move the 'Install Info' & 'mods' folders to completely different locations. This time I was allowed, and I thought all was good, but after doing the same for FNV, I again had to recheck the "which game" selector to FO3 and bingo! the error again. All looked good until after selecting the locations for those folders. Since I was getting errors with Fallout 3 I decided to try and install it and work with it first. That included any 'Install Info' or 'mods' folders that were generated and all FOMM registry entries. The fact that the error was being generated upon the 'Update required' dialog I posted about earlier, made me think that something wasn't being set in the program when FOMM tried to make changes to that location.Ĭompletely uninstalled FOMM and purged any reference from my disk or the registry to anything even remotely related to it. At least that is what I can put it down to.


It appears to be a file/folder write permission error.
