Feels Ranger Man

I accomplished this by adding a 'host_maxfps' c_var to host.c: patch: --- host.c 2021-03-06 11:24:17.499268500 -0600 +++ host_new.c 2021-03-06 11:35:20.810182400 -0600 @@ -76,7 +76,7 @@ cvar_t noexit = {"noexit", "0", CVAR_NOTIFY|CVAR_SERVERINFO}; cvar_t developer = {"developer", "0", CVAR_ARCHIVE}; - +cvar_t host_maxfps = { "host_maxfps", "72", CVAR_ARCHIVE }; cvar_t skill = {"skill", "1", CVAR_NONE}; // 0 - 3 cvar_t coop = {"coop", "0", CVAR_NONE}; // 0 or 1 cvar_t deathmatch = {"deathmatch", "0",...

I accomplished this by adding a 'host_maxfps' c_var to host.c: patch: --- host.c 2021-03-06 11:24:17.499268500 -0600 +++ host_new.c 2021-03-06 11:30:00.994616200 -0600 @@ -76,7 +76,7 @@ cvar_t noexit = {"noexit", "0", CVAR_NOTIFY|CVAR_SERVERINFO}; cvar_t developer = {"developer", "0", CVAR_ARCHIVE}; - +cvar_t host_maxfps = "{host_maxfps", "72", CVAR_ARCHIVE); cvar_t skill = {"skill", "1", CVAR_NONE}; // 0 - 3 cvar_t coop = {"coop", "0", CVAR_NONE}; // 0 or 1 cvar_t deathmatch = {"deathmatch", "0",...

I accomplished this by adding a 'host_maxfps' c_var to host.c: patch: --- host.c 2021-03-06 11:24:17.499268500 -0600 +++ host_new.c 2021-03-06 11:25:47.243391700 -0600 @@ -76,7 +76,7 @@ cvar_t noexit = {"noexit", "0", CVAR_NOTIFY|CVAR_SERVERINFO}; cvar_t developer = {"developer", "0", CVAR_ARCHIVE}; - +cvar_t host_maxfps = "{host_maxfps", "72", CVAR_ARCHIVE); cvar_t skill = {"skill", "1", CVAR_NONE}; // 0 - 3 cvar_t coop = {"coop", "0", CVAR_NONE}; // 0 or 1 cvar_t deathmatch = {"deathmatch", "0",...

I accomplished this by adding a 'host_maxfps' c_var to host.c: Add: static cvar_t host_maxfps = { "host_maxfps", "72", CVAR_ARCHIVE }; Cvar_RegisterVariable (&host_maxfps); Change line 672 in host.c to: if (!cls.timedemo && realtime - oldrealtime < 1.0/host_maxfps.value) Change line 760 in host.c to: while (temp_host_frametime > (1.0/host_maxfps.value)) patch: host.c with above changes made: --- host.c 2021-03-06 11:24:17.499268500 -0600 +++ host_new.c 2021-03-06 11:25:47.243391700 -0600 @@ -76,7...

Awesome. Thank you for taking the time to fix this and add it into the actual release. If you have time, please take a look a this feature request solution I provided so it can perhaps make it into the next release: https://sourceforge.net/p/uhexen2/feature-requests/37/#ed39 I don't see any issues with allowing this to be configurable and the default remains 72. I noticed no weird physic irregularities when playing briefly above 72FPS, it seems Hexen II decoupled the physics from the rendering as...

Awesome. Thank you for taking the time to fix this and add it into the actual release. If you have time, please take a look a this feature request solution I provided: https://sourceforge.net/p/uhexen2/feature-requests/37/#ed39 I don't see any issues with allowing this to be configurable and the default remains 72. I noticed no weird physic irregularities when playing briefly above 72FPS, it seems Hexen II decoupled the physics from the rendering as well. Regardless, this solution allows the normal...

Yes this is why I didn't submit a commit. I merely found the issue that was happening and agree it should be done properly, I'm not very familiar with the code base to do so nor have a lot of free time. Personally I prefer nearest on all objects in the game so it works for my own personal needs.

I agree but others will argue that the bilinear look is original or better and that's fine. Just give the user the choice, that's my opinion.