Jump to content

Creature Framework CTD (warning: Assigning None to a non-object variable named "::temp6")


Recommended Posts

Posted

Hello people,
 
Since I updated Creature Framework to RC12 my game crashes at random times. Every time I get a CTD the same error shows up in my Papyrus log:

 

warning: Assigning None to a non-object variable named "::temp6"

Judging by the stack trace it seems like it comes from Creature Framework.

 

I have attached the full papyrus log, if anyone could help me find a fix that would be much apreciated.

Papyrus.0.log

Posted

Any luck?

I'm getting this same issue with Creature Framework RC12 as soon as my character is "Defeated" by zombies.  Haven't tried it elsewhere.  I'm not sure if it's RC12 specific or something else, but it does cause a CTD every time.

stack:
	[Active effect 1 on  (000E94D6)].CFEffectCreatureApply.OnEffectStart() - "CFEffectCreatureApply.psc" Line 10
[10/21/2015 - 03:07:43AM] [CF][Framework] Didn't activate actor ["Skeleton" [Actor < (000E94DE)>]]; already has effect
[10/21/2015 - 03:07:43AM] Warning: Assigning None to a non-object variable named "::temp6"
stack:
	[Active effect 1 on  (000E94DE)].CFEffectCreatureApply.OnEffectStart() - "CFEffectCreatureApply.psc" Line 10
[10/21/2015 - 03:07:43AM] [CF][Framework] Didn't activate actor ["Skeleton" [Actor < (000E94DB)>]]; already has effect
[10/21/2015 - 03:07:43AM] Warning: Assigning None to a non-object variable named "::temp6"
stack:
	[Active effect 1 on  (000E94DB)].CFEffectCreatureApply.OnEffectStart() - "CFEffectCreatureApply.psc" Line 10
[10/21/2015 - 03:07:43AM] [CF][Framework] Didn't activate actor ["Skeleton" [Actor < (000E9524)>]]; already has effect
[10/21/2015 - 03:07:43AM] Warning: Assigning None to a non-object variable named "::temp6"
stack:
	[Active effect 1 on  (000E9524)].CFEffectCreatureApply.OnEffectStart() - "CFEffectCreatureApply.psc" Line 10
[10/21/2015 - 03:07:43AM] [CF][Framework] Didn't activate actor ["Skeleton" [Actor < (000E94E9)>]]; already has effect
[10/21/2015 - 03:07:43AM] Warning: Assigning None to a non-object variable named "::temp6"
stack:
	[Active effect 1 on  (000E94E9)].CFEffectCreatureApply.OnEffectStart() - "CFEffectCreatureApply.psc" Line 10
  • 2 months later...
Posted

Harmless or not - this IS an error, and should be fixed.

 

For anyone, who is interested (mod authors) - look at the assembly (generate it with PapyrusAssembler or add -keepasm option to compiler), and it all become clear in a couple of seconds. This error is caused by some function declared as returning scalar type, but in fact returning nothing. When there is no "return something" statement, the function will actually return None, which is then attempted to be assigned to scalar-typed ::tempxx and generate this error

  • 2 years later...
Posted
On 1/7/2016 at 3:58 AM, fredinator said:

I get this CTD when running around randomly. Looks like it tries to apply stuff to Mammoth or Fox and fails

I actually get this too. It's been a large problem for me recently, as I continue to get CTD's when I get this error in my papyrus log. It's usually only with this error, however. And I haven't been able to find a fix for it yet.

Posted
1 hour ago, Ahvulon said:

I actually get this too. It's been a large problem for me recently, as I continue to get CTD's when I get this error in my papyrus log. It's usually only with this error, however. And I haven't been able to find a fix for it yet.

this have nothing to do with whatever ctd you have, like everything that get in the log...

"warning: Assigning None to a non-object variable named "::temp6" "

that script have an x property auto that isn't in the thing calling that script

so... it don't have any value for x... so "none"

and it don't have name for that property... so "temp6" (there was 5 others before that one, and there was no ctd because of that, because that doesn't matter)

 

 

 

 

 

 

 

 

Posted

I don't know anything about Papyrus but I know that 'Error' and 'Warning' are two different words. I also know that 99% of Skyrim CTDs are down to user error.

Learn how to fault find. If you think mod A is causing problems then uninstall the mod, start a new game and see what happens.

Get your basic game set up properly and stable. Read up or watch videos on how to mod Skyrim.

Read mod descriptions.

Learn that just because a mod has tits in it doesn't mean it's a great idea to install it.

Stop blaming everything on 'bad mods'.

  • 3 years later...

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