svg exporter & viewport render #43300

New Issue

Cezary Kopias · 2015-01-17T22:02:42+01:00

Cezary Kopias commented

2015-01-17 22:02:42 +01:00

System Information
Win7x64 GTX660M

Blender Version
Broken: 2.73

Short description of error
there are two bugs:

internal viewport rendering is not working (unless you do f12 render),
doing blender internal viewport rendering appended to svg file

Exact steps for others to reproduce the error
open prepared simple blend svg-exporter-bug.blend
for first problem with viewport rendering not working just hit f12 render to create svg file
and after that there comes second issue - enable viewport rendering (now it works), rotate view and see how svg file goes bigger in size also you can open it to see that every viewport render is appended to this file.

besides that this is very cool - thx for great work

**System Information** Win7x64 GTX660M **Blender Version** Broken: 2.73 **Short description of error** there are two bugs: 1. internal viewport rendering is not working (unless you do f12 render), 2. doing blender internal viewport rendering appended to svg file **Exact steps for others to reproduce the error** open prepared simple blend [svg-exporter-bug.blend](https://archive.blender.org/developer/F137818/svg-exporter-bug.blend) for first problem with viewport rendering not working just hit f12 render to create svg file and after that there comes second issue - enable viewport rendering (now it works), rotate view and see how svg file goes bigger in size also you can open it to see that every viewport render is appended to this file. besides that this is very cool - thx for great work

Cezary Kopias commented

2015-01-17 22:02:42 +01:00

Changed status to: 'Open'

Tamito Kajiyama was assigned by Cezary Kopias

2015-01-17 22:02:42 +01:00

Cezary Kopias commented

2015-01-17 22:02:42 +01:00

Added subscriber: @kopias

blender-admin commented

2015-01-17 22:02:42 +01:00

#44392 was marked as duplicate of this issue

Julian Eisel commented

2015-01-18 13:02:06 +01:00

Added subscriber: @JulianEisel

Julian Eisel commented

2015-01-18 13:02:06 +01:00

If I understand correctly you mean the freestyle part is not working in the viewport rendering? Or is the viewport not rendering in general? In this case better to open 2 separate reports.

Cezary Kopias commented

2015-01-18 13:26:00 +01:00

the freestyle line rendering is not working (internal is ok) when you enable svg exporter unleass the *.svg file is created wich takes place when do f12 render

Tamito Kajiyama commented

2015-01-18 15:49:03 +01:00

Added subscriber: @flokkievids

Tamito Kajiyama commented

2015-01-18 15:49:03 +01:00

Thanks @kopias for the bug report. I confirmed the issue on my side. I will look into the problem.

Tamito Kajiyama commented

2015-01-19 14:35:27 +01:00

Added subscriber: @ideasman42

Tamito Kajiyama commented

2015-01-19 14:35:27 +01:00

I believe disabling SVG export entirely during viewport preview is the way to go. Generated SVG files are likely intermediate results and not supposed to be final output.

Plus, unlike the case of F12 rendering, none of render_init, render_write, render_pre and render_complete callback functions are executed in the case of viewport preview. The SVG export addon relies on these callbacks to get things done behind the scene.

We then need a reliable way to check if the Freestyle rendering process at hand is for viewport preview. Since none of the render callbacks are out of service, I feel like we need to employ something like proposed in the patch D921 (at the moment the checking is not done properly but that is easy to fix).

@ideasman42, do you have any thoughts on this matter?

I believe disabling SVG export entirely during viewport preview is the way to go. Generated SVG files are likely intermediate results and not supposed to be final output. Plus, unlike the case of F12 rendering, none of `render_init`, `render_write`, `render_pre` and `render_complete` callback functions are executed in the case of viewport preview. The SVG export addon relies on these callbacks to get things done behind the scene. We then need a reliable way to check if the Freestyle rendering process at hand is for viewport preview. Since none of the render callbacks are out of service, I feel like we need to employ something like proposed in the patch [D921](https://archive.blender.org/developer/D921) (at the moment the checking is not done properly but that is easy to fix). @ideasman42, do you have any thoughts on this matter?

Tamito Kajiyama commented

2015-04-15 02:05:32 +02:00

Added subscribers: @DanielGrauer, @kjym3