Hello guys! I’m the first learner in away3d4
i love away3d,i made an application and it’s cool in desktop air.but I turn it to android or IOS,I found it not smooth.I tested it on ipad2 or Galaxy P7510 tablet.
does the Anti-aliasing(View3D.antiAliasing) is not supported by mobile devices? how can i improve the quality?
I saw Fabrice’s sample RoomDemoMobileCR.apk,it is wonderful.have you typed some special codes in mobile project?
Thank you !

No secret code
The demo was made with the early draft of Prefab’s AS3 outputs (after merge was used). The model on itself, nicely crafted by Olivier Boscournu, a french artist, does lots of the overall impression.

Here another demo using similar technic and same artist: http://www.closier.nl/HermanDemoMobileCR.apk

Prefab?This is my first time to hear that,and i searched some infomation about Prefab,It’s a useful tool.
if I want to create a simple geometry like a cube object,and if i want this cube smooth in mobile device,should i still create it by Prefab?

woooo!Prefab it’s amazing….http://blog.closier.nl/

have fun
oh and yes, there is a primitive editor in there. And till v2 do not have all v1 features restored such as the UV editor. You can install v1 too and combine them. Export as awd1 is the easyest way to transport from one to the other.

To answer the original questions:

Anti-aliasing is not supported on most if not all mobile devices (limitation of the Stage3D API and/or the device.)

Performance is generally slower on mobile devices, so things that you might get by with on a PC might be too slow on a mobile device. Generally, if you follow good practice on a PC, you will get good performance on mobile as well since the general concepts are the same. Some of these are:

Try to use few buffers. Merge objects that do not need to move into single buffers. Re-use geometry between several meshes if they are intended to look the same.

Use few textures. Merge textures into atlases and adapt the UV coordinates to match the new texture coordinates in the atlas.

Don’t do things that require upload from CPU memory to GPU memory, e.g. video materials (or other animated materials that require texture upload every frame), CPU vertex or skeletal animation et c.

Anti-aliasing is really needed on mobile.However,the stage3D does not support anti-aliasing on even ipad4.May away3d4 supply a nice filter3D of FXAA please?

Hello Fabrice! Can you tell, if i will use Prefab3D it smooth big pixels around spheres?

Hi,

since I’ve spent hours trying the figure out what’s the point with Away3D anti-aliasing on iOS, Away3D anti-aliasing on a retina display, Away3D retina, Away3D retina display resolution, AIR Stage3D anti-aliasing on iOS, AIR Stage3D anti-aliasing on mobile devices etc. Here is one, clear answer, so you don’t have to waste your time websearching, reading dead-end-forum-conversations and end up being frustrated about all that:

As for today (December 2015) AIR / Away3D / Stage3D anti-aliasing of 3D-content is disabled for all mobile devices on the runtime-side.

That means that the edges of your 3d-object will always be jagged on a mobile device, no matter what value you set on View3D.antiAlias property. On hiDPI devices (e.g. Retina Display) the jaggedness is less obvious, but still clearly visible. And no, you currently can’t make this better, i.e. “supersharp”.

You could use a FXAA-filter, but this solution doesn’t make runtime-side-anti-aliasing redundant. The only filter I could find for Away3D is this one, shared by iY0Yi:

FXAAFilter3D: https://gist.github.com/iY0Yi/9214675
Filter3DFXAATask: https://gist.github.com/iY0Yi/9214656

There is a new feature-request on Adobe Bugbase concerning stage3D anti-aliasing on mobile devices I would strongly encourage you to vote for:
https://bugbase.adobe.com/index.cfm?event=bug&id=4101164

Thank you & good luck with your 3D mobile app.