Windows 7 Pro 64-bit, SP 2
GeForce GTX760 driver 334.89
I have encountered the following problems with the new Freestyle SVG output. I have lumped all of these issues into the same report because they all relate to filenaming conventions, numbering and layer problems within the output file(s).
(1) The filename as created by Blender does not automatically add the .svg extention to the filename. Not all programs (in the Windows OS) correctly identify the SVG file as such without this extension. By way of example, the freeware program, Inkscape, does not care whether or not the filename has the .svg extension and opens the file as expected. The Adobe Illustrator (version CS5) on the other hand incorrectly identifies the file without the .svg extension as a text file. The safest approach is to make certain that the output filename always has the .svg extension.
(2) If the user fails to provide a directory namefor the file output field (RenderSettings.svg.path) then the program will provide no SVG output whatsoever. This is not consistant with the behaviour of the the image file output from Blender. In my opinion, if the file output field remains empty then Freestyle should default to writing the SVG output to the same directory where the image files are put.
(3) If the user does provide a directory path but fails to put in a filename then the program will again provide no SVG output. There is an error message concerning this, but this is only to be seen in the system console window... if one has it open and if one remembers to look.
(4) Freestyle fails to append the frame number to the SVG output. This should happen in the same way as for image output... where each frame is numbered by default. Rendering separate frames has the unfortunate result of simply overwriting the same SVG file each time. The expected output would be something like filename_0001.svg, filename_0002.svg, etc.
(5) The SVG Export setting (RenderSettings.svg.mode) seems to have no effect and always produces the same results. In both cases the program writes every frame of animation to the same file. Unfortunately, the individual frame output is not separated into layers. This makes the output very difficult to use.
In my opinion, if the SVG Export setting is set to 'Frame' then the program should always output a sequence of individual, numbered files. If the SVG Export setting is 'Animation' then perhaps one could expect one single file, with each frame of SVG information written to a separate layer (with numbered layer name) within that file.