Jump to content

Lovers Check Error Message


Recommended Posts

Posted

My Message Log is nothing but this warning, checked  every second and seems to be causing my CTDs.

 

[005170B1] [WARNING]   Unable to find function definition for command 0 in script 'xLoversCheckObse2QuestScript'.
 

So...does anyone know what this is and how to fix it? LO attached.

xExported Load Order.txt

Posted (edited)

Maybe game in C : \ program files ? And OBSE does not work right.

Or one of the not working xOBSE versions ? Have you tried OBSE21  ? Or do you have a Mod that needs xOBSE ?

 

Wrong load order: Your load order is a mess. . .  a miracle that your game starts.

Read

https://www.loverslab.com/topic/36443-oblivion-install-gametoolsbodiesbbbmod-sorting-and-cleaningcs-cse-body-stretching/?do=findComment&comment=915257

 

And a comment on your other thread: Never Lovers and Tamago/Hiyoko mods in the BashedPatch.

Edited by fejeena
Posted (edited)

My LO is primarily from Reign Of The Septims mod guide, with Lover's mods added, and the order of those mods are based on the installation guide in the Lover's Purification Lite readme, which lists the appropriate order as:

 

Lovers with PK.esm (esms are master files and always go on top)
 ------ (You may have other mods between here including official DLC) ------
 LoversAdultPlayPlusforSSP.esp
 LoversVoiceSSPplus.esp
 Lovers with PK.esp
 LoversMB2.esp
 LoversPurification.esp (This mod)
 ------ (You may have other mods between here) ------
 LoversIdleAnimsPriority.esp
 LoversAnimObjectsPriority.esp (These two go at the bottom of your load order)
 

So I do not see how my load order is "a mess". Also, I notice that you frequently accuse people of installing this game in the C programs folder. No. I never install in C. this is basic. But thanks anyway.

 

My game runs just fine, so my load order can't be that bad. The only issue is this message before CTD. This is how my Message Log looks:

 

2025/04/08 03:08:17  [005170B1] [WARNING]   Unable to find function definition for command 0 in script 'xLoversCheckObse2QuestScript'.
2025/04/08 03:08:23  [005170B1] [WARNING]   Unable to find function definition for command 0 in script 'xLoversCheckObse2QuestScript'.
2025/04/08 03:08:30  [005170B1] [WARNING]   Unable to find function definition for command 0 in script 'xLoversCheckObse2QuestScript'.
2025/04/08 03:08:36  [005170B1] [WARNING]   Unable to find function definition for command 0 in script 'xLoversCheckObse2QuestScript'.
2025/04/08 03:08:43  [005170B1] [WARNING]   Unable to find function definition for command 0 in script 'xLoversCheckObse2QuestScript'.
2025/04/08 03:08:49  [005170B1] [WARNING]   Unable to find function definition for command 0 in script 'xLoversCheckObse2QuestScript'.
2025/04/08 03:08:55  [005170B1] [WARNING]   Unable to find function definition for command 0 in script 'xLoversCheckObse2QuestScript'.
2025/04/08 03:09:02  [005170B1] [WARNING]   Unable to find function definition for command 0 in script 'xLoversCheckObse2QuestScript'.
2025/04/08 03:09:08  [005170B1] [WARNING]   Unable to find function definition for command 0 in script 'xLoversCheckObse2QuestScript'.
2025/04/08 03:09:14  [005170B1] [WARNING]   Unable to find function definition for command 0 in script 'xLoversCheckObse2QuestScript'.
2025/04/08 03:09:21  [005170B1] [WARNING]   Unable to find function definition for command 0 in script 'xLoversCheckObse2QuestScript'.
2025/04/08 03:09:27  [005170B1] [WARNING]   Unable to find function definition for command 0 in script 'xLoversCheckObse2QuestScript'.
2025/04/08 03:09:34  [005170B1] [WARNING]   Unable to find function definition for command 0 in script 'xLoversCheckObse2QuestScript'.
2025/04/08 03:09:40  [005170B1] [WARNING]   Unable to find function definition for command 0 in script 'xLoversCheckObse2QuestScript'.
2025/04/08 03:09:46  [005170B1] [WARNING]   Unable to find function definition for command 0 in script 'xLoversCheckObse2QuestScript'.
2025/04/08 03:09:53  [005170B1] [WARNING]   Unable to find function definition for command 0 in script 'xLoversCheckObse2QuestScript'.

 

Nothing else. This is why I'm asking for help here.

Edited by StewDaddy1
Posted (edited)

Yes that is the right Load order, but . . .

 

LoversAdultPlayPlusforSSP.esp
 LoversVoiceSSPplus.esp
 Lovers with PK.esp
 LoversMB2.esp
 LoversPurification.esp (This mod)
 ------ (You may have other mods between here) ------  Must be " You may have other Lovers Mods between here"  !
 LoversIdleAnimsPriority.esp
 LoversAnimObjectsPriority.esp (These two go at the bottom of your load order)

 

----------------------------------

And you see it in all example load orders

see

https://www.loverslab.com/topic/4487-please-read-before-posting-here/

Or see BOSS load order ( download the Oblivion masterlist.txt )

 

esm

e.g. your esm in right order: (BOSS)

Oblivion.esm

SettlementsOfCyrodiil.esm 

Cobl Main.esm 

Waalx Animals & Creatures.esm 

Lovers with PK.esm 

MigMaster.esm

Av Latta Magicka.esm   I would place it here

 

<<<<<Now here  no-Lovers-Mods>>>>>

Then  you have all Tamago and Hiyoko mods

LoversAdultPlayPlusforSSP.esp
 LoversVoiceSSPplus.esp

Here you have LoversRapers, Joburg, LoversBed, . . .
Lovers with PK.esp

Here you have LoversBitch.esp, LoversCreature.esp, LoversSlaveTrader, . . .

<<<<<Now you can have no-Lovers-Mods, like SetBody, Race Mods, BetterCity >>>>> 

!!! No armor, clothes, quest, landscape,  Mods !  No no-Lovers-mods between the Lovers Mods !

Then this is the end of your load order
 LoversMB2.esp
 LoversPurification.esp (This mod)

Lovers3dorgasmMB2.esp  < here you can have
LoversIdleAnimsPriority.esp
Lovers3dorgasm.esp  < here you can have
 LoversAnimObjectsPriority.esp (These two go at the bottom of your load order)

 

 

You have Loves Mods after  LoversAnimObjectsPriority.esp  (this can prevent the Lovers mods from working) and many other Mods.  Maybe a Map-Mod after   LoversAnimObjectsPriority.esp is ok.

Your LoversMods are scattered throughout the load order.

And many other Mods wrong.

e.g.

MigMiscellanea.esp should be near the start of your load order, before DLCHorseArmor.esp.

Unique Landscapes  before Lovers/Tamago

Sensual Walks.esp near the end, after Race Mods and BetterCity

. . .

 

This is the most badly sorted load order I have seen in a long time, I call it a mess. If you had taken a quick look at the link I posted, you would have noticed it yourself.

An incorrect loading order can cause many errors, including some that you haven't anticipated. If your game is working well, then stick to your LO. But if errors occur, always consider that it could be due to the incorrect load order.

 

Yes, the lovers with PK-OBSE check have nothing to do with your load order.

 

---------------

The error is the Lovers with PK.esm OBSE check, if OBSE is installed. And the script says NO.  I have given you some reasons.

There are many other threads about the OBSE Check error.

e.g.

https://www.loverslab.com/topic/237057-lovers-with-pk-not-working-error-script-080090ea/

Usually it's xOBSE. Then use an older version. the  xOBSE 22.9.  version was OK. Or you the original OBSE21 version.

And people had problems after Windows 11 updates. Then you have to wait for the next update and a fix.

Unfortunately, people often do not post whether and how they fixed the error.  You can send a PM and ask.

Fortunately I don't have Windows 11 yet, and no Oblivion Steam version (still a disk version)

 

 

 

Edited by fejeena
Posted (edited)
2 hours ago, fejeena said:

Yes that is the right Load order, but . . .

 

LoversAdultPlayPlusforSSP.esp
 LoversVoiceSSPplus.esp
 Lovers with PK.esp
 LoversMB2.esp
 LoversPurification.esp (This mod)
 ------ (You may have other mods between here) ------  Must be " You may have other Lovers Mods between here"  !
 LoversIdleAnimsPriority.esp
 LoversAnimObjectsPriority.esp (These two go at the bottom of your load order)

 

----------------------------------

And you see it in all example load orders

see

https://www.loverslab.com/topic/4487-please-read-before-posting-here/

Or see BOSS load order ( download the Oblivion masterlist.txt )

 

esm

e.g. your esm in right order: (BOSS)

Oblivion.esm

SettlementsOfCyrodiil.esm 

Cobl Main.esm 

Waalx Animals & Creatures.esm 

Lovers with PK.esm 

MigMaster.esm

Av Latta Magicka.esm   I would place it here

 

<<<<<Now here  no-Lovers-Mods>>>>>

Then  you have all Tamago and Hiyoko mods

LoversAdultPlayPlusforSSP.esp
 LoversVoiceSSPplus.esp

Here you have LoversRapers, Joburg, LoversBed, . . .
Lovers with PK.esp

Here you have LoversBitch.esp, LoversCreature.esp, LoversSlaveTrader, . . .

<<<<<Now you can have no-Lovers-Mods, like SetBody, Race Mods, BetterCity >>>>> 

!!! No armor, clothes, quest, landscape,  Mods !  No no-Lovers-mods between the Lovers Mods !

Then this is the end of your load order
 LoversMB2.esp
 LoversPurification.esp (This mod)

Lovers3dorgasmMB2.esp  < here you can have
LoversIdleAnimsPriority.esp
Lovers3dorgasm.esp  < here you can have
 LoversAnimObjectsPriority.esp (These two go at the bottom of your load order)

 

 

You have Loves Mods after  LoversAnimObjectsPriority.esp  (this can prevent the Lovers mods from working) and many other Mods.  Maybe a Map-Mod after   LoversAnimObjectsPriority.esp is ok.

Your LoversMods are scattered throughout the load order.

And many other Mods wrong.

e.g.

MigMiscellanea.esp should be near the start of your load order, before DLCHorseArmor.esp.

Unique Landscapes  before Lovers/Tamago

Sensual Walks.esp near the end, after Race Mods and BetterCity

. . .

 

This is the most badly sorted load order I have seen in a long time, I call it a mess. If you had taken a quick look at the link I posted, you would have noticed it yourself.

An incorrect loading order can cause many errors, including some that you haven't anticipated. If your game is working well, then stick to your LO. But if errors occur, always consider that it could be due to the incorrect load order.

 

Yes, the lovers with PK-OBSE check have nothing to do with your load order.

 

---------------

The error is the Lovers with PK.esm OBSE check, if OBSE is installed. And the script says NO.  I have given you some reasons.

There are many other threads about the OBSE Check error.

e.g.

https://www.loverslab.com/topic/237057-lovers-with-pk-not-working-error-script-080090ea/

Usually it's xOBSE. Then use an older version. the  xOBSE 22.9.  version was OK. Or you the original OBSE21 version.

And people had problems after Windows 11 updates. Then you have to wait for the next update and a fix.

Unfortunately, people often do not post whether and how they fixed the error.  You can send a PM and ask.

Fortunately I don't have Windows 11 yet, and no Oblivion Steam version (still a disk version)

 

I saw you recommended OBSE 22.9 on a thread a while back when I was looking into this a few days ago. I went ahead and went from 22.11 back to 22.9 and it broke my game. I couldn't even load it at all. I saw that a rollback had helped others with similar errors, so I gave it a shot. Ultimately, I ended up with 22.12, hoping this would fix this issue, but it hasn't solved it either. So...I suppose I'll have to wait. I did notice that I ran into some issue with Skyrim and Pathfinder after I moved to W11, but all of my new gaming pc's came with it. I would've loved to had stayed with W10. Anyway, after setting this order and teaching LOOT, this is where it put those mods. Again, it seemed to be a working LO and it eliminated orange squares in Wrye Bash, a sign that things are in the right order. I'm reading green with a couple of yellow squares. This was in addition to following RotS mod guide. However, I'll standby and hope for a new OBSE update (probably a while since .12 is so fresh). In the meantime, I'll play around with my LO and see if some of your suggestions help. Thanks!

I just realized, the link you posted was the one I already checked out, which is why I had taken these steps the other day. I'm going to make some adjustments to my LO. So far, your recommendations hasn't harmed anything (didn't think the would anyway), but it hasn't fixed this. I am using the latest OBSE from silverlock for Steam copy. Installed per instructions, but I'm going to focus now on PK detecting OBSE. Something's happen with that. Would you like to know if I get this worked out?

Edited by StewDaddy1
More info
Posted

Yes tell me if you find a solution.

 

If OBSE works ( test it with ther OBSE Mods)  I would delete the OBSE check scripts in Lovers with PK.esm.  Why does it even exist?

It is mentioned in the requirements, and if someone doesn't install it, and Lovers doesn't work because of it, it's their own stupidity. So why the check?

So I would open the esm with the Construction set (started with OBSE !!!!, or the CS can not save scripts with OBSE commands and you "destroy" the esm ) Then delete the scripts .

Or much easier, use TES4Edit and delete the scripts

 

You must delete

scn xLoversCheckObse1QuestScript

scn xLoversCheckObse2QuestScript

and the quests

xLoversCheckObse1Quest

xLoversCheckObse2Quest

 

Here the Lovers with PK.esm without the OBSE check.

I tested  Lovers with PK.esp, there is no check/script that need the esm scripts or quests

Lovers with PK.7z

 

Posted

Ok, so that was an ordeal. Rearranging my LO with your suggestions caused additional CTDs. Zero idea why, as there seemed to be no conflicts or anything. Going back to my original LO stopped it. I don't doubt that your normally works, but whatever I have going on didn't like those changes, so I went back.

 

Deleting those scripts from the LPK .esm fixed those constant warning messages and subsequent CTDs, but it caused me some other CTDs with the following messages: 

 

2025/04/09 15:15:49  [005F404C] [WARNING]   Bishop doesn't have a NORMAL power attack animation to use for casting.
2025/04/09 15:15:49  [005F3FE0] [WARNING]   Bishop doesn't have a casting animation.
2025/04/09 15:15:49  [005F4016] [WARNING]   Bishop doesn't have a LEFT attack animation to use for casting.
2025/04/09 15:15:49  [005F404C] [WARNING]   Bishop doesn't have a NORMAL power attack animation to use for casting.

 

This pattern just repeated. It also rearranged my control keys. Casting caused attacks, walking did nothing, etc. Checking the control settings did nothing. The settings were correct, but the keys didn't match the mapping. 

 

All very interesting, but a bit annoying. It took me a while to reacquire the original LPK .esm and .esp, but Ihave them now. I'm going to try your script suggestion again, but this time I'm only going to remove script 2, since that's the one throwing my error. I'll let you know how it goes. 

 

Once again, thanks for even taken the time to help with this. This has been going on for about a week, and you're helping me by giving me some suggestions I hadn't thought of. I wanted to delete the scripts, but had no idea I could actually do it. 

 

Also, if it matters, I only try removing the scripts with TES4Edit.

Posted

Yes with TES4Edit is OK. I also did it with TES4Edit.

 

The new errors have nothing to do with the removed Loves script. It can not affect fighting animations.

Bishop is not a vanilla NPC. Must be a mod NPC. Remove the Mod with Bishop. Or check if you have all files/Requirements installed.

Maybe the same Mod messed up your keys.

 

And sorting load order. You started a new game? You can not use an old save with saved errors . Always start a new game for testing. If the game works you can try old saves ( and maybe a old save works)  But your load order must be completely re-sorted, you have to start a new game, no old save will work.

 

---------------------

And have you tried a new game without most of your mods? 

Install  OBSE, Pluggy, Elys Universal Silent Voice , MenuQue. Fast Exit2 OR Stutter remover (Stutter Remover has a exit fix )

Test your game

Use the 4GB patcher and test your game

Install body replacers, BBB armor/clothing replacer and BBB animation and Growlf's Universal skeleton ( the controllable version, not the total controllable version . Later it will be overwritten by the LAPF skeleton )

Test your game.

Only if it worky you start with Lovers. LAPF and 1-2 Mod. NOT all at once !  Let LAPF overwrite the skeletons !  Then test.

Never install all you want at once, you don't know when and where you made a mistake and it is almost impossible to find it.

Install more Lovers Mods or other mods. Only 2-3-4 and then test. If you get a problem you know  one of the recently installed mods is to blame. And you can delete and then install and test one by one.

 

Posted

Bishop is my pc, but that was just a glitch. Going back to a previous save didn't help. It did help when directly loading to a previous save at start up. I removed script2 and it did stop those constant checks and messages. I appreciate your help. I'll try your other suggestions as well. I appreciate you.

Posted

????  Never load another save during the game !!!!  This has been known since 2006.  Scripts are still running, commands like “Free Camera” or “No Collision” are still active.

You have to quit the game and then start and load a save.

Loading in-game is the best way to corrupt your save file! If you encounter an error and load without exiting the game, the error will persist and be copied to your next save.

Really, never do that!  Especially if you have glitches, problems, or graphic errors, you copy these (or remnants of them) into your save file the next time you save.

When I die, I never click "load an old save", I always quit the game and start again.

 

Only if I die in real life will I try to load an old save.  :classic_wink:

Posted (edited)

I'm not sure which version on Pluggy I should be using. The most recent versions have lower version numbers than the original and the description even says that it's probably safer than the others. How do I know if my mods require Pluggy?

 

Btw, your guidance in your last post is much appreciated. I didn't even know most of that stuff.

Edited by StewDaddy1
Posted (edited)

Pluggy  132 or 125c 

I use  125c  , I have 3 save files: ...ess ; ...obse ; ...pluggy

Version 132 saves in 2 files:  ...ess and ...obse

ess in the vanilla save file

obse is ... yes the obse save

and pluggy use a own save file, but with 132 and newer it stores its data in the OBSE file.

 

You know the A Bomb fix  ? mentioned in my yellow Link. The game slows down, and all effects are very slow. For example, fireballs fly very slowly, secret doors take over a minute to start moving, and a few more minutes to open.

I use Oblivion Animation fixer (OAF) but it only works with the 3 save files, so you need Pluggy 125c

With Pluggy 132 (two save files) you can fix the A Bomb with WryeBash . But I don't use WryeBash.

 

I think Lovers needs it for ini files. Not to read them but to write. Lovers rapers or Lovers Joburg writes ini.  And in scripts.

From Pluggy page:  . . .  string, array, ini and text file creation and manipulation.

----------------------------------------

 

And an addendum to "save without quit the game"

Also if player controls are turned off (e.g. during sex) and you load a save, then the player controls are still turned off.

They are not reset, they are not part of the save, they are a game setting that remains until you turn them off (console or script) or quit the game.

And you think the game has a bug, a mod is crazy and start looking for the error.

 

It was very scary when I had Collision off or Free Camera on (don't remember exactly)  and loaded a save. I was floating in the void or so far above the ground that I didn't see it. So not at all the place where my player was when I saved. And thought something serious had broken my game.

 

So always remember, Oblivion doesn't reset everything when you load a save in the game.

 

Edited by fejeena

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...