Skip to content

Spline attachment surgery - #91

Open
gageLink wants to merge 6 commits into
mholtkamp:mainfrom
gageLink:SplineAttachmentSurgery
Open

Spline attachment surgery#91
gageLink wants to merge 6 commits into
mholtkamp:mainfrom
gageLink:SplineAttachmentSurgery

Conversation

@gageLink

Copy link
Copy Markdown

This started as a feature addition, giving a new Spline3D Lua function for adding attachment nodes, but Dingle suggested building out a new attachment system from scratch and uhhhh this is that.
I made a few design choices such as error handling, and starting conditions, and they were guided by the firm hand of "what would I want to see in a bibeo game endjinn"
tried my darndest to comment where i could but sometimes you get caught up in the heat of things and well...

adds Spline3D doc to tree
Adds new function documentation
Adding in new funcs, removing old variables and adding in new vector and support vars
exchange old logic with new vector logic, adding support functions where necessary.
adding SetAttachment function
This update is not as big as it seems, just adding in the attachment function, and binding it.
GitHub decided to normalize the file, so thats why it looks so beeg
@gageLink

Copy link
Copy Markdown
Author

Whoa my comment didnt actually talk about it sorry:
This changes out the previous system of spline attachments, individual variable pointers for camera, light, audio, etc. that allowed for 1 attachment of 6 node types, and a wildcard node3D.
It is replaced with a vector of pointers to allow for an indeterminate amount of node3Ds of any type.

The Lua function allows for adding attachments, as well as replacing attachments in the vector with other nodes

The documentation is updated to reflect the added function.

The UI is updated to account for this new method of storing attachments, in the property window for Spline3D nodes.

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

Successfully merging this pull request may close these issues.

1 participant