lokster/cura-custom-supports

Custom Supports plugin for Cura

cura-custom-supports's Issues

Plugin is always disabled - Cura 4.9

I have installed this plugin through the marketplace window and of course restarted Cura.
But it's always disabled in the plugin list and not visible on the Cura UI.

I see that my version 0.0.4 is old- but the deinstall button does not work.
Is there a way to install/activate the current version?

Thanks for your help

Add option for custom Tree Supports

Thank you so much for the Custom Supports plugin. It can really be a life saver. However, sometimes I need a support in a spot that is not over the build plate and I don't want to rotate the model. It would be amazing if placing of a custom support block at a spot would make Cura work as hard as it can to support that block with whatever the current support settings are (be they regular or tree supports, "touching build plate" or "everywhere").

Cura 4.6.1: No G-Code created for Custom Supports

I have created some custom support blocks in Cura 4.6.1 but neither in the Cura internal preview nor in an external g-code viewer I see any custom support.

The picture shows the preview with the custom support block selected but no generated support.

When creating a duplicate support it is locked on Z axis

I tried using this software yesterday for the first time. I noticed that if I create a support, and then try to duplicate that support, that the duplicate support is locked on the Z axis. Even if I check and uncheck the lock model option. There's no way to move it on the Z axis that I can see without deleting it and just creating a new support. It moves up but snaps back to the build plate.

I'm using Cura 4.9.1 and custom supports 0.1.0.

Support scales and moves my model

Custom support is a great tool but I have an issue with it.

In Cura 4.8 the Custom support scales and moves my model

Support Blocker not working

Cura 5

Will this be updated any time soon for cura 5?

Thanks

Support interface not generated

hello,
custom supports are not generating the support interface.

without support interface DISABLED :

with support interface ENABLED :

thanks :D

Plugin stays disabled when trying to install on latest Cura 4 beta

I install the plugin, restart cura, and don't get the plugin.
looking on the installed list, it appears there, but grayed. I mark the checkbox, it requests a restart,
and after that get to the same state of unchecked again.

Cura does not launch, Symbol not found: _fdopendir$INODE64

(Moved from Ultimaker/Cura#4461)

Application Version
3.4

Platform
OS X 10.9.5 (some Macs don't run later versions)

Printer
creality_cr10

Steps to Reproduce

• Run Cura on OS X 10.9.5. Runs well initially
• Install CustomSupports plugin

Actual Results

When launching Cura:

Process:         cura [287]
Path:            /Applications/Ultimaker Cura.app/Contents/MacOS/cura
Identifier:      nl.ultimaker.cura
Version:         3.4 (3.4.1)
Code Type:       X86-64 (Native)
Parent Process:  launchd [150]
Responsible:     cura [287]
User ID:         501

Date/Time:       2018-10-02 14:06:04.025 +0200
OS Version:      Mac OS X 10.9.5 (13F1911)
Report Version:  11
Anonymous UUID:  (...)


Crashed Thread:  0

Exception Type:  EXC_BREAKPOINT (SIGTRAP)
Exception Codes: 0x0000000000000002, 0x0000000000000000

Dyld Error Message:
  Symbol not found: _fdopendir$INODE64
  Referenced from: /Applications/Ultimaker Cura.app/Contents/MacOS/cura
  Expected in: /usr/lib/libSystem.B.dylib

Expected results

Application launches

Workaround

$ rm -rf "./Library/Application Support/cura//3.4/plugins/CustomSupports"

Problems on Cura 4.1.0

Hi,

I try to install this plugin but seems not work properly. The only thing it is work is a Custom blocker support, but the custom supports only work on tree, can you help me? Is Cura 4.1.0

expect more intuitive custom supports

cura by custom supports plugin:

simplify3d:

Supports do not overlap with model

In Cura 4.8 Custom Supports do not overlap with model but there is a gap. Please help.

Tree support overlaps

Tree supports are incompatible with the custom supports as it does not join the tool paths but instead overlaps them