halieslade Posted March 31, 2012 Posted March 31, 2012 Please forgive me. I'm new to this forum and I hate to whine, but I'm feeling extremely frustrated right now. Let me preface this by saying that I've been a huge F:NV fan since release. I've played through the game twice and have used a huge number of mods I felt added to the enjoyment. (Also a veteran of Morrowind, Oblivion, Fallout 1 & 2 and now Skyrim). But nothing has had me as excited about FNV as the potential offered by Sexout. I'm tired of the de-sexualized games produced in the US and emasculated by the Sexual Morality crowd. Don't get me started - they lie and wield undue power just to force their morality on everyone else. *Deep breath* So I've been working hard on getting Sexout to work. I have a new test game started, still in Goodsprings at Level 1, and I've been very carefully adding individual mods, then making sure the game still functions. So far so good until it came to Sexout. I've gone through the "how to" thread twice now, but I'm apparently missing something. I've downloaded ESPs, script extender, plugins and common resources as listed in Loogie's "how to" post. I've activated them through FOMM. And now FNV crashes on startup. I disabled all of the mods in FOMM and it still crashes on startup. I've also verified game files integrity and cache through Steam. It checks out fine. I realize this might indicate a problem with something other than Sexout, though I'm dubious given the sequence of events. But after a couple of hours following directions and downloading, then another couple of hours trying to make things work I'm ready to either scream or give up. Or both. I'm on a new Windows 7/64bit machine, 3.0Ghz Quadcore with an NVIDIA GTX460 card and 8GB of Ram. Generic, vanilla FNV runs great, but I don't want vanilla FNV any more. I want Sexout Please tell me there's an easy answer. I know I have a better chance of winning the lotto, but right now I'll take anything I can get. I want to play!
Guest Loogie Posted March 31, 2012 Posted March 31, 2012 Post your load order in the tech support thread. Also, did you install the script extender Prideslayer released? I haven't added that to my how to post yet.
Stormsone Posted March 31, 2012 Posted March 31, 2012 is your load order correct?Because thats the most common reason for mods to crash a game on start up.Its easy to have legion or scr before sexout esm which will crash you.
halieslade Posted March 31, 2012 Author Posted March 31, 2012 Thanks. I will post load order over there, but I double-checked that sexout.esm loads before the other stuff. And installing the script extender was one of the first things I did.
Chase Roxand Posted March 31, 2012 Posted March 31, 2012 Crash on startup means either a missing ESM for a mod or you're missing the NVSE script extender v5 (which goes in fallout new vegas\Data\nvse\plugins). EDIT: Oh, you have the extender. Well, make sure it's installed in the correct place.
halieslade Posted March 31, 2012 Author Posted March 31, 2012 It turns out that the culprit was the mod "PerkEveryLevel", which I ran successfully through an entire game without any problems. Apparently there's something in it that Sexout doesn't like. I'll ditch the cheat mod, go without my extra perks and have some sexy fun. Thank you guys for being so helpful. And special thanks to Loogie for the most helpful tip of all, even if it was obvious to normal people
sen4mi Posted March 31, 2012 Posted March 31, 2012 Personally, I had PerkEveryLevel installed early on in my current game (where I just blindly installed most mods from the nexus top lists, so I could try them out). I got rid of it, but I do not remember having any crashes from it. So your probablem could easily have been a conflict between that particular mod and one of your other mods?
Chase Roxand Posted March 31, 2012 Posted March 31, 2012 What? I use PerkEveryLevel. That wasn't the problem.
halieslade Posted March 31, 2012 Author Posted March 31, 2012 So should I reinstall it and make sure it's last on the load order? Or is there something else I need to do?
zippy57 Posted March 31, 2012 Posted March 31, 2012 Just because PerkEveryLevel didn't cause crashes for one person doesn't mean it's not the cause of a crash for another. Rather, it means that your crashes might be the product of Sexout, PerkEveryLevel, and a third mod working together to create a problem.
Chase Roxand Posted March 31, 2012 Posted March 31, 2012 I don't see how. It has one master and changes one value (the iLevelsPerPerk global). Giving your computer a funny look would cause more conflicts.
zippy57 Posted March 31, 2012 Posted March 31, 2012 Nevertheless, it was, for whatever reason, causing a CTD. Something it was doing was causing a conflict somewhere.
sen4mi Posted March 31, 2012 Posted March 31, 2012 So should I reinstall it and make sure it's last on the load order? Or is there something else I need to do? You should probably post your load order. Load orders can reveal problems.
halieslade Posted March 31, 2012 Author Posted March 31, 2012 So should I reinstall it and make sure it's last on the load order? Or is there something else I need to do? You should probably post your load order. Load orders can reveal problems. I posted it over in Tech Support. Repeated attempts to activate it at various positions in load order have failed. I'm more concerned right now with getting Sexout to work. I can get the sex dialog to come up, and the NPC leads me to another room but then he just sits down and acts bored. Same thing with the "How About" mod that should permit multiple partners. Dialog runs up fine to the point where everyone's supposed to get naked and start doing it, then nothing. EDIT: Searched around over in the Tech Support section and others who have had this problem were pointed to NVSE 5. I have that installed already, even reinstalled it to be sure. I can get NPCs to accost me and agree to fuck, but then they go braindead. Did someone suck their brains out?
saladboy21 Posted March 31, 2012 Posted March 31, 2012 Did all the meshes and animations install correctly? When I first installed Sexout I dumped everything in the Data folder. Dumping everything in the data folder does not work. All meshs need to be in the mesh folder, not multiple mesh folders in other folders or mesh folders in the mesh folder, for example. esps and esms need to be in the Data folder, not in folders in the data folder. NVSE needs to be in it's own folder which is different from other folders. Fortunately, folks here rock and patiently helped me. I'd check all that first. If you downloaded not just plugins but datafiles correctly and animation files correctly and put them in the proper place, conflicts seem most likely as the problem, though I saw no conflicts in your list.
halieslade Posted March 31, 2012 Author Posted March 31, 2012 Did all the meshes and animations install correctly? When I first installed Sexout I dumped everything in the Data folder. Dumping everything in the data folder does not work. All meshs need to be in the mesh folder' date=' not multiple mesh folders in other folders or mesh folders in the mesh folder, for example. esps and esms need to be in the Data folder, not in folders in the data folder. NVSE needs to be in it's own folder which is different from other folders. Fortunately, folks here rock and patiently helped me. I'd check all that first. If you downloaded not just plugins but datafiles correctly and animation files correctly and put them in the proper place, conflicts seem most likely as the problem, though I saw no conflicts in your list. [/quote'] The NVSE docs state: "Copy the .dll and .exe files to your Fallout NV directory." So that's where they are, rather than their own sub-folder. Is that incorrect? Also, I'm using FOMM to activate and install my mods now (learned that lesson the hard way). All the .fomod files are in \Data\Mods and all the .esm and .esp files are in \data. The more I think about this, the more convinced I am that the issue is NVSE. I have both nvse_extender_v5 and nvse_2_beta1.2 installed. When I use the console "GetNVSEVersion" command, it tells me I have version 2 installed. Could that be it?
sen4mi Posted March 31, 2012 Posted March 31, 2012 The NVSE docs state: "Copy the .dll and .exe files to your Fallout NV directory." So that's where they are' date=' rather than their own sub-folder. Is that incorrect? [/quote'] Yes! And this is probably your problem. The nvse plugin .dll files need to be placed in data\nvse\plugins\ underneath your Fallout NV directory. I think that the page where you downloaded it from talks about this.
halieslade Posted March 31, 2012 Author Posted March 31, 2012 Yes! And this is probably your problem. The nvse plugin .dll files need to be placed in data\nvse\plugins\ underneath your Fallout NV directory. I think that the page where you downloaded it from talks about this. Thank you, sen4mi. I moved the dll files into a new \nvse\plugins folder but now FOMM can't find it. When I just move the .exe file back to \data the game bombs and tells me it hasn't been properly installed. I have this automatic reaction making me want to set a %path% variable, but dammit this is Windows7, not DOS!
halieslade Posted March 31, 2012 Author Posted March 31, 2012 Update: The problem was that the file "nvse_extender.dll" belongs in that plugin folder but the rest of the nvse files all go in the FalloutNV root directory. Once I did that, it works!
Guest Loogie Posted March 31, 2012 Posted March 31, 2012 Don't move your EXE file. It does not belong in anything but the base NV folder.
prideslayer Posted April 1, 2012 Posted April 1, 2012 The NVSE docs state: "Copy the .dll and .exe files to your Fallout NV directory." So that's where they are' date=' rather than their own sub-folder. Is that incorrect? [/quote'] Yes! And this is probably your problem. The nvse plugin .dll files need to be placed in data\nvse\plugins\ underneath your Fallout NV directory. I think that the page where you downloaded it from talks about this. No! Only NVSE plugins (i.e. plugins FOR NVSE) go in that directory, like the extender or geck powerup. NVSE itself does NOT go in that directory. Install according to the NVSE instructions.
sen4mi Posted April 2, 2012 Posted April 2, 2012 The NVSE docs state: "Copy the .dll and .exe files to your Fallout NV directory." So that's where they are' date=' rather than their own sub-folder. Is that incorrect? [/quote'] Yes! And this is probably your problem. The nvse plugin .dll files need to be placed in data\nvse\plugins\ underneath your Fallout NV directory. I think that the page where you downloaded it from talks about this. No! Only NVSE plugins (i.e. plugins FOR NVSE) go in that directory, like the extender or geck powerup. NVSE itself does NOT go in that directory. Install according to the NVSE instructions. Where you responding to the wrong message? Or did I say something other than what I thought I was saying (which was that plugins belonged in that directory -- i do not think i was saying anything else belonged there?)
prideslayer Posted April 2, 2012 Posted April 2, 2012 The NVSE docs state: "Copy the .dll and .exe files to your Fallout NV directory." So that's where they are' date=' rather than their own sub-folder. Is that incorrect? [/quote'] Yes! And this is probably your problem. The nvse plugin .dll files need to be placed in data\nvse\plugins\ underneath your Fallout NV directory. I think that the page where you downloaded it from talks about this. No! Only NVSE plugins (i.e. plugins FOR NVSE) go in that directory, like the extender or geck powerup. NVSE itself does NOT go in that directory. Install according to the NVSE instructions. Where you responding to the wrong message? Or did I say something other than what I thought I was saying (which was that plugins belonged in that directory -- i do not think i was saying anything else belonged there?) He asked if the NVSE install instructions were incorrect and you said "yes".. the install instructions for NVSE are not incorrect. The NVSE EXE and DLL both go in the top level FalloutNV directory.
Recommended Posts
Archived
This topic is now archived and is closed to further replies.