Compositor Doesn’t Show Terminals For Freestyle-Only Layer #43201

New Issue

Lawrence D'Oliveiro · 2015-01-11T02:19:39+01:00

2015-01-11 02:19:39 +01:00

The enclosed .blend file Freestyle_Outline_Only_Bug.blend demonstrates a bug when trying to create a Freestyle-only renderlayer. The scene has two layers being merged in the compositor. The Foreground layer had Freestyle settings enabled, and then was connected into the Alpha Over node, after which I turned off all the actual render passes to get just the Freestyle lines.

This works, but however if you look in the Compositor window, you cannot see any terminals coming from this renderlayer node! This even though they are still connected to the right places. To adjust the connections, you have to temporarily re-enable at least one pass, make your connections/disconnections, then disable all the passes again.

Seems to me there is a checkbox missing from the renderlayer Passes panel for explicitly including a Freestyle pass, and the output terminal should not be disabled unless this is unchecked as well.

The enclosed `.blend` file [Freestyle_Outline_Only_Bug.blend](https://archive.blender.org/developer/F136594/Freestyle_Outline_Only_Bug.blend) demonstrates a bug when trying to create a Freestyle-only renderlayer. The scene has two layers being merged in the compositor. The Foreground layer had Freestyle settings enabled, and then was connected into the Alpha Over node, after which I turned off all the actual render passes to get just the Freestyle lines. This works, but however if you look in the Compositor window, you cannot see any terminals coming from this renderlayer node! This even though they are still connected to the right places. To adjust the connections, you have to temporarily re-enable at least one pass, make your connections/disconnections, then disable all the passes again. Seems to me there is a checkbox missing from the renderlayer Passes panel for explicitly including a Freestyle pass, and the output terminal should not be disabled unless this is unchecked as well.

Lawrence D'Oliveiro commented

2015-01-11 02:19:39 +01:00

Changed status to: 'Open'

Lawrence D'Oliveiro commented

2015-01-11 02:19:39 +01:00

Added subscriber: @ldo

Bastien Montagne commented

2015-01-11 11:01:58 +01:00

Changed status from 'Open' to: 'Archived'

Bastien Montagne closed this issue

2015-01-11 11:01:58 +01:00

Bastien Montagne self-assigned this 2015-01-11 11:01:58 +01:00

Bastien Montagne commented

2015-01-11 11:01:58 +01:00

There is no Freestyle pass. Freestyle is a render option, like solid, halo, etc., not a layer. So if you want only freestyle, you shall only enable it in the Layer panel, and then use usual passes (probably simply combined in your case)…

Thanks for the report, but no bug here.

There is no Freestyle pass. Freestyle is a render option, like solid, halo, etc., not a layer. So if you want only freestyle, you shall only enable it in the Layer panel, and then use usual passes (probably simply combined in your case)… Thanks for the report, but no bug here.

Lawrence D'Oliveiro commented

2015-01-11 21:59:49 +01:00

But if I turn on the Combined pass, I get the rendered image as well as the Freestyle lines, which I don’t want in this case.

There is no Freestyle pass, but there should be one! That’s the bug.

But if I turn on the Combined pass, I get the rendered image as well as the Freestyle lines, which I don’t want in this case. There is no Freestyle pass, but there should be one! That’s the bug.

Lawrence D'Oliveiro commented

2015-01-11 22:41:11 +01:00

Changed status from 'Archived' to: 'Open'

Lawrence D'Oliveiro reopened this issue

2015-01-11 22:41:11 +01:00

Julian Eisel commented

2015-01-11 23:11:05 +01:00

Changed status from 'Open' to: 'Archived'

Julian Eisel closed this issue

2015-01-11 23:11:05 +01:00

Julian Eisel commented

2015-01-11 23:11:05 +01:00

Added subscribers: @mont29, @JulianEisel

Julian Eisel commented

2015-01-11 23:11:05 +01:00

Please leave bug triaging to us!!

As @mont29 said, there is no Freestyle pass and if you want one, this is a feature request and not a bug!
This is no user support forum, but I'll give you a quick description on what you can do to get separate "passes" for freestyle:

create two different renderlayers
enable all render options exept of Freestyle in one
enable only Freestyle in the other
The layers should now look like this:
go to the Compositor
you can use the renderlayers similar to this:

Please leave bug triaging to us!! As @mont29 said, there is no Freestyle pass and if you want one, this is a feature request and not a bug! This is no user support forum, but I'll give you a quick description on what you can do to get separate "passes" for freestyle: * create two different renderlayers * enable all render options exept of Freestyle in one * enable only Freestyle in the other * The layers should now look like this: ![freestyle_bug4.png](https://archive.blender.org/developer/F136678/freestyle_bug4.png) * go to the Compositor * you can use the renderlayers similar to this: ![freestyle_bug3.png](https://archive.blender.org/developer/F136680/freestyle_bug3.png)

Lawrence D'Oliveiro commented

2015-01-11 23:36:52 +01:00

Changed status from 'Archived' to: 'Open'

Lawrence D'Oliveiro reopened this issue

2015-01-11 23:36:52 +01:00

Lawrence D'Oliveiro commented

2015-01-11 23:36:52 +01:00

Sorry, I didn’t see that there was a Freestyle checkbox. and that it’s in the “Layer” panel, not the “Passes” panel.

There is still a bug though: take my example, where the Foreground node looks like it is unconnected. in fact it is still being included in the composite result. (The “Freestyle” checkbox only has an effect in the Foreground node, not the Background one.)

Sorry, I didn’t see that there **was** a Freestyle checkbox. and that it’s in the “Layer” panel, not the “Passes” panel. There is still a bug though: take my example, where the Foreground node looks like it is unconnected. in fact it is still being included in the composite result. (The “Freestyle” checkbox only has an effect in the Foreground node, not the Background one.)

Bastien Montagne was unassigned by Julian Eisel

2015-01-12 00:03:16 +01:00

Lukas Tönne was assigned by Julian Eisel

2015-01-12 00:03:16 +01:00

Julian Eisel commented

2015-01-12 00:03:16 +01:00

Added subscriber: @LukasTonne

Julian Eisel commented

2015-01-12 00:03:16 +01:00

First, as I said, please leave bug triaging to us! This includes opening and closing of tasks.

Regarding the bug, yeah, that is indeed a bit strange. @LukasTonne, looks like the flags aren't updated properly... Just look at the .blend attached. The second input of the Alpha Over node isn't displaying the color button as it should and the Render Layer node that doesn't have any outputs is included in the tree as if it was connected... Mind having a look?

First, as I said, please leave bug triaging to us! This includes opening and closing of tasks. Regarding the bug, yeah, that is indeed a bit strange. @LukasTonne, looks like the flags aren't updated properly... Just look at the .blend attached. The second input of the Alpha Over node isn't displaying the color button as it should and the Render Layer node that doesn't have any outputs is included in the tree as if it was connected... Mind having a look?

Lawrence D'Oliveiro commented

2015-01-12 00:15:33 +01:00

First of all, I thought “triage” is something you do when you first encounter the bug. If you don’t like me changing the status of a bug afterwards, then why do I have the power to do so? Clearly it is up to my judgement to exercise that power, which I did.

Because the alternative would be to pester you by continually filing new bug reports each time, instead of reopening the existing one. That would have meant 3 or 4 separate reports instead of this one. Which would you prefer?

First of all, I thought “triage” is something you do when you first encounter the bug. If you don’t like me changing the status of a bug afterwards, then why do I have the power to do so? Clearly it is up to my judgement to exercise that power, which I did. Because the alternative would be to pester you by continually filing new bug reports each time, instead of reopening the existing one. That would have meant 3 or 4 separate reports instead of this one. Which would you prefer?

Julian Eisel commented

2015-01-12 00:51:18 +01:00

IIRC this is not in our hands, this is how Phabricator works (the system beneath developer.blender.org). If you want a bug to be reopened, give us the reasons and we decide if they're good enough to reopen (sometimes you have to be a bit pushy though)

Lawrence D'Oliveiro commented

2015-01-12 01:19:22 +01:00

sometimes you have to be a bit pushy though

You mean, like I was?

> sometimes you have to be a bit pushy though You mean, like I was?

Julian Eisel commented

2015-01-13 11:29:48 +01:00

Kind of, but still, leave opening and closing of tasks to us (not meant to be rude or so, but we have to inform you to not do so after you did).

But let's get back to topic now, this really isn't a forum this is a bug tracker.

Kind of, but still, leave opening and closing of tasks to us (not meant to be rude or so, but we have to inform you to not do so after you did). But let's get back to topic now, this really isn't a forum this is a bug tracker.

blender-admin commented

2015-01-14 11:15:55 +01:00

This issue was referenced by 90a8aa2dab

This issue was referenced by 90a8aa2dab381f21704c3199d4fcd8ed64e059ce

Lukas Tönne commented

2015-01-14 11:16:02 +01:00

Changed status from 'Open' to: 'Resolved'

Lukas Tönne closed this issue

2015-01-14 11:16:02 +01:00

Lukas Tönne commented

2015-01-14 11:16:02 +01:00

Closed by commit 90a8aa2dab.

Closed by commit 90a8aa2dab.

Sign in to join this conversation.

No Label

Download

What's New

Blender Studio

Manual

Developers Blog

Documentation

Benchmark

Blender Conference

Development Fund

One-time Donations

Compositor Doesn’t Show Terminals For Freestyle-Only Layer #43201