Sexlab not appearing in sseedit after applying conflict filter

[housewalker123]

I want to solve some inconsistencies between sexlab, aroused, zaz animation pack and sexual fame, but i cant load them up in sseedit with the conflict filter

[Monoman1]

1 hour ago, housewalker123 said:

I want to solve some inconsistencies between sexlab, aroused, zaz animation pack and sexual fame, but i cant load them up in sseedit with the conflict filter

Because there are no conflicts between sl and your currently loaded mods.

[housewalker123]

54 minutes ago, Monoman1 said:

Because there are no conflicts between sl and your currently loaded mods.

 

Why does it have so much orange in wrye bash then? it also didnt detect any bash tags with the auto bash tags script. I know my skyrim right now is super unstable, with frequent crashes in dibellas garden or when interacting with the salvery framework

[Just Don't]

3 hours ago, housewalker123 said:

Why does it have so much orange in wrye bash then?

Not because there's a conflict at a record level (which is what xEdit conflicts detects). You should check the Wrye Bash readme to know what these colors mean. I can assure you it's not because it's detecting conflicting records, there are none between SL, Aroused and ZAZ at least. They work together but this doesn't mean they share the same records. Also you won't fix anything by editing these plugins really, at most you'll do some questionable edits and break something.

 

And if you're crashing the only way to properly troubleshoot that is getting crash logs. Once you have a few you can start searching the logs for potential clues to isolate the issue.

[Monoman1]

7 hours ago, housewalker123 said:

 

Why does it have so much orange in wrye bash then? it also didnt detect any bash tags with the auto bash tags script. I know my skyrim right now is super unstable, with frequent crashes in dibellas garden or when interacting with the salvery framework

https://wrye-bash.github.io/docs/Wrye Bash General Readme.html#load-symbols

 

They're load order issues. Run loot and/or organise your load order by hand. 

Loot is not a silver bullet. Bad load orders can cause ctds.

Edited June 20, 2023 by Monoman1

[housewalker123]

Thanks for the answers. Stability improved massively.