ljacquard Posted February 28, 2015 Posted February 28, 2015 Using the latest version of LAPF here Oblivion 120461 - Steam OBSE v2.1 OBSE: initialize (version = 21.4 010201A0) <Lovers with PK.esm> has two scripts :scn xLoversCheckObse1QuestScriptscn xLoversCheckObse2QuestScript From what I gather (please keep in mind that I am no TES4 script guru), one is to detect if OBSE is running, and the second one is to throw a warning message in English if it's not.Usually, I couldn't care less, but <MessageLogger> hooks handlers from the game which repeatedly complains every 5 seconds about a missing function definition : 2015/02/18 14:48:30 [005170B1] [WARNING] Unable to find function definition for command 0 in script 'xLoversCheckObse2QuestScript'.2015/02/18 14:48:35 [005170B1] [WARNING] Unable to find function definition for command 0 in script 'xLoversCheckObse2QuestScript'.2015/02/18 14:48:40 [005170B1] [WARNING] Unable to find function definition for command 0 in script 'xLoversCheckObse2QuestScript'.2015/02/18 14:48:45 [005170B1] [WARNING] Unable to find function definition for command 0 in script 'xLoversCheckObse2QuestScript'.2015/02/18 14:48:50 [005170B1] [WARNING] Unable to find function definition for command 0 in script 'xLoversCheckObse2QuestScript'.2015/02/18 14:48:55 [005170B1] [WARNING] Unable to find function definition for command 0 in script 'xLoversCheckObse2QuestScript'.2015/02/18 14:49:00 [005170B1] [WARNING] Unable to find function definition for command 0 in script 'xLoversCheckObse2QuestScript'.2015/02/18 14:49:05 [005170B1] [WARNING] Unable to find function definition for command 0 in script 'xLoversCheckObse2QuestScript'.2015/02/18 14:49:10 [005170B1] [WARNING] Unable to find function definition for command 0 in script 'xLoversCheckObse2QuestScript'.2015/02/18 14:49:15 [005170B1] [WARNING] Unable to find function definition for command 0 in script 'xLoversCheckObse2QuestScript'.2015/02/18 14:49:20 [005170B1] [WARNING] Unable to find function definition for command 0 in script 'xLoversCheckObse2QuestScript'.2015/02/18 14:49:25 [005170B1] [WARNING] Unable to find function definition for command 0 in script 'xLoversCheckObse2QuestScript'.2015/02/18 14:49:30 [005170B1] [WARNING] Unable to find function definition for command 0 in script 'xLoversCheckObse2QuestScript'.2015/02/18 14:49:35 [005170B1] [WARNING] Unable to find function definition for command 0 in script 'xLoversCheckObse2QuestScript'.2015/02/18 14:49:40 [005170B1] [WARNING] Unable to find function definition for command 0 in script 'xLoversCheckObse2QuestScript'.2015/02/18 14:49:45 [005170B1] [WARNING] Unable to find function definition for command 0 in script 'xLoversCheckObse2QuestScript'.2015/02/18 14:49:50 [005170B1] [WARNING] Unable to find function definition for command 0 in script 'xLoversCheckObse2QuestScript'.2015/02/18 14:49:55 [005170B1] [WARNING] Unable to find function definition for command 0 in script 'xLoversCheckObse2QuestScript'.2015/02/18 14:50:00 [005170B1] [WARNING] Unable to find function definition for command 0 in script 'xLoversCheckObse2QuestScript'. I would like to fix issues if they appear in my error log, to keep it as tidy as possible (which in turn helps spotting new issues). One option I have is to disable said scripts in <Lovers with PK.esm>. Another one is to ask for your insight, and ideally an official fix. I would much prefer the second one if you had some time. Thank you.
gregathit Posted February 28, 2015 Posted February 28, 2015 I take it that you are absolutely sure that OBSE is properly running? If so, the try PM'ing WappyOne and see if it is something he can ferret out script wise. It may be that with OBSE 21 that the LAPF script can't properly detect OBSE (could be something minor was changed just enough to break things). I am still running version 20 and I have never noticed errors like that.
ljacquard Posted March 1, 2015 Author Posted March 1, 2015 I take it that you are absolutely sure that OBSE is properly running? If so, the try PM'ing WappyOne and see if it is something he can ferret out script wise. It may be that with OBSE 21 that the LAPF script can't properly detect OBSE (could be something minor was changed just enough to break things). I am still running version 20 and I have never noticed errors like that. Thank you for your reply, Greg. I am 100% certain that my OBSE is correctly installed (all the logs tell me so). It's running in-game, and it's acknowledged by all my mods that depend on OBSE. LAPF and submods for example work fine (well, except the game engine spam which I would like to reduce). At this point, I don't want to bother Wappy for such a minor annoyance. I will comment out the <xLoversCheckObse2QuestScript> script and see how it goes from there (*crossing fingers*). Hopefully, this can be replicated by other users, and fixed in a future version of LAPF (or OBSE).
gregathit Posted March 1, 2015 Posted March 1, 2015 There is no reason that commenting that out should break anything. It shouldn't be anything more than just checking to see if OBSE is running. I'm curious if this is just an OBSE 21 issue or has it been spitting errors with version 20 as well. That would help narrow down what to look at and for.
ljacquard Posted March 1, 2015 Author Posted March 1, 2015 Will do the test and report back with my findings.
ljacquard Posted March 4, 2015 Author Posted March 4, 2015 Back with some results, as I said I would. I chose to disable the following quests : - <xLoversCheckObse1Quest> - <xLoversCheckObse2Quest> and have had no further warnings from the game. I am not certain that these quests should be running every 5 seconds after initialisation, so adding a "stopquest" might be something to look into for a future version of LAPF. However, this is not my decision to take, of course. I also did the test with OBSE v20, and still had the same warning appearing. So maybe is it the fact that I own a Steam version of the game ? I am content with what I have right now, and thank you again for your advice, which allowed me not to break anything with personal "fixes".
Slammer64 Posted March 4, 2015 Posted March 4, 2015 There are known problems with OBSE and the Steam version of Oblivion, it's a long standing issue that most likely will never be resolved.
gregathit Posted March 5, 2015 Posted March 5, 2015 I've tried to replicate the issue with OBSE v20 and my non-steam game and can't. I guess as Slammer64 stated, it is just one of those things we might have to just chalk up to the Steam version of the game and live with.. The check is merely a troubleshooting one, so disabling the two scripts is side effect free. Might be something we just disable permanently, as it is easy enough to spot someone who is trying to run the game without OBSE enabled.
Recommended Posts
Archived
This topic is now archived and is closed to further replies.