Author Topic: Rndering issue on AIR Mobile build  (Read 197 times)

Stanislav Rimsha   «   on: May 16, 2012, 01:28:49 PM »
I was doing it just for testing purpose but I thought you guys may want to see this. I've built an app for AIR Mobile 3.2 for android from a flare3d example showing my own collada model (around 5500 polys). Application runs very smooth (more than 30fps for sure) just requires about 10 seconds to load the model. But it shows a rendering issue as shown at the pics (screenshots from phone) which doesn't exist in a usual flash player 11 build for desktop.

http://dl.dropbox.com/u/37429612/2012-05-16%2015.50.23.jpg
http://dl.dropbox.com/u/37429612/2012-05-16%2015.50.29.jpg

Please tell me if there's a way to solve this)

Ivan Vodopiviz   «   Reply #1 on: May 16, 2012, 06:47:57 PM »
Hi,



Do you have depthAndStencil enabled in your AIR application XML file? Always make sure that your config has the following lines:

<renderMode>direct</renderMode>
<depthAndStencil>true</depthAndStencil>

Regards,
Stanislav Rimsha   «   Reply #2 on: May 17, 2012, 10:08:51 AM »
Hello!
Thank you for the reply.
In which section shall I add the line and what exactly does it do?
Regards,



               
                  
                     "Hi,



Do you have depthAndStencil enabled in your AIR application XML file? Always make sure that your config has the following lines:

<renderMode>direct</renderMode>
<depthAndStencil>true</depthAndStencil>

Regards,"
                     Ivan V.
                  
               
               
Ivan Vodopiviz   «   Reply #3 on: May 17, 2012, 10:26:49 AM »
Hi,

renderMode configures the app to use direct 3d rendering and is needed for Stage3D, while depthAndStencil enables the depth and stencil buffers, that are needed to sort polygon order effectively. This is a gross oversimplification, though.

In this particular case, enabling depthAndStencil should fix the polygon order issues you seem to be experiencing.

Cheers,
Ivan Vodopiviz   «   Reply #4 on: May 17, 2012, 10:28:02 AM »
Argh, forgot to mention: These two settings should be in your initialWindow XML node.
Stanislav Rimsha   «   Reply #5 on: May 17, 2012, 06:59:59 PM »
Worked perfectly, thank you for the hint!
Regards
Pages: [1]