How to make items disable at the same time?

[samv96UK]

I made a script earlier which was placed on an x marker. It basically made some items enable when the player pulls a lever, then disable when they pull it again. When I realised that you can't fade out the objects when they are the children of an enable parent, I just deleted the x marker and added in all the items I was disabling/enabling as properties.

 

So my original script was:

 

Items.Enable()

Items.Disable()

 

But now it's:

 

Item1.Enable(True)
Item2.Enable(True)
Item3.Enable(True)
Item4.Enable(True)

Item1.Disable(True)
Item2.Disable(True)
Item3.Disable(True)
Item4.Disable(True)

 

The only problem is that all of the items appear/disappear one after the other, in the order they are listed (E.g Item 1 appears, then Item 2, Then Item 3 etc.).

 

However, I want them to all appear disappear at the same time.

 

Anyone know how this is done?

 

Thanks

[HerrBaron]

Fairly simple; add an xmarker, or some other static object, and then for each of the objects you want to disable at the same time, make this object the Enable Parent. All you need to do then is Disable() or Enable() the single Enable Parent to Enable or Disable all the children.

 

Hope this helps.

-HB

[David Brasher]

You can even leave out the X-marker and parent all the items to one of your objects. then your scripts can enable and disable this one object as needed.

[samv96UK]

Fairly simple; add an xmarker, or some other static object, and then for each of the objects you want to disable at the same time, make this object the Enable Parent. All you need to do then is Disable() or Enable() the single Enable Parent to Enable or Disable all the children.

 

Hope this helps.

-HB

 

I used an x marker originally, but the problem with that was that you couldn't have the Fade Out as True, as that just fades out the X marker, the children still just pop-out, and I want them to fade.

 

Unfortunately, using David's still didn't work. It just made the main object fade then the others poped-out afterwards.

 

I'll probably just forget about the fading out and just use my original x marker method.

[gasti89]

Yeh the CKwiki says that that there's no way to make children fade in via papyrus.

 

The funny thing is that the console command works exactly the opposite:

 

When called on an Enable Parent, the [FadeIn] property will not be passed to its enable children. They will Enable as through the default Enable (with Fadein=1) was called on them.

In order for the Enable Children to Pop In (instead of fade in), you must go to each child and, under the enable parent tab, check the 'Pop In' checkbox.

 

This is the console command one

[samv96UK]

Yeh the CKwiki says that that there's no way to make children fade in via papyrus.

 

The funny thing is that the console command works exactly the opposite:

 

When called on an Enable Parent, the [FadeIn] property will not be passed to its enable children. They will Enable as through the default Enable (with Fadein=1) was called on them.

In order for the Enable Children to Pop In (instead of fade in), you must go to each child and, under the enable parent tab, check the 'Pop In' checkbox.

 

This is the console command one

 

Very strange. Like I said, I've just gone back to my original method of using an x marker. it means they can't fade out, but I prefer that than to have them disappear one after the other.

[steve40]

Try doing it this way. They should fade in and out all at the same time:

 

Item1.EnableNoWait(True)
Item2.EnableNoWait(True)
Item3.EnableNoWait(True)
Item4.EnableNoWait(True)

Item1.DisableNoWait(True)
Item2.DisableNoWait(True)
Item3.DisableNoWait(True)
Item4.DisableNoWait(True)

 

Edit: for compactness/convenience you could consider putting your items in a FormList and doing this:

 

int i = ItemList.GetSize()

While i > 0
Item.GetAt(i).EnableNoWait(True)
i -= 1
EndWhile

 

with a property defined at the beginning of the script like this:

 

FormList Property ItemList auto

 

Then make a FormList in the CK and drag-and-drop your items into it. Nice if you have lots of items to manipulate. This way you don't need to have a property for each item :thumbsup:

Edited July 30, 2012 by steve40