Adrien F wrote:
1. It is very sloooooow compared to V1.1 beta7. I mean is is absurdly sloooooo...ooow, it is just unacceptable I feel. Is this a consequence of adopting a new Flash 'rendering' technology/technique so as to remove limits to the size of panos it can handle?
We are aware of this problem, and working on it. It, effectively, has to do with the new way we internally handle pictures. This problem only shows up for 360x180 pano because we need to do a lot of work remapping the equi onto cube faces. (full 360 spherical projection has a too bad quality to be considered).
A current/provisory workaround : use less CPU and more memory.
Just to provide some data for those following this thread who haven't been experimenting with APT V.1 beta 9 :
The screenshot below shows the small test tour I am 'playing with'.
There are three pano images and a Map image that I also use as an Intro image:
Pano 1 - 360x180 - 8,000x4,000 pixels, 7.24MB JPEG.
Pano 1 - 360x180 - 8,000x4,000 pixels, 5.12MB JPEG.
Pano 1 - 360x180 - 2851x1626 pixels, 1.24MB JPEG.
Map/Intro image - 400x200 pixels, 10KB PNG.
To Export to Flash took 14 minutes 17 seconds on a Dell T3400 desktop PC, with Intel Q9300 quad core CPU, 3GB RAM, Windows XP Pro 32-bit.
Incidentally when timing the Export I found the xx% progress bar somewhat misleading; it took ages to get to 51% and the almost instantly finished. Is there any simple explanation for such behaviour? Is there any chance we might get more informative stats such as those now offered with APG 2.5 Alpha 1.