You could probably replicate what shounic did here with Cheat Engine or similar to set the value of gpGlobals->tickcount over about a billion, so that gpGlobals->curtime (that keeps the current time in seconds as a 32-bit float) gets close to the magical 16777215.0 offset. Due to the nature of floating-point numbers, even long before 6 months anomalies start to occur. For example, the face-melting level 1 sentries begin after about 3 months (since 0.2 is getting rounded down to 0 instead of 0.5) and the flamethrowers might stop shooting particles after as little as 24.3 days.
Garry's Mod with being pretty intense with lua and stuff i suppose(?), is even worse in that servers start to feel "off" around the 6 hour mark, which is why servers that stay on one map, tend to restart every day or so. The developer wiki for Garry's Mod even recommends this.
I did, and weapons look kind of retarded when you use them on wrong class. Shounic still probably t-poses while using batsaber but first person animations looks dope
@@GeneraliskYT you really can't, the way levels are designed (bsp) prevents you from really being able to build levels that far out, and IIRC you cannot move past the grid
Floats like to function incorrectly at large values. No matter if it's position or time. (It's just that position in source is kinda limited by the map size, which is itself limited to (130k units)^3)
2:22 I've noticed something similar when playing on x10 servers. Flamethrowers don't work there unless you use them point-blank. I guess flamethrowers' range gets extremely reduced and thus can't reach enemy players or something, but it must be even more severe in this case
The cause is different. In a times 10 server, all stats, including negative stats, both hidden and shown, are multiplied by ten, which means the range reduction on a weapon will become ridiculous. Here, it's due to the flame's lifespan being ridiculously short due to the server time being messed up.
@@thefunpolice2645 multiple stats are affected by x10, some being arbitrary and unrelated to any visible weapon stats, which is why the airblast is hilariously fast on the stock flamethrower, or why the backburner's airblast sends you into orbit (there is no visible stat on the backburner which increases airblast strength, this is just what was chosen by the original x10 mod to compensate for a single airblast use).
It's because ever since jungle inferno valve moved the flamethrower's stats from hardcoded cvar variables to weapon attributes and the server owners haven't updated the attributes file to accommodate for this.
2:04 we not gonna talk about how all of the rockets shot in a straight line? Either Shounic got incredible luck or it also breaks the beggars' deviation stat
Hmm, those laggy animations remind me of the weird skeleton/sentry animation effects. Apparently it is caused by different interp settings? I haven't tested it but if you change your interp settings to full default, those laggy animated skeletons become full smooth animations.
I noticed it is nothing special anymore to see glitched sentry build/upgrade animations. I mean, instead of animating between a previous level and the new level, it is already in the new level but motionless. Then after the animation is supposed to end it just starts working. When that glitch happens with level 3 sentries, they also have some smeared metal-textured polygons connecting the right minigun and right side of base.
this happens in gmod too, you can't spawn certain props after the server being up for a day and it gets unstable, it requires a restart every 12 hours or so good vid my man
This is what happens when you go outside the effective range of floating point numbers. In exchange for precision for smaller numbers, large gaps between big numbers result. So the longer the timer runs, the more inaccurate the timer becomes. I'm surprised the global timer's data type is not an integer.
@@arstulex it is source engine. I would not be surprised if the "decision" for using a float there happened a long long time ago, before considering multiplayer, let a lone online servers, let alone windows being able to not crash within a day. Such "decisions" do not have to happen consciously (you just write up mock up code, clean it up, review, commit to head/develop) and even when you find them, you have to prove that they are relevant... then you have to prove that and int solves the problem, write a mock up, clean it up, identify edge cases, fix bugs, ... or you just shrug and consider reloading the map after 24h to be reasonable, as even a crunch season is interrupted by involuntary falling a sleep.
@@sarowie based off the tf2 leak, valve doesnt exactly do the whole "clean it up, identify edge cases, fix bugs" part. interestingly, that decision could have been made while developing quake, and seeing as the timer is a core component it would be early on, so late 94/early 95. i doubt it though, as id was pretty good with optimizations and efficiency, especially while making one of the first full 3d games
@@arstulex the global time is a result of the tick counter * tick interval, predicted across commands. Trying to add 0.03 to an already large time results in the same issue. Using solely the tickcount you won't be able to perform smooth actions, such as smoothing an animation to make it end at a specified time. You'd have to use clients time, which can drift, and won't be in sync for when you want to use a timer shared between both realms.
@@sarowie how does it feel to roleplay as a developer? This is not the pipeline at all for valve, they leak their debug symbols every 4 seconds, let developers jump projects, push shit updates that have to get hotfixed (case in point, dota disruptor w cooldown, dota sell items on illusion, dota sell any item for infinite gold). Delusional if you think their testing is that rigorous.
Before the pyro update, the length of your flamethrower could be extended with high latency. My guess is that to fix the issue they tied the duration of flame particles to the global timer, and they way they did it might have some weird interactions with "removing" the timer. Since the dragons fury fires a normal projectile rather than fire particles, that is probably why it still works, although the projectiles themselves have a maximum lifespan, so idk.
Pretty sure the engineer's buildings build at the same speed. The animations are buggy, but the sound plays at the same speed as normal and the building is finished until the sound finishes playing. Although, I suppose that if those moments of lag are actually the server just calculating things and not buggy rendering, then they are stupid fast relative to the game's simulation speed.
Yeah my guess is the buildings are building relative to the closest second. So if the timer is at 15 seconds, and the sentry gun takes 5.5 seconds to build, it will be finished at the 21 second mark (6 seconds). For example. The only thing we are losing here is rounding.
there's a timer that the game uses to keep track of everything, and synchronize everyone's games' at home together. if you shoot a gun, tf2 uses this timer to mark when you can fire a weapon again (for example). marking these events are done relative to the timer, ie the current timer is at 100, so the game writes down - "you can fire again when the timer hits 105". computers can't infinitely hold numbers, so when this timer becomes too big, the game breaks in some ways.
*I'm likely incorrect. See edit* Timers are rarely floats. It takes about two months for a 32-bit integer to roll over if incremented once a millisecond. 32-bit floats aren't accurate enough to measure milliseconds in the time span of several months. Floats are a really bad fit for this sort of application. *Edit: I commented before watching the whole video. They might really use floats. The strange behavior is one reason floats generally aren't used as timers. A 64-bit float would improve performance but this sure seems like a bad application for floating point numbers.*
@@ddegn the way I understand it is: floats are for physics, movement, rendering, and the loop, and doubles are used for timers and other times when accuracy is important.
@@ddegn Not for improved performance, for accuracy. Yea it is a bad application and shouldn't really be done. Although some really popular game engines like Unity or Unreal will use its own time and pass it to you as a float if you wish to use it; for whatever reason. So that mistake probably won't go away anytime soon if the built in timer is used :P. In Unity's case they use it internally as a double then convert it to a float. So the inaccuracy will remain an slight inaccuracy of the decimals. I'm sure in most games their own clock would be used instead that is a double.
This also makes Spread less and less functional, you can get multiple bullets in a row with the same exact spread. This also happens way quicker because spread bases on uptime * 1000.0f
2:45 why is the teleporter entrance building by square numbers? I would guess that it has to do with the build progress increasing by consecutive odd numbers, but idk.
What I’m wondering is what it would look like if you tried to use the shortstop’s shove ability in a situation like this, would you just become an unstoppable wall of shove that pushes away anyone who gets close?
