Pmove_fixed 1 explained
-
Pmove_Fixed 1
The effects and compatibility of fixed player movement
Better known as
pmove_fixed "1", this command exists to give every player the same advantage of the movement. It gives the same advantage as stable 125 FPS (frames per second) which is a slightly lower gravity. Example; If a player wants to jump on top of a box but is 1mm short on the jump, he should try enabling 125 FPS. If the FPS is unstable, then he needs to enable fixed player movement to get on top of the box. Unstability of FPS is very common sight with older computers which can be improved in many ways, however that is a whole different subject.Good to know
- 43, 76, 125, and 333 are the best FPS values for trickjumping
com_maxfps "value"limits the FPS to what player choosescg_drawfps "1"enables the FPS-calculator on the player HUD- 333 FPS gives the lowest possible gravity and the highest recoil
- 500 FPS gives the highest possible gravity
- 71 FPS gives the lowest recoil
- While using pmove you don't get any of the side effects related to
com_maxfps
Compatibility with other commands
Fixed player movement is not always advantageous, in fact, it can be considered as a disadvantage with usage of any weapon that has recoil. The spread is larger as well as the recoil of the weapons which causes the bullets to not hit where they are supposed to hit. This is one of the reasons why many if not all competition leagues use ETPro mod where the player moves can be fixed with one serverside command,
b_fixedphysics "1". With this the normal advantage is a little bit lower, but still effective. No matter what settings players have, they all jump as high as everyone else. This concludes few FPS values such as 500 FPS which gives highest gravity in the game.Example how fixed player movement affect weapons
Sniper (long range)
- pmove + 43 or lower fps = every bullet misses
- pmove + 90 or around fps = half of the bullets miss
- pmove + 125 or higher fps = every bullet hits
- no pmove + any fps = every bullet hits
-
Or we could just prevent the pk3 from applying custom shit to ET
-
Well I may have some ideas on how to solve your problems but it seems you are very new to linux...
I wouldn't recommend starting by compiling ETH if you don't have any knowledge about that OS, AFAIK eth-1.4-archit3ct-b3 does not compile on Ubuntu 64 bits (libghf which depends on libelf, libbfd and libopcodes will cause you headaches). That is why I started modifying it till it was so different that it eventually became eth-annihilation, which I later ported to Windows since nobody were playing ET on linux anymore, so I haven't touched Linux since 2017, I would have hard time helping you if I'm honest.
That said, eth-1.4-archit3ct-b3 is fairly old and outdated, you wouldn't be able to play on any mods nowadays except etpro and perhaps etpub. If you still really want to do that, look at sETH32nix, eth32nix salvation or resurrection which are the best hacks for raging ever made for ET. -
Well so first of all ETLegacy is a game and a mod, you don't need ETL to play on servers running Legacy mod. The benefits of ETL, on the top of my head, is that it works on much more devices than 2.60b, for example Mac OS X Catalina, Linux 64 bits, Raspberry Pi, Android and even PS Vita.
It also fixes the pain points of ET with built-in minimizer, auto desktop resolution, etkey generator.
Now, if you are using Windows 10, ETL will not give you any substantial benefits over 260b if you are using Nexus. I have benchmarked ETL 277 and ET 260b, and 260b gives me higher framerate, which matters if you are using Nexus. You can use ETWC to mininize ET, I added an etkey generator in Nexus, and it is very easy to use a custom resolution with cvars on 260b. Also ETL does not support ETPro / Punkbuster.
Nexus does not support ETL, but Legacy mod via 260b.
