Suggestion of a new "Render state" node


I have a little free idea!
It could be useful to have a node readable by renderers to access a high-definition version of the component.
We would have in SketchUp the proxy version that we configured. And the renderer would have access to the HD version with another set of parameters. A Switch for rendering engines. We would have a proxy worthy of the name as with the ephemeral state node
A render state node

What do you think? Possible ?

1 Like

It is a built-in feature of some rendering applications, V-Ray, for instance.

1 Like

The idea is to have the control to realize the proxi and the hd with the same graph. We would have a lighter, more fluid model. and without compromising on the quality of the renderings.

As @Anssi says, several stand alone render engines already do this. They have a library of low poly SketchUp items which are automatically swapped for lights and hi-rez objects when the file is sent to the render.

The way each render engine handles this is different so I’m not sure how a native solution would work effectively for all of them.

There is the existing one and there are the new features!
To Trimble to offer the possibility to the render to exploit the Hd information of the graph provided by the designer of the graph.
To the rendering engine to set up the capabilities to read this information.
The user remains the master and the services adapt, and not the other way around!

The maintenance or the modification of proxy is often a gas factory, one is obliged to have a proxy by colors, or by dimensions.
A dynamic proxy would be a better way!
Without weighing down its scene or the number of operations for the user.
We would have a live component which would be the proxy and the HD object according to the SketchUp player or the rendering engine.
It is a paradigm shift that I am proposing!

Great suggestion, we’ve got a few ideas floating around that are very much in this vein. Allowing apps to decide which LOD of a given model they wish to display would be a powerful workflow.

In the shorter term, we have some goals to make LCs performant without having to “switch” contexts or render a different model to that displayed in the editable scene.

Hello Keith
While waiting for stability in all the tests, it will be necessary to remain vigilant on the number of edges and faces.
We can however create a switch to create a “low poly” state in order to create the proxy of a “high poly” state. But we lose the dynamic side of live components
Have a nice weekend