Fixture At Fixture = Broken Update

BECOME PART OF THE COMMUNITY - Sign up here
  • I honestly hadn't noticed this before, but I checked in 1.7 and 1.5 and it seems also to do the same thing:

    1 At 100

    2 At 50

    Store Cue 1

    Go+

    Fixture 2 at 100

    Update


    It works as expected.


    However, this does not:

    1 At 100

    2 At 50

    Store Cue 1

    Go+

    Fixture 2 at Fixture 1 /o

    Update


    Fixture 2 if left stranded in the programmer


    This only stores fixture 3 and not fixture 2:

    1 At 100

    2 At 50

    3 At 10

    Store Cue 1

    Go+

    3 At 50

    Fixture 2 at Fixture 1 /o

    Update

    • New
    • Official Post

    This is a bug I would say...
    It seams that Fixture at Fixture doesn't give the condition for update but from the user expectation this would make sense...

  • This is quite strange because I am using fixture x at fixture y quite often and it works fine.

    you are updating with “original content” or “add new content”?


    With Original content.


    This example is with a new show and two fixtures patched and it fails every time.


    1 At 100

    2 At 50

    Store Cue 1

    Go+

    Fixture 2 at Fixture 1 /o

    Update


    In this case Cue 1 is active with Fixture 1 and 2 Dimmer information. Fixture 2 @ 1 should copy dimmer information that already exists in Cue 1 so Original Content should work.


    Fixture At Fixture itself does work but updating with information from the fixture copy does not. The workaround is to Store Merge but given that it works in MA 2, this definitely seems broken.

  • for the exact scenario given in hoss example, a plausible workaround could be to apply the fixture at fixture command directly to the cue, instead of taking a detour via the programmer and the update procedure.


    Fixture 2 at Fixture 1 If Cue /o