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.

Sign up for GitHub

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

Jump to bottom

Scene handling #66

Open
BrendanParmer opened this issue Sep 9, 2023 · 1 comment
Open

Scene handling #66

BrendanParmer opened this issue Sep 9, 2023 · 1 comment
Assignees
@BrendanParmer
Labels
enhancement New feature or request

Comments

@BrendanParmer
Copy link
Owner

BrendanParmer commented Sep 9, 2023 •
edited

  • If a scene referenced by a node/socket is the current scene, then initialize the generated version with the current scene
  • If it's not, I don't think there's a good way of handling that aside from importing an entire scene from a packaged blend file. Might push handling this case to a future release
@BrendanParmer BrendanParmer self-assigned this Sep 9, 2023
@BrendanParmer BrendanParmer added this to the v3.0 milestone Sep 9, 2023
@BrendanParmer BrendanParmer added the enhancement New feature or request label Sep 9, 2023
@BrendanParmer
Copy link
Owner Author

Automatically handled with nodes where you don't explicitly need to set to scene in the first place (only the defocus node doesn't have this behavior), pushing to later release

@BrendanParmer BrendanParmer removed this from the v3.0 milestone Jan 22, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@BrendanParmer BrendanParmer

Labels
enhancement New feature or request
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@BrendanParmer