murarinayak / papervision3d

Automatically exported from code.google.com/p/papervision3d
0 stars 0 forks source link

BitmapFileMaterial sub-domain silent fail issue. #207

Open GoogleCodeExporter opened 8 years ago

GoogleCodeExporter commented 8 years ago
Trying to implement BitmapFileMaterial from a flash movie that resides on 
a different subdomain to the flash movie, and also with a different 
subdomain for the image asset being loaded. 

expected output would be the image being loaded as a texture/material, but 
instead only the black image loader is seen. If a moviematerial is used 
with, say, a pink background, and an image loaded via a normal loader 
object into the same movieclip, then the texture can be seen to go black, 
overlaying the pink mc underneath.

using the latest 2.0.833 zip version from the google code site.

The issue seems to silently fail. In the same SWF using a traditional 
loader as a simple MC added to the stage seems to work as normal. The 
silent fail may be to do with "Bitmap" in my opinion, but haven't got the 
time to investigate further at the moment. No security error or io error 
is encountered during the operation. Have tried with a fresh image and 
without the normal Loader object in the movie, so don['t think this is 
anything to do with local caching of the image asset.

have tried gif, png and jpeg and all seem to load in fine under normal 
core "Loader" conditions. Issue seems to be soley limited to use with 
BitmapMaterial.

Even tried loading in an image via "Loader", casting to Bitmap in a 
COMPLETE event handler, casting the bitmap from the loader, and then using 
the .bitmapData attribute for use in a BitmapMaterial object, and the same 
happened. I could see the normal "Loader" MC image, but not the loaded 
(cast) texture. Infact, the code, in a try catch, still seemed to SILENTLY 
fail!.

Hope this can be of some help. If not, I can provide badly coded source.

Fantastic product by the way!

Graham Campbell
graham.theguerrilla@googlemail.com
0776 997 6120 (UK +44 I think...)

Original issue reported on code.google.com by graham.t...@googlemail.com on 5 Jul 2009 at 10:27