Crashing on rendering.

[Hauvega]

Here is my crash zip.  Trying to figure this out.  Hanging on rendering.

[dkulp]

You have a lightning effect that doesn't have any of the lightning properties defined:

Code: [Select]

    Rendering layer effect for frame 984 of Arch7, layer 0.
    BUTTON_Palette1=#FF0000,BUTTON_Palette2=#00FF00,BUTTON_Palette3=#0000FF,BUTTON_Palette4=#FFFF00,BUTTON_Palette5=#FFFFFF,BUTTON_Palette6=#000000,CHECKBOX_LayerMorph=0,CHECKBOX_OverlayBkg=0,CHECKBOX_Palette1=0,CHECKBOX_Palette2=0,CHECKBOX_Palette3=0,CHECKBOX_Palette4=0,CHECKBOX_Palette5=1,CHECKBOX_Palette6=1,CHOICE_LayerMethod=Normal,Effect=Lightning,SLIDER_Brightness=100,SLIDER_Contrast=0,SLIDER_EffectLayerMix=0,SLIDER_SparkleFrequency=0,TEXTCTRL_Fadein=0.00,TEXTCTRL_Fadeout=0.00

That's causing the crash.   I've updated the code to defend agains that (so if #bolts is 0, make it 1, etc...) so next build won't crash, but I'm kind of curious how that lightning effect was created.

[Hauvega]

Random generation.  I also notice duplication and out of order effect ref number ordering in xml file

[Gilrock]

That doesn't sound like a problem.  It creates an effect database to conserve space so its expected that effect reference numbers will show up multiple times and in different orders.

[Hauvega]

Well I still am having trouble with rendering.  It does not complete.  I have to either crash the program or kill in the task manager.  XL3 does not have this problem.  Random generated effects in XL3 works.

[Gilrock]

Well I still am having trouble with rendering.  It does not complete.  I have to either crash the program or kill in the task manager.  XL3 does not have this problem.  Random generated effects in XL3 works.

Well Dan's fix obviously isn't released yet so did you change something to expect a different outcome?

[dkulp]

That said, if you can look in the backtrace.txt of the crash report and if it's NOT rendering a lightning effect, send the report.   I only fixed the lightning effect, if some other random effect is causing a problem, we'd like to know about it.

[Hauvega]

Even when I remove the lightning effect on loading.  I then attempt to render the sequence and it hangs in rendering.  I left it alone for 45 mins and it still never completed.  I force a crash by clicking on the grid.  Is there a way to remove some suspected effects or correct them in the xml file?

[Gilrock]

Sounds like maybe some other effects aren't getting proper default values during random generation.  For now can you just create a random sequence in XL3 and then open the XML file in XL4 to convert it?

[dkulp]

No, this was another bug that I fixed with fixing the lightning effect.  In certain cases, the single strand chase can get into an infinite loop, usually when dropped on a model that is only a single node.   I think we need another release real soon to get these fixes out.

[Hauvega]

What models are really good for randomizing?  I would like to see a feature that allows the user to customize
the random effect set.   Not all effects are good for randomizing. 

[Rod R]

Sounds like maybe some other effects aren't getting proper default values during random generation.  For now can you just create a random sequence in XL3 and then open the XML file in XL4 to convert it?

I'm the same issue, I tried making up a random sequence in XL3 and opening it up in XL4 to convert but same issue.  It crashes whenever I try to render or save any sequence that I have.  The last thing I was doing was cutting and pasting ramp up/down effects.  If I just open and play any sequence its fine only crashes when saving or rendering.

[Gilrock]

Maybe some good incentive to actually learn how to create your own effects.

[Rod R]

I was actually cutting and pasting my own effects from one group of elements to another its a bunch of A/C lawn elements (20 items) too much to redo by hand each one. Simple on, offs ramps but to redo each line (20) cutting and pasting was faster that's when the crash occurred which was weird nothing intensive just time consuming to recreate.  I was coping from other views (lawn to roof) switching back and forth did it in the past with no issues. Just can't seem to recover from it.  Doesn't matter which sequence I have I open so it does look like the something that is common got corrupted not sure how.

[dkulp]

WOW!!!  Someone has spent a lot of time on custom models.    Very very nice.   Love the dinosaur.    I might just save your xml to copy some of the custom models.   Awesome job.


That said, your problem is entirely due to your "Mini Tree #1" model being corrupt.   Somehow, in the xml, I see:

Code: [Select]

<model name="Mini Tree #1" DisplayAs="Effect" StringType="RGB Nodes"

"Effect" is not a valid type.   I assume that should be "Tree 180"?