Issue Data
|
Issue #27219: FusionGeneratorSCRIPT: cannot enable an object with an enable state parent
[08/10/2019 - 01:08:39PM] error: (000E6FB2): cannot enable an object with an enable state parent.
stack: [ (000E6FB2)].ObjectReference.Enable() - "<native>" Line ? [ (000C781F)].FusionGeneratorSCRIPT.::remote_ObjectReference_OnActivate() - "C:\Users\Dr. Peter Haas\AppData\Local\Temp\PapyrusTemp\FusionGeneratorSCRIPT.psc" Line 111 [08/10/2019 - 01:08:39PM] error: (000E6FB2): cannot enable an object with an enable state parent. stack: [ (000E6FB2)].ObjectReference.Enable() - "<native>" Line ? [ (000C781F)].FusionGeneratorSCRIPT.::remote_ObjectReference_OnActivate() - "C:\Users\Dr. Peter Haas\AppData\Local\Temp\PapyrusTemp\FusionGeneratorSCRIPT.psc" Line 116 [08/10/2019 - 01:08:39PM] error: (000E6FB2): cannot enable an object with an enable state parent. stack: [ (000E6FB2)].ObjectReference.Enable() - "<native>" Line ? [ (000C781F)].FusionGeneratorSCRIPT.::remote_ObjectReference_OnActivate() - "C:\Users\Dr. Peter Haas\AppData\Local\Temp\PapyrusTemp\FusionGeneratorSCRIPT.psc" Line 121 [08/10/2019 - 01:08:40PM] error: (000E6FB2): cannot enable an object with an enable state parent. stack: [ (000E6FB2)].ObjectReference.Enable() - "<native>" Line ? [ (000C781F)].FusionGeneratorSCRIPT.::remote_ObjectReference_OnActivate() - "C:\Users\Dr. Peter Haas\AppData\Local\Temp\PapyrusTemp\FusionGeneratorSCRIPT.psc" Line 126 [08/10/2019 - 01:08:40PM] error: (000E6FB2): cannot enable an object with an enable state parent. stack: [ (000E6FB2)].ObjectReference.Enable() - "<native>" Line ? [ (000C781F)].FusionGeneratorSCRIPT.::remote_ObjectReference_OnActivate() - "C:\Users\Dr. Peter Haas\AppData\Local\Temp\PapyrusTemp\FusionGeneratorSCRIPT.psc" Line 131 The errors come from the linked light 000E6FB2 that is supposed to get turned off by the script if the fusion core is taken from the generator. Due to being enable-parented however, this light will never be turned off even if the generator is no longer running. |
The enable parent does not include the generator, i.e. the light is toggled independently. Which doesn't make much sense considering that the light is supposed to be directly powered by the generator (because that's the intention of the linked lights on fusion generators after all).
It's difficult to tell what the intentions were however, because the enable parent is linked to pretty much all light sources in that cell. The marker, in turn, is toggled by the Arc Jets quest script, suggesting that it was deemed important to disable all light sources in that cell. In that case, we simply should remove the linked light property from the generator.
On the other hand, we also could unlink the generator light from the enable parent. This would be more consistent with the "generator visuals".
It's difficult to tell what the intentions were however, because the enable parent is linked to pretty much all light sources in that cell. The marker, in turn, is toggled by the Arc Jets quest script, suggesting that it was deemed important to disable all light sources in that cell. In that case, we simply should remove the linked light property from the generator.
On the other hand, we also could unlink the generator light from the enable parent. This would be more consistent with the "generator visuals".
Per dicussion on Discord, the generator light has been removed from the enable parent.
Showing Comments 1 - 2 of 2