View source for GPU Instancer Pro:GettingStarted

{{GPUIProHeaderLinks}}
<br>
'''<big>[https://u3d.as/3kbz Go to Asset Store Page]</big>'''
<br>

GPU Instancer Pro consists of various main Monobehavior classes called Managers. The most commonly used ones are the Prefab Manager, Detail Manager and Tree Manager. The managers are designed with mainly ease of use in mind, and adding them to your scene is as easy as clicking a menu item. 

On this page, you will find information about these managers and everything GPUI comes with - including, various tools and components that will quickly get you started using GPUI Pro.


{| class="wikitable"
|-
|[[File:HelpButton.png|frameless|border|middle]] &nbsp;All the GPU Instancer Pro Managers also have a question mark icon on their top right corners. Clicking this icon will make the managers show descriptions on their settings. You can always click this button to get information about a manager setting.
|}


<div style="clear: both"></div>
__TOC__

== Quick Start ==

<br>
'''The Prefab Manager'''
[[File:GPUIProPrefabManager.png|The Prefab Manager|thumb|left]]

Use the Prefab Manager for rendering and managing a multitude of prefab instances in scenes.

* Add Prefab Manager: '''<code>Tools -> GPU Instancer Pro -> Add Prefab Manager</code>''' 
* Click on the '''Add''' button.
* Select the prefabs with or expected to have many instances in the scene. (See [[GPU_Instancer_Pro:BestPractices#Instance_Counts|Instance Counts]])
* Enable the necessary options under [[GPU_Instancer_Pro:GettingStarted#Prefab_Manager_Prototype_Settings|Prefab Prototype Settings]]
<div style="clear: both"></div>

'''The Tree Manager'''
[[File:GPUIProTreeManager.png|The Tree Manager|thumb|left]]

Use the Tree Manager for rendering Unity terrain trees.

* Add Tree Manager: '''<code>Tools -> GPU Instancer Pro -> Add Tree Manager For Terrains</code>''' 
<div style="clear: both"></div>

'''The Detail Manager'''
[[File:GPUIProDetailManager.png|The Detail Manager|thumb|left]]

Use the Detail Manager for rendering Unity terrain details.

* Add Detail Manager: '''<code>Tools -> GPU Instancer Pro -> Add Detail Manager For Terrains</code>''' 
<div style="clear: both"></div>
'''No-GameObjects Workflow'''
* Create a new renderer with the [[GPU_Instancer_Pro:APIDocumentation#RegisterRenderer|RegisterRenderer]] API method and store the rendererKey output.
* Set the transform matrices using the [[GPU_Instancer_Pro:APIDocumentation#SetTransformBufferData|SetTransformBufferData]] API method using the given rendererKey.
* To stop the rendering, call the [[GPU_Instancer_Pro:APIDocumentation#DisposeRenderer|DisposeRenderer]] API method.
<div style="clear: both"></div>

== Manager Setup ==

=== Common Manager Settings ===
The following Manager Settings are common in every manager.

[[File:GPUIProCommonManagerSettings.png|Manager Settings|thumb|left]]

'''Dont Destroy On Load:''' When enabled, the GPUI Manager will not be destroyed when loading a new Scene.

'''Default Profile:''' New prototypes that are added to the Manager will use this profile by default.

'''Revert When Disabled:''' Enable default rendering when the manager is disabled.

<br>
<div style="clear: both"></div>

=== Profile Settings ===

The settings related to rendering (culling, LOD, etc.) are stored in a Profile Scriptable Object, which is shared between prototypes. Profile Settings are written to persistent GPU buffers instead of sending the data to GPU every frame. This reduces the number of files, simplifies the addition/removal of prototypes, and optimizes GPU data transfer.

You can use the '+Create' button located on the right side of the Profile object to generate a new Profile Scriptable Object in your project.

[[File:GPUIProProfileSettings.png|Profile Settings|thumb|left]]

==== Culling ====

'''Is Distance Culling:''' When Distance Culling is enabled, you can specify minimum and maximum distance values. Objects beyond these distances will be culled.

'''Is Frustum Culling:''' Is Frustum Culling determines whether objects outside the camera's view frustum will be rendered. When enabled, GPU Instancer will exclude objects outside the frustum from rendering, enhancing performance. It's advisable to enable frustum culling unless there's a specific reason not to.

'''Frustum Offset:''' Frustum Offset expands the camera frustum planes, affecting the area within which objects are rendered when frustum culling is enabled.

'''Is Occlusion Culling:''' Is Occlusion Culling determines whether objects occluded by other objects will be rendered. When enabled, GPU Instancer will skip rendering objects that are behind others and would not normally be visible. While occlusion culling adds some additional GPU operations, it's recommended to enable it when beneficial.

'''Occlusion Offset:''' Occlusion Offset defines the depth value (ranged between 0 to 1) that the differences will be discarded while calculating culled objects from the depth texture. Higher offset values will result in less culling.

'''Occlusion Accuracy:''' Occlusion Cull Accuracy defines the accuracy of the occlusion culling. Higher values will result in more accurate culling with higher number of texture samples. 
1 => 5 samples (middle point and corner points)
2 => 9 samples (adds 1/4 points)
3 => 17 samples (adds 1/8 and 3/8 points)

'''Min Culling Distance:''' Min. Culling Distance defines the minimum distance that any kind of culling will occur. If it is a value higher than 0, the instances with a distance less than the specified value to the Camera will not be culled.

'''Bounds Offset:''' Bounds Offset can be used to increase the bounding box size of the prototype. This will affect the culling and LOD calculations. It is particularly useful for prototypes with shaders that modify vertex positions.

<br>
==== Shadow Culling ====

'''Is Shadow Casting:''' Is Shadow Casting specifies whether the object will cast shadows or not. Enabling shadow casting requires extra shadow passes, resulting in additional rendering operations. GPU Instancer implements various techniques to optimize these operations, but disabling shadow casting when unnecessary can enhance performance.

'''Is Distance Culling:''' Shadow distance culling is based on the shadow caster position. In situations with very long shadows, shadow distance culling may result in less consistent shadows. In such cases, it's generally better to increase the <b>Custom Shadow Distance</b> value. However, if necessary, this option allows you to disable shadow distance culling altogether.

'''Custom Shadow Distance:''' When Custom Shadow Distance is set to 0, GPU Instancer will render shadows based on the Quality Settings. You can adjust this setting to specify a lower value, effectively culling shadows for distant objects.

'''Is Frustum Culling:''' If enabled, frustum culling results will be applied to the shadows. This will result in more performance, but might also lead to less consistency in shadows.

'''Shadow Frustum Offset:''' Shadow Frustum Offset expands the camera frustum planes, affecting the area within which shadows are rendered when frustum culling is enabled.

'''Is Occlusion Culling:''' If enabled, occlusion culling results will be applied to the shadows. This will result in more performance, but might also lead to less consistency in shadows.

'''Shadow Occlusion Offset:''' Shadow Occlusion Offset defines the depth value (ranged between 0 to 1) that the differences will be discarded while calculating culled shadows from the depth texture. Higher offset values will result in less shadow culling.

'''Min Shadow Culling Distance:''' Min. Shadow Culling Distance defines the minimum distance that any kind of shadow culling will occur. If it is a value higher than 0, the shadows with a distance less than the specified value to the Camera will not be culled.

<br>
==== LOD ====

'''LOD Cross-fading:''' LOD Cross-Fade enables cross-fade style blending between the LOD levels of this prototype. This can have a minor impact on performance since during cross-fading, both LOD levels will be rendering.

'''Animate Cross-fading:''' Animate Cross-Fading animates cross-fading instead of it being distance based. The animation starts with the first occurrence of the changed LOD. During the animation, both LOD levels will be rendered.

'''LOD Cross Fade Animate Speed:''' LOD Cross Fade Animate Speed determines the duration of the transition between different LODs.

'''LOD Cross Fade Transition Width:''' You can use the Transition Width value to define the cross-fading zone between LOD Levels. This zone is the distance in which the prototype LODs are cross faded. Higher numbers result in wider transition zones. In the transition zone, both LOD levels will be rendered.

'''LOD Bias Adjustment:''' The LOD Bias Adjustment value effects the LOD level distances per prototype. When it is set to a value less than 1, it favors less detail. A value of more than 1 favors greater detail.

'''Shadow LOD Map:''' Shadow LOD Map can be utilized to adjust the level of detail used for rendering shadows for each LOD.

<br>
<div style="clear: both"></div>

=== Billboard Settings ===

[[File:GPUInstancer-Scr-BillboardGenerator.png|thumb|left]]
GPU Instancer Pro has the capability to automatically generate billboard renderers for prefabs. However, it's important to note that the billboard system is primarily designed for terrain trees. Generating billboards for prefabs that do not use default Unity tree shaders (such as SpeedTree, TreeCreator, or SoftOcclusion shaders) might lead to unexpected results.

<div style="clear: both"></div>
<br>

[[File:GPUIProBillboardSettings.png|Manager Settings|thumb|left]]

'''Generate Billboard:''' When Generate Billboard option is enabled, a billboard mesh and material will be created and added as the last LOD to the prototype.

'''Replace LOD Culled:''' When enabled, the billboard will replace the Culled section of the LOD Group component, instead of using a custom distance value.

'''Billboard Distance:''' The Billboard Distance value is similar to the LOD percentage setting on the LOD Group component. For example a value of 0.9 is similar to 10% on the LOD Group component.

'''Atlas Resolution:''' Atlas Resolution defines the resolution of the billboard textures. Higher resolutions result in better looking billboards, but use more memory. Texture atlases are not square for 2D billboards; so for example "x2048" option results in a 2048x256 texture resolution.

'''Frame Count:''' Frame Count defines the total amount of snapshots that are taken from different angles for this billboard. Higher frame counts result in more accurate view differences in different view angles, but result in lower resolution frames since they are all packed in the same atlas.

'''Brightness:''' You can use Brightness to adjust the brightness of the billboard textures. A zero value is fully black whereas one is lighter.

'''Cutoff Override:''' You can use the Cutoff Override option to override the alpha cutoff value of the original materials for the billboard textures. This is normally necessary if you use the alpha value as some other data (e.g. metallic, etc.) in the textures of the material for the prefab of this prototype.

'''Normal Strength:''' Normal Strength controls the intensity of the normal texture effect. Values lower than 1 will decrease it, while higher values will amplify the effect of the normal texture.

'''Add To Billboard Assets:''' When Add To Billboard Assets option is enabled, the billboard asset will be added to the 'Billboard Assets' List inside [[GPU_Instancer_Pro:GettingStarted#GPU_Instancer_Pro_Preferences|Runtime Settings]], which will make the billboard asset discoverable when creating prototypes at runtime.

<br>
<div style="clear: both"></div>

=== Statistics Tab ===
The Statistics Tab provides insights into GPU Instancer rendering information, enabling users to identify bottlenecks and optimize performance.

[[File:GPUIProStatisticsTab.png|Manager Settings|thumb|left]]

'''Show Visibility:''' When enabled, the GPUI Manager will readback culling results from the GPU and display additional information such as vertex counts and visible LOD counts.


<br>
<div style="clear: both"></div>

=== The Prefab Manager ===
----

[[File:GPUI-PrefabInstancing002.png|thumb|left]]
By adding your prefabs to the Prefab Manager, the prefab instances you add to your scenes are automatically rendered by GPU Instancer. It also provides additional functionality such as adding/removing/updating instances at runtime. Note that the Prefab Manager only accepts user created prefabs. It will not accept prefabs that are generated when importing your 3D model assets.

When using the Prefab Manager, the most important thing to have in mind is that you should only add the prefabs that you have many instances of as prototypes. GPU Instancer uses various techniques to increase performance, but ultimately it renders its prototypes using GPU Instancing. Therefore, it is highly recommended to read the Terminology and the Best Practices pages to familiarize with the concept of GPU Instancing and to get the most out of the Prefab Manager and GPUI in general.

<br>
<div style="clear: both"></div>

==== Prefab Manager Settings  ====

[[File:GPUIProCommonManagerSettings.png|Prefab Manager Settings|thumb|left]]

'''Find Instances At Start:''' When enabled, the Prefab Manager will search for GPUIPrefab components in the scene during initialization. When disabled, you can manually register the prefab instances in the scene, using the Register Instances In Scene button.

<br>
<div style="clear: both"></div>

==== Prefab Manager Prototype Settings  ====

[[File:GPUIProPrefabManager-PrototypeSettings.png|Prefab Manager Prototype Settings|thumb|left]]

'''Transform Updates:''' When enabled, the transform data of the prefab instances will be read and uploaded to a GPU buffer every frame. If the prefab instances are not changing their transform data, it is better to keep it disabled. If there are rarely changes, you can use the [[GPU_Instancer_Pro:APIDocumentation#UpdateTransformData|GPUIPrefabManager.UpdateTransformData]] method to notify the Prefab Manager about the changes while keeping this setting disabled.

'''Auto. Add/Remove:''' When enabled, GPUIPrefabAutoAddRemove component will be added to the prefab. The instances containing this component will be automatically added to or removed from the Prefab Manager.

<br>
<div style="clear: both"></div>

==== Prefab Manager Material Variations  ====

[[File:GPUIProPrefabManager-MaterialVariations.png|Prefab Manager Material Variations|thumb|left]]

'''+Create Button:''' Clicking this button creates a Material Variation Definition asset and adds the [[GPU_Instancer_Pro:BestPractices#Material_Variation_Instance|GPUI Material Variation Instance]] component to the prefab.

'''Enable/Disable Checkbox:''' Use this checkbox to enable or disable the material variation.

'''Material Variation Definition:''' This field displays the Material Variation Definition Scriptable Object. Refer to the [[GPU_Instancer_Pro:BestPractices#Material_Variation_Definition|Material Variation Definition documentation]] for setup instructions.

'''Remove Button:''' Clicking this button removes the [[GPU_Instancer_Pro:BestPractices#Material_Variation_Instance|GPUI Material Variation Instance]] component from the prefab and optionally deletes the Material Variation Definition asset.

<br>
<div style="clear: both"></div>

=== The Detail Manager ===
----

[[File:GPUI-DetailInstancing001.png|thumb|left]]
The primary objective of the Detail Manager is to enhance performance and improve visual quality compared to Unity's default terrain details. It offers native support for multiple terrains, minimizing draw calls and efficiently managing runtime changes with reduced allocations. Additionally, it introduces optimization features to reduce the number of distant detail instances, thereby boosting performance while preserving visual quality.

The Detail Manager utilizes single channel density textures to render detail instances, and these textures can be edited at runtime without incurring CPU overhead using the provided Density Modifiers. Users have the capability to dynamically add and remove detail instances at runtime, leading to improved flexibility and usability of the terrain system.

The foliage shader included with the Detail Manager offers various quality enhancements and customization options for texture detail instances.

Furthermore, users can add prefabs with LOD Group components to the Detail Manager's prototypes. GPUI will add the first LOD into the terrain, allowing it to be painted using terrain tools. However, GPUI will continue to utilize the prefab with all its LOD levels during rendering.

<br>
<div style="clear: both"></div>

==== Detail Manager Settings  ====

[[File:GPUIProDetailManager-ManagerSettings.png|Detail Manager Settings|thumb|left]]

'''Render In Edit Mode:''' When enabled, the GPUI Manager will render the objects in edit mode.

'''Terrains:''' List of Terrains this manager is currently rendering the detail and tree instances for.

'''Auto. Add New Prototypes:''' When enabled, new prototypes will be created on the Manager when there are prototypes on the terrains that do not match any of the existing prototypes on the Manager.

'''Auto. Remove Deleted Prototypes:''' When enabled, prototypes on the Manager that do not match any of the terrain prototypes will be automatically removed.

'''Detail Distance:''' Determines the maximum distance that the detail instances will be drawn.

'''Detail Update Distance:''' Detail instances are updated based on camera position. Update distance determines after how much camera movement the detail instances will be updated. When set to zero, the detail instances will be updated every frame.

'''Healthy/Dry Noise Texture:''' Healthy/Dry Noise Texture is used for determining detail instance scales and colors.

<br>
<div style="clear: both"></div>

==== Detail Manager Prototype Settings  ====

[[File:GPUIProDetailManager-PrototypeSettings.png|Detail Manager Prototype Settings|thumb|left]]

'''Mesh:''' For Texture Detail Prototypes, GPUI uses a quad mesh named 'DefaultDetailMesh'. You have the option to change this default quad mesh by assigning a custom mesh to this property.

'''Materials:''' For Texture Detail Prototypes, GPUI uses a material with the 'GPUInstancerPro/Foliage' shader. You have the option to change this by assigning a custom material to this property.

'''Material Description:''' To minimize the number of materials used for texture prototypes, GPUI employs Material Property Blocks and shares the same material across different texture prototypes. The 'Material Description' property enables users to utilize custom shaders, leveraging this functionality by creating custom material descriptions for their shaders.

'''Layer:''' You can use this dropdown to choose a Layer that the texture type Terrain details will be using. The terrain details that use prefabs will get the Layer value from the prefab object.

'''Terrain Detail Properties:''' The Terrain Detail Prototype settings are read from the terrain and displayed here for testing purposes. Any changes made to the values on the terrain will automatically update these settings.

<br>
<div style="clear: both"></div>

===== Detail Shader Properties  =====

GPUI uses a custom foliage shader that uses the Standard Lighting Model for rendering texture type detail properties. You can use this shader also on your prefabs by creating a material from the <code>GPUInstancerPro/Foliage</code> shader and assigning this material to the Mesh Renderer of your prefabs. These settings on the manager show only when a texture type detail prototype is selected and the default detail material is used, and they can be used to change prototype settings individually.

[[File:GPUIProDetailManager-ShaderProperties.png|Detail Shader Properties|thumb|left]]

'''Ambient Occlusion:''' The amount of ambient occlusion to apply to the objects that use the foliage shader.

'''Gradient Power:''' GPUI's foliage shader provides an option to darken the lower regions of the mesh that uses it. This results in a more realistic look for foliage. You can set the amount of this darkening effect with the this property, or turn it off completely by setting the slider to zero.

'''Wind Idle Sway:''' Specifies the amount of idle wind animation for the detail prototypes that use the foliage shader. This is the wind animation that occurs where wind waves are not present. Turning the slider down to zero disables this idle wind animation.

'''Wind Waves On:''' Specifies whether there will be wind waves for the detail prototypes that use the foliage shader. The normal texture that is used to calculate winds can be changed from the material by editing the <code>Wind Wave Normal Texture</code> property.

'''Wind Wave Size:''' Specifies the size of the wind waves for the detail prototypes that use foliage shader.

'''Wind Wave Tint:''' Specifies how much the '''Wind Wave Tint Color''' applies to the wind wave effect for the detail prototypes that use the foliage shader. Turning the slider down to zero disables wind wave coloring.

'''Wind Wave Sway:''' Specifies the amount of wind animation that is applied by the wind waves for the detail prototypes that use the foliage shader. This is the wind animation that occurs in addition to the idle wind animation. Turning the slider down to zero disables this extra wave animation.

<br>
<div style="clear: both"></div>

===== Detail Density Reduction  =====

Distance Based Density Reduction reduces the amount of detail instances when they are far away. It can also increase the scale of the far away objects to make them cover a similar area.

[[File:GPUIProDetailManager-DensityReduction.png|Detail Density Reduction|thumb|left]]

'''DR Start Distance:''' The starting distance from the camera for the distance reduction.

'''DR Multiplier:''' Higher DR Multiplier values will remove more instance, lower values will remove less. For best performance, keep it as high as possible without compromising visual quality.

'''DR Max Scale:''' Distant detail instances will be scaled to cover the emptied areas left behind by the removed instances. DR Max Scale determines the maximum scale value.

'''DR Height Scale:''' When set to zero, the distance objects are scaled only on the X and Z axises. When set to one, the Y axis will have the same scale increase as the others.

<br>
<div style="clear: both"></div>

===== Detail Adjustments  =====

Detail Adjustments allow you to modify the density, scaling, and positioning of detail instances without altering the terrain data.

[[File:GPUIProDetailManager-DetailAdjustments.png|Detail Adjustments|thumb|left]]

'''Density Multiplier:''' By changing the Density Adjustment value, you can increase or decrease the density of detail instances.

'''Healthy/Dry Scaling:''' The Healthy/Dry Scaling setting allows you to modify the scale values for detail instances based on the Healthy/Dry noise. Values higher than 0 will result in higher scales for healthy instances, while values lower than 0 will result in higher scales for dry instances.

'''Noise Seed:''' The Noise Seed adjustment value can be used to modify the seed for random positioning and scaling values of detail instances.

'''Noise Spread Multiplier:''' The Noise Spread Multiplier value determines the scale of the Healthy/Dry noise texture used for coloring and scaling detail instances.

<br>
<div style="clear: both"></div>

===== Advanced Settings  =====

[[File:GPUIProDetailManager-PrototypeAdvancedSettings.png|Detail Advanced Settings|thumb|left]]

'''Max Instance Per Unit:''' The 'Max Instance Per Unit' setting determines the maximum number of detail instances that can be generated at each index, based on the 'Detail Resolution' value set on the terrain.

'''Initial Buffer Size:''' Initial Buffer Size is used to create the GPU buffers when rendering starts. Depending on the calculated instance counts, the buffer size will be dynamically changed. If the initial buffer size is small, some instances will not be rendered during the first few frames.

'''Extra Buffer Percent:''' When determining the required buffer size for detail instances, additional allocations are made to avoid reallocating the buffer for small changes. This value determines the percentage of the actual buffer size that will be left empty during allocation.

'''Buffer Reduction Percent:''' The Detail Manager automatically makes new allocations when the allocated buffer size is insufficient. It can also reduce the buffer size to free up memory using the Buffer Reduction Percent value. For instance, when this value is set to 0.6, if 60% of the buffer is unused, the buffer will be resized to free up GPU memory. Setting it to 0 disables buffer size reduction altogether. Setting a very low value is not recommended since it might cause performance issues because of frequent memory allocations.

<br>
<div style="clear: both"></div>

=== The Tree Manager ===
----

[[File:GPUI-TreeInstancing001.png|thumb|left]]

The Tree Manager provides a solution for instancing Unity terrain trees. By adding a Tree Manager to your scene, GPUI can extract tree data from the Unity Terrain and generate the necessary GPUI prototypes. Additionally, the Tree Manager automatically enables billboarding for tree prototypes and generates billboards as needed. This manager supports various tree shaders, including SpeedTree, TreeCreator, and many custom tree shaders. If you prefer to use trees without registering them to the Unity terrain, you can utilize the Prefab Manager instead.

<br>
<div style="clear: both"></div>

==== Tree Manager Settings  ====

[[File:GPUIProTreeManager-ManagerSettings.png|Tree Manager Settings|thumb|left]]

'''Render In Edit Mode:''' When enabled, the GPUI Manager will render the terrain trees in edit mode.

'''Terrains:''' List of Terrains this manager is currently rendering the detail and tree instances for.

'''Auto. Add New Prototypes:''' When enabled, new prototypes will be created on the Manager when there are prototypes on the terrains that do not match any of the existing prototypes on the Manager.

'''Auto. Remove Deleted Prototypes:''' When enabled, prototypes on the Manager that do not match any of the terrain prototypes will be automatically removed.

'''Tree Instance Colors:''' When enabled, the Tree Manager will create color variation buffers based on the color property of [https://docs.unity3d.com/ScriptReference/TreeInstance.html TreeInstances]. Suitable shaders, such as the Tree Creator shaders, can use this buffer to create color variations.

<br>
<div style="clear: both"></div>

==== Tree Manager Prototype Settings  ====

[[File:GPUIProTreeManager-PrototypeSettings.png|Tree Manager Prototype Settings|thumb|left]]

'''Apply Rotation:''' When enabled, trees will be rotated based on the rotation property of the [https://docs.unity3d.com/ScriptReference/TreeInstance.html TreeInstance].

'''Apply Prefab Scale:''' When enabled, the scale value of the tree prefab will be applied to the instances.

'''Apply Height:''' When enabled, tree heights will be modified based on the heightScale property of the [https://docs.unity3d.com/ScriptReference/TreeInstance.html TreeInstance].

<br>
<div style="clear: both"></div>

== Utilities ==
==== GPUI Debugger Window  ====

[[File:GPUIProDebuggerWindow.png|thumb|left]]

The Debugger Window offers comprehensive insights into draw calls and compute shader calculations, aiding in analysis and debugging. It provides information on the cameras utilized for instanced rendering, statistical data on the currently rendered instances for each camera, and GPU allocations for each prototype. Furthermore, by selecting the [[GPU_Instancer_Pro:GettingStarted#GPUI_LOD_Group_Data|GPUI LOD Group Data]] objects for each prototype, users can access details on the meshes, materials, keywords, and LOD settings utilized for draw calls.

<br>
To open this window, navigate to : '''<code>Tools -> GPU Instancer Pro -> Utilities -> Show Debugger Window</code>''' 

<br>
<div style="clear: both"></div>

==== Billboard Generator Window  ====

[[File:GPUIProBillboardGeneratorWindow.png|thumb|left]]

The Billboard Generator Window is a tool provided by GPUI for testing and fine-tuning settings related to billboards generated by the system. It allows users to adjust parameters such as resolution, frame count, and brightness to achieve the desired visual appearance for billboard rendering. For detailed information on these settings, please refer to the [[GPU_Instancer_Pro:GettingStarted#Billboard_Settings|Billboard Settings]] section.


'''Save as Asset:''' This button saves the billboard settings to a Scriptable Object, along with the generated textures. It allows users to preserve their billboard configurations for future use within GPUI Managers.

'''Save Standalone:''' Clicking this button creates a mesh, a material, and a billboard prefab that can be used independently of the GPUI Managers. It provides a way to add the generated billboards as LOD levels to other objects or scenes.

'''Close and Return:''' This button closes the preview scene and returns the user to the previous scene.

<br>
To open this window, navigate to : '''<code>Tools -> GPU Instancer Pro -> Utilities -> Show Billboard Generator</code>''' 

<br>
<div style="clear: both"></div>

==== Prefab Replacer Window  ====

[[File:GPUIProPrefabReplacerWindow.png|thumb|left]]

GPUI includes a Prefab Replacer tool designed to simplify the process of replacing GameObjects in your scene hierarchy with prefab instances with just a few clicks. This tool is particularly useful if you didn't follow a prefab workflow when initially creating your scene. Additionally, it allows you to effortlessly replace instances of one or multiple prefabs with another while retaining the transform data, such as positions, rotations, and scales.

<br>
To open this window, navigate to : '''<code>Tools -> GPU Instancer Pro -> Utilities -> Show Prefab Replacer</code>''' 

<br>
<div style="clear: both"></div>

==== Grass Mesh Generator Window  ====

[[File:GPUIProGrassMeshGeneratorWindow.png|thumb|left]]

The Grass Mesh Generator tool in GPUI facilitates the creation of custom meshes for texture detail prototypes managed by the Detail Manager. This feature enables users to tailor the appearance of grass and other textured details to suit their specific project requirements.

<br>
To open this window, navigate to : '''<code>Tools -> GPU Instancer Pro -> Utilities -> Show Grass Mesh Generator</code>''' 

<br>
<div style="clear: both"></div>

== Additional Components and Scriptable Objects ==
==== GPUI Camera  ====

[[File:GPUIProCameraComponent.png|thumb|left]]

Users can designate the cameras to be used for instanced rendering by attaching the GPUI Camera component to each respective camera. The flexibility of employing multiple cameras simultaneously is straightforward; users simply need to add this component to each camera they intend to use. During GPUI rendering initiation, if no cameras with this component are detected, the system will automatically search for a camera based on the behavior selected in the [[GPU_Instancer_Pro:GettingStarted#GPU_Instancer_Pro_Preferences|Runtime Settings]].

'''Enable Occlusion Culling:''' This option determines whether depth textures will be generated for this camera, allowing for the utilization of the Occlusion Culling feature.

'''HiZ Depth Texture:''' This property displays the depth texture used for Occlusion Culling at runtime, which can be helpful for debugging purposes.

<br>
<div style="clear: both"></div>

==== GPUI LOD Group Data  ====

[[File:GPUIProLODGroupData.png|thumb|left]]
For each prototype, the system generates a GPUI LOD Group Data object, which specifies the meshes, materials, keywords, and LOD transition values utilized for rendering. This information is accessible to users, allowing them to make runtime modifications for debugging and testing purposes.

<br>
<div style="clear: both"></div>

==== GPUI Prefab ====

[[File:GPUIProPrefabComponent.png|thumb|left]]
GPUI Prefab component is automatically attached to prefabs when they are added to the Prefab Manager. It enables the Prefab Manager to track the prefab instances by maintaining their instancing status and GPU buffer information.

<br>
<div style="clear: both"></div>

==== GPUI Prefab Auto Add Remove ====

[[File:GPUIProPrefabAutoAddRemoveComponent.png|thumb|left]]
GPUI Prefab Auto Add Remove component is automatically attached to prefabs when the 'Auto. Add/Remove' option is enabled on the Prefab Manager. It facilitates the automatic registration of prefab instances to the Prefab Manager when they are added to the scene or enabled, and removes them from the Prefab Manager when they are removed from the scene or disabled.

<br>
<div style="clear: both"></div>

==== GPUI Terrain ====

[[File:GPUIProTerrainBuiltin.png|thumb|left]]
GPUI Terrain component is automatically attached to terrains when they are added to the Tree or Detail Managers. It provides essential terrain information, such as heightmap texture, tree instances, and detail density textures, to the GPUI Managers.

<br>
'''Auto. Find Tree Manager:''' When this option is enabled, the terrain will be automatically assigned to a GPUI Tree Manager present in the scene at runtime.

'''Auto. Find Detail Manager:''' When this option is enabled, the terrain will be automatically assigned to a GPUI Detail Manager present in the scene at runtime.

'''Bake Detail Textures:''' This button saves the single channel density texture used for terrain detail rendering as a texture asset. It accelerates Detail Manager initialization and reduces allocations.

<br>
<div style="clear: both"></div>

==== Detail Material Description ====

[[File:GPUIProDetailMaterialDescription.png|thumb|left]]
To reduce the number of materials required for texture prototypes, GPUI utilizes Material Property Blocks, allowing the same material to be shared across different texture prototypes. The 'Detail Material Description' Scriptable Object enables users to leverage this functionality with custom shaders by defining which properties on the shader correspond to specific functions.

<br>
To create a new Detail Material Description, right click on the Project window and select: '''<code>Create -> Rendering -> GPU Instancer Pro -> Detail Material Description</code>''' 

<br>
<div style="clear: both"></div>

==== GPUI Event System  ====

[[File:GPUIProEventSystem.png|thumb|left]]

The GPUI Event System enables users to execute custom methods at different stages of the rendering process of cameras. These stages include:

'''OnPreCull:''' Executed before the camera visibility calculations.

'''OnPreRender:''' Executed after the camera visibility calculations and before the draw calls.

'''OnPostRender:''' Executed after the draw calls.

<br>
The event system can be added to your scenes by navigating to: '''<code>Tools -> GPU Instancer Pro -> Helpers -> Add Event System</code>''' 

<br>
<div style="clear: both"></div>

===== Floating Origin Event  =====

The "GPUI Event Floating Origin" component can automatically adjust all instances managed by a GPUI Manager according to the movements of a specified transform. Please note that these adjustments are limited to the matrix data stored in GPU memory. GameObjects in your scenes will not be modified.

<br>
<div style="clear: both"></div>

===== Face Camera Event  =====

The "GPUI Event Face Camera" component can automatically adjust all instances specific prototype to face the camera. Please note that these adjustments are limited to the matrix data stored in GPU memory. GameObjects in your scenes will not be modified.

<br>
<div style="clear: both"></div>

== System Settings ==
=== GPU Instancer Pro Preferences ===

[[File:GPUIProPreferences.png|thumb|left]]

The GPU Instancer Pro Preferences contain settings that can modify the default behavior of the GPUI in edit mode.

<br>
To access the preferences, navigate to : '''<code>Edit -> Preferences -> GPU Instancer Pro</code>''' 

<br>
'''Generate Shader Variant Collection:''' If enabled, a ShaderVariantCollection with reference to shaders that are used in GPUI Managers will be generated automatically inside Resources folder. This will add the GPUI shader variants automatically to your builds. These shader variants are required for GPUI to work in your builds.

'''Auto. Shader Conversion:''' If enabled, shaders of the prefabs that are added to the GPUI Managers will be automatically converted to support GPU Instancer.

<br>
<div style="clear: both"></div>


=== GPU Instancer Pro Runtime Settings ===

[[File:GPUIProRuntimeSettings.png|thumb|left]]

The GPU Instancer Pro Runtime Settings contain settings that can modify the default behavior of the GPUI rendering system and affect all GPUI managers and prototypes.

<br>
To modify the Runtime Settings, navigate to : '''<code>Tools -> GPU Instancer Pro -> Utilities -> Add Runtime Settings Overwrite</code>'''
<br>Then click the '''Create''' button on the '''GPUI Runtime Settings Overwrite''' component to create a new settings file.


'''Occlusion Culling Condition''': Occlusion Culling Condition setting can be used to disable the occlusion culling feature project-wide, avoiding depth texture generation and additional visibility calculations. This might be beneficial for projects where occlusion culling is unnecessary or too expensive.

'''Camera Selection''': This setting changes the camera selection behavior based on priority. The possible selections, ordered by priority, are:<br>
'Default' => GPUICamera component, MainCamera tag<br>
'Any' => GPUICamera component, MainCamera tag, Camera.allCameras[0]<br>
'GPUICameraComponent' => GPUICamera component<br>

'''Instancing Bounds Size''': Defines world space bounds for the geometry. Used to cull and sort the rendered geometry.

'''Billboard Assets''': Assets added to the Billboard Assets list are discoverable to GPUI Managers when creating prototypes at runtime.

<br>
<div style="clear: both"></div>

=== GPUI Shader Bindings ===

[[File:GPUIProShaderBindings.png|thumb|left]]

The Shader Bindings asset stores information about shaders used by prototypes for rendering with GPUI. Shaders lacking GPUIPro shader setup will have an automatically created replacement shader, and its information will be stored in this asset. This data is utilized at runtime to determine which shader to use for instanced rendering.

<br>
The Shader Bindings asset is located at: '''<code>Assets/GPUInstancerPro/Resources/GPUIShaderBindings</code>''' 

<br>
<div style="clear: both"></div>

=== GPUI Shader Variant Collection ===

[[File:GPUIProShaderVariantCollection.png|thumb|left]]

The Shader Variant Collection asset stores the shader variants used by prototypes for rendering with GPUI. It ensures that all the necessary shader variants are included in your builds, as GPUI modifies materials for instanced rendering at runtime, and Unity's default build behavior may not include all the necessary variants.

<br>
The Shader Variant Collection asset is located at: '''<code>Assets/GPUInstancerPro/Resources/GPUIShaderVariantCollection</code>''' 

<br>
<div style="clear: both"></div>

== Shader Setup Guide ==
<br>
GPUI has a system that automatically generates a converted version of most shaders to work with itself. This system keeps track of shader changes and handles re-conversions automatically as well. This includes most of the shaders created by shader creation editors like Amplify Shader Editor. But in some special cases, it might be needed to change the shader manually to support GPU Instancer Pro. GPUI detects if a shader is compatible with it and will not generate a separate shader if that is the case. Here is the information you need to manually edit your shaders to support GPUI.

<br>
<div style="clear: both"></div>
=== Built-in RP Shader Setup ===

In Built-in Render Pipeline, for all passes, you need to include the <code>multi_compile_instancing</code> and the <code>instancing_options procedural:setupGPUI</code> pragma directives. Please note that the <code>GPUInstancerSetup.hlsl</code> must be included after the <code>UnityCG.cginc</code> file:

==== Surface Shaders ====
<div class="code" style="border: 1px solid #c8ccd1;padding:5px;">
<div style="font: normal normal 1em/1.2em monospace; margin:0; padding:0; background:none; vertical-align:top;">...</div>
<div style="font: normal normal 1em/1.2em monospace; margin:0; padding:0; background:none; vertical-align:top;"><span style="color: #660066;">SubShader</span> <span style="color: #009900;">{</span></div>
<div style="font: normal normal 1em/1.2em monospace; margin:0; padding:0; background:none; vertical-align:top;">&nbsp; &nbsp; ...</div>
<div style="font: normal normal 1em/1.2em monospace; margin:0; padding:0; background:none; vertical-align:top;">&nbsp; &nbsp; <span style="color: #660066;">CGPROGRAM</span></div>
<div style="font: normal normal 1em/1.2em monospace; margin:0; padding:0; background:none; vertical-align:top;">&nbsp; &nbsp; #include <span style="color: #3366CC;">"UnityCG.cginc"</span></div>
<div style="font: normal normal 1em/1.2em monospace; margin:0; padding:0; background:none; vertical-align:top;">&nbsp; &nbsp; #include <span style="color: #3366CC;">"Packages/com.gurbu.gpui-pro/Runtime/Shaders/Include/GPUInstancerSetup.hlsl"</span></div>
<div style="font: normal normal 1em/1.2em monospace; margin:0; padding:0; background:none; vertical-align:top;">&nbsp; &nbsp; #pragma instancing_options procedural<span style="color: #339933;">:</span>setupGPUI</div>
<div style="font: normal normal 1em/1.2em monospace; margin:0; padding:0; background:none; vertical-align:top;">&nbsp; &nbsp; ...</div>
<div style="font: normal normal 1em/1.2em monospace; margin:0; padding:0; background:none; vertical-align:top;">&nbsp; &nbsp; <span style="color: #660066;">ENDCG</span></div>
<div style="font: normal normal 1em/1.2em monospace; margin:0; padding:0; background:none; vertical-align:top;"><span style="color: #009900;">}</span></div>
<div style="font: normal normal 1em/1.2em monospace; margin:0; padding:0; background:none; vertical-align:top;">...</div>
</div>
<br>
Since the '''#pragma multi_compile_instancing''' directive is automatically added to the generated code from surface shaders, you do not need to include it. However, if you have a additional passes (such as a shadowcaster pass), you need to add support to these passes as well (see Vertex/fragment Shaders below).
<br>
Please also note that if your shadows are not showing correctly (e.g. they show on camera position), you can add the addshadow option to your surface pragma directive to have your surface shader generate a shadow pass for you. This will make sure that your shadow pass is also setup for GPUI. If you do not define the addshadow option, and if your surface shader also does not have a shadow pass, Unity will use the shadow pass from the defined fallback shader, and this shader may not be setup for GPUI.

<br>
<div style="clear: both"></div>

==== Vertex/fragment Shaders ====


For all passes:


<div class="code" style="border: 1px solid #c8ccd1;padding:5px;">
<div style="font: normal normal 1em/1.2em monospace; margin:0; padding:0; background:none; vertical-align:top;">...</div>
<div style="font: normal normal 1em/1.2em monospace; margin:0; padding:0; background:none; vertical-align:top;"><span style="color: #660066;">Pass</span> <span style="color: #009900;">{</span></div>
<div style="font: normal normal 1em/1.2em monospace; margin:0; padding:0; background:none; vertical-align:top;">&nbsp; &nbsp; ...</div>
<div style="font: normal normal 1em/1.2em monospace; margin:0; padding:0; background:none; vertical-align:top;">&nbsp; &nbsp; <span style="color: #660066;">CGPROGRAM</span></div>
<div style="font: normal normal 1em/1.2em monospace; margin:0; padding:0; background:none; vertical-align:top;">&nbsp; &nbsp; ...</div>
<div style="font: normal normal 1em/1.2em monospace; margin:0; padding:0; background:none; vertical-align:top;">&nbsp; &nbsp; #include <span style="color: #3366CC;">"UnityCG.cginc"</span></div>
<div style="font: normal normal 1em/1.2em monospace; margin:0; padding:0; background:none; vertical-align:top;">&nbsp;</div>
<div style="font: normal normal 1em/1.2em monospace; margin:0; padding:0; background:none; vertical-align:top;">&nbsp; &nbsp; #include <span style="color: #3366CC;">"Packages/com.gurbu.gpui-pro/Runtime/Shaders/Include/GPUInstancerSetup.hlsl"</span></div>
<div style="font: normal normal 1em/1.2em monospace; margin:0; padding:0; background:none; vertical-align:top;">&nbsp; &nbsp; #pragma multi_compile_instancing</div>
<div style="font: normal normal 1em/1.2em monospace; margin:0; padding:0; background:none; vertical-align:top;">&nbsp; &nbsp; #pragma instancing_options procedural<span style="color: #339933;">:</span>setupGPUI</div>
<div style="font: normal normal 1em/1.2em monospace; margin:0; padding:0; background:none; vertical-align:top;">&nbsp; &nbsp; <span style="color: #660066;">ENDCG</span></div>
<div style="font: normal normal 1em/1.2em monospace; margin:0; padding:0; background:none; vertical-align:top;"><span style="color: #009900;">}</span></div>
<div style="font: normal normal 1em/1.2em monospace; margin:0; padding:0; background:none; vertical-align:top;">...</div>
</div>


You also need to add instancing setup to your input structs and vertex functions if you don't already have it:


<div class="code" style="border: 1px solid #c8ccd1;padding:5px;">
<div style="font: normal normal 1em/1.2em monospace; margin:0; padding:0; background:none; vertical-align:top;"><span style="color: #660066;">struct</span> appdata_custom</div>
<div style="font: normal normal 1em/1.2em monospace; margin:0; padding:0; background:none; vertical-align:top;"><span style="color: #009900;">{</span></div>
<div style="font: normal normal 1em/1.2em monospace; margin:0; padding:0; background:none; vertical-align:top;">&nbsp; &nbsp; ...</div>
<div style="font: normal normal 1em/1.2em monospace; margin:0; padding:0; background:none; vertical-align:top;">&nbsp; &nbsp; UNITY_VERTEX_INPUT_INSTANCE_ID</div>
<div style="font: normal normal 1em/1.2em monospace; margin:0; padding:0; background:none; vertical-align:top;"><span style="color: #009900;">}</span></div>
</div>


<div class="code" style="border: 1px solid #c8ccd1;padding:5px;">
<div style="font: normal normal 1em/1.2em monospace; margin:0; padding:0; background:none; vertical-align:top;">v2f <span style="color: #660066;">vert</span>( appdata_custom v )</div>
<div style="font: normal normal 1em/1.2em monospace; margin:0; padding:0; background:none; vertical-align:top;"><span style="color: #009900;">{</span></div>
<div style="font: normal normal 1em/1.2em monospace; margin:0; padding:0; background:none; vertical-align:top;">&nbsp; &nbsp; v2f o;</div>
<div style="font: normal normal 1em/1.2em monospace; margin:0; padding:0; background:none; vertical-align:top;">&nbsp; &nbsp; <span style="color: #660066;">UNITY_SETUP_INSTANCE_ID</span>(v);</div>
<div style="font: normal normal 1em/1.2em monospace; margin:0; padding:0; background:none; vertical-align:top;">&nbsp; &nbsp; ...</div>
<div style="font: normal normal 1em/1.2em monospace; margin:0; padding:0; background:none; vertical-align:top;">&nbsp; &nbsp; return o;</div>
<div style="font: normal normal 1em/1.2em monospace; margin:0; padding:0; background:none; vertical-align:top;"><span style="color: #009900;">}</span></div>
</div>


<div style="clear: both"></div>

=== URP Shader Setup ===

For all passes, you need to include the <code>multi_compile_instancing</code> and the <code>instancing_options procedural:setupGPUI</code> pragma directives. Please note that the <code>GPUInstancerSetup.hlsl</code> must be included after the URP include files:


<div class="code" style="border: 1px solid #c8ccd1;padding:5px;">
<div style="font: normal normal 1em/1.2em monospace; margin:0; padding:0; background:none; vertical-align:top;">...</div>
<div style="font: normal normal 1em/1.2em monospace; margin:0; padding:0; background:none; vertical-align:top;"><span style="color: #660066;">Pass</span> <span style="color: #009900;">{</span></div>

<div style="font: normal normal 1em/1.2em monospace; margin:0; padding:0; background:none; vertical-align:top;">&nbsp; &nbsp; ...</div>
<div style="font: normal normal 1em/1.2em monospace; margin:0; padding:0; background:none; vertical-align:top;">&nbsp; &nbsp; <span style="color: #660066;">HLSLPROGRAM</span></div>
<div style="font: normal normal 1em/1.2em monospace; margin:0; padding:0; background:none; vertical-align:top;">&nbsp; &nbsp; ...</div>
<div style="font: normal normal 1em/1.2em monospace; margin:0; padding:0; background:none; vertical-align:top;">&nbsp; &nbsp; #include <span style="color: #3366CC;">"Packages/com.unity.render-pipelines.universal/ShaderLibrary/Core.hlsl"</span></div>
<div style="font: normal normal 1em/1.2em monospace; margin:0; padding:0; background:none; vertical-align:top;">&nbsp;</div>
<div style="font: normal normal 1em/1.2em monospace; margin:0; padding:0; background:none; vertical-align:top;">&nbsp; &nbsp; #include <span style="color: #3366CC;">"Packages/com.gurbu.gpui-pro/Runtime/Shaders/Include/GPUInstancerSetup.hlsl"</span></div>
<div style="font: normal normal 1em/1.2em monospace; margin:0; padding:0; background:none; vertical-align:top;">&nbsp; &nbsp; #pragma multi_compile_instancing</div>
<div style="font: normal normal 1em/1.2em monospace; margin:0; padding:0; background:none; vertical-align:top;">&nbsp; &nbsp; #pragma instancing_options procedural<span style="color: #339933;">:</span>setupGPUI</div>
<div style="font: normal normal 1em/1.2em monospace; margin:0; padding:0; background:none; vertical-align:top;">&nbsp; &nbsp; <span style="color: #660066;">ENDHLSL</span></div>
<div style="font: normal normal 1em/1.2em monospace; margin:0; padding:0; background:none; vertical-align:top;"><span style="color: #009900;">}</span></div>
<div style="font: normal normal 1em/1.2em monospace; margin:0; padding:0; background:none; vertical-align:top;">...</div>
</div>


Same as with other vertex/fragment shaders above, you also need to add instancing setup to your input struct and vertex function if you don't already have it.


For the vertex input struct:

<div class="code" style="border: 1px solid #c8ccd1;padding:5px;">
<div style="font: normal normal 1em/1.2em monospace; margin:0; padding:0; background:none; vertical-align:top;"><span style="color: #660066;">struct</span> VertexInput</div>
<div style="font: normal normal 1em/1.2em monospace; margin:0; padding:0; background:none; vertical-align:top;"><span style="color: #009900;">{</span></div>
<div style="font: normal normal 1em/1.2em monospace; margin:0; padding:0; background:none; vertical-align:top;">&nbsp; &nbsp; ...</div>
<div style="font: normal normal 1em/1.2em monospace; margin:0; padding:0; background:none; vertical-align:top;">&nbsp; &nbsp; UNITY_VERTEX_INPUT_INSTANCE_ID</div>
<div style="font: normal normal 1em/1.2em monospace; margin:0; padding:0; background:none; vertical-align:top;"><span style="color: #009900;">}</span></div>
</div>


For the vertex output struct:

<div class="code" style="border: 1px solid #c8ccd1;padding:5px;">
<div style="font: normal normal 1em/1.2em monospace; margin:0; padding:0; background:none; vertical-align:top;"><span style="color: #660066;">struct</span> VertexOutput</div>
<div style="font: normal normal 1em/1.2em monospace; margin:0; padding:0; background:none; vertical-align:top;"><span style="color: #009900;">{</span></div>
<div style="font: normal normal 1em/1.2em monospace; margin:0; padding:0; background:none; vertical-align:top;">&nbsp; &nbsp; ...</div>
<div style="font: normal normal 1em/1.2em monospace; margin:0; padding:0; background:none; vertical-align:top;">&nbsp; &nbsp; UNITY_VERTEX_INPUT_INSTANCE_ID</div>
<div style="font: normal normal 1em/1.2em monospace; margin:0; padding:0; background:none; vertical-align:top;"><span style="color: #009900;">}</span></div>
</div>


The vertex function:

<div class="code" style="border: 1px solid #c8ccd1;padding:5px;">
<div style="font: normal normal 1em/1.2em monospace; margin:0; padding:0; background:none; vertical-align:top;">VertexOutput<span style="color: #660066;">vert</span>(VertexInput v)</div>
<div style="font: normal normal 1em/1.2em monospace; margin:0; padding:0; background:none; vertical-align:top;"><span style="color: #009900;">{</span></div>
<div style="font: normal normal 1em/1.2em monospace; margin:0; padding:0; background:none; vertical-align:top;">&nbsp; &nbsp; VertexOutput o;</div>
<div style="font: normal normal 1em/1.2em monospace; margin:0; padding:0; background:none; vertical-align:top;">&nbsp; &nbsp; <span style="color: #660066;">UNITY_SETUP_INSTANCE_ID</span>(v);</div>
<div style="font: normal normal 1em/1.2em monospace; margin:0; padding:0; background:none; vertical-align:top;">&nbsp; &nbsp; ...</div>
<div style="font: normal normal 1em/1.2em monospace; margin:0; padding:0; background:none; vertical-align:top;">&nbsp; &nbsp; return o;</div>
<div style="font: normal normal 1em/1.2em monospace; margin:0; padding:0; background:none; vertical-align:top;"><span style="color: #009900;">}</span></div>
</div>


And the fragment function:

<div class="code" style="border: 1px solid #c8ccd1;padding:5px;">
<div style="font: normal normal 1em/1.2em monospace; margin:0; padding:0; background:none; vertical-align:top;"><span style="color: #660066;">half4 frag</span>(VertexOutput IN)</div>
<div style="font: normal normal 1em/1.2em monospace; margin:0; padding:0; background:none; vertical-align:top;"><span style="color: #009900;">{</span></div>
<div style="font: normal normal 1em/1.2em monospace; margin:0; padding:0; background:none; vertical-align:top;">&nbsp; &nbsp; <span style="color: #660066;">UNITY_SETUP_INSTANCE_ID</span>(IN);</div>
<div style="font: normal normal 1em/1.2em monospace; margin:0; padding:0; background:none; vertical-align:top;">&nbsp; &nbsp; <span style="color: #660066;">UNITY_SETUP_STEREO_EYE_INDEX_POST_VERTEX</span>(IN);</div>
<div style="font: normal normal 1em/1.2em monospace; margin:0; padding:0; background:none; vertical-align:top;">&nbsp; &nbsp; ...</div>
<div style="font: normal normal 1em/1.2em monospace; margin:0; padding:0; background:none; vertical-align:top;">&nbsp; &nbsp; return o;</div>
<div style="font: normal normal 1em/1.2em monospace; margin:0; padding:0; background:none; vertical-align:top;"><span style="color: #009900;">}</span></div>
</div>
<div style="clear: both"></div>
<br/>

=== HDRP Shader Setup ===


Same as with URP shaders. For all passes, you need to include the <code>multi_compile_instancing</code> and the <code>instancing_options procedural:setupGPUI</code> pragma directives. Please note that the <code>GPUInstancerSetup.hlsl</code> must be included after the HDRP include files:


<div class="code" style="border: 1px solid #c8ccd1;padding:5px;">
<div style="font: normal normal 1em/1.2em monospace; margin:0; padding:0; background:none; vertical-align:top;">...</div>
<div style="font: normal normal 1em/1.2em monospace; margin:0; padding:0; background:none; vertical-align:top;"><span style="color: #660066;">Pass</span> <span style="color: #009900;">{</span></div>

<div style="font: normal normal 1em/1.2em monospace; margin:0; padding:0; background:none; vertical-align:top;">&nbsp; &nbsp; ...</div>
<div style="font: normal normal 1em/1.2em monospace; margin:0; padding:0; background:none; vertical-align:top;">&nbsp; &nbsp; <span style="color: #660066;">HLSLPROGRAM</span></div>
<div style="font: normal normal 1em/1.2em monospace; margin:0; padding:0; background:none; vertical-align:top;">&nbsp; &nbsp; ...</div>
<div style="font: normal normal 1em/1.2em monospace; margin:0; padding:0; background:none; vertical-align:top;">&nbsp; &nbsp; #include <span style="color: #3366CC;">"Packages/com.unity.render-pipelines.core/ShaderLibrary/Common.hlsl"</span></div>
<div style="font: normal normal 1em/1.2em monospace; margin:0; padding:0; background:none; vertical-align:top;">&nbsp; &nbsp; #include <span style="color: #3366CC;">"Packages/com.unity.render-pipelines.high-definition/Runtime/ShaderLibrary/ShaderVariables.hlsl"</span></div>
<div style="font: normal normal 1em/1.2em monospace; margin:0; padding:0; background:none; vertical-align:top;">&nbsp;</div>
<div style="font: normal normal 1em/1.2em monospace; margin:0; padding:0; background:none; vertical-align:top;">&nbsp; &nbsp; #include <span style="color: #3366CC;">"Packages/com.gurbu.gpui-pro/Runtime/Shaders/Include/GPUInstancerSetup.hlsl"</span></div>
<div style="font: normal normal 1em/1.2em monospace; margin:0; padding:0; background:none; vertical-align:top;">&nbsp; &nbsp; #pragma multi_compile_instancing</div>
<div style="font: normal normal 1em/1.2em monospace; margin:0; padding:0; background:none; vertical-align:top;">&nbsp; &nbsp; #pragma instancing_options procedural<span style="color: #339933;">:</span>setupGPUI</div>
<div style="font: normal normal 1em/1.2em monospace; margin:0; padding:0; background:none; vertical-align:top;">&nbsp; &nbsp; <span style="color: #660066;">ENDHLSL</span></div>
<div style="font: normal normal 1em/1.2em monospace; margin:0; padding:0; background:none; vertical-align:top;"><span style="color: #009900;">}</span></div>
<div style="font: normal normal 1em/1.2em monospace; margin:0; padding:0; background:none; vertical-align:top;">...</div>
</div>


Same as with other vertex/fragment shaders above, you also need to add instancing setup to your input struct and vertex function if you don't already have it.


For the vertex input struct:

<div class="code" style="border: 1px solid #c8ccd1;padding:5px;">
<div style="font: normal normal 1em/1.2em monospace; margin:0; padding:0; background:none; vertical-align:top;"><span style="color: #660066;">struct</span> AttributesMesh</div>
<div style="font: normal normal 1em/1.2em monospace; margin:0; padding:0; background:none; vertical-align:top;"><span style="color: #009900;">{</span></div>
<div style="font: normal normal 1em/1.2em monospace; margin:0; padding:0; background:none; vertical-align:top;">&nbsp; &nbsp; ...</div>
<div style="font: normal normal 1em/1.2em monospace; margin:0; padding:0; background:none; vertical-align:top;">&nbsp; &nbsp; UNITY_VERTEX_INPUT_INSTANCE_ID</div>
<div style="font: normal normal 1em/1.2em monospace; margin:0; padding:0; background:none; vertical-align:top;"><span style="color: #009900;">}</span></div>
</div>


For the vertex output struct:

<div class="code" style="border: 1px solid #c8ccd1;padding:5px;">
<div style="font: normal normal 1em/1.2em monospace; margin:0; padding:0; background:none; vertical-align:top;"><span style="color: #660066;">struct</span> PackedVaryingsMeshToPS</div>
<div style="font: normal normal 1em/1.2em monospace; margin:0; padding:0; background:none; vertical-align:top;"><span style="color: #009900;">{</span></div>
<div style="font: normal normal 1em/1.2em monospace; margin:0; padding:0; background:none; vertical-align:top;">&nbsp; &nbsp; ...</div>
<div style="font: normal normal 1em/1.2em monospace; margin:0; padding:0; background:none; vertical-align:top;">&nbsp; &nbsp; UNITY_VERTEX_INPUT_INSTANCE_ID</div>
<div style="font: normal normal 1em/1.2em monospace; margin:0; padding:0; background:none; vertical-align:top;"><span style="color: #009900;">}</span></div>
</div>


The vertex function:

<div class="code" style="border: 1px solid #c8ccd1;padding:5px;">
<div style="font: normal normal 1em/1.2em monospace; margin:0; padding:0; background:none; vertical-align:top;">PackedVaryingsMeshToPS<span style="color: #660066;">Vert</span>(AttributesMesh inputMesh)</div>
<div style="font: normal normal 1em/1.2em monospace; margin:0; padding:0; background:none; vertical-align:top;"><span style="color: #009900;">{</span></div>
<div style="font: normal normal 1em/1.2em monospace; margin:0; padding:0; background:none; vertical-align:top;">&nbsp; &nbsp; PackedVaryingsMeshToPS outputPackedVaryingsMeshToPS;</div>
<div style="font: normal normal 1em/1.2em monospace; margin:0; padding:0; background:none; vertical-align:top;">&nbsp; &nbsp; <span style="color: #660066;">UNITY_SETUP_INSTANCE_ID</span>(inputMesh);</div>
<div style="font: normal normal 1em/1.2em monospace; margin:0; padding:0; background:none; vertical-align:top;">&nbsp; &nbsp; <span style="color: #660066;">UNITY_TRANSFER_INSTANCE_ID</span>(inputMesh, outputPackedVaryingsMeshToPS);</div>
<div style="font: normal normal 1em/1.2em monospace; margin:0; padding:0; background:none; vertical-align:top;">&nbsp; &nbsp; ...</div>
<div style="font: normal normal 1em/1.2em monospace; margin:0; padding:0; background:none; vertical-align:top;">&nbsp; &nbsp; return outputPackedVaryingsMeshToPS;</div>
<div style="font: normal normal 1em/1.2em monospace; margin:0; padding:0; background:none; vertical-align:top;"><span style="color: #009900;">}</span></div>
</div>


And the fragment function:

<div class="code" style="border: 1px solid #c8ccd1;padding:5px;">
<div style="font: normal normal 1em/1.2em monospace; margin:0; padding:0; background:none; vertical-align:top;"><span style="color: #660066;">void Frag</span>(PackedVaryingsMeshToPS packedInput, OUTPUT_GBUFFER(outGBuffer) #ifdef _DEPTHOFFSET_ON, out float outputDepth : SV_Depth #endif)</div>
<div style="font: normal normal 1em/1.2em monospace; margin:0; padding:0; background:none; vertical-align:top;"><span style="color: #009900;">{</span></div>
<div style="font: normal normal 1em/1.2em monospace; margin:0; padding:0; background:none; vertical-align:top;">&nbsp; &nbsp; <span style="color: #660066;">UNITY_SETUP_STEREO_EYE_INDEX_POST_VERTEX</span>(packedInput);</div>
<div style="font: normal normal 1em/1.2em monospace; margin:0; padding:0; background:none; vertical-align:top;">&nbsp; &nbsp; <span style="color: #660066;">UNITY_SETUP_INSTANCE_ID</span>(packedInput);</div>
<div style="font: normal normal 1em/1.2em monospace; margin:0; padding:0; background:none; vertical-align:top;">&nbsp; &nbsp; ...</div>
<div style="font: normal normal 1em/1.2em monospace; margin:0; padding:0; background:none; vertical-align:top;"><span style="color: #009900;">}</span></div>
</div>

<div style="clear: both"></div>
<br/>

=== Shader Graph Setup ===

[[File:GPUIProShaderGraphSetup.png|450px|thumb|left|GPUI Pro Shader Graph Setup]]

To set up a Shader Graph shader, simply add the '''<code>GPU Instancer Pro Setup</code>''' node to the shader and connect it to the Vertex Position output.

<br>
The primary function of the 'GPU Instancer Pro Setup' node is to incorporate instancing pragma directives and include necessary files in the shader. Essentially, it copies the provided input to the output without any alterations. If another node is already connected to the Vertex Position output, you can link it to the input of the 'GPU Instancer Pro Setup' node and then connect the output to the Vertex Position. If there are no nodes currently connecting to the Position output, you can add a '''[https://docs.unity3d.com/Packages/com.unity.shadergraph@14.0/manual/Position-Node.html Position]''' node in '''Object''' space, connect it to the input of the 'GPU Instancer Pro Setup' node, and then link the output to the Vertex Position, as illustrated in the image.

<div style="clear: both"></div>
<br>