Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Feature Request - Move side nodes horizontally / vertically #17

Open
Felger opened this issue Jun 18, 2015 · 2 comments
Open

Feature Request - Move side nodes horizontally / vertically #17

Felger opened this issue Jun 18, 2015 · 2 comments

Comments

@Felger
Copy link

Felger commented Jun 18, 2015

Trying to configure the KW Expanded Fairing Bases for Procedural Fairings, ran into an issue. It seems Procedural Fairings uses the top node and the side nodes to initially determine the fairing shape (and presumably, the enclosed area). When I move the top node below the side attach nodes, the fairing starts at the side attach nodes, drops down to below the top node, then rises again as per normal:

screenshot2

It'd be nice for these sorts of fairing bases to be able to move the side attach nodes horizontally (EG: side nodes at radius = 1.0 with part diameter of 1.25), and potentially more importantly, to be able to move them above the top node.

Thanks!

@Felger
Copy link
Author

Felger commented Jun 18, 2015

As an aside, the offset shown above was achieved by moving the model and top/bottom nodes down, leaving the side nodes alone. This achieves some pretty good-looking results:

screenshot3

@Felger
Copy link
Author

Felger commented Jun 19, 2015

A little more tinkering, and I'm starting to understand the issue a bit better. It looks like no matter where the nodes are, the fairing starts at the node radius at height zero. The encapsulated parts are all those which are "downstream" of the reference node (top).

I attempted a workaround by placing a dummy node at the zero point for the fairings to base themselves from, like so:

screenshot5

Unfortunately, the second node (placed at the structural point) is not counted as inside the fairings, so parts attached there will not resize the fairings:

screenshot6

I suspect a workaround might lie in checking the "top" node's height relative to the part's zero height, and starting the fairing component scan there, but leaving off fairing model rings until you get to height zero.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant