|
#1
|
|||
|
|||
texblend or visible for multiple textures
I have implemented the flipping between textures two different ways and would like to know if there are advantages to either approach (memory management, limits, etc).
I am loading about 1GB of texture at a time. Therefore, I would like to be displaying one texture while loading the next. First approach was to have tiles that have two textures each. Then use texblend to flip between them. I used director to load a new texture while displaying the other. The only drawback I have seen is panning over the texture was slowed by the loading. This was not visible when I moved to a faster PC. Second approach was to load each texture onto its own set of tiles. Then switch between them with quad.visible(viz.TOGGLE). This works well in that I can pan the texture while loading the other. However, as I try to load another texture I run out of memory. Removing the old textures at the right time may resolve this problem. As I initial said I would like to know if either approach is better and for what reasons. Thanks,
__________________
VizMaster |
#2
|
|||
|
|||
Hi,
Is it necessary to use texblend to flip between the textures? Can you simply apply the new texture to the tile once it is loaded, overriding the old one? I'm not clear on what you are doing in the second method. Is it loading both sets of textures into memory at once, then toggling between them? If this is the case then the first method won't have as much memory issues since you are loading the tiles on demand, but you will have performance issues from the loading. The second method requires more memory, but if all the data fits into memory then the performance should be better than the first method. For your case memory seems to be more of a bottleneck, so I would prefer the first method. Let me know if I misunderstood anything. |
#3
|
|||
|
|||
Hi,
Since I am loading over 1GB of texture, I load 2048x2048 of texture onto a each tile of a tiled billboard. If I load the texture dynamically it takes upto 20 seconds to load. To slow. The second method is loading both textures into memory. The thing is I don't want to only load two textures. While I am displaying one texture I would like to load the next texture to be displayed. In both approachs are the textures loaded into memory? Thanks,
__________________
VizMaster |
#4
|
|||
|
|||
some ideas ?!
@ Vizmaster:
Hi, I'm not quite sure what you're trying to achieve... are you trying to put up like an "advertising" within Vizard where the images loop / change with time? 2k x 2k texture is way to huge for this purporse, I don't know what your spec is, but loading a 2k x 2k for something to be displayed for less than 20 sec is a waste of hardware resources (IMHO) May I suggest another method if you're doing an "Advertising" within vizard where the image changing over time... [1] Use jahshaka to string all the images together, create a movie file .avi or .mpg where each image will be diaplayed for only say .. 10 sec. [2] export this video at this res 512 x 384 pixels or lower [3] Apply this video file onto a quad / poly and loop it. I hope this helps/gives some ideas. Regards, Iwan Macquarie University |
#5
|
|||
|
|||
A bigger picture
I am panning over a large panorama 50000x6000 pixels. Each tile represents 2kx2k portion of the entire image. Once the viewer is done with one image I want to display the next image in a timely manner. Currently an image can take up to 15 seconds to load. This is not acceptable for my needs. Therefore I plan on preloading the next image based on one of the methods I describe in this thread.
thanks for the ideas. Currently I am looking at still images. If I need motion I will keep your ideas in mind.
__________________
VizMaster |
#6
|
|||
|
|||
I've found ways to potentially speed up the loading time of the images and perform it asynchronously, while cutting down on the memory overhead. Do you need the entire image to be displayed at once, or can it show up in pieces as it is being loaded?
|
|
|