As Viewports have gotten more advanced over the years, they now have a slew of parameters in the OIP so it can be hard to find what you’re looking for at a glance. Viewport parameters are also a little overwhelming for new users. It would be great to implement OIP Widget Groups for Viewports so that parameters are arranged into categories with headers, making it easier to find what you need.
Implementing widget groups would be a great opportunity to reorganize parameters so that related settings are near each other. For example, Lighting Options and Image Effects affect the rendered portion of a viewport so they should be near the Background Render setting. There are currently a number of cases where the order of things in the OIP seems arbitrary and scattered, rather than presented logically.
In the images below I’ve laid out mock-ups of a Viewport and a Section Viewport OIP. I’ve carefully rearranged all the parameters into simple categories that I think would make sense to an average user. I’d be happy to further explain any logic behind these choices but would also be interested in hearing what others think.
You can post now and register later.
If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.
Question
Andy Broomell
As Viewports have gotten more advanced over the years, they now have a slew of parameters in the OIP so it can be hard to find what you’re looking for at a glance. Viewport parameters are also a little overwhelming for new users. It would be great to implement OIP Widget Groups for Viewports so that parameters are arranged into categories with headers, making it easier to find what you need.
Implementing widget groups would be a great opportunity to reorganize parameters so that related settings are near each other. For example, Lighting Options and Image Effects affect the rendered portion of a viewport so they should be near the Background Render setting. There are currently a number of cases where the order of things in the OIP seems arbitrary and scattered, rather than presented logically.
In the images below I’ve laid out mock-ups of a Viewport and a Section Viewport OIP. I’ve carefully rearranged all the parameters into simple categories that I think would make sense to an average user. I’d be happy to further explain any logic behind these choices but would also be interested in hearing what others think.
I've filed this on JIRA as VE-102612. Also suggested by @trashcan in another post.
Link to comment
0 answers to this question
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.