Is the textNode verry buggy?

[NEO]

Is the text node verry buggy or do I just have that bad luck I always tend to have, aka user error. :rolleyes: Having many many craches in 4.73 atm while animating some text and using vector blur on it. Same thing with all fonts I tried out so thought I check with you guys if there is something worth nowing about the text node. Like what nodes it doesn't like to be hooked up to and so.
One annoying bug is that the text when I render scales in X on some frames. So it looks like it's in somekind of river dance. Pretty annoying to say the least.

One of the trees that gives me a hard time looks like this. Then hooked up in a scene node.


set cut_paste_input [stack 0]
version 4.7300
push 0
push 0
push 0
push 0
push $cut_paste_input
Text {
message "Simon flyttar"
font C:/WINDOWS/Fonts/VeraIt.ttf
size 35
kerning -0.01
yjustify bottom
translate {229 83}
scale {1 1}
color {0 0 0 1}
p1 {100 400}
p0 {100 100}
name Text3
label "Rubrik\n@b;\[value message]"
selected true
xpos 1366
ypos -762
addUserKnob {20 User}
}
Text {
message "7 000:-"
font C:/WINDOWS/Fonts/MyriadPro-Bold.otf
size 56
translate {{root.Text3.translate.x} 32}
scale {1 1}
color {0 0 0 1}
p1 {100 400}
p0 {100 100}
name Text2
label "Summa\n@b;\[value message]"
selected true
xpos 1366
ypos -705
addUserKnob {20 User}
}
set N45c9480 [stack 0]
push $N45c9480
CornerPin2D {
to1 {5 4}
to2 {730 -38.5}
to3 {720 576}
to4 {4 586}
from2 {720 0}
from3 {720 576}
from4 {0 576}
name CornerPin2D2
selected true
xpos 1454
ypos -630
}
Transform {
translate {10 -2}
center {360 288}
name Transform5
selected true
xpos 1454
ypos -604
}
Blur {
size 15
name Blur2
selected true
xpos 1454
ypos -579
}
Grade {
blackpoint -0.02
unpremult rgba.alpha
name Grade1
selected true
xpos 1454
ypos -539
}
Merge2 {
inputs 2
name Merge8
selected true
xpos 1366
ypos -480
}
add_layer {mask mask.blurStack mask.backgcorner mask.vb mask.vbSec mask.vbThir mask.vbFour}
Bezier {
output {-rgba.red -rgba.green -rgba.blue mask.vb}
points {{
{206 143 0 -2.7}
{199 -10 0 -0.44}
{516 -12 0 0.44}
{519 145 0 2.7}
}}
center {360 288}
p1 {100 400}
p0 {100 100}
name Bezier3
selected true
xpos 1366
ypos -454
}
Transform {
translate {{curve x46 472.9999847 s0 x60 129.9999771 s-25.5 t-0.2 v1.43906 x62 135.9999771 x67 129.9999771 s-0 u1.31195 x220 129.9999771 x240 -320} {curve x203 121}}
center {230 288}
name Transform3
label "text motion"
selected true
xpos 1366
ypos -416
}
set N45d26d0 [stack 0]
push $N45d26d0
MotionBlur2D {
inputs 2
uv forward
name MotionBlur2D1
selected true
xpos 1366
ypos -376
}
VectorBlur {
channels rgba
uv forward
scale 0.75
method forward
alpha mask.vb
name VectorBlur1
selected true
xpos 1366
ypos -350
}
Card {
p0 {-0.5 -0.5 0}
p1 {-0.5 0.5 0}
p2 {0.5 0.5 0}
p3 {0.5 -0.5 0}
m00 {-1.49012e-008 0.333333 0}
m01 {-1.49012e-008 -0.333333 0}
m10 {0.333333 1.49012e-008 0}
m11 {-0.333333 1.49012e-008 0}
m20 {1.49012e-008 -0.333333 0}
m21 {1.49012e-008 0.333333 0}
m30 {-0.333333 -1.49012e-008 0}
m31 {0.333333 -1.49012e-008 0}
name Card3
label "money fill"
selected true
xpos 1366
ypos -305
}
TransformGeo {
inputs 3
translate {-2.76999 4.45 -10}
uniform_scale 13
name TransformGeo5
label "adjust to 3dscene"
selected true
xpos 1366
ypos -265
}
TransformGeo {
inputs 3
translate {0 0 1}
pivot {0 0 -10}
name TransformGeo6
label "offset from wall"
selected true
xpos 1366
ypos -225
}

[NEO]

Thought I add a little render of the problem so you know what I'm talking about. Look at how the text scales in X while it animates. Also look at the first and second frame of that "counter". That one also scales. There are absolutly no keys on the scale attributes on any of the nodes.

Will bake all scale attributes at 1,1 now and see if that helps...

The preview render:
http://www.irry.com/neo/bilder/temp/3d/bouncytext.mov

[nathan]

I'm not saying this isn't a bug but here on Linux I cant get that squishing like your video displays. Is that scene you pasted above one that gives you the problem? I ran that scene here and I didn't get any squishing, you sure you pasted the correct scene file and not another version? I ask because if you pasted another version you might of accidentally animated a knob to cause it to squish in that version.

I'll have to fire up a Windows box and check it here on my end to see if its a Windows problem. If anyone else using Windows can try the scene before I do that would be appreciated.

[NEO]

Hey nrgy. I pasted the correct one. Though the scene is much much bigger then that snip. But it is that part that is causing me problems. I had the whole scene on render over the night but it died on me. For no reason at all it just stops render without any error message (command line render). I can restart the render from the frame it died on without any problem. So maybe it's my computer that can not keep up with Nuke.

I will know in 30 mins if my key-baking did solve this or not. Otherwise I'll try at another computer in linux tomorrow.

Thanks for helping out man. =)

[NEO]

When baking the scale attribute in all textnodes it works fine. Though the render still dies on me for no reason at all. But I can just restart it where it died and it goes on. So I'll have to live with that. Might be my computer that's acting like a moron. =) I have a feeling it has something to do with the vecotorBlurs but I'm not saying that out loud until I have proof. =)

[JohnnyBlaze]

I found the VectorBlur to be very buggy, too. That's only under Windows, though. The Mac-version doesn't seem to suffer from that...

[NEO]

Oooh. That puts some water on the mill regarding my speculation above. The "krux in this crow song" is that there's no VBlur on the counter. And that one also suffers from the scale-problem. But it might be some unlucjy combination of nodes and a bit of general computer strangeness. I have stoped to look for logic when it comes to software related problems. I just try to work around it. And seems like the baking worked in this case. *knock knock on wood*


I found the VectorBlur to be very buggy, too. That's only under Windows, though. The Mac-version doesn't seem to suffer from that...

[NEO]

Thought it would be good to post the progress of this. It must have been either the text node or the font's I were using that was causing this. I couldn't take all the crasches so I hooked all text nodes up to write nodes and wrote them out. Then I just put a read node in their place. Still an easy thing then to replace the text since the text nodes still are present bud disabled. I'm pretty ok with that solution and thought that it could be good for others to know that text nodes can cause headache. =)