FreestyleSVGExporter-RelativePath #47804

Closed
opened 2016-03-15 11:44:48 +01:00 by Maciej · 9 comments

System Information
WIN8.1x64 GPU=2xGTX770-4GiB

Blender Version
Broken: 2.76b f337fea

Short description of error
Exporter works just fine when
bpy.context.scene.render.filepath is absolute
and does nothing when relative

Exact steps for others to reproduce the error
Based on a attached .blend file with minimum amount of steps
ikonki.zip

Just change output from relative to absolute.

**System Information** WIN8.1x64 GPU=2xGTX770-4GiB **Blender Version** Broken: 2.76b f337fea **Short description of error** Exporter works just fine when bpy.context.scene.render.filepath is absolute and does nothing when relative **Exact steps for others to reproduce the error** Based on a attached .blend file with minimum amount of steps [ikonki.zip](https://archive.blender.org/developer/F292075/ikonki.zip) Just change output from relative to absolute.
Author

Changed status to: 'Open'

Changed status to: 'Open'
Folkert de Vries was assigned by Maciej 2016-03-15 11:44:48 +01:00
Author

Added subscriber: @ethoriell

Added subscriber: @ethoriell

Added subscriber: @Sergey

Added subscriber: @Sergey

@flokkievids, are you around to look into the issue?

@flokkievids, are you around to look into the issue?

Added subscriber: @AditiaA.Pratama

Added subscriber: @AditiaA.Pratama

I've check the blend file and manage to fix this issue, please check the diff below

render_freestyle_svg.diff

I've check the blend file and manage to fix this issue, please check the diff below [render_freestyle_svg.diff](https://archive.blender.org/developer/F336489/render_freestyle_svg.diff)

Sorry that this took so long

The patch by @AditiaA.Pratama does not work correctly for me: it uses the location of where the blender executable is called instead of
the location of the current file as the base for a relative path. This also makes me wonder what the correct semantics would be,
currently I think:

  • if the file is saved, use the location of the current file
  • otherwise, use the location of the blender executable

I guess that for most artists, these two locations are the same. For developers this is not the case. I will try to have this fixed later today.

Sorry that this took so long The patch by @AditiaA.Pratama does not work correctly for me: it uses the location of where the blender executable is called instead of the location of the current file as the base for a relative path. This also makes me wonder what the correct semantics would be, currently I think: * if the file is saved, use the location of the current file * otherwise, use the location of the blender executable I guess that for most artists, these two locations are the same. For developers this is not the case. I will try to have this fixed later today.

Changed status from 'Open' to: 'Resolved'

Changed status from 'Open' to: 'Resolved'

closed by commit fab62e930c

I am not able to test this on windows at the moment. I assume Python solves any problems, but a windows test would still be much appreciated.

closed by commit fab62e930c I am not able to test this on windows at the moment. I assume Python solves any problems, but a windows test would still be much appreciated.
Sign in to join this conversation.
No Milestone
No project
No Assignees
4 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: blender/blender-addons#47804
No description provided.