problem:
get one high quality object / panorama without embeding QTVR ones and avoid deal with medium-advance AS.
The final result its this easy but rudamentary intent to solve that problem I know its the most anti code/memory/time/common sense friendly need a lot of repetetive work changing the number of frames, but works.
1.- How to configure your 3d scene
determine the quality of your Vr object/panorama that means the number of your horizontal and vertical images, your horizontal images its the total amount of images you need to surround your object example:80 frames means one freme go 4.5 deg ( 360 / 8 = 4.5), for the vertical in most cases you only use 90 deg. if its for example something in the ground, and you need less layers or rows, the best results I get horizontal = 130 frames ( 2.76 deg each) vertical = 7 rows ( 12.87 deg. each) in this case the total images used = 7 x 130 = 910
You could easy bypass this calculations using one of your best friends the array tool, but its important you know where the number of frames comes and why that number give you the best quality/speed ratio
in this example we only have 5 layers and 20 frames per layer thats = 100 images
2.- Flash scene setup
create 3 layes 1.- code, 2.-buttons, 3.-images, in the code layer on the first frame just add one “stop” from as library, next in the layer images import all your images, its important to have order on this you could create a plain string from 1 to 100 or different strings to identify layers something like a_001 to a_020 for the first layer b_021 to b_40 for the seccond layer and so on
Now in the buttons layer create one button symbol, this button ony has one rectangle in the hit section, and thats all,in the scene just add the nex code to the button.
on (rollOver) {
gotoAndStop(1);
}
Here is when comes the hard part you need to copy several times your button and change the number 1, for 2 from the code and so on, that depends on the number of your total number of images/frames
In this example you need to place and align 5 layers of buttons each has 20 frames/buttons, if your image has 800 x 500 pixels, you need to array 20 buttons width and 5 buttons heigh that means each button its 40x100 pixels, in this case its a low res object, and you note the change, the vertical its more exagerated than the horizontal movement, you just need to add more images but that increase the amount of work in the 3d app, in flash changing the number of each frame in each button (here is when I think Im in the middle age using AS)
Pros:
1.- Well looking result if you add the correct amount of images the transitions could be near perfect.
2.- If your project its one catalog you could use the same .fla file just replacing the images and avoiding the process of changing each frame number in each button.
3.- Same good results for panoramas or objets.
4.- The image quality its better than the used in QTVr
5.- If you dont know plenty AS just perfect! wellcome to the middle age and start colecting patience to rename each button.
6.- Could be usefull for real images too but only using the 3d app as a bridge to render each precise frame
Cons:
1.- Did I mention the hard work to rename each button? specialy when you want to achive smooth results like using lets say 1500 images! that cause you nightmares believe me
2.- Do your math if you use 1500 images and each use 50kb you easy deal with one fla file of 75 Mb and here is when flash crash and you have more nightmares.
3.- As you use “on (rollOver)” you loose that dragin feeling like in real QTVr, thats undesireable if you use this tecnique in presentations, because you cant point with your mouse one specific area in the object or panorama.
4.- 3d apps knowledge
Download flash files
[URL=“http://rapidshare.com/files/102445912/flashVRobject.fla”]flashVRobject.fla
flashVRobject.swf
