Release 2017.18 xlights released

[smeighan]

xLights release 2017.18
numerous Vixen 2.x import issues and added some enhancements. Some more crash fixes.


Latest releases are found at www.xlights.org
Videos tutorials are found at videos.xlights.org
Forums are located at nutcracker123.com/forum
Issue Tracker is found here: www.github.com/smeighan/xLights/issues

XLIGHTS/NUTCRACKER RELEASE NOTES:
---------------------------------
2017.18 Jun 29, 2017
-- bug (dkulp) Vixen import was not reading channel names/colors from profile files.
-- enh (keith) Add a show all effects row header right click menu option which opens up all groups/models/strands
to show all effects ... but only those that are necessary to see them all
-- bug (keith) Fix some crashes when mapping due to empty lists
-- bug (keith) Fix hue vc not working on layers other than zero
-- enh (keith) Add splitter to mapping dialog
-- enh (keith) Add splitter to sequence elements dialog.
-- bug (keith) Fix test tab throws error if output to lights was already on
-- enh (keith) Connect up menu items for controller upload on OSX
-- enh (dkulp) Update vixen import to try and find the profile file and use the channel names from there
-- bug (keith) Fix color panel value curves not setting correctly as you move from effect to effect

 

[OzAz]

Thanks team.
FYI all, the 'show all effects' appears to be causing xLights to crash, it's been noted on the main nutcracker xlights forum

 

[scamper]

does this mean you can attempt to import your profile and sequences from vixen into xlights?

 

[smeighan]

i do believe that is what dan kulp has fixed. give it a try

 

[Gilrock]

Pretty sure it won't import Vixen3 if that's what you were looking for. I believe he added an import for Vixen+ and improved the Vixen 2.5 import. Vixen3 is structured in a way that will probably never have an importer created.

 

[marmalade]

not sure if my request for a inbuilt power budget/checker was put in. Probably a big chunk of code to add

The idea was to be able to input a string/elements current draw, and assign it to a power group (or power supply). You could then get an report of the duty cycle that group was running at, the peak current drawn and other stuff during/after the sequence was run.

Would be very helpful, especially when adjusting brightness levels, forecasting for buying psu's etc..