Difference between revisions of "Bug: cutscene editor in toolset lags when headtracking is set"

From Dragon Age Toolset Wiki
Jump to: navigation, search
m (category)
m (more detailed status`)
 
(One intermediate revision by the same user not shown)
Line 1: Line 1:
 
*'''Version found: 1.0.1008.0''' <!-- put the version number of your toolset here -->
 
*'''Version found: 1.0.1008.0''' <!-- put the version number of your toolset here -->
*'''Status:''' Open
+
*'''Status:''' Already fixed via the "accurate headtracking" option
  
 
== Description ==
 
== Description ==
The cutscene editor will begin to lag very badly when I have headtracking set. The type of lag is 3-4 second delays when I do
+
The cutscene editor can begin to lag very badly when you have headtracking set. The lag can be on the order of 3-4 second delays when doing anything.
anything! I'll click the timeline and it will hang for 4 seconds.
+
 
If I scrub a slider it will take 3-5 seconds for it to respond. But
+
This is due to the complexity of the headtracking operation, and the fact that to be fully accurate the cutscene editor has to re-simulate all of the frames prior to the current one to find out where the heads would really be pointing.
as soon as I disable headtracking from all headtracking slots and
+
set them to blank the problem goes away.  
+
  
 
== Workarounds ==
 
== Workarounds ==
Don't turn on headtracking until your cutscene is completely done.
 
Do all your headtracking work last!
 
  
[[Category:Toolset bugs]]
+
Headtracking can be set to use a simpler simulation system during cutscene work via the "accurate headtracking" button in the toolbar or the option of the same name in the cutscene editor options panel. See [[Headtracking#Cutscene editor performance]] for more details.
[[Category:Cutscenes]]
+
 
 +
[[Category:Closed bugs]]

Latest revision as of 22:35, 18 January 2010

  • Version found: 1.0.1008.0
  • Status: Already fixed via the "accurate headtracking" option

Description

The cutscene editor can begin to lag very badly when you have headtracking set. The lag can be on the order of 3-4 second delays when doing anything.

This is due to the complexity of the headtracking operation, and the fact that to be fully accurate the cutscene editor has to re-simulate all of the frames prior to the current one to find out where the heads would really be pointing.

Workarounds

Headtracking can be set to use a simpler simulation system during cutscene work via the "accurate headtracking" button in the toolbar or the option of the same name in the cutscene editor options panel. See Headtracking#Cutscene editor performance for more details.