Single strand with "all arches" doesn't chase anymore?

[danj]

In XL 3.6 and earlier betas of XL4, my single strand effect with all six arches grouped "chased" back & forth across the arches.    Now in .14 and later betas, this effect just "sits there" with no movement and only a few of the pixels light up.  Just wondering if anyone else has seen similar thing with this effect?

[JonB256]

I applied that setting to a set of Mini trees and got nothing. Since I wasn't technically using Arches, I didn't think much of it, but I think you are correct.

[danj]

I turned off "group all arches" for now and it still somewhat looks like a chase.  Seems like this doesn't function like it used to, though....

[Skunberg]

I can't get a single chase. The smallest amount is 2 that run one in each direction. I tried separate arches after a group didn't work. Any ideas?

[sean]

I am rewriting the single chase. It will be all new, it will be 1-2 weeks to complete because of. Other obligations


Sent from my iPhone using Tapatalk

[danj]

Thanks Sean.   Enjoying all the new stuff this already excellent software is doing and will be doing!!!!
And thanks to all the developers!!!!

[danj]

Has anyone tried "group all arches" to set a chase effect on their grouped arches?   I am trying to set my six arches to chase but am not having success. I have tried numerous combinations of the different single strand parameters....  Thanks

[kevinp]

I just opened an "older" sequence I did from earlier this year in XL4, and my chases are still functioning just fine.  I have 4 arches, each defined as their own individual models, set as part of my display.  I then have a model defined as a single line, encompassing all of the channel numbers from the four arches, and not part of my display.  Any time I want to do a chase on all of the arches (1-4) as if they were one model, I drop my effect on that single line model.  I have two additional models based on that one, (1-2) and (3-4) so that I could do separate effects as if I only had two arches.

I've used the SingleStrand and Curtain effects to create a chase.  With the SingleStrand effect, make sure the cycles field is set high enough to create moment.  That field is the equivalent of selecting a speed.

Hope that all makes sense?

[danj]

Thanks Kevin.  I'll play around with it tonight when I get back from work.
It is not doing what I remember it doing when "group all arches" was first setup for this purpose.

[bwinter]

I then have a model defined as a single line, encompassing all of the channel numbers from the four arches, and not part of my display.  Any time I want to do a chase on all of the arches (1-4) as if they were one model, I drop my effect on that single line model.  I have two additional models based on that one, (1-2) and (3-4) so that I could do separate effects as if I only had two arches.

I'm stumped on how to make a model "not part of my display."  Is that done in the Layout Tab, as part of defining the model?  I'm not seeing this option, or how this is done.

[keithsw1111]

Put it in unassigned.

[Gilrock]

I then have a model defined as a single line, encompassing all of the channel numbers from the four arches, and not part of my display.  Any time I want to do a chase on all of the arches (1-4) as if they were one model, I drop my effect on that single line model.  I have two additional models based on that one, (1-2) and (3-4) so that I could do separate effects as if I only had two arches.

I'm stumped on how to make a model "not part of my display."  Is that done in the Layout Tab, as part of defining the model?  I'm not seeing this option, or how this is done.

We posted my video several times on many forums and Facebook that would have taught you that.  Every model and model group now has a "Preview" assignment that you can set down in the property grid area.  Change the preview assignment to "Unassigned".

[gerry]

bwinter,

After doing as Gil/Keith have suggested , you also need to ensure that if that model is part of a group than ,
either do the same for that group ie make it unassigned or remove model from group.

As I understand..
So if you have a group called Arches , then Arch 1,2,3,4 are assigned to default preview.
"Arch1-2" and "Arch3-4" of Kevin's example , should not be assigned to group Arches AND should also be set to a preview window of unassigned.

A model will appear on a preview if either it is set to that preview or it belongs to a group that is part of that preview.