Jump to content

Recommended Posts

Posted
13 hours ago, NymphoElf said:

 

The MCM not loading is likely a hidden bug. Unfortunately Load Order is not particularly useful. I need a papyrus log to see where the MCM is getting hung up. This has happened before with the MCM in my personal testing, but I thought I fixed it for good. Seems not.

 

Please Set "bEnableLogging" and "bEnableTrace" to 1 in your Skyrim.ini (default is 0). If you can, please try to reproduce the issue and send me the Papyrus log afterwards. This will give me the information I need to find the bug.

 

Also, just to make sure, which version of the mod are you using? And did you make sure to clean your save (or start a new game) when updating? This is rather important to do since I've been making numerous changes to the mod.

 

Thank you for reporting this.

 

As for the Tattoo Slots, I'm not sure if SlaveTats recognizes more than 6 slots? Can you explain more about how you extended the slot limit? If it's something SlaveTats recognizes, then adding an option to extend the slots will be fairly easy. If it's something else, that's a different story.

 

Also, thank you for the kind words. I'm glad you enjoy the mod! Sorry that it's still a bit buggy. As you can imagine, this is extremely difficult to test by myself, so having people like you be able to report these things is ultra-valuable. :heart:

 

Gotcha.  Papyrus log get, and given.  While snagging the log I waited around on the MCM for a while, and it does actually load eventually - it just takes 2-ish minutes, but it has to go through the entire loading process every time I open it.  So if I accidentally click off your menu I have to wait for the whole loading again.  I'm not 100% sure what version I'm using, but I installed it on the 25th, and it was the most recent version I could find.

Papyrus.0.log

Posted
5 hours ago, TrickyK said:


I believe the hard limit is 128, but that is 128 for body, 128 for hands, etc.

 

Yeah I'm not sure if anyone would want the MCM to load 512 menus (128x4) JUST for tattoos. Lol, that would take forever.

Posted
4 hours ago, ARTistness said:

 

Gotcha.  Papyrus log get, and given.  While snagging the log I waited around on the MCM for a while, and it does actually load eventually - it just takes 2-ish minutes, but it has to go through the entire loading process every time I open it.  So if I accidentally click off your menu I have to wait for the whole loading again.  I'm not 100% sure what version I'm using, but I installed it on the 25th, and it was the most recent version I could find.

Papyrus.0.log 3.06 MB · 1 download

 

Ok, thank you. You might be on 0.5 if you downloaded on the 25th, but you could also be on 0.4. The Zip file you downloaded should have the version included at the end of the name.

 

Also since it DOES actually load, I'll try to find a way to optimize it then. The MCM pulls data whenever the menu is opened, so that's probably where your wait time is coming in.

Posted
5 hours ago, NymphoElf said:

Yeah I'm not sure if anyone would want the MCM to load 512 menus (128x4) JUST for tattoos. Lol, that would take forever.

Have you looked at Rape Tattoos Continued? If you applied a Fame category and body section to each tattoo instead of each body slot the user would only have to set it up once (unless they decide to make changes). Each MCM tab can have up to 50 tattoos and the number of pages is based on the number of tattoos. If you had the default be none, then the user can just go through and select the tattoos they want to contribute to a fame category. For the subcategory they can leave the default option or change it to a specific body area. This way you don't care how many slots a user has to use, just whether they have any 'Fame' tats applied.

Just a thought.

Posted (edited)
11 hours ago, Seeker999 said:

Have you looked at Rape Tattoos Continued? If you applied a Fame category and body section to each tattoo instead of each body slot the user would only have to set it up once (unless they decide to make changes). Each MCM tab can have up to 50 tattoos and the number of pages is based on the number of tattoos. If you had the default be none, then the user can just go through and select the tattoos they want to contribute to a fame category. For the subcategory they can leave the default option or change it to a specific body area. This way you don't care how many slots a user has to use, just whether they have any 'Fame' tats applied.

Just a thought.

 

Good idea!  Except for the part of everyone setting it up for themselves.

 

Keywords on tattoos would be great!    It would solve things like tattoos for drool and tears being counted for tattoo fame.  This assumes that tattoos can be tagged with keywords (but if not they could be in formlists, I guess).   The issue is ... is there a list somewhere of what keywords each tattoo should have and if not who would build it?

 

Even if we don't have a good white list of fame categories maybe there could be a black list for stuff like drool, tears, etc.   It would be cool if we could say to whitelist all tats from a given mod (which sounds like a job for FormList Manipulator - FLM).   On the other hand, how much accuracy do we need?  Maybe it's OK if the PC unfairly gets some tattoo fame?

Edited by Arcane Wanderer
Posted
12 hours ago, Seeker999 said:

Have you looked at Rape Tattoos Continued?

 

I haven't, but I'll check it out now just to see what I can do with it.

 

12 hours ago, Seeker999 said:

If you applied a Fame category and body section to each tattoo instead of each body slot the user would only have to set it up once (unless they decide to make changes).

 

If I can pull that off, that definitely makes things a bit easier to manage. I looked at how SlaveTats handles that kind of data, but it's difficult for me to understand. It's not that it's written poorly or anything, it's simply a knowledge/skill set I haven't developed yet.

 

1 hour ago, Arcane Wanderer said:

Good idea!  Except for the part of everyone setting it up for themselves.

 

I'm not sure if there's really any good way of "automating" the process. Person A may want a certain tattoo to give "Slut" fame, but Person B may want it to give something else. That's why I personally tend to leave that stuff in the user's hands. They can't complain about anything if they're the one ultimately in control.

 

1 hour ago, Arcane Wanderer said:

Keywords on tattoos would be great!    It would solve things like tattoos for drool and tears being counted for tattoo fame.  This assumes that tattoos can be tagged with keywords (but if not they could be in formlists, I guess).

 

Is drool/tears something giving tattoo fame in SLSFR? I didn't think those were detected by SlaveTats, but maybe I assumed incorrectly? If that's the case then I'm definitely interested in finding a fix for this.

 

I haven't worked with formlists before, so I'll need to take some time to properly familiarize myself with how to work with that data if that's where the solution lies.

 

1 hour ago, Arcane Wanderer said:

On the other hand, how much accuracy do we need?  Maybe it's OK if the PC unfairly gets some tattoo fame?

 

I'm definitely interested in making sure fame is applied appropriately, so I'll explore what options are available and how they can be implemented.

 

 

I also need to find a better way to do things in the MCM, because it's getting a bit large right now. Regardless of which solution is settled on for this, I have an idea of how to trim the MCM code a fair bit, particularly for Tattoos.

Posted
4 hours ago, NymphoElf said:

[snipped]

 

 

Is drool/tears something giving tattoo fame in SLSFR? I didn't think those were detected by SlaveTats, but maybe I assumed incorrectly? If that's the case then I'm definitely interested in finding a fix for this.

 

 

I don't know.  I just noticed that tats were being used for drool and tears.   Sorry, but I don't recall where I saw them listed - maybe in the slavetats mcm?   I'll keep an eye out to see what is applying those and how and whether or not it triggers fame.    But, if they are slavetats I would expect that they'd add tattoo fame unless you have some sort of way to exclude certain tats or only count certain tats...

Posted
8 minutes ago, Arcane Wanderer said:

 

I don't know.  I just noticed that tats were being used for drool and tears.   Sorry, but I don't recall where I saw them listed - maybe in the slavetats mcm?   I'll keep an eye out to see what is applying those and how and whether or not it triggers fame.    But, if they are slavetats I would expect that they'd add tattoo fame unless you have some sort of way to exclude certain tats or only count certain tats...

 

Yeah if they're detected as a tattoo by slavetats it will count. I can add a way to stop that if that's the case.

Posted

BTW, you may know that people are working on new versions of SlaveTats.

 

In additon to the current SlaveTats, there's also (ALPHA) Fast Tats and SlaveTatsNG.   The author of Fast Tats, ponzipyramid, recommends not using his mod yet due to I think a CTD issue and says it's better to use SlaveTatsNG than Fast Tats.  I'm not sure if SlaveTatsNG will be offering full backwards compatibility - for now, it doesn't support modevents.

 

I mention this because I notice that he has patches for Bathing In Skyrim Tweaked, STA, and maybe others ... to switch them from overlays to SlaveTats.

 

Long term, the SlaveTatsNG author posts that "... the OverlayManager from ponzipyramid is a very good idea, we need a central overlay management to avoid concurrency issues".  The OverlayManager is a dll that's part of FastTats.

Posted
2 hours ago, Arcane Wanderer said:

I'm not sure if SlaveTatsNG will be offering full backwards compatibility - for now, it doesn't support modevents.

 

Ok. I'll pay attention to how this progresses. If there's at least something that can pull the data from the new code into papyrus for SLSFR to use then it should be fine. I don't use mod events for the SlaveTats stuff, it's all pulled from the SlaveTats script.

Posted (edited)

I have this installed yet it's missing SexLab - Sexual Fame [SLSF].esm....

 

I have SLSF installed, so no idea where I'm supposed to get this file from.

 

Can't find this anywhere. Please help?

Screenshot 2024-08-31 204208.png

Edited by RJJames91
adding extra info
Posted (edited)
On 8/29/2024 at 5:22 PM, Arcane Wanderer said:

Keywords on tattoos would be great!    It would solve things like tattoos for drool and tears being counted for tattoo fame.  This assumes that tattoos can be tagged with keywords (but if not they could be in formlists, I guess).   The issue is ... is there a list somewhere of what keywords each tattoo should have and if not who would build it?


Incidentally, there's been a fair bit of discussion around a kind of tagging framework for tattoos when ponzipyramid was discussing development of the Overlay Manager (which is the native framework that underlies Fast Tats). As mentioned already, it's not really ready for serious usage yet, but I'm hoping that it will go some way towards providing a unified way of managing tattoos and their metadata when it is ready, and I'm very much hoping to make use of it in a future version of Rape Tattoos.

Edited by elliesec
Posted
7 hours ago, RJJames91 said:

I have this installed yet it's missing SexLab - Sexual Fame [SLSF].esm....

 

I have SLSF installed, so no idea where I'm supposed to get this file from.

  

On 8/17/2024 at 9:13 PM, NymphoElf said:

READ THIS MESSAGE BEFORE POSTING

I am aware that Fame Comments does not currently work with this mod.

You say you have SLSF installed, but I'm not sure if you are referring to this mod or the original. If you want to use Fame Comments you need the original Sex Lab Sexual Fame Mod. You can find a link to it on the  SLSF Fame Comments mod page.

Posted
9 hours ago, RJJames91 said:

I have this installed yet it's missing SexLab - Sexual Fame [SLSF].esm....

 

I have SLSF installed, so no idea where I'm supposed to get this file from.

 

Can't find this anywhere. Please help?

Screenshot 2024-08-31 204208.png

 

"SexLab - Sexual Fame [SLSF].esm" is not provided by RELOADED.   That file is part of Versh's old version (at LE and SE conversion).

Posted
9 hours ago, elliesec said:

there's been a fair bit of discussion around a kind of tagging framework for tattoos when ponzipyramid was discussing development of the Overlay Manager (which is the native framework that underlies Fast Tats).

 

This would be a godsend!

Posted

the mod is made for comments right? what do you expect from the testers?.

also after it's complete it's made to replace the old SLSFF is that include framework?

Posted
3 hours ago, abinisa said:

the mod is made for comments right?

 

Read the top of page 1. Not sure how you missed it.

 

3 hours ago, abinisa said:

what do you expect from the testers?

 

Test what you can. Report anything that seems wrong. I'll confirm if it's a bug and fix it if needed.

 

3 hours ago, abinisa said:

after it's complete it's made to replace the old SLSFF is that include framework?

 

I'm not 100% sure what you're asking here, but I'll try to answer anyway.

 

This mod is intended to be a replacement for SLSF, yes. However, mods that use the old SLSF must update.

Posted (edited)

I'm getting a whole ton of log spam on a fresh game, and I'm assuming from logs that its related to SL Cum Overlays Extended.

stack:
	[ (00000014)].Actor.HasMagicEffectWithKeyword() - "<native>" Line ?
	[SexLabQuestFramework (10000D62)].sslactorlibrary.CountCum() - "sslActorLibrary.psc" Line 194
	[SexLabQuestFramework (10000D62)].sexlabframework.CountCumVaginal() - "SexLabFramework.psc" Line 546
	[SLSF_Reloaded_Managers (FE08880A)].slsf_reloaded_visibilitymanager.IsVaginalCumVisible() - "SLSF_Reloaded_VisibilityManager.psc" Line 417
	[SLSF_Reloaded_Managers (FE08880A)].slsf_reloaded_visibilitymanager.OnUpdate() - "SLSF_Reloaded_VisibilityManager.psc" Line 70

 

Is there a particular overwrite/load order I should be using, or is this not supported yet?
Edit, I will note, I am running with SLUtility+ v24-4-7

Edited by applesandmayo
Posted (edited)
57 minutes ago, applesandmayo said:

I'm getting a whole ton of log spam on a fresh game, and I'm assuming from logs that its related to SL Cum Overlays Extended.

stack:
	[ (00000014)].Actor.HasMagicEffectWithKeyword() - "<native>" Line ?
	[SexLabQuestFramework (10000D62)].sslactorlibrary.CountCum() - "sslActorLibrary.psc" Line 194
	[SexLabQuestFramework (10000D62)].sexlabframework.CountCumVaginal() - "SexLabFramework.psc" Line 546
	[SLSF_Reloaded_Managers (FE08880A)].slsf_reloaded_visibilitymanager.IsVaginalCumVisible() - "SLSF_Reloaded_VisibilityManager.psc" Line 417
	[SLSF_Reloaded_Managers (FE08880A)].slsf_reloaded_visibilitymanager.OnUpdate() - "SLSF_Reloaded_VisibilityManager.psc" Line 70

 

Is there a particular overwrite/load order I should be using, or is this not supported yet?
Edit, I will note, I am running with SLUtility+ v24-4-7

 

Cum Overlays Extended is not currently supported. I'm also not 100% sure how I would go about adding support since it edits the core Sexlab Scripts. I think I would have to make an entirely separate version or an optional patch to do so, because I won't be able to compile my current scripts since they rely on Sexlab's internal scripts.

 

I'll add support to my request list.

 

I'm currently working on 0.6 which will add support for extended tattoo slots and other things.

Edited by NymphoElf
Posted
1 hour ago, NymphoElf said:

 

Cum Overlays Extended is not currently supported. I'm also not 100% sure how I would go about adding support since it edits the core Sexlab Scripts. I think I would have to make an entirely separate version or an optional patch to do so, because I won't be able to compile my current scripts since they rely on Sexlab's internal scripts.

 

I'll add support to my request list.

 

I'm currently working on 0.6 which will add support for extended tattoo slots and other things.

 

Yeah, especially for the version of COE I have, which is taking priority over SLU+ and SL. I don't want to make you have to do version control for multiple patches/modifiers, but I do appreciate the effort you're taking in rewriting SLSF - sometimes you look at a code base and just go 'what in the actual fuck' and just scrap it all for a better, more maintainable version. Definitely no small undertaking, but thank you again for doing it!

Posted (edited)
4 minutes ago, applesandmayo said:

 

Yeah, especially for the version of COE I have, which is taking priority over SLU+ and SL. I don't want to make you have to do version control for multiple patches/modifiers

 

Honestly it shouldn't be a super big deal. There's only one script I'll have to edit and release as a separate version. Plus, as long as there's no earth-shattering alterations made to Sexlab or COE, it should be a "one and done" type of thing.

 

I've added COE support as an objective for the 1.0 release.

 

  

5 minutes ago, applesandmayo said:

sometimes you look at a code base and just go 'what in the actual fuck' and just scrap it

 

Yup. Literally what happened :joy:

Edited by NymphoElf

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...