I think ill go with scrollRect, ill try to hide everything except what the user sees on his monitor. That would be like 1600x1200 px of visible parts of the map.
If anyone has some math for scroolRect done post it here. If not, after a fiew days of brainstorming ill post the whole map component with zooming, scrooling and other features. --- In [email protected], "Troy Gilbert" <[EMAIL PROTECTED]> wrote: > > Oh, and another issue you may run into... coordinates inside a container > can't be outside of the range +/- 8191 or the object vanishes. So, that too > could be an issue when you get into larger maps depending on how you're > scrolling them around. > > I've run into both of these issues in my current work where I'm developing a > pretty open-ended game system which has required me to take on a lot of > issues that I had hoped Flash's native renderer would juggle for me, like > smart bitmap caching and coordinate virtualization (moving beyond the +/- > 8191 limit). I'll be honest, I've not solved them both myself, yet... but > will have to over the next few weeks, so anything you learn would be much > appreciated... > > Troy. > > > On 5/2/07, Troy Gilbert <[EMAIL PROTECTED]> wrote: > > > > Yeah, you're hitting the 2880 pixel limit with bitmaps. No bitmap, > > including cached bitmaps, can be bigger than 2880 px in either dimension. In > > the case of cacheAsBitmap, it stops caching when that's the case. > > > > Fortunately, you can control it a bit... I'd imagine that even when > > zooming in you're only showing less than 2880 pixels actually on screen. So, > > you can do a bit of caching. And you can control the size of the cached > > bitmap by setting the scrollRect for the displayObject. > > > > Now, I'm not sure if the scrollRect is "smart" in that when you move it it > > simply redraws (stupid) or does a partial copy and a partial render > > (smart)... if its smart, then you've got it pretty easy, just move the > > scrolllRect around your map instead of moving the map (or its SWFLoader) > > around inside a container. > > > > Another option would be to simply make the scrollRect be as big as > > possible while still being smaller than 2880px. This would allow you to drag > > the map around locally without it having to redraw but forcing a redraw if > > you dragged too far. Kinda similar result to a tiled renderer, not quite as > > efficient, but a whole lot less code! > > > > Troy. > > > > > > On 5/2/07, helix206 <[EMAIL PROTECTED]> wrote: > > > > > > Hello all, > > > > > > I have this strange ans stupid problem and the deathline is comming > > > in a fiew days, so i hope someone will be able to help me. > > > > > > First of, I am trying to drag a vector map inside another container > > > fluidly. > > > > > > So, I have a vector map, exported to .SWF. This map is loaded with > > > SWFLoader in another container, and the SWFLoader has a property > > > CacheAsBitmap set to True. Everything works just fine, and the map > > > drags very well inside the container. Problems araise when i zoom the > > > map (actualy scale it) beyond 2000px. Then draging becomes very slow, > > > and i sopose that CacheAsbitmap property just stops working. > > > > > > So, does anyone has any idea why is this heppening, and how could i > > > solve it? > > > > > > I will accept any sollution except tiling my map into 100 tiles and > > > showing only the ones that are on the screen. If no sollution will be > > > provided then i guess ill have to do it that way. > > > > > > Any help appriciated. > > > > > > > > > > > > > >
