-
-
Notifications
You must be signed in to change notification settings - Fork 35.5k
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
Nodes: ViewportNode #24934
Nodes: ViewportNode #24934
Conversation
import { Vector2 } from 'three'; | ||
import { NodeUpdateType } from '../core/constants.js'; | ||
|
||
let resolution; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Maybe we should move this variable to instances? Because it is possible that a user would want to render for different sizes.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I thought about it, but it shouldn't happen since .update()
will force the update in GPU level every time that it is called.
I'm going to start working on porting the computational renderer to three.js now :-) |
Description
This contribution is funded by Google