Rtgi+01702+release+verified -

Find and Download Plugins

This page lists plugins made by research groups and developers around the world. It is generated automatically from RDF descriptions published by the plugin authors.

▶ How to Install — For installation instructions see the bottom of this page.

▶ Vamp Plugin Pack — Some of these plugins are also available in the Vamp Plugin Pack, a convenient bundle installer.

Spotted a mistake? Want to get your plugins listed here?


Platform Windows  Mac OS/X  32-bit Linux  64-bit Linux  Other 

Rtgi+01702+release+verified -

Only download RTGI from the official Marty’s Mods website or the creator's Patreon.

Recent verified builds have introduced features like "HiZ Min-Max Tracing" to improve performance, making it playable on mid-range hardware like the GTX 1060. Installation and Verification

The "01702" designation typically refers to a or specific release hash used by the community and developers to ensure stability and compatibility. Verification is crucial for this mod because it is primarily distributed through Pascal Gilcher’s Patreon , and "verified" status often indicates a build that has been cleared of major bugs for public or beta use. Key Features of the Verified Release rtgi+01702+release+verified

Works on a vast range of games that support ReShade, from older classics like GTA V and Skyrim to newer titles lacking native RT.

Install the latest version of ReShade for your specific game. Only download RTGI from the official Marty’s Mods

RTGI stands for . Unlike native ray tracing built into a game's engine, this shader operates in "screen space." It uses the information visible on your monitor (the depth buffer) to simulate how light bounces off surfaces, creating realistic shadows and color bleeding.

To ensure you are using a "verified" and safe version of RTGI: Verification is crucial for this mod because it

Provides much deeper, more accurate shadows in corners and crevices than standard game settings.


How to Install

A Vamp plugin set consists of a single dynamic library file with .dll, .dylib, or .so extension (depending on your platform), plus optionally a category file with .cat extension and an RDF description file with .ttl or .n3 extension.

To install a plugin set, copy the plugin's library file and any supplied category or RDF files into your system or personal Vamp plugin location.

The plugin file extension and the location to copy into depend on which operating system you are using:

Your operating systemFile extension for pluginsWhere to put the plugin files
macOS.dylibOn a Mac:
  • Put plugins for all users to use in /Library/Audio/Plug-Ins/Vamp
  • Put plugins for only the current user in $HOME/Library/Audio/Plug-Ins/Vamp
  • The Library folders are hidden by default; see here for details of how to show them
64-bit Windows.dllWhen using a 64-bit version of Windows:
  • Put 32-bit plugins in C:\Program Files (x86)\Vamp Plugins
  • Put 64-bit plugins in C:\Program Files\Vamp Plugins
  • Both 32-bit and 64-bit plugins can be used, as long as you put them in the right places as above
  • If a plugin package is not described as 64-bit, then it is a 32-bit plugin. Some older plugins were only published in 32-bit form.
32-bit Windows.dllWhen using a 32-bit version of Windows:
  • Put 32-bit plugins in C:\Program Files\Vamp Plugins
  • You cannot use 64-bit plugins at all on 32-bit Windows
  • If a plugin package is not described as 64-bit, then it is a 32-bit plugin. Some older plugins were only published in 32-bit form.
Linux, other Unix.soOn Linux, BSD systems, etc:
  • Put plugins for all users to use in /usr/local/lib/vamp
  • Put plugins for only the current user in $HOME/vamp
  • Only plugins with the correct architecture can be used (32-bit plugins on 32-bit systems, and 64-bit on 64-bit).

You can alternatively set the VAMP_PATH environment variable to override the search path for for Vamp plugins. VAMP_PATH should contain a semicolon-separated (on Windows) or colon-separated (macOS, Linux) list of directory locations. If it is set, it will completely override the standard locations listed above. (N.B. When using 32-bit plugins on 64-bit Windows, some hosts will check for the VAMP_PATH_32 environment variable instead of VAMP_PATH.)