Drag[en]gine Wiki

User Tools

Site Tools

Trace:
democap:performanceimprovements

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision		Previous revision
democap:performanceimprovements [2022/04/24 11:33] – dragonlorddemocap:performanceimprovements [2022/08/14 01:57] (current) – [SteamVR Motion Smoothing] dragonlord
Line 4: Line 4:
 </WRAP> </WRAP>
  
-<WRAP right :en>{{ :democap:ui_panel_settings.png?direct|Panel Settings}}</WRAP>+VR is heavy on the GPU and thus performance problems are common. Following the steps outlined here can help to improve performance.
  
-The Drag[en]gine game engine is currently (as of version 1.7.1) not optimized yet for VR use. This can cause performance issues with less performant GPUs or graphics intensive scenes. You can improve the performance for motion capture by changing a few [[dragengine:modules:opengl:main|Graphic Module Parameters]].+====== SteamVR Motion Smoothing ======
  
-The OpenGL module automatically adjusts the VR render frame rate to 90, 45, 30 or 15Hz depending on the performance of the GPU. For motion capturing a frame rate of 30 is enough for quick motion while a frame rate of 15 is still acceptable for common animations. But for the actor wearing the HMD, low frame rates can be strainable. It is thus recommended to improve the performance as much as possible, for the sake of your actor.+The biggest problems seems to come from the  use of SteamVR Motion Smoothing feature. This feature is designed to improve the perceived frame rate of games not able to keep up with the required 90Hz frame rate. This causes though wavy and nauseating images in DEMoCap.
  
-In the [[democap:uipanelsettings|UI Settings Panel]] click on <wrap em><wrap hi>Module Parameters</wrap></wrap> button.+<WRAP center round important 60%> 
 +It is highly recommended to <wrap em>disable</wrap> the SteamVR <wrap em>Motion Smoothing</wrap> feature. 
 +</WRAP>
  
-The module parameters dialog allows to change game engine module parameters. The graphic module parameters are of highest interest here to improve performance.+While taking care of the biggest issue these following steps can help improve the performance further
  
-Once you are done making changes click on <wrap em><wrap hi>Save</wrap></wrap> button to apply the changes. Upon exiting DEMoCap the changes are saved by the launcher and will be restored the next time DEMoCap is run. +====== Settings Panel ======
-<WRAP clear/>+
  
-<WRAP center round tip 60%> +<WRAP right :en>{{ :democap:ui_panel_settings.png?direct|Panel Settings}}</WRAP> 
-It is recommended to begin by disabling <wrap em>SSAO</wrap> and setting <wrap em>VR Render Scale</wrap> to 50. This is usually enough to make DEMoCap render fast enough on different types of systems. + 
-</WRAP>+The settings panel provides these parameters you can tune. 
 + 
 +===== Global Illumination ===== 
 + 
 +Global Illumination is heavy on the GPU. For motion capture these are usually not required hence you can disable this option in the settings panel. By default this option is disabled. Should this be enabled you can disable it to improve performance. 
 + 
 +<WRAP clear/>
  
 ====== Graphic Module Parameters ====== ====== Graphic Module Parameters ======
  
 <WRAP box right :en>{{ :democap:settings.png|Settings Dialog}}<WRAP centeralign>Settings Dialog</WRAP></WRAP> <WRAP box right :en>{{ :democap:settings.png|Settings Dialog}}<WRAP centeralign>Settings Dialog</WRAP></WRAP>
 +
 +In the [[democap:uipanelsettings|UI Settings Panel]] click on <wrap em><wrap hi>Module Parameters</wrap></wrap> button.
 +
 +The module parameters dialog allows to change game engine module parameters. The graphic module parameters are of highest interest here to improve performance.
 +
 +Once you are done making changes click on <wrap em><wrap hi>Save</wrap></wrap> button to apply the changes. Upon exiting DEMoCap the changes are saved by the launcher and will be restored the next time DEMoCap is run.
  
 ===== SSAO ===== ===== SSAO =====
Line 41: Line 54:
 ===== GI Quality ===== ===== GI Quality =====
  
-The OpenGL supports True Dynamic Global Illumination. This uses ray-tracing (without RTX for the time being) and thus has a performance impact on complex scenes. On simple scenes this should be of little impact. You can though lower the quality or disable GI altogether. +If Global Illumination (GI) is enabled you can improve the performance by lowering the GI Quality parameter.
  
 This parameters accepts the values "off", "low", "medium", "high" and "veryHigh". This parameters accepts the values "off", "low", "medium", "high" and "veryHigh".
Line 48: Line 60:
 ===== Shadow Quality ===== ===== Shadow Quality =====
  
-Defines the size of rendered shadow maps. This is usually not a problem unless complex scenes are used. You can though lower the quality or disable shadow casting altogether.+Defines the size of rendered shadow maps. This is usually not a problem unless the GPU is not so strong. You can though lower the quality or disable shadow casting altogether.
  
 This parameters accepts the values "off", "low", "medium", "high" and "veryHigh". This parameters accepts the values "off", "low", "medium", "high" and "veryHigh".
Line 54: Line 66:
 ===== SSR ===== ===== SSR =====
  
-SSR (Screen Space Reflection) is another effect which is sensitive to the render size. In general though this effect has less impact on performance but if you are in a pinch you can try disabling this effect too.+SSR (Screen Space Reflection) is another effect which can improve performance if it is disabled. In general though this effect has less impact on performance but if you are in a pinch you can try disabling this effect too.
  
 ===== Transparency Layer Limit ===== ===== Transparency Layer Limit =====
  
-If you use scenes or characters with lots of transparency this can cause performance issues since the OpenGL module renders depth peeled transparency to ensure fully correct transparency. Using this parameter you can limit the count of peeled layers that are rendered. This causes artifacts if more layers than allowed are required but keeps the performance impact in checks.+If you use scenes or characters with lots of transparency this can cause performance issues. Using this parameter you can limit the count of transparent layers rendered. This can causes artifacts if more layers than allowed are required to render each pixel correctly. Still limiting the maximum count of transparent layers rendered can improve the performance.
  
 Using a value of 4 is usually a good value to use. If performance is an issue you can try dropping it down to 2. Going down to 1 is not recommended as this can easily break rendering. Using a value of 4 is usually a good value to use. If performance is an issue you can try dropping it down to 2. Going down to 1 is not recommended as this can easily break rendering.
  
democap/performanceimprovements.1650799991.txt.gz · Last modified: 2022/04/24 11:33 by dragonlord

Page Tools

Except where otherwise noted, content on this wiki is licensed under the following license: CC Attribution-Noncommercial-Share Alike 4.0 International
CC Attribution-Noncommercial-Share Alike 4.0 International Donate Powered by PHP Valid HTML5 Valid CSS Driven by DokuWiki