Questions about multiplayer

[half-lifeer]

Hello, you just did a really good job, and i have a few requests.

1. Could you create an antilag fix for your classic patch? (entitiesmp.dll & gamemp.dll)
   I mean the screenstuttering in fragmatch, when ping is less than 54 ms.
   Ofc we have a version of it, one with autoscreenshot and without, but its unstable and brokes demos.
   If its will be yours solution, thats could improve multiplayer expirience.

2. Could you create a timestamp for events in dedicated server?
   For kills, server shutdowns and etc that is important.
   It must be a real helpful thing for server administration.

[DreamyCecil]

1. There's already a solution against stuttering at lower latency but it's only available in the custom mod, i.e. not vanilla or other mods with own code. The command is gam_bDisableLocalPrediction and the respective option is also available in-game under "Custom mod settings".

2. If you mean the timestamps next to every line in the game log, I've already implemented them for the upcoming version.

[half-lifeer]

1. You mean i'll write ingame console - /gam_bdisablelocalpredictions=1 ?
   Just tried, its works. Thanks. Why its dont turned on by default? It causes some issues if its set "1"?

Updated 2 hours later: screenshaking was stopped, but players are shaking, Any solutions to fix that?

2. About timestamp - you mean SeriousSam_Custom.log or dedicated.log or both?

[DreamyCecil]

1. Local prediction is configured to "Auto" by default (gam_bDisableLocalPrediction = -1), which is disabled only when the latency goes too low, otherwise enabled to eliminate input lag at higher latency. It doesn't affect entities of remote players.
   If you want to disable all prediction, you can just switch the network connection setting to "LAN gaming", or disable prediction in the custom Classics Patch preset (cli_bCustomPrediction = 0), if using that one (needs to be selected again after changing its values).
   There are also just regular prediction settings in the game in OPTIONS -> ADVANCED OPTIONS -> Advanced prediction options

2. Timestamps universally appear in any log file and console output.

[half-lifeer]

I have already an experience with LAN gaming network preset, it's causing an inputlag then. Mouse axis comes to hard to play with.
That's why I am asking about that making that lag fix, similar to https://www.gamezone24.net/forums/downloads.php?do=file&id=324

[DreamyCecil]

The only difference between the LAN gaming preset and the rest is the disabled prediction setting, which is what my command essentially does too but only for the local player entity instead of everything that can be predicted. It should not have any input lag that's worse than playing locally when latency is below 50 ms.

I cannot access the link because the browser asks me to sign into the site somehow.

[half-lifeer]

Here the files.

I tried to found out the functions with Codex, maybe its tell to you something:

?GetLerpedPlacement@CPlayer@@UBE?AVCPlacement3D@@XZ
?csm_bAntiLowPingLag@@3JA
?csm_bAutoScreenShot@@3JA
?csm_bTakeScreenshot@@3JA

So i am preparing video right now to show you what i am talking about. Trying to collect more information to show you, needs more tests.

45750-Ping54Fix+AutoScreenshot.zip

[half-lifeer]

Hi, so i ve tried a lot of combinations with commands on the client side, here's a most common variant:

Network setting - Classic Patch Preset.
Prediction = 1
BufferActions = 0 or 1 (doesnt matter)
Max/MinBps = 1000000

Advanced prediction options:
/cli_bpredictremoteplayers = 1
/cli_bpredictlocalplayers = 1
Range = 100m

Classic Patch command:
/gam_bdisablelocalpredictions = -1 (by default)

And after that ping comes to 10-50ms, but when i playing, players are shaking.
I ve started to dig deeper, and found a command - /cli_iMaxPredictionSteps = 10 (by game default).
I set /cli_iMaxPredictionSteps = 0 > no screenshakes, but mouse axis have an inputlag (delay when i aiming)
I set back /cli_iMaxPredictionSteps = 10 > players shaking, screen shaking, no mouse axis inputlag.

So here's the video of playing on the server, when i switch from /cli_iMaxPredictionSteps = 0 to /cli_iMaxPredictionSteps = 10 but marcos keys while running.

https://youtu.be/Yli3hcVLDDE

Could you create something to fix that inputlag (mouse delay) and exclude shakes like i am doing by set this command /cli_iMaxPredictionSteps = 0?

[half-lifeer]

1. I noticed one thing.

When using vanilla DLL libraries (custom mode = 0), ping 20–30, prediction of local players ON → screen shakes. (Turning local prediction OFF → no shakes.)

When using classic patch DLL libraries (custom mode = 1), ping 20–30, prediction of local players OFF → screen shakes. (Turning local prediction ON → no shakes.)

So it's based on gam_bDisableLocalPrediction = -1, am I right?

2. Have you checked the antilag DLLs? They were created by Politician. Also, Zdzichu has a solution by Politician in source version — maybe it helps.

3. And one last question: could you improve the netcode for a more stable version, without global changes, for vanilla compatibility? Or would that cause desynchronizations between vanilla and patch clients on the server?

[DreamyCecil]

gam_bDisableLocalPrediction setting only works with custom mod libraries, so it won't affect anything in the vanilla game. It's supposed to dynamically mimic cli_bPrediction toggle specifically for players. I'm not sure why you're experiencing the opposite effect with it. Also, the code for it was shared with me a while ago, most likely from that mod. I used it as a reference.

I can't see any proper way of improving the netcode, not that I even know what to do with it even with full engine sources. It's just a very old game with a very old system for networking, there's not much I can do at all, especially on a scale of a simple patch atop the regular engine.

[half-lifeer]

Hi, i asked an author about this antilag fix dlls, and he shared the source code: https://codeshare.io/GbWnbV
Could you check it?

[DreamyCecil]

Yes, I already have a similar algorithm implemented in the patch based on this exact piece of code. This function is used for multiple entities to control local prediction, not just player's.

Instead of checking for local player entities, I just check whether the generic entity is a prediction of the original and adjust it according to that. In theory, it should work identically, and I haven't gotten complaints about this feature from others who had tried using it. If it doesn't, then I don't know, needs more testing of some kind.