You may not be using Bitmap functions - but any filters etc. will use them under-the-hood, and will have the 2880x2880 limits.
I'd be tempted to suggest that you break up your large background JPG into four chunks; see if that clears the crash. HTH, Ian On Sat, Sep 5, 2009 at 4:41 PM, Paul Steven<paul_ste...@btinternet.com> wrote: > Thanks Ian > > I am not using any bitmap functions. I literally just have the jpg inside a > movie clip and move it based on the mouse position in relation to the plane > (the plane is centred on the screen). The only other game element really is > 20 clouds that randomly move across the screen. > > I am doing as you suggest and commenting out each potential game element and > trying to isolate the problem. > > I was hoping there was some way of using a debugger version of the flash > player to get more information on the problem but this does not seem to be > possible. > > Cheers > > Paul > > -----Original Message----- > From: flashcoders-boun...@chattyfig.figleaf.com > [mailto:flashcoders-boun...@chattyfig.figleaf.com] On Behalf Of Ian Thomas > Sent: 04 September 2009 19:22 > To: Flash Coders List > Subject: Re: [Flashcoders] Rather urgent advice on how to track the cause of > a crash > > On Fri, Sep 4, 2009 at 6:16 PM, Paul Steven<paul_ste...@btinternet.com> > wrote: > >> The game is basically a top down flying game with a scrolling background >> (JPG 5120 X 4320). The flash movie is published at 1600 x 1200 30 FPS. It >> includes an embedded FLV video on the Splash screen which is apparently >> 639kb of video data. There are no audio files in the game. > > Only immediate thing in that is that bitmaps in Flash Player 8 and 9 > need to be less than 2880 x 2880 pixels or bitmap functions will > simply fail. (Doesn't apply to Flash 8/9 content being run in Flash > Player 10, afaik). > > Other than that - my normal approach to such things is to find a way > to replicate the error if possible, comment out potentially offending > code in large chunks until the crashing stops, uncomment code > gradually until it starts crashing again. Judiciously combined with > trace statements which show you how far along execution has got. That > should narrow down the routines causing the problem. Can't think of > any immediate solutions other than that, sorry! > > HTH, > Ian > _______________________________________________ > Flashcoders mailing list > Flashcoders@chattyfig.figleaf.com > http://chattyfig.figleaf.com/mailman/listinfo/flashcoders > > _______________________________________________ > Flashcoders mailing list > Flashcoders@chattyfig.figleaf.com > http://chattyfig.figleaf.com/mailman/listinfo/flashcoders > _______________________________________________ Flashcoders mailing list Flashcoders@chattyfig.figleaf.com http://chattyfig.figleaf.com/mailman/listinfo/flashcoders
