Unity Engine settings

C#
Show gutter mark or Code Vision for implicit script usages | Controls Unity gutter icons and Code Vision hints for classes, methods, and fields that Unity uses implicitly: |
Enable performance analysis in frequently called code | When this option is enabled, ReSharper shows you performance-sensitive areas: event functions that are called each frame, such as |
Highlight performance critical contexts: | Unity has a number of methods that get called frequently. These methods are treated as a performance-critical context and can be highlighted in the editor gutter. Choose Always to highlight all such areas, Current method only to highlight the current method, or Never to hide these highlights. ![]() |
Show gutter mark or Code Vision for frequently called methods | When this option is enabled, you will see the following gutter indicators next to frequently called methods. The option also controls the corresponding Code Vision hints: ![]() |
Enable analysis for Burst compiler issues | Toggles Burst compiler warnings. |
Show gutter mark or Code Vision for Burst-compiled methods | Toggles additional gutter icons and Code Vision hints for Burst-compiled methods. This option requires Enable analysis for Burst compiler issues. |
Use assembly definition folder as namespace root | Calculates C# namespaces relative to the folder containing the assembly definition (.asmdef), excluding parent folders. If the assembly specifies a root namespace, ReSharper uses it instead of the assembly definition folder name. Regenerate Unity project files after changing the root namespace in the assembly definition. This option is disabled by default. |
Skip 'Editor' folders when calculating namespaces | Excludes folders named Editor when calculating C# namespaces in Unity projects. This avoids adding an |
DOTS
Exclude DOTS-generated code from navigation results | Hides source-generated partial declarations of Unity DOTS types from navigation results, so you can navigate to the declarations you wrote. Clear this checkbox to include generated declarations. |
Refactoring
Serialized field refactoring settings | Controls whether the Rename refactoring adds
|
Text-based assets
Parse text-based asset files for script and event handler usages | Indexes Unity assets saved in text format to find references to scripts, serialized fields, and event handlers in scenes, prefabs, and other assets. This lets Find Usages include references from asset files. Clear this checkbox to reduce indexing work at the cost of asset usage information. |
Cache prefab data to improve Find Usages performance | Caches imported prefab data so that repeated Find Usages searches can reuse it. Clear this checkbox to reduce cache memory usage at the cost of slower searches through prefabs. |
Automatically disable asset indexing for large solutions | Disables asset indexing when an external file to index exceeds 250 MiB or their total size exceeds 4,000 MiB. Large binary assets that cannot be indexed do not count toward these limits. ReSharper shows a notification when it disables indexing. You can re-enable it with Parse text-based asset files for script and event handler usages. |
Shaders
Suppress resolve errors of unqualified names | Suppresses unresolved-name errors in HLSL shader code in Unity projects. Enable this option if Unity-specific shader declarations cause false errors. This option is disabled by default. |


