InfiSTAR – User talk
Jump to navigation
Jump to search
Killzone Kid (talk | contribs) |
No edit summary |
||
Line 3: | Line 3: | ||
Please post them on Feedback Tracker and make ticket private [[User:Killzone Kid|Killzone Kid]] ([[User talk:Killzone Kid|talk]]) 16:40, 2 April 2015 (CEST) | Please post them on Feedback Tracker and make ticket private [[User:Killzone Kid|Killzone Kid]] ([[User talk:Killzone Kid|talk]]) 16:40, 2 April 2015 (CEST) | ||
no cluet how to respond but why did you undo my change to: | :no cluet how to respond but why did you undo my change to: | ||
https://community.bistudio.com/wiki/diag_tickTime | :https://community.bistudio.com/wiki/diag_tickTime | ||
it is not ms it is seconds :) | :it is not ms it is seconds :) | ||
:I explained it in the reason for undo [[User:Killzone Kid|Killzone Kid]] ([[User talk:Killzone Kid|talk]]) 22:15, 2 April 2015 (CEST) | ::I explained it in the reason for undo [[User:Killzone Kid|Killzone Kid]] ([[User talk:Killzone Kid|talk]]) 22:15, 2 April 2015 (CEST) | ||
::@InfiSTAR Key word in the description, '''Resolution'''. That doesnt mean 1.0 tick == to 1ms. It means 1 tick is accurate down to 1ms, which I disagree with, but thats to be disputed when I'm done preparing solid evidence. That means you can have results like 1.321s, which is wrong, it should be less than 1ms. You see here you are going in the other direction, which is more wrong then it is now. Arma has a funny way of how it stores and displays floats as a string. --[[User:Benargee|Benargee]] ([[User talk:Benargee|talk]]) 23:12, 2 April 2015 (CEST) |
Revision as of 22:12, 2 April 2015
posting exploits on biki
Please post them on Feedback Tracker and make ticket private Killzone Kid (talk) 16:40, 2 April 2015 (CEST)
- no cluet how to respond but why did you undo my change to:
- https://community.bistudio.com/wiki/diag_tickTime
- it is not ms it is seconds :)
- I explained it in the reason for undo Killzone Kid (talk) 22:15, 2 April 2015 (CEST)
- @InfiSTAR Key word in the description, Resolution. That doesnt mean 1.0 tick == to 1ms. It means 1 tick is accurate down to 1ms, which I disagree with, but thats to be disputed when I'm done preparing solid evidence. That means you can have results like 1.321s, which is wrong, it should be less than 1ms. You see here you are going in the other direction, which is more wrong then it is now. Arma has a funny way of how it stores and displays floats as a string. --Benargee (talk) 23:12, 2 April 2015 (CEST)