xOBSE

[Ceimnithe]

I know there was already a thread here about the console throwing script errors over xOBSE a year or so ago but I'm making a new one because it's old 😛

 

Some of my mods require xOBSE and I'd prefer to play with them with the Lovers mods installed, so I'm hoping for a solution. But if the LPK mods are just fundamentally not able to run with xOBSE versions then I won't shit myself, I'll take the L.

I followed install instructions (right now I only have the LPK base package installed, wanted to start slow) and load order instructions from fejeena, I believe. I can post my LO if needed, but that shit is a nightmare. I play with about 280 mods (when not imported). All LPK mods not imported and loaded after, as per instructions.

I use MO2 and Steam. Any help is appreciated 💀

 

[tda4]

5 hours ago, Ceimnithe said:

I know there was already a thread here about the console throwing script errors over xOBSE a year or so ago but I'm making a new one because it's old 😛

 

Some of my mods require xOBSE and I'd prefer to play with them with the Lovers mods installed, so I'm hoping for a solution. But if the LPK mods are just fundamentally not able to run with xOBSE versions then I won't shit myself, I'll take the L.

I followed install instructions (right now I only have the LPK base package installed, wanted to start slow) and load order instructions from fejeena, I believe. I can post my LO if needed, but that shit is a nightmare. I play with about 280 mods (when not imported). All LPK mods not imported and loaded after, as per instructions.

I use MO2 and Steam. Any help is appreciated 💀

 

There's practically nothing in these scripts.(There are no exotic operators or commands. (Although, I use the old LPK. I don't think it's critical in this case))

 

Are you sure that the master is higher in the loading order than the ESP (base LPK)?
For Oblivion, the loading order is determined by the DATE of the file creation, and not by the order file, as for Skyrim.

also *Oblivion.esm - must have the earliest creation date

 

 

Edited September 10, 2024 by tda4

[Ceimnithe]

Yeah, the ESM is loaded higher. I use LOOT to sort my load order and it's always worked good. Oblivion.esm is loaded first.

 

I haven't actually checked to see if anything works, I just saw these messages first and figured there was a big problem. 

Here's my LO if you want to look. I felt like I did it right, but I could be wrong.

AAAAAAA.txt

Edited September 10, 2024 by Ceimnithe

[LongDukDong]

Allow me to throw my two cents in here...

 

First, I know that Fejeena would point out not to use LOOT to sort load orders, particularly the load orders of Lovers mods.  Just don't.  It doesn't sort them properly.  He would suggest you look at the recommended load order documents within the topic his and my signatures would point.

 

HOWEVER...

 

I was asked to look at an old Lovers mod, LoversTachiCat2, which did not work with the requester's copy of xOBSE.  I found that the only OBSE commands within LoversTachiCat2 were merely these I am presenting here, including what version of OBSE they were created/updated: sv_Construct (OBSE16),  GetName (OBSE16), IsControlPressed (OBSE13).

 

There is absolutely nothing wrong with any of these OBSE commands within LoversTachiCat2.  

 

The code within LoversTachiCat2 had a fair amount of incorrectly machine-translated  comments originally in Japanese (and thus became garbage).  And when I replaced the poorly translated garbage comments  with actual English translations, the person who asked me to look at LoversTachiCat2 said the revision with the re-translation worked. In the edition I sent him, it was nothing but a change/replacement of comments that allowed an old Lovers mod that did not work with xOBSE to finally function.

 

Oh, I have since made my own version of TachiCat2, but that's separate thing.

 

Strange as it sounds, I have to suggest that xOBSE had issues with the comments, and those alone within TachiCat2.

 

Meanwhile, I hereby ask... Are you using xOBSE 22.8 or 22.10?   Even in the xOBSE 'posts' tab in Nexus, there are suggestions that those two versions have been problematic.

[Sladen2019]

The error in the picture is just an OBSE detection error. It does not mean LAPF is totally broken. It just doesnt recognize the version that is installed. I use the latest version of xOBSE 22.10 and I did have an issue with TachiCat2 which caused the game to crash when the Target spell was cast on a NPC. He fixed it. That is the only mod I had a serious problem with. I use a number of LAPF mods and the only other issue I have at the moment, which I suspect is related to xOBSE 22.10 is with Lovers Slave Trader Dukky version. The slaves do not rise in rank as they normally should. I used a console command to give my player character Rank 5 Trainer and still had the issue. They simply stay at level -1. I use the console now to give them Rank 5. I suggest sticking with xOBSE so you can use the mods you want and simply live with any issues that pop up with Lovers mods. You can always try an older vesion of xOBSE and also hope the next version fixes whichever issue you are having.

[LongDukDong]

41 minutes ago, Sladen2019 said:

I use the latest version of xOBSE 22.10 and I did have an issue with TachiCat2 which caused the game to crash when the Target spell was cast on a NPC. He fixed it. T

It is true, Sladen was the individual that asked me to look into TachiCat.  And I found that the only three OBSE commands that 'could' have been at issue are still relevant.  I changed out the comments with my own... and *shrugs* put in a couple extra touches.  Not as extensive as what I released. 

 

I do find it hilarious that the XOBSE page at Nexus has no 'bugs' tab to report issues, but all issues are within the 'posts' tab.  And the top of the posts tab states:
 

Quote

 

15 June, 2023

xOBSE 22.9 Released. This release solve various issues as MOO duplicated items, Realtime Interactions name discovery,  Take or Equip crash, Break Armor malfunctioning  (either with itself or with Take or Equip) ,various instabilities.

 

https://www.nexusmods.com/oblivion/mods/37952?tab=posts&BH=1

 

It is further down you see those with issues with 22.10.  And good luck if you want to use MenuQue according to an August 2, 2024 complaint.


 

Edited September 10, 2024 by LongDukDong

[Sladen2019]

24 minutes ago, LongDukDong said:

It is further down you see those with issues with 22.10.  And good luck if you want to use MenuQue according to an August 2, 2024 complaint.

I have no issues with MenuQue. I suspect a large amount of the reported issues are from users who do not know how to install xOBSE correctly. Such as using the Steam loader with the GOG version and not knowing how to install mods manually and not knowing how to use such managers as Vortex and MO2. Alot of them are one liners with no further explanation and no more replies to any questions asked to them. This happens with almost all mods and Nexus users in general.

Edited September 10, 2024 by Sladen2019

[Ceimnithe]

Hoo boy okay
 

4 hours ago, LongDukDong said:

First, I know that Fejeena would point out not to use LOOT to sort load orders, particularly the load orders of Lovers mods.  Just don't.  It doesn't sort them properly.  He would suggest you look at the recommended load order documents within the topic his and my signatures would point.

I did look at their guide and find where all the lovers mods were in relation to each other, and edited their priority manually. I figured as long as I manually edit the load order every time I install a lovers mod, it should be okay? I would absolutely hate to not use LOOT, I've been using it for years for my games (after the death of BOSS) and it's been a staple for me.

 

 

4 hours ago, LongDukDong said:

Meanwhile, I hereby ask... Are you using xOBSE 22.8 or 22.10?   Even in the xOBSE 'posts' tab in Nexus, there are suggestions that those two versions have been problematic.

xOBSE 22.10, I download from GitHub. So far I, at least, have not run into any issues. Not with MenuQue either. Like Sladen said, nexus user skill issue 💀

 

2 hours ago, Sladen2019 said:

The error in the picture is just an OBSE detection error. It does not mean LAPF is totally broken. It just doesnt recognize the version that is installed

Okay so what I'm gathering from all of this is that it should be fine to simply ignore these errors? Like you mentioned, I'm sure there will be small issues but I'll work around them (or come back here to bitch about it) as I go I suppose.

 

I'll run a test on actually playing the mod once everybody in the house is asleep, and return with the results 😜 thank you guys for the snappy responses, LL is SO much more helpful than Nexus when it comes to this kind of shit.

[Sladen2019]

If you know how to adjust load order to your preferences using LOOT, then there is no problem with it. Both LOOT and Boss are just load order sorters. Both do the same thing. Only advantage to BOSS is it does a better job at sorting Lovers mods with its default master list. It would still need some adjustments. LOOT has the advantage of being newer and having newer mods sorted better. It also has the advantage of automatically adding modern Bash Tags to mods. BOSS still does get some updates to its masterlist, but very rarely lately.

[Ceimnithe]

Yeah everything works just fine. Sorry for the nothing sandwich of a problem. Thanks for the help though! I appreciate the advice. 

[fejeena]

Yes I couldn't resist saying something about LOOT.

 

Spoiler

During the 10 years of LOOT it was said again and again that LOOT fixed the problems with Oblivion. !!!! I'm not talking about Lovers Mods !!!!
People said they used LOOT and it worked great, but they had a problem and then posted their load order... and it was a mess.
People said I was talking bullshit, LOOT works great with Oblivion. ... and their load order was a mess.
People called me a nutcase... and in one of those LOOT load orders LOOT had positioned a master file below the plugin (was no Lovers Mod)

So what should I do with a tool that requires me to re-sort everything? ( again I don't talk about Lovers Mods )

 

Most people are just lazy and want to use LOOT for that reason.
Because with BOSS there are always mods that are not in the BOSS "oblivion masterlist.txt". The BOSS tool creates a message at the end and says which mods have been placed unsorted at the end of the load order and that you have to sort them manually.  ( And LOOT sorts all mods... even if it does it wrong )
But many people ignore the BOSS message you get at the end. ( You can enter the unknown mods in the "oblivion masterlist.txt" and then you never have to sort them manually again )
And if you keep old load order lists like I do, you don't need the BOSS tool at all. With a new game you know where the standard mods are placed, others you look in the old lists or search in the "oblivion masterlist.txt" with notepad++.

 

You can also make changes manually in LOOT and save them so that you don't have to do it again.
I don't know if you can insert/load the entire "oblivion masterlist.txt" into LOOT. (too much work)

 

And I don't know if LOOT respects exceptions.
In the "oblivion masterlist.txt" there are entries like...
If file Mod XY : Mod AA ( if you have Mod xy installed/activated load Mod AA here )
And further down in the loader you will find
Ifnot file Mod xy : Mod AA ( if you have not Mod xy installed/activated load Mod AA here )

 

And entries about:
Bash TAG
outdated version ... or included in mod xxx
Requirements. That you need masterfile yyy at least version 4.3
Needs TES4Edit cleaning  ( e.g. all DLC should be cleaned (except the empty DLCShiveringIsles.esp )
And errors

 

In all 10 years and 5 months LOOT, I have not seen a single correct LOOT load order.
It would be a great pleasure and surprise for me to see one. 

One can still dream. One day when...

Spoiler

 

 

 

[ruziy]

By the way.  It seems that the problem is not in xOBSE, but in the script itself:

 

scn xLoversCheckObse2QuestScript

short ObseNotFound

Begin GameMode
	if ObseNotFound
		set ObseNotFound to 0
		MessageBox "Lovers requires OBSE to run! You didn't read the instructions, did you?"
		Message "Lovers requires OBSE to run! You didn't read the instructions, did you?"
	endif
End

 

I'm not a real modder, but it seems that in this form the interpreter perceives "ObseNotFound" as a function, not a variable.

 

P.S. For verification, I changed (in the most barbaric way: just open the esm file in mcedit) the suspicious string to "(ObseNotFound)" and "ObseNotFound == 1". In both cases, the spam "Unable to find function definition" has stopped, but I can't say whether the mod has retained its functionality (of the adult mods, I currently install only BBB and LAPF).

[fejeena]

LAPF is from 2013 and there was ( and is) no problem with OBSE, the scripts  xLoversCheckObse1QuestScript   and   xLoversCheckObse2QuestScript  worked all the years.

The OBSE check is in script 1 a OBSE command "GetOBSEVersion"  and it set the short "ObseNotFound" in quest script 2

So ObseNotFound is just a word, cound be "HaveCheckedOBSE" or "Done" or "Checked" or "A" . It is no a variable

 

If you only have BBB and LAPF why do you use xOBSE ? Install OBSE21 and you will see no message.

You may see the message if you have installed your game in C : / Program files  and OBSE /xOBSE does not work right, Then it is not an OBSE problem, but a wrongly installed game.