This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
objectprops:objectpropertiesoverride [2014/05/31 16:17] grantadam |
objectprops:objectpropertiesoverride [2023/07/11 00:39] (current) |
||
|---|---|---|---|
| Line 1: | Line 1: | ||
| ====== Object Property Overrides ====== | ====== Object Property Overrides ====== | ||
| \\ | \\ | ||
| - | Object Property Overrides is a way to control more properties than are currently supported by the Object Properties Per pass, new for version 6 of RPM. | + | Object Property Overrides extends RPM's control to many more properties than are currently supported by the Object Properties Per Pass system, and is new for version 6 of RPM. |
| - | It provides a way to control modifier properties (ie on, off, turbosmooth iterations reduced), texturemap settings (ie subsurface settings of a vray SSS dropped for a preview), material settings, and baseobject properties for previews and renders. | + | It provides a way to control modifier properties (on, off, turbosmooth iterations reduced, etc.), texturemap settings (subsurface settings of a vray SSS dropped for a preview, bitmap paths), material settings, and baseobject properties for both previews and renders, and these changes are applied just for that particular preview/render. |
| + | |||
| + | Almost all object/modifier/material/texmap properties are supported, a list of avaiable properties is procedurally generated based on selection (see section below on creating entries). | ||
| + | |||
| + | An important point to note is that the settings in the UI are not per pass, they are global and affect all matching objects in the scene if not filtered - each entry can be assigned which passes it affects, along with filtering by the name of the item being modified, as well as bythe name of the object the item is assigned to, to control exactly what properties are modified. | ||
| - | The settings in the UI are not per pass, they are global - each entry can be assigned which passes it affects, along with filtering for the name of the item being modified, as well as the name of the object the item is assigned to (ie both the modifier name, and the object the modifier is assigned to, can be used to control what is updated. | ||
| **Not per object - per class**\\ | **Not per object - per class**\\ | ||
| \\ | \\ | ||
| - | The most important aspect is to understand that you are not picking which objects to affect - as you do with the Object Properties Per Pass controls - but which class of object to modify. After that it is what property of that class to modify, and what to set the property to. All objects of that class in the scene are potentially modified at this point, and there are name filters so you can limit it to affecting just the items you want. | + | The most important aspect is to understand that you are not picking which objects to affect - as you do with the Object Properties Per Pass controls - but which class of object across the entire scene to modify. After that it is what property of that class to modify, and what to set the property to. All objects of that class in the scene are potentially modified at this point, and there are name filters so you can limit it to affecting just the items you want. |
| In addition, there are separate settings for previews and renders, and you can limit each entry to one or more passes. Functions can be assigned for setting values, filtering by name, and also which passes to operate on. | In addition, there are separate settings for previews and renders, and you can limit each entry to one or more passes. Functions can be assigned for setting values, filtering by name, and also which passes to operate on. | ||