Difference between revisions of "Simulation vs Render Time Scope"

From Bohemia Interactive Community
Jump to navigation Jump to search
m (Text replacement - "\[ *(https?\:\/\/[^\[ ]+\.bohemia\.net[^\[]+) ([^ ]+) *\]" to "{{ExternalLink|link= $1|text= $2}}")
 
(6 intermediate revisions by 2 users not shown)
Line 1: Line 1:
{{SideTOC}}
+
{{TOC|side}}
 
{{GVI|arma2oa|1.60}} {{GVI|TKOH|1.00}} {{GVI|arma3|1.00}}
 
{{GVI|arma2oa|1.60}} {{GVI|TKOH|1.00}} {{GVI|arma3|1.00}}
 
== Definitions ==
 
== Definitions ==
Line 9: Line 9:
 
* Refresh frequency is lowered the further the object is from the camera. {{cn}}<!--
 
* Refresh frequency is lowered the further the object is from the camera. {{cn}}<!--
  
-->=== Render Time Scope ===
+
-->
 +
=== Render Time Scope ===
  
 
'''Render Time Scope''' is working with the '''visual''' position of objects, which is rendered (''estimated'') separately from the calculated one.
 
'''Render Time Scope''' is working with the '''visual''' position of objects, which is rendered (''estimated'') separately from the calculated one.
Line 15: Line 16:
 
* The object's position is interpolated depending on its speed and movement direction.
 
* The object's position is interpolated depending on its speed and movement direction.
 
* Due to interpolation, the position might not be accurate but it is updated frequently, resulting in a smooth motion.
 
* Due to interpolation, the position might not be accurate but it is updated frequently, resulting in a smooth motion.
* Usually, [[:Category:Render Time Scope Scripting Commands|Render Time Scope commands]] should be used when something is visible to the player, such as UI or on-model precision.
+
* Usually, [[:Category:Command Group: Render Time Scope|render time scope scripting commands]] should be used when something is visible to the player, such as UI or on-model precision.
  
  
Line 29: Line 30:
 
[https://www.youtube.com/watch?v=6xUw0K292sw Video Showcase]
 
[https://www.youtube.com/watch?v=6xUw0K292sw Video Showcase]
  
<div style="clear: both"></div>
+
{{Clear}}
  
 
== Before Simulation and Render separation ==
 
== Before Simulation and Render separation ==
Line 39: Line 40:
 
== See Also ==
 
== See Also ==
  
* [https://www.bohemia.net/blog/experimental-betas-interpolating-the-future Experimental betas - Interpolating the future] blog article
+
* {{ExternalLink|link= https://www.bohemia.net/blog/experimental-betas-interpolating-the-future|text= Experimental betas - Interpolating the future}} blog article
* [https://forums.bohemia.net/forums/topic/151099-scripting-discussion-dev-branch/?page=21&tab=comments#comment-2720342 Sniperwolf572 forum post] explanation
+
* {{ExternalLink|link= https://forums.bohemia.net/forums/topic/151099-scripting-discussion-dev-branch/?page=21&tab=comments#comment-2720342|text= Sniperwolf572 forum post}} explanation
  
  
 
[[Category:Scripting Topics]]
 
[[Category:Scripting Topics]]

Latest revision as of 15:25, 26 July 2021

A2 OA Logo.png1.60 tkoh logo small.png1.00 Arma 3 logo black.png1.00

Definitions

Simulation Time Scope

Simulation Time Scope is working with the calculated position of objects.

  • It is updated on a lower frequency than the rendered position in order to save performance. [citation needed]
  • Refresh frequency is lowered the further the object is from the camera. [citation needed]

Render Time Scope

Render Time Scope is working with the visual position of objects, which is rendered (estimated) separately from the calculated one.

  • It is updated on a very high frequency (presumably on each frame). [citation needed]
  • The object's position is interpolated depending on its speed and movement direction.
  • Due to interpolation, the position might not be accurate but it is updated frequently, resulting in a smooth motion.
  • Usually, render time scope scripting commands should be used when something is visible to the player, such as UI or on-model precision.


Render Visual Time Scope.gif

Simulation vs Render

For performance concerns, Simulation and Render cycles are separated since Arma 2: Operation Arrowhead v1.60. This means that any object has now "two" positions: the computed one (simulation), and the visual one (render).

Video Showcase

Before Simulation and Render separation

From Operation Flashpoint to Arma 2: Operation Arrowhead v1.59, the simulation first updated the world's state (units position) then the visual rendering was done.
Sequencing these operations worked fine only in non-intensive scenarios; as soon as the CPU reached its limits, the simulation frequency was lowered in order to maintain acceptable FPS, resulting in units visually "jumping".


See Also