InfiSTAR – User talk

From Bohemia Interactive Community
Jump to navigation Jump to search
No edit summary
m (Text replacement - "Killzone Kid" to "Killzone_Kid")
 
(3 intermediate revisions by 2 users not shown)
Line 1: Line 1:
== posting exploits on biki ==
== posting exploits on biki ==


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:
Line 8: Line 8:
: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 tickTime == 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)
::@InfiSTAR Key word in the description, '''Resolution'''. That doesnt mean 1.0 tickTime == to 1ms. It means 1 tick is accurate down to 1ms, <strike>which I disagree with, but thats to be disputed when I'm done preparing solid evidence.</strike> That means you can have results like 1.321s, <strike>which is wrong, it should be less than 1ms</strike>. You see here you are going in the other direction, <strike>which is more wrong then it is now. Arma has a funny way of how it stores and displays floats as a string.</strike> --[[User:Benargee|Benargee]] ([[User talk:Benargee|talk]]) 23:12, 2 April 2015 (CEST)

Latest revision as of 13:48, 12 March 2024

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 tickTime == 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)