Comments

Grazie wrote on 3/19/2010, 3:42 PM
Reproed. Report it. I have NOT seen this before. It is only when going to a Stroke Width larger than 4.5 .

I've now reproed it in VP8, so it was there too.

It's as if the Stroke is taking the graphic from the internal angle of the rising-splay in the M legs?

Weird.

Grazie
Editguy43 wrote on 3/19/2010, 9:38 PM
Hey WAY Cool or not, :-) I have it to, it is not just arial many others have it to this seems like a pretty big glitch.

Have you opened a trouble ticket yet if not please do. What a find..

Paul B
ushere wrote on 3/19/2010, 9:47 PM
interestingly enough, i had the same problem way back in v8, i just thought it was a corrupt font so did nothing about it (other than change the font. or font size, can't remember).

surprised it's not been picked up before now......
farss wrote on 3/20/2010, 12:22 AM
Proanimator has the same issue, more exciting in 3D. Seems to have something to do with using the GPU. Proanimator has a Spike Busting slider. Problem seems to go away when you do a software render.

Do these spikes show up in the rendered output?
Most GPU accelerated apps give you the option of using a software only render which is slower but more accurate.

Bob.
Grazie wrote on 3/20/2010, 12:51 AM
"Spikes" in Render. - g
Grazie wrote on 3/20/2010, 2:32 AM
Bob? I am not wholly convinced it is a Graphics acceleration or whatever . . . I think this is a graphics's "bug", resulting from pushing the Stroke slider to the upper most. The spikes are clean and perfectly reflect the angularity of the underlining angle of the graphic too!

My opinion? This Stroke slider hasn't been debugged for this "shape". I don't think this is a maths-graphics issue. I think this is far simpler? If you know what I mean . . ?

Grazie
baysidebas wrote on 3/20/2010, 9:01 AM
I remember seeing this type of artifact in the early days of Corel Draw. It was caused by an odd combination of settings for outline thickness (on the type) and the type of line "join" and/or "termination" set in the preferences. It wasn't a bug per se, just the result of settings outside the norm.