!****ed Non Antialias Fonts!

1

-if i place a font without antialias on the root, at a perfect pixel (no .4 .5 blablabla) it’s ok (note:but not always)

-if I place it in a movieclip, on the right pixel and even the movieclip is placed right the font will blur almost always, I can’t understand why!!!

I’m using a Trebouchet at size 11.
Just to be sure I’ve tried with a Verdana at a even number size and I tried to publish the movie with different flash player versions… nothing… ALWAYS BLURRED…

I wonder why even if Macromedia choosed to put the “non antialias text” the fonts will still blur… and MX 2004 sounded like it worked better… but it doesn’t!!!
I don’t know what to do…
If you have any suggestion…

2

Just do a board search for font aliasing…this is such a tired topic, you’ll find boatloads of threads for it.

Or try google…

Or place your fonts at even X/Y values and make sure the aliasing button is in the right state.

3

:h: this is already ok… :sleep: that’s the problem…
I was hoping somebody had the definitive solution.

[complain]
What I don’t understand is how Macromedia hasn’t corrected this problem yet… I don’t think it would be too hard to stick the property of an object as not antialiased even in realtime playing…
[/complain]

4

im not sure ive ever experienced that problem…if your using a superpixel font just make sure its at the intended size its supposed to be, if your using a non super pixel font then maybe you have it too small.

5

If you place your text at an even X/Y (ie. 14, 56 – instead of 14.2, 56.3), and make sure the alias text button in the properties inspector is pressed in, your text WILL NOT alias.

That’s one of the ways to tell the experienced Flasher from the newbies, the veterans usually have crisp, clean text – which gives the impression that they took their time on the site…

Again, follow the above and your text WILL NOT ALIAS. If it’s still aliasing, you’re doing something wrong. MM has fixed the problem, it’s up to the user to take the proper steps to fix the aliasing. :wink:

6

Also, if you’ve got text nested within movie clips:

Make sure the text box itself is at an even X/Y, but also be sure that every MC it’s in is also at an even X/Y.

7

ahem… thanks for treating me as a newbie but actually I’m not:P

I’ve already done all you said and checked it several times, firts movie clip is right placed, even the nested one and even the textbox inside the nested clip.
Last but not least, alias button is pressed. :m:

Assuming the container clips ar on even x and y have a look at the properties of the textbox and tell me if there’s something wrong because I don’t see any error.

May it be that it’s trebouchet font fault?

8

Post your FLA.

9

here is the object, note that in the middle of the gear there’s something that seems like an empty clip. it’s the one with the text inside.
Don’t look at bad programming ^^; it’s something I did long ago (two years) and has to be renewed (font for example…)

10

I’ve noticed one important thing!!!

If the text is at first frame of a sequence of frames (not necessarily keyframed) it will be perfectly pixelated.
Whenever you move to the next frame (even if nothing changes) the font will blur.

…or something like that… I’m going crazy… have a look at my file.

11

yawn

12

The problem is coming from that odd component thing. Why not just code the rotation of the gear using an easing function (so it slows down after it’s done spinning), and drop the clip nesting down to the essentials?

Create a MC for your button, then within that MC create a shape (we’ll pretend there’s one called “pentagonMC”), and add this AS to the first frame within your button MC (in its own actions layer):

rotateMC = function(targetMC) {
	targetMC._rotation++;
}
pentagonMC.onRollOver = function() {
	rotateInterval = setInterval(rotateMC, 10, this);
}

pentagonMC.onRollOut = function() {
	clearInterval(rotateInterval);
	rotationTween = new mx.transitions.Tween(this, "_rotation", mx.transitions.easing.Regular.easeOut , this._rotation, 0, 1, true);
}

I haven’t tested the code, but it’ll work.

13

wait so now im confused, bento, was your issue with your font being blurry or with your actionscript?

14

If he/she ditches the component and replaces it with a few lines of AS, it’ll alleviate the aliasing issues by leaving the text only a few levels deep.

15

well i already fixed his font a few posts up…just as i suspected, you didnt have your fonts on an absolute integer! tsk tsk

16

Daniel, go at the beginning and read all the posts!!! :upset: That fla was just an example to show how a text field on an absolute integer even if aliased will blur…

The real problem was on fla.fla…

Anyway, Kenny thanks for the trick, I’m going to try it now; You believe te problem is the odd coding? I can’t see how…

**still having problems!!! horray!!! :krazy: **
have a look at the new fla I’ve posted and tell me what you see. There’s no actionscript there, nothing, just a clip containing a text field. (because I have to make the text move/fade)

17

bento, my point was that your FLA. did NOT have the font or mc’s on absolute integers…go back and check my FLA that i posted compared to yours. i can never figure out how soooo many people have sooo many problems with fonts?

18

errrrgh, ok dude, i fixed this new one. this time, you had your character spacing set to -0.2…its got to be 0.

19

Danielthelion, the imcrazy.fla the text mc you sent isn’t absolute either on my computer. is it because we have different montior resolutions. But they are crisp. Just wanted to see if your fla is absolute

20

interesting, well im using FlashMX 2004…i dont know if thats an issue. but when i look at it the mcs are all on x: 405 , and y: 154, 176, and 198 respectively. when i go inside the mcs ,
l’idea : x: -15, y = -9
l’ideatore : -24, -8
and
la nascita: x = -24, y = -9

go figure.

oh yeah, and im using screen res 1280 x 1024