Author Topic: Crashing After Adding in a Spiral Tree  (Read 3043 times)

Offline djohnson1810

  • Jr. Member
  • **
  • Posts: 58
    • View Profile
Crashing After Adding in a Spiral Tree
« on: June 24, 2015, 12:56:36 PM »
So I am trying to add a Spiral Tree.  After adding the tree and then importing effects to it from LOR, xlight starts to crash.  If I remove the Spiral Tree then everything works fine.  I am attaching some screen shots and the crash report.

The tree is a simple 8 strand setup with RGB lights.

Offline JonB256

  • Hero Member
  • *****
  • Posts: 832
    • View Profile
    • My Christmas Website
Re: Crashing After Adding in a Spiral Tree
« Reply #1 on: June 24, 2015, 01:05:27 PM »
Does it start to crash after adding the tree?

Or after importing the LOR data?
And how are you bringing in that data?

I see nothing wrong with your posted spiral tree setup.

Offline djohnson1810

  • Jr. Member
  • **
  • Posts: 58
    • View Profile
Re: Crashing After Adding in a Spiral Tree
« Reply #2 on: June 24, 2015, 01:16:56 PM »
I make the model ---  Add it to the time line ---Go to Import ---Add Effects  --- pick my LOR file and chose the correct LOR channels to import.  I see the data in xlights but when I go to render... CRASH.

Offline Gilrock

  • Supporting Member
  • Hero Member
  • *
  • Posts: 6946
    • View Profile
Re: Crashing After Adding in a Spiral Tree
« Reply #3 on: June 24, 2015, 02:08:07 PM »
You didn't attach a zip file with the crash report.

Offline djohnson1810

  • Jr. Member
  • **
  • Posts: 58
    • View Profile
Re: Crashing After Adding in a Spiral Tree
« Reply #4 on: June 24, 2015, 02:11:20 PM »
Oops.  Sorry.  Here it is.

Offline Gilrock

  • Supporting Member
  • Hero Member
  • *
  • Posts: 6946
    • View Profile
Re: Crashing After Adding in a Spiral Tree
« Reply #5 on: June 24, 2015, 02:11:33 PM »
Instead of hitting Render hit the Save button then it will usually at least save the XML before it crashes during Render.  Then you can open up that XML file and try to render again.  If the Render works after re-opening let us know because I have a theory of what could cause that.

Offline Gilrock

  • Supporting Member
  • Hero Member
  • *
  • Posts: 6946
    • View Profile
Re: Crashing After Adding in a Spiral Tree
« Reply #6 on: June 24, 2015, 02:13:06 PM »
If it still fails the second time then upgrade to 4.1.8 and try again and report the results.

Offline Gilrock

  • Supporting Member
  • Hero Member
  • *
  • Posts: 6946
    • View Profile
Re: Crashing After Adding in a Spiral Tree
« Reply #7 on: June 24, 2015, 02:14:06 PM »
Actually looking at that backtrace I would go directly to trying it with 4.1.8.

Offline djohnson1810

  • Jr. Member
  • **
  • Posts: 58
    • View Profile
Re: Crashing After Adding in a Spiral Tree
« Reply #8 on: June 24, 2015, 02:44:34 PM »
Updating worked.  Your the bomb!

Can you elaborate a little more on:

Allow "-P#", "-P##", " p#", and " p##" for detecting CCR/CCBs in LMS import

I am hopeful this will help me somehow in converting the old LMS files faster.  Right now I have to do the smart RGB's node by node.

Offline Gilrock

  • Supporting Member
  • Hero Member
  • *
  • Posts: 6946
    • View Profile
Re: Crashing After Adding in a Spiral Tree
« Reply #9 on: June 24, 2015, 03:59:43 PM »
Dan created the LMS import code and he has to parse the LMS file.  He is trying to detect the name fields for CCR or CCB strands.  Originally he followed a sample file that had names like CCR01-P01, CCR01-P02 or something like that.  Then others ended up with different naming schemes.  We are expanding the import to cover the different naming schemes as we figure out what they are.  You can open up your LMS file in a text editor and go find your RGB channel names if you want to see what yours look like.

Offline djohnson1810

  • Jr. Member
  • **
  • Posts: 58
    • View Profile
Re: Crashing After Adding in a Spiral Tree
« Reply #10 on: June 24, 2015, 09:14:38 PM »
Thanks.  With that information, I was able to open the LMS text file in notepad and do some bulk replacing of names.  For example if my soffit element was Soffit 01, Soffit 02, Soffit 03, then I just went in and replaced all occurrences of "Soffit " with Soffit -P".  That made the outcome Soffit -P01, Soffit -P02 etc.  It was then easy to import.