What happened here? The image looks OK in inkscape. But when I export it I get this. blob.

This a screen cap is what it is supposed to look like:



This is what the exported file looks like:


The SVG file here: http://www.petaimg.com/uploads/1217139069.svg

Is there a way to fix this?

Dunno if this has anything to do with the problem. I made the left 50% of that shape then dupped, reflected and combined that paths to make as symmetric as was reasonably possible.

PS please don't post an svg image in this thread. I don't know why but SVG crash my FF (which, yes, is the latest version) and won't display in IE. For some reason when they are posted to petaimg I can see them if I go to the site directly. And FF doesn't crash. Life is crazy under window

I can't reproduce it on Inkscape 0.46 on Windows. What version are you using?

I'm using 0.46. Hmmmm. Well it's reproducible with this file. But only happens as resolutions above 214, for some reason. I was exporting at 300 by default. If the export resolution is between 200 or 150 the png file it looks right. Is it just this file that has gotten corrupted? I can send you the svg file if you want to see it for yourself. I made that intending to use it as part of a desktop wallpaper so I need a fair amount of resolution, I think.

Yeah I think that may be it. Similar things have happened to me when working on projects that take a lot of memory.

llogg wrote:Yeah I think that may be it. Similar things have happened to me when working on projects that take a lot of memory.

Yayh, it's not one of the bugs that only happens to me I can die happy now or something.

If you don't have a work around already, you could try using Batik Rasteriser to convert the SVG to PNG. Or you might like to try one of the dev builds - viewtopic.php?f=6&t=1289

microUgly wrote:If you don't have a work around already, you could try using Batik Rasteriser to convert the SVG to PNG. Or you might like to try one of the dev builds - viewtopic.php?f=6&t=1289

I used to complain about the reallllllllyyyy slow speed of the exports in 0.45. But I exported a more complicated image at 600 dpi resolution without a problem. It took a couple of hours but it worked. Maybe I should down grade. J/K

Inkscape has long had a problem with parts of paths disappearing at certain sizes, though it usually only happens with very complicated paths. I doubt that 0.46 is any worse than 0.45 in this respect.

You should be able to work around it by exporting at a larger size for which the problem doesn't occur, and then scaling the resulting PNG in a bitmap editor. Or just use Batik, as microUgly has suggested.

sas wrote:Inkscape has long had a problem with parts of paths disappearing at certain sizes, though it usually only happens with very complicated paths. I doubt that 0.46 is any worse than 0.45 in this respect.

You should be able to work around it by exporting at a larger size for which the problem doesn't occur, and then scaling the resulting PNG in a bitmap editor. Or just use Batik, as microUgly has suggested.

Does a clipped path with 316 nodes including 15 exclusions count as complicated?

It's OK when I export at 600 dpi and 1200 dpi. I thought the problem would just get worse as I increased the resolution. I figured it was an out of memory problem or something like that also.

It's weird how the left side comes out OK and the the right side (which is just and flipped duplicate of the left) gets messed up. Seems like they should be the same size.

Thanks sas and microUgly now I got multiple options on how to fix it.

EarlyBlake wrote:Does a clipped path with 316 nodes including 15 exclusions count as complicated?

No, I don't think that should be too complicated. But if it's memory related answer might depend on your system--I was able to export it fine with 2GB of RAM.

I remember now that a complicated drawing I had done (210 objects and possibly many thousands of nodes--don't know how to check that number) suffered from missing sections. But Inkscape 0.45 and 0.46 trimmed away different parts, so I had to manually combine the results of the two

microUgly wrote:No, I don't think that should be too complicated. But if it's memory related answer might depend on your system--I was able to export it fine with 2GB of RAM.

I thought if it was a memory problem the image degradation would get worse as you upped the resolution on the exported file The missing parts magically reappeared when I jumped to 600 dpi and 1200 dpi. They are missing between 214 dpi and 400 something dpi... go figure. I've go 2 gig on my lap top. I went heavy memory wise when I go it so I could use speech recognition software. The speech recognition eat more memory than it does CPU time for some reason.

So you were able to down load the svg file form petaimg and export it yourself?

Yes, but I didn't check what res I used. I think it was the default res.