56 - Implement a delay in post-combat processing
After exiting combat, QH2 will begin processing achievements and stuff resulting in a loss of system performance.
During combat, various forms of crowd control may be used, such as mind control. When all non-mind controlled mobs are slain, combat will be exited, however there is still one more mob to kill. The resulting hitches caused by QH2's resumption of processing can interfere with fluid combat when the final mob is engaged.
This could be rectified by implementing a delay of some few seconds (user-configurable?) to allow the final mob(s) to be dealt with.
| User | When | Change |
|---|---|---|
| theondry | Jan 29, 2011 at 02:37 UTC | Create |
- 1 comment
- 1 comment
Facts
- Last updated
- Mar 30, 2012
- Reported
- Jan 29, 2011
- Status
- New - Issue has not had initial review yet.
- Type
- Defect - A shortcoming, fault, or imperfection
- Priority
- Medium - Normal priority.
- Votes
- 2
Reported by
Possible assignees
-
- Manager
- Author
-
- Author
-
- Maintainer
- Translator
-
- Ticket Manager
-
- Ticket Manager
- Reply
- #1
theondry Feb 17, 2011 at 06:26 UTC - 0 likesThe component that seems to be the most egregious slow-down-inator is the collection addon. If I disable QH2, the collector addon continues to run, and I continue to get post-combat slowdowns.
Additionally, I've noticed that the drake run in Grim Batol is all-but-unplayable while this is running.