Your current tdr is too low substance painter что это
Русские Блоги
Substance Painter TDR проблема TDR проблема
TDR означает обнаружение и восстановление тайм-аута.
Это функция операционной системы Windows, которая может обнаруживать проблему с ответом графической карты и восстанавливать работоспособность рабочего стола путем сброса карты.
Если операционная система не получает ответа от видеокарты в течение определенного периода времени (по умолчанию 2 секунды), операционная система сбросит настройки видеокарты.
До того, как существовал TDR, проблемы такого характера вызывали зависание системы и требовали перезапуска операционной системы.
Если TDR включен и вы видите сообщение об ошибке TDR «Драйвер дисплея перестал отвечать и был восстановлен», это означает, что операционная система Windows сбрасывает драйвер дисплея.
В среде Windows при открытии новой версии SP может появиться следующее окно с запросом вашего TDR (Timeout Detection).
Восстановление) слишком мало, нажмите Продолжить
В любом случае может войти в программное обеспечение, но это может вызвать такие проблемы, как сбои программного обеспечения и чрезмерная задержка. Эта статья предлагает решение этой проблемы вместе с официальной документацией.
Слишком сложно изменить реестр. Откройте собственное программное обеспечение для настройки NVIDIA ==>
“C:\Program Files (x86)\NVIDIA Corporation\Nsight Visual Studio Edition XXX\Monitor\Common\Nsight.Monitor.exe”
После изменения необходимо перезагрузить компьютер, чтобы изменения вступили в силу.
SP рекомендует 60 секунд
TDR stands for Timeout Detection and Recovery. This is a feature of the Windows operating system which detects response problems from a graphics card, and recovers to a functional desktop by resetting the card. If the operating system does not receive a response from a graphics card within a certain amount of time (default is 2 seconds), the operating system resets the graphics card.
Before TDR existed, problems of this nature would have resulted in a system freeze and required a reboot of the operating system. If TDR is enabled and you see the TDR error message, “Display driver stopped responding and has recovered,” this means that the Windows operating system reset the display driver.
There are three different possible debugging configurations:
Local debugging with a single GPU,
Local debugging with multiple GPUs, or
Remote debugging.
Choose the one that most closely reflects your NVIDIA Nsight setup:
Local Debugging with a Single GPU
Disabling TDR removes a valuable layer of protection, so it is generally recommended that you keep it enabled.
However, setting the TDR delay too low can cause the debugger to fail for one of two reasons:
Debugging on some GPUs will fails with a TDR delay of less than 10 seconds.
Debug builds of CUDA kernels run more slowly and may intrinsically require additional time to complete. With too low of a TDR delay, the kernels may not have enough time to complete.
Therefore, if you are using local debugging with a single GPU, it’s recommended that you leave TDR enabled, and set the delay to 10 seconds.
To enable TDR and change the delay, do the following:
Right-click the Nsight Monitor icon in the system tray.
Select Options.
In the Options window on the General tab, set WDDM TDR enabled to True.
Change the WDDM TDR Delay from the default setting to 10.
Local Debugging with Multiple GPUs or Remote Debugging
When using either a local debugging configuration with multiple GPUs, or a remote debugging configuration, it’s important to disable TDR. This is because with most CUDA applications, a TDR means that any debugging operation after the TDR will fail. You will not be able to step, set breakpoints, view variables, etc. The application will receive a grid launch failure, and the CUcontext will begin to report errors.
Having TDR enabled can interfere with GPU debugging because the graphics card is perceived by the operating system as unresponsive when the execution of a target application is paused or when the debugger is performing certain operations.
To disable TDR, do the following:
Right-click the Nsight Monitor icon in the system tray.
Select Options.
In the Options window on the General tab, set WDDM TDR enabled to False.
Documentation
Substance 3D Painter
Substance 3D Painter
Applications
Plugins & Integrations
Content Platforms
Pipeline Support
Local Search
Sections
GPU drivers crash with long computations (TDR crash)
On Windows, this window will appear if Substance 3D Painter detects that the current TDR value is below a specific limit (10 seconds).
In order to prevent any rendering or GPU computation from locking up the system, the Windows operating system kills the GPU driver whenever a rendering takes more than a few seconds. When the driver is killed, the application using it crashes automatically. It is not possible to know how long a rendering task or a computation may take (it depends on the GPU, the drivers, the OS, the mesh size, the texture size, etc.), therefore it is not possible to put a limit on how much the computer should process and avoid the crash from the application level.
On Windows there is a registry key specifying how long the OS should wait before killing the GPU driver. Application are not authorized to modify this setting directly, this procedure has to be done manually (see below).
List of Keys that need to be changed
To adjust the TDR simply increase the TDR Delay: change both TdrDelay and TdrDdiDelay to a higher value (like 60 seconds).
How to edit the TDR values
Follow this procedure to change the TDR value.
Note that two different keys will have to be created/edited.
Please note that editing the registry can have serious, unexpected consequences that can prevent the system from starting and may require to reinstall the whole operating system if you are unsure of how to modify it. The registry keys mentioned in this page shouldn’t create these kind of issues however.
Adobe take no responsibility for any damage caused to your system by modifying the system registry.
Click on Start then Run (or press the Windows and R key). It will open the Run window.
Type regedit in the text field and press OK.
The registry window will open.
In the left pane, navigate in the tree to the GraphicsDrivers key by going into:
Be sure to stay on «GraphicsDrivers» and to not click on the Registry keys below before going through the next steps.
This value indicates in seconds how long the operating system will wait before considering that the GPU is unresponsive during a computation.
This value indicates in seconds how long the operating system will wait before considering that a software took too much time to leave the GPU drivers.
Hexadecimal is the default value, simply switch to decimal to display the right value. Note that 3C (Hexadecimal) equals to 60 (Decimal).
The right pane should now looks like this:
The TdrValue is only looked at when the computer start, so to force a refresh a reboot is necessary.
If the application still crashes when doing a long computation, try increasing the delay (in seconds) from 60 to 120 for example.
There are two ways to revert the TDR to its default values :
Documentation
Substance 3D Painter
Substance 3D Painter
Applications
Plugins & Integrations
Content Platforms
Pipeline Support
Local Search
Sections
GPU drivers crash with long computations (TDR crash)
On Windows, this window will appear if Substance 3D Painter detects that the current TDR value is below a specific limit (10 seconds).
In order to prevent any rendering or GPU computation from locking up the system, the Windows operating system kills the GPU driver whenever a rendering takes more than a few seconds. When the driver is killed, the application using it crashes automatically. It is not possible to know how long a rendering task or a computation may take (it depends on the GPU, the drivers, the OS, the mesh size, the texture size, etc.), therefore it is not possible to put a limit on how much the computer should process and avoid the crash from the application level.
On Windows there is a registry key specifying how long the OS should wait before killing the GPU driver. Application are not authorized to modify this setting directly, this procedure has to be done manually (see below).
List of Keys that need to be changed
To adjust the TDR simply increase the TDR Delay: change both TdrDelay and TdrDdiDelay to a higher value (like 60 seconds).
How to edit the TDR values
Follow this procedure to change the TDR value.
Note that two different keys will have to be created/edited.
Please note that editing the registry can have serious, unexpected consequences that can prevent the system from starting and may require to reinstall the whole operating system if you are unsure of how to modify it. The registry keys mentioned in this page shouldn’t create these kind of issues however.
Adobe take no responsibility for any damage caused to your system by modifying the system registry.
Click on Start then Run (or press the Windows and R key). It will open the Run window.
Type regedit in the text field and press OK.
The registry window will open.
In the left pane, navigate in the tree to the GraphicsDrivers key by going into:
Be sure to stay on «GraphicsDrivers» and to not click on the Registry keys below before going through the next steps.
This value indicates in seconds how long the operating system will wait before considering that the GPU is unresponsive during a computation.
This value indicates in seconds how long the operating system will wait before considering that a software took too much time to leave the GPU drivers.
Hexadecimal is the default value, simply switch to decimal to display the right value. Note that 3C (Hexadecimal) equals to 60 (Decimal).
The right pane should now looks like this:
The TdrValue is only looked at when the computer start, so to force a refresh a reboot is necessary.
If the application still crashes when doing a long computation, try increasing the delay (in seconds) from 60 to 120 for example.
There are two ways to revert the TDR to its default values :
Your current tdr is too low substance painter что это
This script (Substance-TDR-Values.bat) sets the registry values TdrDelay and TdrDdiDelay to the recommended amounts. If your Substance software keeps crashing within heavy GPU computations or shows you the following prompt after starting it, this script may solve your problem as it sets the recommended TDR (Timeout Detection Recovery) for Substance. For more information on this issue visit the Substance Painter Docs.
Add registration entries
Download the registration entries file here.
A warning message will pop up, asking if you really want to add/modify the entries. Click Yes to proceed.
Restart your computer.
Whenever the issue comes up again, just re-run the script (and restart your computer).
Run script via context menu
Download the script here.
Open the folder containing the script in the File Explorer.
In the File Explorer, right click Substance-TDR-Values.bat and then select Run as administrator from the context menu. 
Restart your computer. If you run Substance-TDR-Values-Restart.bat instead, it will restart automatically.
Whenever the issue comes up again, just re-run the script (and restart your computer).
Run script via PowerShell
Download the script here.
Open the folder containing the script in the File Explorer.
In the File Explorer, go to File > Open Windows PowerShell > Open Windows PowerShell as administrator. 
In the PowerShell type .\Substance-TDR-Values.bat and press Enter. Your PowerShell result should look like this: 
Restart your computer. If you run Substance-TDR-Values-Restart.bat instead, it will restart automatically.
Whenever the issue comes up again, just re-run the script (and restart your computer).
About
TDR (Timeout Detection Recovery) values recommended for Substance
Documentation
Substance 3D Painter
Substance 3D Painter
Applications
Plugins & Integrations
Content Platforms
Pipeline Support
Local Search
Sections
Painter doesn’t start on the right GPU
On Windows, the application may not use the right GPU when starting up which can lead to performance and stability issues. Below is a list of of common issues and their solutions to make sure the software works with the right GPU.
To know which GPU is used, you can check the log file.
Monitor Cables Configuration
On Windows the GPU assigned to an application depends of the monitor on which the application is running. This is because the monitor cables are linked directly to the output of the GPU itself. The application may start on the wrong GPU therefore if the monitor on which it starts is linked to the graphics output of the motherboard instead of the one from the graphic card itself. In that case, Windows is likely to use the integrated GPU rather than the dedicated GPU.
To solve this issue : simply fix the cable configuration by un-plugin the monitor linked to the motherboard and then linking it to the GPU outputs instead.
Incorrect GPU Driver Installation
If the GPU drivers are not properly installed the application will be unable to reach the dedicated GPU and it will have to fallback on the integrated GPU instead.
To solve this issue : uninstall the current GPU drivers, perform a cleanup and then reinstall the GPU drivers after a reboot of the computer.
Nvidia GPU driver profile setting
On some computers, such as Laptops, the application may run on the integrated GPU instead of the dedicated Nvidia GPU by default. With an NVIDIA GPU, the switch to the right GPU depends on application profiles. If an application does not have such profile, you can assign one manually.
To solve this issue :
Windows Performance Setting
Windows may have set the wrong GPU setting for the application because of the default performance and power consumption settings.
To solve this issue : follow the step by step below to override the default GPU configuration.