Rule
- Substance 3D home
- Home
- Getting Started
- Getting Started overview
- Activation and licenses
- System requirements
- Project creation
- Export
- Export overview
- Export window
- Export presets
- Export overview
- Glossary
- Performance
- Getting Started overview
- Interface
- Assets
- Substance 3D Assets
- Color picker
- Display settings
- History
- Layer stack
- Main menu
- Project configuration
- Properties
- Settings
- Shader settings
- Texture Set
- Toolbars
- Viewport
- Miscellaneous
- Assets
- Painting
- Painting overview
- Tool list
- Straight line
- Lazy mouse
- Symmetry
- Fill projections
- Presets
- Presets overview
- Creating and saving presets
- Creating particles presets
- Photoshop brush presets (ABR)
- Dynamic strokes
- Advanced channel painting
- Vector graphic (.svg & .ai)
- Text resource
- Effects
- Baking
- Content
- Creating custom effects
- Importing assets
- Creating custom effects
- Features
- Automatic UV Unwrapping
- Physical size
- Smart Materials and Masks
- Subsurface Scattering
- Dynamic Material Layering
- UV Reprojection
- UV Tiles
- Color Management
- Post Processing
- Iray Renderer
- Plugins
- Sparse Virtual Textures
- Custom Shaders
- SpaceMouse® by 3Dconnexion
- Universal Scene Description (USD)
- Send to
- Technical Support
- Performance Guidelines
- Configuring Pens and Tablets
- Exporting the log file
- Exporting a DXDiag
- Technical issues
- GPU Issues
- Crash when working with overclocked GPU
- Forcing the external GPU on Mac OS
- GPU drivers compatibility
- GPU drivers crash with long computations (TDR crash)
- GPU has outdated drivers
- GPU is not recognized
- GPU is not recognized and is mentionned as GDI Generic
- Issues with Nvidia GPUs on recent Mac OS versions
- Multi/Bi-GPU
- Running on integrated GPU
- Painter doesn't start on the right GPU
- Startup Issues
- Rendering Issues
- Stability Issues
- Miscellaneous Issues
- GPU Issues
- Workflow Issues
- Export Issues
- Tools Issues
- Project Issues
- Library Issues
- Viewport Issues
- Plugins Issues
- License Issues
- Pipeline and integration
- Installation and preferences
- Configuration
- Resource management
- Scripting and development
- Scripts and plugins
- Shader API Reference
- Shader API overview
- Changelog - Shader API
- Libraries - Shader API
- Lib Alpha - Shader API
- Lib Bayer - Shader API
- Lib Defines - Shader API
- Lib Emissive - Shader API
- Lib Env - Shader API
- Lib Normal - Shader API
- Lib PBR - Shader API
- Lib PBR Aniso - Shader API
- Lib Pom - Shader API
- Lib Random - Shader API
- Lib Sampler - Shader API
- Lib Sparse - Shader API
- Lib SSS - Shader API
- Lib Utils - Shader API
- Lib Vectors - Shader API
- Parameters - Shader API
- Shaders - Shader API
- Release notes
- Release notes overview
- All Changes
- Version 10.1
- Version 10.0
- Version 9.1
- Old versions
- Version 9.0
- Version 8.3
- Version 8.2
- Version 8.1
- Version 7.4
- Version 7.3
- Version 7.2
- Version 2021.1 (7.1.0)
- Version 2020.2 (6.2.0)
- Version 2020.1 (6.1.0)
- Version 2019.3
- Version 2019.2
- Version 2019.1
- Version 2018.3
- Version 2018.2
- Version 2018.1
- Version 2017.4
- Version 2017.3
- Version 2017.2
- Version 2017.1
- Version 2.6
- Version 2.5
- Version 2.4
- Version 2.3
- Version 2.2
Excluding resources in a resource path
This page explains how to setup an ignore file to specify resources and folders that will be ignored during the crawling process of the the Assets window. It allows to avoid unwanted resources from being displayed.
This functionality is available since version 7.2.3.
Creating an ignore file
Navigate to the location of the resource folder in which you want to hide resources. Then create a file named as follow:
.ignore_assets_pt
It should look like this once created:
Example
The following file content will discard any resources and folders other than the default library folders:
# exclude all * # re-include library directories !alphas !colorluts !effects !emitters !environments !export-presets !generators !materials !presets !procedurals !receivers !shaders !smart-masks !smart-materials !templates !textures
Rules and guidelines
The following table shows the general rules that applies to the ignore file.
The pattern matching of the ignore file is case sensitive, independently from the Operating System behavior.
|
Description |
Example |
---|---|---|
Blank Line |
Empty line that doesn't match anything. Can be used as a separator for readability. |
|
Directory separator |
The forward slash is used as a directory separator. Separators may occur at the beginning, middle or end of a search pattern. If there is a separator at the beginning or middle (or both) of the pattern, then the pattern is relative to the directory level of the ignore file itself. Otherwise the pattern may also match at any level below the ignore file level. If there is a separator at the end of the pattern it will be ignored, the pattern will still match both files and directories. |
folder/filename.extension folder/sub-folder |
Comment line |
A line starting with the number sign (or hash) serves as a comment. |
# This is a comment |
Asterisk |
An asterisk matches anything except a forward slash. |
# Match anything starting with Alpha alpha* # Match any file with given extension *.jpg |
Character range |
Range of characters can be specified between brackets to match folder and filenames.
Range and list can be numbers as well with the format [0-9]. |
# Exclude any UDIM image in PNG *_[0-9][0-9][0-9][0-9].png |
Escaping character |
Indicate literal characters that would otherwise be ignored or used as rules. |
# This is a comment [#]This/Is/A/Path |
Trailing spaces |
Trailing spaces are ignored unless they are escaped. |
# Match a subfolder with trailing space folder/subfolder[ ] |
Exclamation Prefix |
Prefixing a pattern with an exclamation point allows to negate it. Any matching file excluded by a previous pattern will become included again. It is not possible to re-include a file if a parent directory of that file is excluded. Crawling doesn’t list excluded directories for performance reasons, so any patterns on contained files have no effect, no matter where they are defined. |
# Re-include specific file !my_file_name.png |