Moho Animation Forum

Funnily I haven't noticed this before, but:

I have a new character with really thick lines. Now when a body part is crossing the screen border, the line doesn't get rendered completely - AS somehow stops rendering at the point which is nearest to the screen border.

Anybody else has this problem?

http://slowtiger.de/examples/bodytest.html, watch the feet.

Yes, I have seen this happen as well. But now for some reason I can't make it happen! I remember seeing this on one of my own projects a while back and being concerned about it but now... for the life of me I can't reproduce this problem.

Can you post the project so I can look at the settings? I think it is probably some setting in there that causes it. Some combination of stroke and fill or proximity to the edge.

Just remember one thing, if the project is for broadcast you would have your "video safe area". Anything outside that gets "cropped" on a TV or whatever. That little angled cut never gets seen.

-vern

The shapes are filled via styles, the line width is set to 3, but grossly enlarged with the W tool, then single points are tweaked as well. Every layer is set to animated line wiggle.

That "video safe" area doesn't exist anymore in an era of digital TV, digital screens, and digital distribution. I guess I could make the project slightly larger, some 5 %, and later crop the rendered video again, but AS shouldn't behave like that.

Here's how he will walk eventually: http://slowtiger.de/examples/bodywalktest.html

I tried and changed the line width of existing styles, but without effect. Does that only work with lines which weren't touched by the W tool?

I've tried every combination of line settings I could think of. Line wiggle, line width, separate styles, etc etc... and I can't replicate that problem again.

As I think back on it I do recall that it required an EXACT situation involving the angle of the line as it hits the edge of the screen, something to do with points hanging over the edge and sharp angles maybe? Sometimes I would see this when zoomed in during editing as the stroke went out of screen. Funny thing is I can't recall the last time I saw this happen. You have the latest update right? 5.6?

This is why I would like the actual file. I can put in all the same settings but without the file that is causing trouble I can't be sure it is exactly the same.

I have tried everything and I just can't make it do this and yet I know it does this sometimes. I've seen it myself.

--------


AHA!!!! Eureka! I got it!

If the stroke is nearly PERFECTLY perpendicular to the edge of the viewing area the stroke thickness "vanishes". To fix this just make certain that the stroke or vectors are not perfectly lined up with the edge of the viewing or rendering area. Just a slight nudging of the points should do it.

This is a RARE bug that doesn't happen often I think.

-vern

Here's a picture that tells the story better:



The trick is not to have two points right on the line. When that happens you get that weirdness.

-vern

That's because for fast render, AS internally checks whether the construction curve can be seen in the visible area. If the construction curve of the line segment is not visible is is not rendered. The bug is that it is not considering that a thick line can be seen although its construction curve is not visible.

Interesting: render to jpeg gives different result than to png. Also the attached file crahses randomly when export animation from frame 1 to 1.

anme file:
http://www.mediafire.com/?ni1umwcftzg

swf export 72 frames:
http://www.mediafire.com/?hdmsrzcvk5h

BMP export 1 frame:
http://www.mediafire.com/?vdd2440mdgt

JPEG export 1 frame:
http://www.mediafire.com/imageview.php? ... ym&thumb=5

PNG export 1 frame:
http://www.mediafire.com/?mymy1zh1dye

PSD export 1 frame:
http://www.mediafire.com/?tx9jtivtdml

TGA export 1 frame:
http://www.mediafire.com/?nxhckjd2mnt

Only PNG, SWF and PSD renders correctly.

Slow, if you render your animation to a PNG sequence does it have the same problem?

Very interesting.

Indeed, the glitch doesn't appear in a PNG sequence, while the QT file of the same scene shows it clearly.