Artur Biesiadowski wrote:
> So my question is, how much time, does this preparation take ? Certainly > too much to do it dynamically between frames, but is it also too lengthy > to do it on level/area load/switch ? To give you a rough idea about ROAM: 833MHz laptop (not known for good I/O performance) takes about 3 seconds to process a 513x513 point grid to break it into the initial patches (64x64). After that, you need to compute the first set of view information, so you're already well on the way to that 5 second mark, without having done any extra information. I think the general problem is that pretty much all of heavy optimisation algorithms are based around computing visibility information of some description. Once you go down that path compute times sky-rocket because it is essentially a huge set of picking from almost every point in the world to every other point. To add one more point, based on the collective experience of the VRML people, waiting an extra 5 seconds for content is a huge turn-off for most people. People want things now and aren't prepared to wait for a little extra time. -- Justin Couch http://www.vlc.com.au/~justin/ Freelance Java Consultant http://www.yumetech.com/ Author, Java 3D FAQ Maintainer http://www.j3d.org/ ------------------------------------------------------------------- "Humanism is dead. Animals think, feel; so do machines now. Neither man nor woman is the measure of all things. Every organism processes data according to its domain, its environment; you, with all your brains, would be useless in a mouse's universe..." - Greg Bear, Slant ------------------------------------------------------------------- =========================================================================== To unsubscribe, send email to [EMAIL PROTECTED] and include in the body of the message "signoff JAVA3D-INTEREST". For general help, send email to [EMAIL PROTECTED] and include in the body of the message "help".
