-
Notifications
You must be signed in to change notification settings - Fork 126
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
Isolate View on Playblast #367
Comments
Just thinking aloud here, but there could be an option on the review instance to isolate the view to "animation" geometry only. That way you would only get the rigs and not the proxy geometry, and shader/material manipulation is not needed. |
I was envisioning an option called "Isolate View" where you could choose which family of instance to isolate the view to. |
Branch feature/367-Isolate_View_on_Playblast created! |
@antirotor did you have some use cases for this as well? |
and @mkolar? |
Yes we have use for this. Mostly for modelling reviews actually. Clients often want to publish multiple LODs from a single maya scene, but to be able to review them individually, we'd need to trigger isolate view for each turnaround. It's actually not completely trivial in this case. Imagine a scene like this.
The models are publishable instances, but the the stage is just helper geometry that we want to see in the review. For example a simple geometry platform model. We'd need to be able to specify what exactly we want to isolate. |
So I guess for your use case @mkolar, we would need multiple review instances and somehow assign a single model instance to each? The easiest workflow I can think of, is to be able to assign the any objectset to a review objectset. When publishing, if there are any objectsets in the review, only those will be shown, else everything in camera will be shown. |
Goal
To be able to isolate the view on certain objects when playblasting.
The text was updated successfully, but these errors were encountered: