Flago Posted May 30, 2024 Posted May 30, 2024 On 5/16/2024 at 10:57 AM, Clockwork-Avatar said: I used GECK to edit the line in LustCheckOkGen to add the missing "playerref." before the GetParentCell and it stopped spamming the error. but now it doesn't even load in MCM so I dunno if I fixed one thing and that broke another or if it's not working for an entirely different reason. Inspired by you I went to the Geck Editor and did the same (NEVER used it before, was a pain to get set up and figure out how to use it, but after an hour I figured it out and did the same thing you did) and it fixed the error for me too. However despite doing the same thing as you, there are two differences. My MCM menu still shows up and shows the mod and configuration settings, and I am having the exact same problem. The edit to add "playerref." before the GetParentCell line in the Geck did remove the error and it is no longer showing, but the Lust meter is still showing up blank with no indication what is wrong. Did you ever figure out how to fix it?
Flago Posted May 30, 2024 Posted May 30, 2024 (edited) On 5/16/2024 at 4:58 PM, Machiavelique said: My guess is that you've fixed something, then it's allowed the script to continue going a bit further but there are another error that's messing things up. Because in any case, you were right to add playerref, it's not a mistake. I tried to have a look at the rest of the LUSTQstScpt as you made the effort to look for it but I didn't see anything abnormal. The only way I know of to keep moving forward is to take the time to read the scripts, to understand how they work, to try to inhibit certain parts to recover the MCM menu and to use DebugPrint. For example, if you add a "return" after each "ScriptEffectUpdate" block in your 3 effect scripts and a return after the GameMode block in your LUSTQstScpt, you should get your MCM Menu back. Of course, this won't really help you find what's wrong, but it might reassure you. There may be many reasons why it doesn't work, but there's often only one reason for everything to work For debugPrint, you can modify LUSTQstScpt as follows Hide contents if GetGameLoaded || GetGameRestarted || iInit != 1 call LustStartup iInit SetDebugMode 1 con_SCOF "MyLustLOG.txt" return endif ;SetDebugMode iDBMode I unfortunately do not know much about how scripting works in Papyrus or the Geck editor, only enough to follow what Clockwork-Avatar did. I know a bit of C++ and python, but I'm so unfamiliar with Geck that I find it very difficult to completely understand what the mod is doing, let alone fix it. That being said my mod is running better than Clockwork-Avatar's and I was able to edit the LUSTQstScpt and get it to generate the MyLustLOG.txt, but it doesn't appear to give anything useful. SCB: Version: 0.1 SCB: Callbacks checked SCB: Registered Callbacks in SexoutNG SCB: ClearOutVars on restart SCB: ClearOut MainQuest Vars! SpunkQuInit: stage 53 Sexout Consequences - October 25 2015 - Loaded at (hex) 32 or (dec) 50 SpunkQuInit: stage 54 SpunkQuInit: stage 55 Add 3rd Party stuff started 3rd Party. Hasn't run before, Continuing Tryout found MPO Set2 done SCR03rdParty: 3rd Party FormList content added ok SpunkQuInit: stage 56 SpunkQuInit: stage 57 msexFort 1.7 SpunkQuInit: stage 58 SpunkQuInit: stage 59 Sexout Wear and Tear v3.9 (2) (March 10 2015) loaded at index 35 (hex) or 53 (dec) / MQ: 35003E90 Sexout Soliciting v5.7 (3) / February 8 2016 loaded at index: (hex) 11 or (dec) 17 Edited May 30, 2024 by Flago
Machiavelique Posted May 31, 2024 Posted May 31, 2024 19 hours ago, Flago said: but it doesn't appear to give anything useful. It won't give anything useful if we don't ask for it. The idea was to add debugging lines everywhere to find out where things go wrong (it's easier to read debug messages from a text file than from the console). I find strange that this problem has been present for several years and that the attempt to correct it produces 2 different effects. I'd have to look into it, but for the moment I can't. If the meter doesn't increase, the first thing to do is to identify the variable concerned and then use the geck search tool to find all the occurrences. Then need to look at what's around it and not just focus on the variable. There are so many mods with so many problems, and not enough people to fix them (recently I wasted 3 days realizing that my bugs were caused by MCM, and the only thing I could do was work around the problem because I can't spend time understanding and fixing MCM).
Machiavelique Posted June 1, 2024 Posted June 1, 2024 (edited) I've done some tests with the following mods/plugins - NVSE 6.3.5b - JIP 57.15 - SexoutNG 2.10.97 - SCR 20210623.1 - SexoutSpunk 1.0108.7 - SexoutLust 7.02 (20141221) - MCM 42507-1-5 I've added the Clockwork-Avatar suggestion (playerref.GetParentCell in LustCheckOKGen) I've recorded all logs in a log file Then, I started a new game I've kept all the Spunk/Lust options at their default values I waited several days my lust increase (with the wait menu) and checks the console for any errors At Lust: 96% - An NPC approached me for sex After sex my Lust dropped to 0% I waited several days my lust increase (with the wait menu) and checks the console for any errors At Lust: 94% - An NPC approached me for sex After sex my Lust dropped to 0% I waited several days my lust increase (with the wait menu) and checks the console for any errors At Lust: 39% I stopped the test I've checked the logs, no errors I'd encourage you to do the same thing: use a minimum number of mods, check that you're using the latest versions (or at least fairly recent), use the default options first and then ‘play with the options’ to work out what's going wrong. Edited June 1, 2024 by Machiavelique
Aasmodeuss Posted July 2, 2024 Posted July 2, 2024 I was feeling lazy but thought I would try editing playerref.GetParentCell in LustCheckOKGen before I called it a night. Didn't make a clean save or uninstall anything and it still seemed to solve the error message in the console.
Machiavelique Posted July 2, 2024 Posted July 2, 2024 It fixes the error message appearing in the console but some players have encountered other problems afterwards (see the posts just above). I've done some tests of my own and I didn't notice any errors after the fix either (however, I didn't push the tests very far or for very long)
cavaleirojustica Posted August 4, 2024 Posted August 4, 2024 Seemly people been aware this mod is broken for a while? Nobody published a fixed version?
_D3V_ Posted December 31, 2024 Posted December 31, 2024 (edited) fixed also the LustCheckOKGen Edited January 1, 2025 by _D3V_
aesir150 Posted July 7, 2025 Posted July 7, 2025 (edited) On 7/2/2024 at 4:36 AM, Machiavelique said: It fixes the error message appearing in the console but some players have encountered other problems afterwards (see the posts just above). I've done some tests of my own and I didn't notice any errors after the fix either (however, I didn't push the tests very far or for very long) Any chance of you sharing your edited esp file? On 11/12/2022 at 7:29 AM, PaulHaul said: How do you fix Error in script 14001942(LustCheckOKGen) in mod SexoutLust.esp Function GetParentCell requires a calling reference but none or NULL was provided Script line approximation: Let rCell:= ##GetParentCell## (error wrapped in ##'s) Where rCell=uninitialized form (0) This is on a clean save and a clean download with only the requirements/frameworks from the List of Sexout Mods installed On 11/14/2022 at 1:10 PM, itami_no_hana said: I'm having exactly the same problem. Followed the List of Sexout Mods On 9/6/2023 at 7:34 AM, lendiforma said: Yep. Same here on the script error as above On 5/8/2024 at 10:49 AM, Clockwork-Avatar said: was the Function GetParentCell error ever sorted out? it's spamming my console and that can't be good. @DoctaSax I know you haven't updated the mod in nearly 10 years but any chance we please can get an official fix for this? Cause I guess it seem to happen for everyone, where sexout lust endlessly spams the console log. Edited July 7, 2025 by aesir150
aesir150 Posted July 7, 2025 Posted July 7, 2025 On 7/2/2024 at 12:19 AM, Aasmodeuss said: I was feeling lazy but thought I would try editing playerref.GetParentCell in LustCheckOKGen before I called it a night. Didn't make a clean save or uninstall anything and it still seemed to solve the error message in the console. I am trying to do the same thing in GECK, but get won't let me save the script for some reason. What am I doing wrong here? scn LustCheckOKGen ref rCell Begin Function {} SetFunctionValue 1 if playerref.IsInCombat PrintD "LustCheckOKGen: combat" SetFunctionValue 0 endif if playerref.NX_GETEVFL "SO:NotNow" PrintD "LustCheckOKGen: NotNow" SetFunctionValue 0 endif let rCell := playerref.GetParentCell if NX_IsInList SexoutListRestrictedCell rCell PrintD "LustCheckOKGen: restricted cell" SetFunctionValue 0 endif End
DoctaSax Posted July 7, 2025 Author Posted July 7, 2025 From the sound of it, and a quick look at my repo, it does seem like GetParentCell is indeed not called on the playerref, which is stupid. I don't have a working install atm, but maybe I'll cook something up tomorrow.
aesir150 Posted July 13, 2025 Posted July 13, 2025 On 7/11/2025 at 2:00 PM, DoctaSax said: Fix released yesterday, btw. Thanks. I thought I wrote a post thanking you for it a day or two go but I guess I forgot to post it.
Drakuld Posted September 25, 2025 Posted September 25, 2025 Hey, can i use the latest version of Lust if i have NX19 and sexoutNG '98 beta 6? i just followed the SOFA guide and i dont wanna touch too much of it tbh coz im kinda new in modding fnv. If so, which version should i pick?
Recommended Posts
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 accountSign in
Already have an account? Sign in here.
Sign In Now