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

Nodes: ViewportNode #24934

Merged
merged 5 commits into from
Nov 11, 2022
Merged

Nodes: ViewportNode #24934

merged 5 commits into from
Nov 11, 2022

Conversation

sunag
Copy link
Collaborator

@sunag sunag commented Nov 10, 2022

@sunag sunag added this to the r147 milestone Nov 10, 2022
@sunag sunag merged commit 87c581c into mrdoob:dev Nov 11, 2022
@sunag sunag deleted the dev-viewport-node branch November 11, 2022 17:19
import { Vector2 } from 'three';
import { NodeUpdateType } from '../core/constants.js';

let resolution;
Copy link
Contributor

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.

Copy link
Collaborator Author

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.

@LeviPesin
Copy link
Contributor

I'm going to start working on porting the computational renderer to three.js now :-)

@0b5vr 0b5vr mentioned this pull request Dec 7, 2022
12 tasks
0b5vr added a commit to three-types/three-ts-types that referenced this pull request Dec 19, 2022
0b5vr added a commit to three-types/three-ts-types that referenced this pull request Dec 19, 2022
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.

2 participants