Page MenuHome

Curve -> Bevel -> Fill caps greyed out unless bevel curve selected
Closed, InvalidPublic


System Information
Operating system: Linux-4.15.0-52-generic-x86_64-with-debian-buster-sid 64 Bits
Graphics card: GeForce GTX 1080 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 410.104

Blender Version
Broken: version: 2.80 (sub 75), branch: master, commit date: 2019-07-29 14:47, hash: rBf6cb5f54494e

Short description of error
The "Fill Caps" option is greyed out under default, normal circumstances. Adding bevel depth and resolution does not make it available. The only thing that currently makes the option available is selecting a bevel curve.

I was initially hesitant to report this as a bug, given that the behavior matches 2.79. However, the lack of ability to easily add end caps has been annoying me for a while. My reasoning for this being a bug is "there should be no technical reason why a normal, beveled curve should not be able to have filled caps, and having filled end caps can be useful"

Bug      Highly Questionable Weird Behavior        UI Paper Cut                Feature Request
 | ----------------------|------------------------------|---------------------------|
              this report, in my opinion

Exact steps for others to reproduce the error

  1. Create a curve object
  2. Add a bevel depth to the curve
  3. Notice unfilled caps
  4. Try to select fill caps

A note on implementation
I'm not sure if fixing this will be as simple as making the fill caps checkbox clickable, even if no bevel curve is selected. If not, I can foresee the following possible solutions

  1. If no bevel curve is selected, pass a default circular bevel curve of the given depth/radius into whatever function does the cap filling
  2. Implement a case in the cap filling algorithm to take into account curves without a custom bevel curve

Event Timeline

Philipp Oeser (lichtwerk) changed the task status from Unknown Status to Unknown Status.Aug 19 2019, 10:22 AM
Philipp Oeser (lichtwerk) claimed this task.

Hi @Finn Bear (finnb),
This was intentionally exluded in rB3b3d811bf0a7.
Not saying this isnt possible (I have made quick tests by removing the check for cu->bevobj from here)
But as the commit message from above commit mentioned, this would not work in any case [has problems with beveled+extruded 2D curves at least].
So you are running into situations like these:

That all being said, this is a nice suggestion, but atm. this would be more like a feature request that could go to instead...
Will close this as not-a-bug [unless @Sergey Sharybin (sergey) has objections and wants to pick this up?]