Using the cached framework should help. If you test from FlexBuilder you may not get correct streaming. Try testing using http: instead of file:
Also, there is a bug if you use # in the URL. It blocks streaming of the SWF and delays startup time. Do you see a progress bar at all? Alex Harui Flex SDK Developer Adobe Systems Inc.<http://www.adobe.com/> Blog: http://blogs.adobe.com/aharui From: [email protected] [mailto:[email protected]] On Behalf Of Dan Sent: Monday, July 06, 2009 8:56 PM To: [email protected] Subject: [flexcoders] Horrible... 3 seconds initialization time for the first frame? Frustrated.... Hi, Does anyone have any idea on why it takes nearlly 3 to 4 seconds after a swf completely downloaded, is it SystemManager initialized and go to the second frame of the movie? It is such a great penality for an web application. Should I put tasks, such as automatic login to the preloader, in order to shorten this penality period??? Otherwise, no matter whatever tuning techique flexcoders applied, the Adobe penality is still too great. I understand there should be initialization time, and that may depends on the client machine configuration. However, for a simplest swf with an <Application> tag only mxml, a log is being output on the onEnterFrame event, it already takes 3 to 4 seconds for the first log after the swf complete download, (time logged from Charles), it is so frustrated... Does it means that we have no way for a faster response time if we choose Flex? (Didn't mention about the download time for swf already...) Anyone can help? Dan
