Jump to content

Photo

Custom workshop light emmiting even if its off ?

workhsop light custom fallout 4 help

  • Please log in to reply
3 replies to this topic

#1
WyvernX1

WyvernX1

    Journeyman

  • Supporter
  • Pip
  • 20 posts

How to solve problem when i created New ( basicly copy ) Workshop spotlight that emmiting light even if its turned off, basicly its permanently on?

 

Also attaching a mod itself ( .esp ) if someone wanna take a look :smile:

 

https://mega.nz/file...YgKLgkol2Tl85Rw

Attached Files


Edited by WyvernX1, 19 June 2022 - 10:25 AM.


#2
greekrage

greekrage

    Resident poster

  • Supporter
  • PipPipPipPipPip
  • 4,185 posts

i have this issue in my latest mod using available assets from the CK...

Example a Hitech ceiling light (on) fixture  combined with light sources that are  linked to a parent and are toggled on/off. Where the fixture still emits a bit of light.

 

I guess the only for me way would be to have both on and off versions and have them switch when enabled or disabled.



#3
LarannKiar

LarannKiar

    Old hand

  • Members
  • PipPipPipPip
  • 1,413 posts

You need to remove the keyword BlockPlayerActivation.



#4
ChuckYufarley

ChuckYufarley

    Fan

  • Members
  • PipPipPip
  • 416 posts
It looks as thought the only thing you changed from the vanilla construction light was to add a custom Addon Node which uses a custom light, is that correct? Otherwise, the nif itself has remained virtually unchanged from the original nif, except for the updated BSValueNode. The vanilla construction light activator also has the BlockPlayerActivation keyword, and I assume it works as it should in game. If that's the case, then there is no need to remove that keyword from your custom light.  I've made many custom lights and when the objective is to have the light turn on/off via a connected power source, I always use the BlockPlayerActivation keyword.
 
 
 
The only things I am seeing that might be causing an issue are the name of the BSValueNode not being changed in the NiDefaultObjectPalette, and perhaps the index number you're using for your custom addon node.  The name in the object palette shouldn't be an issue, but it seems to me that in the past, not having the name and the AV Object match has caused a problem in one or two of my nifs. As for the addon node index number, you might have another mod installed that uses the same index number and that could be causing a conflict. I checked all the vanilla index numbers and 902 isn't used in the base game or any DLC packs, but since it's so close in sequential order to vanilla index numbers that are being used, I would venture to guess that it was generated by the CK when you created the addon node, and you left it unchanged. Chances are pretty good that another mod you've installed has the same, CK generated index number. Try changing the index number to something that would be a little harder to randomly duplicate in some other mod. Something with 4 digits. I use index numbers in the 5000s and have never had a conflict.
 
Hope this helps.

Attached Files







Also tagged with one or more of these keywords: workhsop, light, custom, fallout 4, help

IPB skins by Skinbox
Page loaded in: 1.160 seconds