3.1.6 xspot highlight

stephenwykerstephenwyker Registered User, DL Beta, Hog Beta
any reason why the x.spot std profile doesn't highlight in white ? I remember reading something a while back but it's really annoying.

Comments

  • z6p6tist6z6p6tist6 Registered User
    edited July 2010
    Stephen,

    I don't know why this would be happening (I'm sure someone from HES will chime in) but wanted to mention that you can over-ride the default highlight settings by building Highlight and Lowlight templates of your own.

    This is detailed in sections 18.3.1 and 18.3.2 of the manual.

    I usually grab a fixture, bring it to full, make it White, and record a beam palette using the I and C masks. Then I rig click on that palette and select 'Set as Highlight Palette'.

    I also like to set a Lowlight palette which is the same as above but with color in Congo.

    Let me know if you have any questions about the custom Highlight palettes.

    Cheers,

    Phil
  • cmuenchowcmuenchow Registered User, Administrator, HES Staff
    edited July 2010
    Have you looked at this with a new show file? It was fixed in 3.1.6 with library version v4.1.57.
  • stephenwykerstephenwyker Registered User, DL Beta, Hog Beta
    edited July 2010
    i don't tend to upgrade my show files when I upgrade my console .... is that something I should be doing?
  • cmuenchowcmuenchow Registered User, Administrator, HES Staff
    edited July 2010
    Updating older show files with the latest library is not really neccessary in most cases but for this particular bug the latest library with the latest Xspot profile resolves the issue.
  • stephenwykerstephenwyker Registered User, DL Beta, Hog Beta
    edited August 2010
    Oddly, when I updated, it seems like everything merged cleanly except for some of my fixture pallettes for the xspot. Seems like only a few random ones (that were written as "by fixture" and it was only beam elements (like frost, zoom and iris) yet focus, gobo, and other traits seemed fine. Not a big deal, I just updated them, but figured it may have been a bug.
Sign In or Register to comment.