lee/renderdoc
1
0
Fork 0
mirror of https://github.com/baldurk/renderdoc.git synced 2026-05-05 17:40:39 +00:00
Code Issues Packages Projects Releases Wiki Activity

Update some out-of-date docs

Browse Source
This commit is contained in:
baldurk
2021-07-16 11:56:18 +01:00
parent 3d00a585d4
commit 6130a120ef
2 changed files with 9 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/imgs/Screenshots/TexList.png
BIN
View File
Binary file not shown.
Side by Side Swipe Overlay

Before

Width:  |  Height:  |  Size: 5.5 KiB

After

Width:  |  Height:  |  Size: 20 KiB

docs/window/settings_window.rst
+9 -1
View File
@@ -124,6 +124,14 @@ This option enables the functionality allowing capturing of programs that aren't
This option **can be dangerous** which is why you have to deliberately enable it here. Be careful when using this and only do so when necessary - more details can be found in the :ref:`global process hook <global-process-hook>` details.
---------------
| :guilabel:`Enable process injection (restart required)` Default: ``Disabled``
On windows only RenderDoc is able to inject into running processes. By default this is disabled since it is almost never the right thing to do and can easily break, so you are strongly recommended to instead launch your program from RenderDoc's launch process panel.
Injecting into processes can be unreliable and should only be used as a last resort when no other methods succeed, it should not be used as a primary method of launching applications.
---------------
| :guilabel:`Allow periodic anonymous update checks` Default: ``Enabled``
@@ -291,7 +299,7 @@ Android options
| :guilabel:`Android SDK root path` Default: ``Empty``
RenderDoc requires some android tools from the android SDK to be able to function. In most cases it's able to locate the tools automatically without any configuration needed, but if not this option allows you to manually locate the JDK root.
RenderDoc requires some android tools from the android SDK to be able to function. In most cases it's able to locate the tools automatically without any configuration needed, but if not this option allows you to manually locate the SDK root.
By default it will try to auto-locate those tools by looking in different environment variables like ``ANDROID_HOME`` and ``ANDROID_SDK``, or else searching the default executable path. If it fails completely it will try to use the tools bundled with RenderDoc's installation.