Attempting to reach 280 speed requires the value to be set to 319 on a 66 tickrate server, for example. This causes a lot of inconsistency for PACs between servers that alter movement, as well as trying to set speed for a specific, intended value. 4y if you find the pac3 folder it has text files just put them onto a thumbdrive 2 level 1 IJustMovedIn 4y There's a video somewhere on Youtube where a guy transfers all his PAC3 models into another computer via dropbox or something, but I'm sure you can do it with a USB as well. I had this issue before on a previous server, though never reported it since I could never figure out the cause.
From a 66 tickrate server where the problems usually aren't too noticeable without the command, to a 30 tickrate server where the default value for gravity (-600) is suddenly low gravity. You can check your current movement speed by using the console command "cl_showpos 1" and checking the current velocity value at the top right corner.įurthermore, I wasn't going to report this until I found out that if the hosted server's tickrate is lowered, player movement's inaccuracy in it's default and modified number values becomes even more inaccurate, and sluggish. I would provide an example PAC, but honestly all you have to do is open up the editor, create a player movement part, and immediately test speed values. You can check your current movement speed by using the console command 'clshowpos 1' and checking the current velocity value at the top right corner. For example, you ask for 200 run speed and you end up with: 176. Should have backed up your PAC3 folder in Data in Garrys Mod. I would provide an example PAC, but honestly all you have to do is open up the editor, create a player movement part, and immediately test speed values. Long story short, you don't get what you ask for when setting a number value for speed.
0 kommentar(er)
