Issues with AIR Application on 8000x2500 Interactive Wall

Question

Hello,
I am trying to develop apps for a large interactive wall and I seem to be running into the 4096x4096 bitmapData limit. This post: http://stackoverflow.com/questions/8277639/no-more-constrain-on-bitmap-resolution-in-flash -player-11?rq=1 says that the limit has been removed since Flash version 11 (I'm running Flash 12 and AIR 4.0) however I am seeing display object being cut off at exactly x=4096.
My app is basically this...
I have 30 sprites (each 600x428 and each with an image on front and back) spread evenly across the wall (10 colums and 3 rows). I use Papersprite and Tweener to flip (rotationY) each sprite over once they are touched. Before being touched, they all display perfectly across the wall. When I touch a sprite past x=4096, they dissapear completely, or they are literally cut off/in-half at x=4096. Before x=4096, they flip perfectly. Also, another application I made has many images that are 8000x2500 and they each fade in/out, also using Tweener, to the next with zero issues like this at all.
According to the link above the bitmapData size is dependent on the OS and RAM. The wall is run by very high end computers with the latest graphics cards and stacked RAM.
Can anyone explain what is happening and how I can overcome this issue?

Answer 1

CAB would be detrimental to performance on the top container for sure.  CAB just creates bitmaps of your sprites and therefore uses up a lot of memory -- that's why I was enquiring if you were using it.
I you are using CAB, I would disable it and see what happens.
My guess is that your GPU memory gets filled-up / corrupted during the compositing step of the second frame.   Rendering the first, full frame is fine.  Compositing the portions that have changed in the following frames, isn't.
Things to try:
Using stage.invalidate() to force a redraw of the entire stage, not just the portions that have changed since the last time the frame was drawn.
If you have a mouse move handler, you might also want to try evt.updateAfterEvent() and see what happens.
Try CPU and Direct render modes.
PaperSprite isn't a standard AS3 class, and a cursory look at http://blog.soulwire.co.uk/code/open-source/two-sided-planes-in-flash-player-10 seems to point to it doing some funky things with stage.invalidate() -- surprise, surprise ! -- and the Event.RENDER, etc.  It may all be fine, but it could also be that your problem comes from the PaperSprite class.  What I would try is to use a regular, single-sided Sprite, instead, as a test, and see if the same problem occurs when you try to flip it.  If the problem doesn't happen, then I would dive into the source code for PaperSprite, or come up with a different approach, like flipping quads in Stage3D.
In case you are new to molehill, the best source to get started with Stage3D, imo, besides the AS3 documentation code examples, is this book:
http://www.amazon.com/Adobe-Stage3D-Molehill-Programming-Beginners-ebook/dp/B006EEJSHM/ref =sr_1_1?ie=UTF8&qid=1393740087&sr=8-1&keywords=molehill+stage3d