prop tool bug

  • User_58758
    23rd Oct 2012 Member 0 Permalink

    i noticed a bug in the prop tool when heating wifis

    i clicked on a wifi with the prop tool and set temp and wrote 3000 but it gave me 2726 and not just this number, any number i set on the wifi with the prop, it subtractes the number!

  • sandstorm
    23rd Oct 2012 Member 0 Permalink

    it's on kelvin, so i believe that absolute zero is zero, room temp is around 320, and so on. look it up.

  • User_58758
    23rd Oct 2012 Member 0 Permalink

    ok thx

  • boxmein
    23rd Oct 2012 Former Staff 0 Permalink
    @sandstorm (View Post)
    273.15
    @User_58758 (View Post)
    The game *shows* you values in Celsius, but secretly uses values in Kelvin.
    To convert from Kelvin to the appropriate size in Celsius,
    (to get for example 100° C) you have to do
    100° C + 273.15 = 373.15 K
    Edited once by jacob1. Last: 2nd May 2019
  • User_58758
    23rd Oct 2012 Member 0 Permalink

    well thats annoying and useless

  • jacob1
    23rd Oct 2012 Developer 0 Permalink
    @User_58758 (View Post)
    I was actually thinking of adding something so you don't need to figure this out, and I already did it for the console (old ! commands only). You can do !set temp all 100C, and that will be in Celsius. Maybe I can even make Celsius the default, and you would need to use 100K for Kelvin, i'm not sure if I will do that though.
    Edited once by jacob1. Last: 2nd May 2019
  • Box-Poorsoft
    23rd Oct 2012 Banned 0 Permalink
    This post is hidden because the user is banned
  • jacob1
    23rd Oct 2012 Developer 0 Permalink
    @Box-Poorsoft (View Post)
    that actually doesn't even work. It just gets reset the next frame by the temp. I have a set wifi v2 script for setting wifi temps really easily.
  • Box-Poorsoft
    23rd Oct 2012 Banned 0 Permalink
    This post is hidden because the user is banned
  • boxmein
    23rd Oct 2012 Former Staff 0 Permalink
    @User_58758 (View Post)
    it's not useless, it allows developers to not use negative values in the game code. This allows them to use unsigned ints they use floating point values anyway (fixed @jacob1) for the memory used, which somehow is more useful.

    In Code C vs K:
    pros -
    - unsigned values can be used
    - no need for negative values in code
    cons -
    - more advanced people have to learn adding
    - a bit of a nuisance if you use prop / console
    The cons can just be overcome with simple math, so it's not much a problem.
    Edited once by jacob1. Last: 2nd May 2019