F3 and F4 sometime having different behavior

[MrChristmas2000]

I produced this example video

http://youtu.be/26ZmhVx_Fos

using this effect.

Ripple,Tree,2 reveals 1,ID_CHECKBOX_LayerMorph=1,ID_SLIDER_SparkleFrequency=182,ID_SLIDER_Brightness=100,ID_SLIDER_Contrast=0,ID_SLIDER_EffectLayerMix=0,E1_SLIDER_Speed=14,E1_TEXTCTRL_Fadein=0.00,E1_TEXTCTRL_Fadeout=0.00,E1_CHECKBOX_FitToTime=0,E1_CHECKBOX_OverlayBkg=0,E1_CHOICE_Ripple_Object_To_Draw=Square,E1_CHOICE_Ripple_Movement=Explode,E1_SLIDER_Ripple_Thickness=73,E1_CHECKBOX_Ripple3D=0,E1_BUTTON_Palette1=#FF0000,E1_CHECKBOX_Palette1=1,E1_BUTTON_Palette2=#00FF00,E1_CHECKBOX_Palette2=1,E1_BUTTON_Palette3=#0000FF,E1_CHECKBOX_Palette3=0,E1_BUTTON_Palette4=#FFFF00,E1_CHECKBOX_Palette4=0,E1_BUTTON_Palette5=#FFFFFF,E1_CHECKBOX_Palette5=1,E1_BUTTON_Palette6=#000000,E1_CHECKBOX_Palette6=0,E2_SLIDER_Speed=10,E2_TEXTCTRL_Fadein=0.00,E2_TEXTCTRL_Fadeout=0.00,E2_CHECKBOX_FitToTime=0,E2_CHECKBOX_OverlayBkg=0,E2_SLIDER_Tree_Branches=8,E2_BUTTON_Palette1=#FF0000,E2_CHECKBOX_Palette1=1,E2_BUTTON_Palette2=#00FF00,E2_CHECKBOX_Palette2=0,E2_BUTTON_Palette3=#0000FF,E2_CHECKBOX_Palette3=0,E2_BUTTON_Palette4=#FFFF00,E2_CHECKBOX_Palette4=0,E2_BUTTON_Palette5=#FFFFFF,E2_CHECKBOX_Palette5=1,E2_BUTTON_Palette6=#000000,E2_CHECKBOX_Palette6=1

I just copied and pasted it into a cell with the results shown in the video.

The layering button shows that for this effect '2 reveals 1'. However when you press F3 to play it seems to be only displaying the effect 2, because if I change the the layering button to simply 'effect 2' the first shown effect will play regardless of using F3 or F4 button or key.

Thanks for your attention.

[jnealand]

I've not tried to narrow it down, but I have noticed similar things where F3 and F4 give me different things.  I usually just do a save and look at in the preview.  I chalked it off to just another annoying thing that will eventually get fixed.  I haven't been willing to take the  time to try to do good diagnostics and document this.

[dkulp]

I just pushed some changes that hopefully fix most of this along with a bunch of other issues we have had.   There are still some differences between F4 and F3 that I'm not TOO sure how to figure out.  For example, the Fade In/Out and the Morph things are really not usable with F3 as there isn't a time frame for reference for those.   With F4, we have the exact grid cell time information for that.

The BIG change with what I pushed (this has been bothering me for a while) is that we now only have a single "render" path used for both the "play" buttons and the saving.   We used to have one for the Play buttons that grabbed the information from the controls and another for saving that used the Effects string from the grid.   The new method generates an effects string from the controls and passes that to the one method that the save used.   Thus, no more issues of "typos" in the save method where the effects looked OK when "playing", but didn't save at all.

[MrChristmas2000]

Thanks for the quick response.

Any timeframe for a new build to be up?

Merry Christmas and Happy New Year

Tom

[sean]

 I will release a build today. Dan, thanks for getting rid of two paths to the render routine. This will help with some effects that would play ok but not show up in preview tab.

[MrChristmas2000]

Thanks,

Have a very Merry Christmas......

[MrChristmas2000]

Did a new build of Nutcracker with these fixes ever get completed?

Thanks,

[jnealand]

Not yet that I have seen, but with the season on the downhill side I can live with it until other stuff accumulates.

[MrChristmas2000]

I am trying to do some last week sequencing and it would be nice to have the fix. I want to finish them for next year while I can still see what they will look like for real.