Sean Meighan
Software => Bugs in xLights/Nutcracker => Topic started by: gerry on June 12, 2016, 01:28:55 AM
-
This is at version 2016.31 .
1. I used the Right click on sequencer-Generate random effects to generate them against a single model group (covering most models) for the whole song. Each time I tried to save ,xLights would crash (disappear) , without a debug report and with the Windows message - trying to find a solution ....
I have attached the Problem files zip file - after opening the sequence and before attempting to save.
So instead , I selected about 20 seconds at a time generated random , saved, repeated for next 20 secs , saved and did the next 20 seconds etc etc , until the group was filled for the whole song.
On the way , I did get two debug reports which I have attached.
2. I also noticed that the render style appeared to be single strand for most of the effects , so I then changed them to default or per preview to get them to work nicely after realising that was the reason most did not "appear to work".
At the end of the process , I did have the whole song working , off the random generated effects on one model group, having discarded just a few along the way ... (was doing this on the plane) . With a few more minor adjustments , I will use it for my display ! I am sure that to the untrained eye of my audience , it will look good :)
Can try and repeat the save on the latest version (2016.37) if u wish by extracting from the debug files.
-
please try on latest code. there have been a number of crash fixes over the last month.
-
I installed 2016_37, then opened the sequence xml that had been generated (and was in the previous problem files) and attempted to save it and xlights ended without a debug report.
Have attached the new Problem Files zip file.
Maybe the problem is when one/some of the effects are actually generated via the Random generator .
-
I think I have found the issue ... try next release.
-
One crash was a problem with the fire effect. The other appears to be a corrupt sequence file. I have changed the load to ignore the invalid data. Not sure how it became corrupt but at least it will load.
-
Thanks Keith,
I did try deleting some of the effects that were generated (from within the sequencer ) to try and isolate which effect/effects was/were failing... but then gave up .
In the same sequence that I have working completely, I do have a few instances of the fire effect still there and they are working fine except that for them and a few others I had to change the render thingy away from single strand to default /per preview , else they had no effect for the model group I dropped them on.
Will give it another shot when released..