History of MembersPage/KevinBlack/Issues
Older Newer
2011-05-19 15:55:41 . . . . 3e44be11.adsl.enternet.hu [IAC flag set correctly regardless of minmap: use 1.1.92 or iac_close_minmap=FF]
2011-05-19 15:23:06 . . . . 3e44be11.adsl.enternet.hu [iac flag saga]
2011-04-29 12:34:53 . . . . pool-141-158-187-251.cap.east.verizon.net [comment about tps and iac close minmap]
2011-04-29 08:39:06 . . . . 3e44a184.adsl.enternet.hu [thanx for the vemslogs. hint about iac TPS threshold]
2011-04-28 23:57:48 . . . . KevinBlack [1.1.90 IAC retard during pulls]


Changes by last author:

Changed:
IAC Close minmap set to 86kpa

(Which I assume closes and/or shuts off all IAC functions above the setting of 86 kpa) - "Iac close position" is set to "0".

We'll check 1.1.90 and 1.1.91 (note that both are unreleased) and reproduce the setup. Thanx for the vemslogs and precise position information !

* IAC Close minmap set to 86kpa

** Which sets iac to "Iac close position" (set to "0") above the setting of 86 kpa (irrelevant of TPS, and unrelated to the IAC flag)

* the IAC flag should theoretically be off when TPS > IAC TPS threshold (1% in this case)

** in some logs on this page, this doesn't seem to hold. Thanx for the vemslogs !

Added:

* The vemslog was captured with the not-extensively tested (and unreleased) 1.1.90 but this also effects 1.1.91 that was a release-candidate.

** We found that with MAP > iac_close_minmap it was theoretically possible to bypass setting the IAC flag

** so in 1.1.91, leave iac_close_minmap at FF (default value)

** fixed in 1.1.92.

** thinking about an extra safety condition to disable retard when TPS > iac_tps_thres (even if IAC flag is on for some reason)