Sean Meighan
Software => Bugs in xLights/Nutcracker => Topic started by: charlie-68 on July 11, 2019, 09:24:36 AM
-
while I was in my sequences changing brightness levels xlights would completely shut down. Ofcourse any changes was not saved. I think this is the file that was generated after the crash. Thanks Charlie J.
-
Not sure what you mean by "changing brightness levels" ... there are at least 4 ways to do that.
I really could do with:
1. A package of the sequence causing you issues
2. A video of you reproducing the problem
Of course that assumes you can reasonably predictably reproduce it.
-
When this happened I was in the sequence and changing the brightness on each effect from 300 to 400. I would change a few and then xlights would shut down completely to desktop. I would double click xlights and restart xlights and continue and sometimes it would happen again. Does this help? Charlie J.
-
There are so many variables that could cause a problem, it could be a computer problem, a program problem, user error to name a few. You have to give the developer something to work with. He already asked for a package of the sequence and possible a video of the error happening. They need to know EXACTLY what you did to cause the problem. Like how was the model built, what effect was on the model that you were modifying, what was your layer blending, any sub buffers, and on and on. If you give them the packaged sequence and a detailed explanation of how you made the program crash, then they will get it fixed. Include something like what model you were modifying the brightness, what effect and what point in the timeline just to start. If you don't include enough information for them to find the error, they are not going to guess and your problem isn't going to get looked at.
BTW, do you have your lights dimmed globally to begin with? If not changing the brightness to higher than 100 will probably change colors and not increase brightness.
-
After the last update I was unable to again make the shutdown happen. So it seems fixed. Thanks Charlie J.