27965 Cable flexible 22L with 2 Bar connectors

[Jaco van der Molen]

Hi all,

I am in need of 27965 Cable flexible 22L with 2 Bar connectors to be made as a template so I can model in LDCad.

Does it exist or can someone make it, please?

Thanks!

[Jaco van der Molen]

Hi all,

I am in need of 27965 Cable flexible 22L with 2 Bar connectors to be made as a template so I can model in LDCad.

Does it exist or can someone make it, please?

Thanks!

OK, I gave it a try and this about right.
Atleast, I can use it for my purpose.
Feel free to download, use and improve.

[Daniele Benedettelli]

OK, I gave it a try and this about right.
Atleast, I can use it for my purpose.
Feel free to download, use and improve.

Awesome, thanks a lot!

[SNIPE]

Can't LDRAW have such helper parts but where you can bend several of them in different ways yet still just have them instancing a single submodel? when I place this part in a new project and bend it, it also modifies the submodel itself instead of just the instance of it.

[Jaco van der Molen]

Can't LDRAW have such helper parts but where you can bend several of them in different ways yet still just have them instancing a single submodel? when I place this part in a new project and bend it, it also modifies the submodel itself instead of just the instance of it.

If you have more of the same part, but with different bending, you'll have to add a new part from the template for each instance of the part.

[N. W. Perry]

Can't LDRAW have such helper parts but where you can bend several of them in different ways yet still just have them instancing a single submodel? when I place this part in a new project and bend it, it also modifies the submodel itself instead of just the instance of it.

LSynth works kind of this way (but kind of not). There is no submodel for the flexible part itself; rather, just a block of code positioning each instance of the helper parts. But it does add a lot of code to the model rather than relegating it to a submodel, so perhaps not what you're looking for.

The method I envision for overriding part placement (and other parameters, such as color), which I have called FLOAT, could theoretically be used in this way. You could create a FLOAT statement, scoped to the flexible part subfile, which would override the positions of the helper parts/path nodes from their default placement at runtime.

From a computational standpoint I don't know how costly this would be, though I do know that today's machines are far better suited to the task than those available in 1997. But it would be a way to manage the proliferation of library files, by requiring only a single part file for any given flexible part. Library entries for formed versions of flexible parts might consist only of a file containing the FLOAT statement that is referenced to a common base part, similar to how my imagined approach toward patterned parts would reference a texturing statement to an unpatterned base part.