you can do it the easy way: your material is a movieclip, you just load some slice of an image each success load, you update the material. Based on a simple check on camera rotationY you can define a mechanism which decides which of the slices needs be loaded first or only if camera looks at them...
Fabrice On Sep 15, 2010, at 3:01 PM, Darko Radiceski wrote: > Hi Fabrice, > > Thank you kindly for your response. > > I have done options 2 and 3 from what you described. The server is top of the > range, the connection is also good speed and images are heavily compressed > using a batch process using the gimp. > > Is there any advice you would offer on the slicing approach you mentioned? > Like the loading imageslice per quandrant? How would i define the quadrants > and what section to load to what quadrant? > > Thank you for your time. > > Cheers > Dan > > On Fri, Sep 10, 2010 at 5:51 PM, Fabrice3D <[email protected]> wrote: > Hi Dan, > Sounds like some 360 pano project... > > A good server is critical, especially if you have more of these pano's > loading. > On a past project I was working on, the chunk loading option was not even > necessary due to this server. > But for slower connections, indeed loading just what you see, say an > imageslice per quadrant does help. > > Also, if you export via photoshop/export for webdevices as jpg. > Even at 80 compression at sizes of 4096x4096 you indeed very often sizes as > yours. > I've wrote a little php using the gd2.dll, and turns out if I do export from > photoshop lossly, once i run my script, the file weights lower than 1/2 of > photoshop size. > with no visible diffs. A good idea is of course to automate, my php for > instance applies on a full directory you pass to it. If you know your way > around, it should cost you max an hour of work. > This little php effort is really worth it and saved me 1/2 the data on entire > content. > > Also very similar to the uvcropping feature Prefab holds, a tiltcropping is > often a way to minimize size for this kind of work, as you usually do not use > the poles because of the distorts. > most app generating these either add top/down some color strips or logos of > their eye fish cameras. There too, cropping and adjust mapping with repeat > and scaleY does save you 3 to 6 % of the map > depending on your tilt constrains. > > Loading low res, is a bad idea. not only you will have to load more, but it > will even slowdown processes on fast connections. > > Hope it helps a bit. > > Fabrice > > On Sep 10, 2010, at 3:15 AM, Dan wrote: > > > Hi all, > > > > My apologies if this may sound a bit noobish. > > > > I have a sphere that is loading a 1.2mb image. Would anyone advice on > > any ways this can be improved in speed? > > > > Maybe tiling the image in segments and load the slices on parts of the > > sphere? Only load those parts that are in view...... > > > > Or are there any other approaches you would suggest for progressive > > rendering? Could flash streaming server maybe be utilised? > > > > Are there any examples of this around? Or white papers? > > > > Thank you for you time. > > > > Dan > > > > > -- > Radiceski Darko > University of Wollongong > Australia > SIFE - UOW Chapter - Alumni > CASUAL ACADEMIC STAFF TEACHING - UOW SITACS > (School of Information Technology and Computer Science,University of > Wollongong) > Univeristy of Wollongong - Alumni
