PDA

View Full Version : Clients feedback - How can I improve ?


DMCDigital
12-05-2007, 11:26 AM
Hello All,

I have used FPP to build several Real Estate Tours thus far, feed back is much better than before...they love the layout and fullscreen but everyone who sees them comments on the "swimmy look" (is that even a look), Blinky look, twinkle look.

These are all clients who have used my Java tours for years. I have segments at 45, quality at best both static and motion, cubefaces 1400 x 1400 (making them smaller doesnt help), Tried both cubefaces and .mov ...only diff was cubefaces seem to load faster.

What can I do to lessen the "look" they describe ? am I doing something wrong?
I would prefer to use FPP as more people have been able to view it without a download than with my java tours. I explain to clients Java 87% installed base VS. Flash 98% and the benefits of flash, still 3 out of 4 have opted to stay with Java if I give them the choice.

Guess I brought it on myself giving them 2 links side by side...obviously java has better anti aliasing .....Has anyone else heard this feedback from clients ?

Will hardware acceleration in Flash 9 solve the problem by allowing more aggressive anti-aliasing ?

I love FPP and will continue to offer it ...just want to get the best quality possible...(Yes I know "but they are REAL ESTATE LOW END TOURS....." Still need to be best possible lol )

Links for comparison:

Flash

http://www.dmcdigitalmedia.com/hostvt/flashbetaCUBE/index.html

Java

http://www.dmcdigitalmedia.com/hostvt/ricksample/index.htm

Regards all,

Dennis

zleifr
12-05-2007, 07:21 PM
Hi Dennis,

Nice photography, nice tour!

You might try setting qualityMotion=high See how much that impacts panorama performance / display quality. I think that what your clients describe as the shimmers is the low quality anti-aliasing while the pano is in motion.

If setting the qualityMotion=high is not feasible, then you might try minimize the actual viewing that is done while the pano is in motion by setting it to behaviour=1 (or 0), or playing with the friction combined with behaviour=2.