Export from XPGD 6, Import to Flash CS4, Problems With Every Format

**Squeaky** · 31 August 2010, 05:20 PM

You are not going mad.
There is something very wrong there. I even had problems when I recreated the 3 circles from scratch.
The only way I could get them into Flash properly was to do them individually and they worked fine. As 3 objects on the page or a group I got the errors you experience. Even converted to editable shapes I got the errors. (as did using squares)
If - however - I drew some freehand shapes with the same fill attributes they exported to flash perfectly....well, apart from being no use at all as circles (or squares). I guess I haven't run into this because nearly all my content for Flash is hand drawn. It looks like a world of pain when I do need that functionality.

I'd say this was a bug and that you should report this to tech support. I'll cheer from the side lines and join in if I can. :-(

**ToddS** · 31 August 2010, 07:07 PM

Originally Posted by Squeaky

You are not going mad.

Thanks for that, Squeaky! I needed to hear it!

**Squeaky** · 31 August 2010, 07:31 PM

I've been there mate. Group testing always helps :-)

**ToddS** · 07 September 2010, 05:53 PM

I opened ticket number BVK-794761 with Xara on 8/25. No response yet.

**Squeaky** · 08 September 2010, 09:16 AM

I'm suspecting the 'fault' is actually pretty useful to the way Xara does animation with quick shapes. Shame it is so disastrous for the basic swf export.
Let's hope it is something they can fix with a patch. I suppose the only other work around is to use older versions of xtreme as i think it is impossible to draw circles point by point.

**Squeaky** · 27 September 2010, 06:25 PM

Yes well. I've just run into this again. I exported some type with a radial fill to Flash. I needed to break it apart in order to animate the transparency. When I did the letters became white. A bit of a problem that!
I have reported it to Support :-(

**ToddS** · 06 October 2010, 04:11 PM

Customer service did some tests, they sent a file to me, I made some revisions, they did some more tests, and they've formally filed a bug report. Hopefully a future update will give us a solution. Perhaps the option to "export for import" since I'm fairly sure this bug is the result of a super-optimization that they surely won't want to undo.