Antialiasing for vectors

Hi, I have read few times that vectors objects supports antialiasing now, but I cannot make it work. Is there some property to set or configuration settings? I rendered objects on GSIII but it wasn’t as smooth as expected (small partial aliasing visible)

You just need to set antialias = true in your config.lua.

However antialiasing is done only if it’s supported by the hardware. I would assume the Samsung Galaxy III would support it.

In my testing I’ve also seen that the antialiasing isn’t perfect, but it’s much better than when it’s turned off!

A word of warning though. Having antialias=true in your config.lua can cause unpredictable behavior on iOS devices in combination with Graphics 2.0. It’s being investigated.

I do not understand why Corona won’t make antialiasing as function, ie. you can turn it on when you need (ex. you need to drawe antialiased chart), and turn off for the rest of application :frowning: Or just turn antialiasing on for vectors alone…

I think many developers will be glad if someone form CoronaLabs Team will give few words regarding this issue (sometimes there are properties or functions or constants that are not included in documentations or are not blogged yet)  :)

I would suggest that you go to http://feedback.coronalabs.com and put in a feature request for this antialasing on/off feature.  I don’t know enough about the graphics pipeline to know if this realistic or not, but the feedback site is the proper place to request it.

Thanks

Rob

Ok, I will send there.

Posted:

http://feedback.coronalabs.com/forums/188732-corona-sdk-feature-requests-feedback/suggestions/5034842-switchable-antialiasing-during-runtime

Assuming the issues are fixed with graphics 2, what are the negative sides of having this turned on for everything? Performance hit?

Assuming… as poted above it’s only assumption

You just need to set antialias = true in your config.lua.

However antialiasing is done only if it’s supported by the hardware. I would assume the Samsung Galaxy III would support it.

In my testing I’ve also seen that the antialiasing isn’t perfect, but it’s much better than when it’s turned off!

A word of warning though. Having antialias=true in your config.lua can cause unpredictable behavior on iOS devices in combination with Graphics 2.0. It’s being investigated.

I do not understand why Corona won’t make antialiasing as function, ie. you can turn it on when you need (ex. you need to drawe antialiased chart), and turn off for the rest of application :frowning: Or just turn antialiasing on for vectors alone…

I think many developers will be glad if someone form CoronaLabs Team will give few words regarding this issue (sometimes there are properties or functions or constants that are not included in documentations or are not blogged yet)  :)

I would suggest that you go to http://feedback.coronalabs.com and put in a feature request for this antialasing on/off feature.  I don’t know enough about the graphics pipeline to know if this realistic or not, but the feedback site is the proper place to request it.

Thanks

Rob

Ok, I will send there.

Posted:

http://feedback.coronalabs.com/forums/188732-corona-sdk-feature-requests-feedback/suggestions/5034842-switchable-antialiasing-during-runtime

Assuming the issues are fixed with graphics 2, what are the negative sides of having this turned on for everything? Performance hit?

Assuming… as poted above it’s only assumption