Screwball Posted February 7, 2014 Share Posted February 7, 2014 [02/07/2014 - 01:27:24PM] Info: ERROR: Bard actor is invalid. Please report this error to the USKP team for investigation.stack: <unknown self>.Debug.TraceStack() - "<native>" Line ? [ (0006E5AE)].SF_BardSongsInstrumentalFlute_0006E5AE.Fragment_15() - "SF_BardSongsInstrumentalFlute_0006E5AE.psc" Line 56 [02/07/2014 - 01:59:07PM] Info: ERROR: Bard actor is invalid. Please report this error to the USKP team for investigation.stack: <unknown self>.Debug.TraceStack() - "<native>" Line ? [ (0006E5AE)].SF_BardSongsInstrumentalFlute_0006E5AE.Fragment_15() - "SF_BardSongsInstrumentalFlute_0006E5AE.psc" Line 56Load Order:- Update.esmUSKP (2.0.1 Beta, Feb 1st)SBBasement.esmno killmoves, no killcams, no killbites.esp(Note to self. Game14Logs\Papyrus.0038.log) Papyrus.0038.log.zip Link to comment Share on other sites More sharing options...
tyrel68 Posted February 7, 2014 Share Posted February 7, 2014 Wait it actually says for the USKP team to investigate in the log???? WTF Link to comment Share on other sites More sharing options...
VaultDuke Posted February 7, 2014 Share Posted February 7, 2014 why does this confuse you? i bet the script in question has been worked upon by the uskp already and they put some messages inside that would appear in the log. they probably knew there were still issues with the script but couldn't pin point the source yet. so this solution was chosen to maximize the amount of data that would be sent in for the problem. you didn't think it was bethesda being lazy, did you? now that would be epic Link to comment Share on other sites More sharing options...
Screwball Posted February 7, 2014 Author Share Posted February 7, 2014 That was my assumption. It says report it - so I have (and added the log for for good measure). p.s. @ Beth putting that in there Link to comment Share on other sites More sharing options...
VaultDuke Posted February 7, 2014 Share Posted February 7, 2014 it's better to upload the savegame as well Link to comment Share on other sites More sharing options...
Screwball Posted February 7, 2014 Author Share Posted February 7, 2014 Done Link to comment Share on other sites More sharing options...
NightStar Posted February 7, 2014 Share Posted February 7, 2014 That's a message we've added to some troublesome scripts. We've done it because we know for a fact that the script in question is not working properly or it's producing errors under certain circumstances and we'd like to get more information on how the error occurs in order to be able to fix it. Hence the use of stack trace. Thanks for reporting it! Link to comment Share on other sites More sharing options...
Arthmoor Posted February 7, 2014 Share Posted February 7, 2014 Unfortunately the result I was hoping for from that didn't pan out. I was trying to determine how that scene was being called and thought a stack trace would do the trick but apparently not since it generated the same data the original error was giving. Link to comment Share on other sites More sharing options...
Screwball Posted February 7, 2014 Author Share Posted February 7, 2014 Shame it didn't help, but at least you know your debugs are working, well, executing. What's so different about that guy and all the orther (NPC) wilderness encounters? Comparing their scripts shouldn't be difficult, quests more so but not (I would guess) impossible. Might shed some light on why he's such a PITA. Link to comment Share on other sites More sharing options...
Arthmoor Posted February 7, 2014 Share Posted February 7, 2014 That's what we were hoping to find out is which guy is causing that. The error never says because the scene fragment alias was not filled. So we were hoping to see the function calls higher up on the stack but it appears as though the scene tried to trigger itself directly. Which should not even be possible. Link to comment Share on other sites More sharing options...
BlackPete Posted February 7, 2014 Share Posted February 7, 2014 I had thought that Talsgar the Wanderer was the culprit for this issue (#14380), because it says his name in the script. I wonder if it's the same guy still causing the problem? Talsgar = Link to comment Share on other sites More sharing options...
Screwball Posted February 8, 2014 Author Share Posted February 8, 2014 Pretty sure it was him, although I didn't get close enough to talk to him, I recognised his attire from a distance. Link to comment Share on other sites More sharing options...
BlackPete Posted February 8, 2014 Share Posted February 8, 2014 Pretty sure it was him, although I didn't get close enough to talk to him, I recognized his attire from a distance. Interestingly, you don't even have to get close to him (or talk to him) for these errors to show up in your log. All that really needs to happen is for the WEDL01 encounter to spawn in the cell that you're in. From personal experience it's quite easy to not realize that the encounter has spawned, which seems to be a bit too often with that guy. Link to comment Share on other sites More sharing options...
Screwball Posted February 8, 2014 Author Share Posted February 8, 2014 I know Many times I've had the original WEDL01 errors without seeing anyone at all. On this occasion though I was actually close enough to recognise him, but only on one of the two occasions in the log i.e. I only saw him once but the 2 USKP "Info" lines are half-an-hour apart (real time). Link to comment Share on other sites More sharing options...
Screwball Posted February 8, 2014 Author Share Posted February 8, 2014 Bit more info - just had a whole bunch of errors, starting with "report to USKP team", centered on SF_BardSongsInstrumentalFlute_0006E5AE.psc. No reference to WEDL01 this time. [02/08/2014 - 01:48:25PM] Info: ERROR: Bard actor is invalid. Please report this error to the USKP team for investigation.stack: <unknown self>.Debug.TraceStack() - "<native>" Line ? [ (0006E5AE)].SF_BardSongsInstrumentalFlute_0006E5AE.Fragment_16() - "SF_BardSongsInstrumentalFlute_0006E5AE.psc" Line 11[02/08/2014 - 01:48:26PM] Info: ERROR: Bard actor is invalid. Please report this error to the USKP team for investigation.stack: <unknown self>.Debug.TraceStack() - "<native>" Line ? [ (0006E5AE)].SF_BardSongsInstrumentalFlute_0006E5AE.Fragment_0() - "SF_BardSongsInstrumentalFlute_0006E5AE.psc" Line 41[02/08/2014 - 01:48:26PM] error: Cannot call IsDead() on a None object, aborting function callstack: [bardSongs (00074A55)].bardsongsscript.PlaySong() - "BardSongsScript.psc" Line 282 [ (0006E5AE)].SF_BardSongsInstrumentalFlute_0006E5AE.Fragment_0() - "SF_BardSongsInstrumentalFlute_0006E5AE.psc" Line 45[02/08/2014 - 01:48:26PM] warning: Assigning None to a non-object variable named "::temp10"stack: [bardSongs (00074A55)].bardsongsscript.PlaySong() - "BardSongsScript.psc" Line 282 [ (0006E5AE)].SF_BardSongsInstrumentalFlute_0006E5AE.Fragment_0() - "SF_BardSongsInstrumentalFlute_0006E5AE.psc" Line 45[02/08/2014 - 01:48:26PM] error: Cannot call Is3DLoaded() on a None object, aborting function callstack: [bardSongs (00074A55)].bardsongsscript.PlaySong() - "BardSongsScript.psc" Line 287 [ (0006E5AE)].SF_BardSongsInstrumentalFlute_0006E5AE.Fragment_0() - "SF_BardSongsInstrumentalFlute_0006E5AE.psc" Line 45[02/08/2014 - 01:48:26PM] warning: Assigning None to a non-object variable named "::temp10"stack: [bardSongs (00074A55)].bardsongsscript.PlaySong() - "BardSongsScript.psc" Line 287 [ (0006E5AE)].SF_BardSongsInstrumentalFlute_0006E5AE.Fragment_0() - "SF_BardSongsInstrumentalFlute_0006E5AE.psc" Line 45[02/08/2014 - 01:49:27PM] Info: ERROR: Bard actor is invalid. Please report this error to the USKP team for investigation.stack: <unknown self>.Debug.TraceStack() - "<native>" Line ? [ (0006E5AE)].SF_BardSongsInstrumentalFlute_0006E5AE.Fragment_15() - "SF_BardSongsInstrumentalFlute_0006E5AE.psc" Line 56[02/08/2014 - 01:50:01PM] Info: ERROR: Bard actor is invalid. Please report this error to the USKP team for investigation.stack: <unknown self>.Debug.TraceStack() - "<native>" Line ? [ (0006E5AE)].SF_BardSongsInstrumentalFlute_0006E5AE.Fragment_16() - "SF_BardSongsInstrumentalFlute_0006E5AE.psc" Line 11[02/08/2014 - 01:50:02PM] Info: ERROR: Bard actor is invalid. Please report this error to the USKP team for investigation.stack: <unknown self>.Debug.TraceStack() - "<native>" Line ? [ (0006E5AE)].SF_BardSongsInstrumentalFlute_0006E5AE.Fragment_0() - "SF_BardSongsInstrumentalFlute_0006E5AE.psc" Line 41[02/08/2014 - 01:50:02PM] error: Cannot call IsDead() on a None object, aborting function callstack: [bardSongs (00074A55)].bardsongsscript.PlaySong() - "BardSongsScript.psc" Line 282 [ (0006E5AE)].SF_BardSongsInstrumentalFlute_0006E5AE.Fragment_0() - "SF_BardSongsInstrumentalFlute_0006E5AE.psc" Line 45[02/08/2014 - 01:50:02PM] warning: Assigning None to a non-object variable named "::temp10"stack: [bardSongs (00074A55)].bardsongsscript.PlaySong() - "BardSongsScript.psc" Line 282 [ (0006E5AE)].SF_BardSongsInstrumentalFlute_0006E5AE.Fragment_0() - "SF_BardSongsInstrumentalFlute_0006E5AE.psc" Line 45[02/08/2014 - 01:50:02PM] error: Cannot call Is3DLoaded() on a None object, aborting function callstack: [bardSongs (00074A55)].bardsongsscript.PlaySong() - "BardSongsScript.psc" Line 287 [ (0006E5AE)].SF_BardSongsInstrumentalFlute_0006E5AE.Fragment_0() - "SF_BardSongsInstrumentalFlute_0006E5AE.psc" Line 45[02/08/2014 - 01:50:02PM] warning: Assigning None to a non-object variable named "::temp10"stack: [bardSongs (00074A55)].bardsongsscript.PlaySong() - "BardSongsScript.psc" Line 287 [ (0006E5AE)].SF_BardSongsInstrumentalFlute_0006E5AE.Fragment_0() - "SF_BardSongsInstrumentalFlute_0006E5AE.psc" Line 45 Link to comment Share on other sites More sharing options...
Arthmoor Posted February 8, 2014 Share Posted February 8, 2014 The only way I can figure on the bard actor becoming invalid is is they're dead or deleted. So yes, Talsgar looks like the likely candidate. Your earlier log also gave a clue as to how that might happen since WEDL01 popped in the log beforehand. WEDL01a had the same issue, with the same solution. The stage 100 cal was on a delayed stack but you could have long since left Talsgar behind and caused him to get unloaded and purged before it continued. It's just a hunch, but one worth pursuing. Here's to hoping it won't pop up again after go-live. Link to comment Share on other sites More sharing options...
Screwball Posted February 8, 2014 Author Share Posted February 8, 2014 Many, though not all, of my recent logs have the above errors (the BardSongsInstrumentalFlute one(s)). Persistent so-and-no isn't he? Link to comment Share on other sites More sharing options...
BlackPete Posted February 8, 2014 Share Posted February 8, 2014 Many, though not all, of my recent logs have the above errors (the BardSongsInstrumentalFlute one(s)). Persistent so-and-no isn't he? The original error that I reported (#14380) was quite inconsistent as to when it appeared in my log (as Screwball is describing with the latest one), so I'm not really surprised that this "new" error is acting the same way. Link to comment Share on other sites More sharing options...
BlackPete Posted February 9, 2014 Share Posted February 9, 2014 New or very similar error after installing the newly released USKP (v. 2.0.1). The change log said that the fix for bug #14380 was retroactive, so I'm thinking this might need a new tracker issue added unless someone believes that the fix was non-retroactive. [02/09/2014 - 12:57:42AM] error: (FF002A99): has no AI process, so no idle can be played.. stack: [ (FF002A99)].WETalsgarTheWandererDeathScript.PlayIdle() - "<native>" Line ? [ (0006E5AE)].SF_BardSongsInstrumentalFlute_0006E5AE.Fragment_15() - "SF_BardSongsInstrumentalFlute_0006E5AE.psc" Line 54 [02/09/2014 - 12:58:36AM] error: (FF002A99): has no AI process, so no idle can be played.. stack: [ (FF002A99)].WETalsgarTheWandererDeathScript.PlayIdle() - "<native>" Line ? [ (0006E5AE)].SF_BardSongsInstrumentalFlute_0006E5AE.Fragment_16() - "SF_BardSongsInstrumentalFlute_0006E5AE.psc" Line 9 [02/09/2014 - 12:58:36AM] error: (FF002A99): has no AI process, so no idle can be played.. stack: [ (FF002A99)].WETalsgarTheWandererDeathScript.PlayIdle() - "<native>" Line ? [ (0006E5AE)].SF_BardSongsInstrumentalFlute_0006E5AE.Fragment_0() - "SF_BardSongsInstrumentalFlute_0006E5AE.psc" Line 39 [02/09/2014 - 12:58:36AM] error: (FF002A99): has no AI process, so no idle can be played.. stack: [ (FF002A99)].WETalsgarTheWandererDeathScript.PlayIdle() - "<native>" Line ? Link to comment Share on other sites More sharing options...
Screwball Posted February 9, 2014 Author Share Posted February 9, 2014 [02/09/2014 - 11:52:05AM] error: (FF000D2D): has no AI process, so no idle can be played.. stack: [ (FF000D2D)].WETalsgarTheWandererDeathScript.PlayIdle() - "<native>" Line ? [ (0006E5AE)].SF_BardSongsInstrumentalFlute_0006E5AE.Fragment_15() - "SF_BardSongsInstrumentalFlute_0006E5AE.psc" Line 54 [02/09/2014 - 11:52:49AM] error: (FF000D2D): has no AI process, so no idle can be played.. stack: [ (FF000D2D)].WETalsgarTheWandererDeathScript.PlayIdle() - "<native>" Line ? [ (0006E5AE)].SF_BardSongsInstrumentalFlute_0006E5AE.Fragment_16() - "SF_BardSongsInstrumentalFlute_0006E5AE.psc" Line 9 [02/09/2014 - 11:52:49AM] error: (FF000D2D): has no AI process, so no idle can be played.. stack: [ (FF000D2D)].WETalsgarTheWandererDeathScript.PlayIdle() - "<native>" Line ? [ (0006E5AE)].SF_BardSongsInstrumentalFlute_0006E5AE.Fragment_0() - "SF_BardSongsInstrumentalFlute_0006E5AE.psc" Line 39 I'm getting them too, with USKP 2.0.1 (release). Link to comment Share on other sites More sharing options...
Arthmoor Posted February 9, 2014 Share Posted February 9, 2014 Well at least those trace logs have identified the responsible party. Link to comment Share on other sites More sharing options...
BlackPete Posted February 9, 2014 Share Posted February 9, 2014 Since Screwball can confirm these errors still exist with a new game, I went ahead and added a new tracker entry (#14808) for the errors posted here. Link to comment Share on other sites More sharing options...
Screwball Posted February 9, 2014 Author Share Posted February 9, 2014 Talsgar is the new Critter He's spamming my logs like crazy. Link to comment Share on other sites More sharing options...
Arthmoor Posted February 9, 2014 Share Posted February 9, 2014 Such is the curse of our existence. Fix a bug, find a bug. Bugs layered on top of bugs. It's like a fossil dig. Link to comment Share on other sites More sharing options...
BlackPete Posted February 9, 2014 Share Posted February 9, 2014 Talsgar is the new Critter He's spamming my logs like crazy. Unfortunately, he is doing the same in my log. He was doing this prior to the 2.0.1 release (with v. 2.0.0) as well. This error (here) appears in my log too every time Talsgar spawns as a wilderness encounter. Link to comment Share on other sites More sharing options...
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