A friendly warning about some gameplay mods and Sexout

[sora3]

Hey guys, I've noticed more and more after looking at the structure of Sexout and as well as a lot of the common gameplay mods like Project Nevada and Arwen's Realism Tweaks. Before I started using Sexout, these ran fine. Then CTD and as well as other weird things started to happen.

 

So I cracked open FNVEdit and as well as GECK and took a look at the scripts. And to surprise, I found the problem for my crashing which I'll share here if there are others out there having the same problem.

 

Majority of the gameplay mods that CHANGE the AI behaviour in any way (to be smarter/more realistic) would cause major problems with the Sexout scripts generally attached to the AI (such as Tryouts and Pregnancy). These conflicts would cause problems and after a while, it'll get too much and crash the system.

 

So if you are thinking of doing these gameplay mods, put all the Sexout mods higher up the list so the gameplay mods would overwrite the scripts/running the script alongside. However, I suggest just enjoying New Vegas as it is.

[Halstrom]

Hey guys' date=' I've noticed more and more after looking at the structure of Sexout and as well as a lot of the common gameplay mods like Project Nevada and Arwen's Realism Tweaks. Before I started using Sexout, these ran fine. Then CTD and as well as other weird things started to happen.

 

So I cracked open FNVEdit and as well as GECK and took a look at the scripts. And to surprise, I found the problem for my crashing which I'll share here if there are others out there having the same problem.

 

Majority of the gameplay mods that CHANGE the AI behaviour in any way (to be smarter/more realistic) would cause major problems with the Sexout scripts generally attached to the AI (such as Tryouts and Pregnancy). These conflicts would cause problems and after a while, it'll get too much and crash the system.

 

So if you are thinking of doing these gameplay mods, put all the Sexout mods higher up the list so the gameplay mods would overwrite the scripts/running the script alongside. However, I suggest just enjoying New Vegas as it is.[/quote']

I don't think Pregnancy alters any AI scripts? Let me know which ones you ssupect and what mods and I will see if I can make them more compatible.

I don't use project Nevada or Awrens as I think they conflicted to much with other things I wanted to run besides Sexout.

[prideslayer]

Legion doesn't modify any script packages, it just adds new ones of its own. Changing the load order wont change its behavior.

 

It does change some other vanilla records, but nothing that should conflict (and definitely nothing that will cause CTDs) with the other mods you mentioned.

[Guest Loogie]

So your Sexout tech support tip of the day is not use Sexout?

[KainsChylde]

I think we need specific examples here. This vague warning is rather alarmist without evidence.

[sora3]

@ All, okay. It does look like I need to verify what I said before in order to make this warning clear to you guys.

 

@ Kainschilde209, I've tried 3 different gameplay changing mods (Project Nevada, Arwen's Realistic Tweaks and as well as nVamp) and all experienced crashes within loading the game down to about 30 minutes into the game. Now, I did crack open the GECK to make the game produce warning messages in the console (my own mod for debugging only) and most of the conflicts tend to happen in regards to the AI packaging. If you want to be pedantic about, it relates to the modified AI packages these gameplay mod changes which makes it incompatible to the Sexout scripts to do have sex or the gameplay itself.

 

I'll take the pregnancy as an example since I've noticed this a lot. The pregnancy script interferes with the gameplay mods that affect the 'smarter' AI behaviour package. From Halstrom thread, the pregnancy adds new variables to the AI such as if in a pregnancy state, the NPC changes accordingly in body and as well as stats. It seems gameplay mods don't like it very well when that happens. And the end result is a crash on my end.

 

@ Loogie, I'm not saying we shouldn't use Sexout or even abandon development in the mods. I'm just trying to help. Sure, my initial post didn't sound like I was helping (in hindsight, it looks like it was an alarmist post). But I just wanted to notify that this happens. Plain and simple. I apologise if I caused undue problems on your end.

 

@ prideslayer, true but certain factors add in which makes it CTD. Perhaps bad coding on both ends or the game just isn't developed enough to do something like this. I've seen bad coding before and this game engine takes the cake given how it is.

 

@ Halstrom, I'll try and dig further tonight and see which particular script the gameplay mods are affecting which are causing this crash. I'll let you know what is being effected here.

[KainsChylde]

Off the top, nVamp is wayyyy out of date. If you've updated any of its components I'm amazed it loads at all. And in your own example, multiple mods that change the same AI behavior (I.E. Project Nevada, Arwens Tweaks, FOOK, etc.) are gonna clash with each other without any help from sexout.

 

That being said, yes mods like pregnancy that change stats are going to conflict with other mods that affect those same stats in any way.

 

Your best bet (and in IMHO an essential step with FNV, considering how unstable the base game is) would be FNVEdit. AND the FNVEdit tutorial PDF. It will help you find what is conflicting where so you can reorganize your load list, and you can use it to make a merged patch to choose which effect you want taking precedence where multiple mods change the same thing.

 

EDIT: Looking back at your OP, I see that you have FNVEdit. I apologize in advance, I know this is going to come off as condescending and I don't want to be rude (Anyone who prefaces with that statement is going to be rude anyway, and that rule applies here, sorry) but you do know that FNVEdit not only FINDS conflicts, but can also FIX them, right?

 

One frequent complaint I've noticed regarding FNVEdit is that the merged patches don't fix all problems. This is because people don't read the manual and just make a patch and move on. READ THE MANUAL!!! I can't emphasize that enough. Merged patches only automatically fix obvious issues, You then have to go through the files manually and choose which effect you want to prevail. This process is very long to explain, so I will say again READ THE MANUAL!!!.

 

You can find FNVEdit here: http://newvegas.nexusmods.com/mods/34703

And the manual is here: http://newvegas.nexusmods.com/mods/38413

 

Did I mention you should read the manual? READ IT!!!