starred/LinuxGSM

Fork 0

mirror of https://github.com/GameServerManagers/LinuxGSM.git synced 2026-04-25 06:05:57 +03:00

[GH-ISSUE #4557] [Bug]: Rust: server lag spikes during newly implemented ping estimates #2836

New issue

Closed

opened 2026-02-27 03:05:43 +03:00 by kerem · 13 comments

kerem commented

2026-02-27 03:05:43 +03:00

Owner

Originally created by @karenmcd on GitHub (Apr 11, 2024).
Original GitHub issue: https://github.com/GameServerManagers/LinuxGSM/issues/4557

User story

I'd like that the new ping variables be added to the server configuration so that we can enter values that work for us.

Game

RUST

Linux distro

Debian 12

Command

command: start

Further information

There's a newly implemented function to adjust the intervals and if even your RUST server executes pings to publish an estimated latency for the client in the server selection list. As I understand it, without being able to adjust this, the default settings execute 20x5 ping commands at once, and it waits for all of the results to return causing a huge lag spike in game for all clients making it near unplayable every five minutes.

Relevant log output

https://commits.facepunch.com/r/rust_reboot/main/ping_estimate_cleanup

There's information here about how to add/fix it? I'm unsure how, what or where i'd put this information without my changes being overwritten by lgsm.

Steps to reproduce

No response

Originally created by @karenmcd on GitHub (Apr 11, 2024). Original GitHub issue: https://github.com/GameServerManagers/LinuxGSM/issues/4557 ### User story I'd like that the new ping variables be added to the server configuration so that we can enter values that work for us. ### Game RUST ### Linux distro Debian 12 ### Command command: start ### Further information There's a newly implemented function to adjust the intervals and if even your RUST server executes pings to publish an estimated latency for the client in the server selection list. As I understand it, without being able to adjust this, the default settings execute 20x5 ping commands at once, and it waits for all of the results to return causing a huge lag spike in game for all clients making it near unplayable every five minutes. ### Relevant log output https://commits.facepunch.com/r/rust_reboot/main/ping_estimate_cleanup There's information here about how to add/fix it? I'm unsure how, what or where i'd put this information without my changes being overwritten by lgsm. ### Steps to reproduce _No response_

kerem

2026-02-27 03:05:43 +03:00

closed this issue
added the
type: bug

distro: Debian

game: Rust

command: start
labels

kerem commented

2026-02-27 03:05:44 +03:00

Author

Owner

@scalbox commented on GitHub (Apr 13, 2024):

Hi
fix for this problem
https://digitalmarketplay.com/product/rust-ping-estimation-lag-stalling-fix-rust-update-04-04-2024/

@scalbox commented on GitHub (Apr 13, 2024): Hi fix for this problem https://digitalmarketplay.com/product/rust-ping-estimation-lag-stalling-fix-rust-update-04-04-2024/

kerem commented

2026-02-27 03:05:44 +03:00

Author

Owner

@dgibbs64 commented on GitHub (Apr 13, 2024):

Its not clear exactly what you want me to do from a LinuxGSM perspective

@dgibbs64 commented on GitHub (Apr 13, 2024): Its not clear exactly what you want me to do from a LinuxGSM perspective

kerem commented

2026-02-27 03:05:44 +03:00

Author

Owner

@scalbox commented on GitHub (Apr 13, 2024):

is a plugin that disables the new rust feature that causes high ping

@scalbox commented on GitHub (Apr 13, 2024): is a plugin that disables the new rust feature that causes high ping

kerem commented

2026-02-27 03:05:44 +03:00

Author

Owner

@dgibbs64 commented on GitHub (Apr 13, 2024):

Thats fine. But what do I need to do for LinuxGSM? If I don't need to make any changes for LinuxGSM then I can just close this

@dgibbs64 commented on GitHub (Apr 13, 2024): Thats fine. But what do I need to do for LinuxGSM? If I don't need to make any changes for LinuxGSM then I can just close this

kerem commented

2026-02-27 03:05:44 +03:00

Author

Owner

@scalbox commented on GitHub (Apr 14, 2024):

Yes, it is not necessary to change LinuxGSM.

@scalbox commented on GitHub (Apr 14, 2024): Yes, it is not necessary to change LinuxGSM.

kerem commented

2026-02-27 03:05:44 +03:00

Author

Owner

@karenmcd commented on GitHub (Apr 14, 2024):

I spoke to their support to get better understanding of what to do. they said that the fix will not be implemented until the next time the server gets updated. the LGSM configuration may need to be updated to include new options in the startup script to allow changes.

the plugin they are describing that "fixes" it only applies if you're running oxide plugins. my server is vanilla without plugins so I can't use that fix they are referring to.

honestly we won't know what to do until they move the patch to add parameters to the main branch, and even then it might not be a lgsm issue, it might end up just being a server.cfg and not a lgsm-config setting? I guess I don't know/understand yet

Sent from my LineageOS device with K-9 Mail. Please excuse my brevity.

@karenmcd commented on GitHub (Apr 14, 2024): I spoke to their support to get better understanding of what to do. they said that the fix will not be implemented until the next time the server gets updated. the LGSM configuration may need to be updated to include new options in the startup script to allow changes. the plugin they are describing that "fixes" it only applies if you're running oxide plugins. my server is vanilla without plugins so I can't use that fix they are referring to. honestly we won't know what to do until they move the patch to add parameters to the main branch, and even then it might not be a lgsm issue, it might end up just being a server.cfg and not a lgsm-config setting? I guess I don't know/understand yet -- Sent from my LineageOS device with K-9 Mail. Please excuse my brevity.

kerem commented

2026-02-27 03:05:44 +03:00

Author

Owner

@karenmcd commented on GitHub (Apr 14, 2024):

this link to digital market play isn't helpful if you're not running plugins. Linux servers without oxide (non-modded community servers) cannot run this and are stuck still with extreme lag spikes every 5 minutes until they deploy the fix to main branch. I don't want to have to manage mods and risk taking my server out of the community servers and moved to the modded servers.

Sent from my LineageOS device with K-9 Mail. Please excuse my brevity.

On April 13, 2024 9:07:42 p.m. UTC, Andrea Angelozzi @.***> wrote:

Hi
fix for this problem
https://digitalmarketplay.com/product/rust-ping-estimation-lag-stalling-fix-rust-update-04-04-2024/

@karenmcd commented on GitHub (Apr 14, 2024): this link to digital market play isn't helpful if you're not running plugins. Linux servers without oxide (non-modded community servers) cannot run this and are stuck still with extreme lag spikes every 5 minutes until they deploy the fix to main branch. I don't want to have to manage mods and risk taking my server out of the community servers and moved to the modded servers. -- Sent from my LineageOS device with K-9 Mail. Please excuse my brevity. On April 13, 2024 9:07:42 p.m. UTC, Andrea Angelozzi ***@***.***> wrote: >Hi >fix for this problem >https://digitalmarketplay.com/product/rust-ping-estimation-lag-stalling-fix-rust-update-04-04-2024/ >

kerem commented

2026-02-27 03:05:44 +03:00

Author

Owner

@scalbox commented on GitHub (Apr 14, 2024):

If not user plugin
https://commits.facepunch.com/r/rust_reboot/main/ping_estimate_cleanup

Add ping_samples to control how many times to ping each endpoint (default 5)

@scalbox commented on GitHub (Apr 14, 2024): If not user plugin https://commits.facepunch.com/r/rust_reboot/main/ping_estimate_cleanup **Add `ping_samples` to control how many times to ping each endpoint (default 5)**

kerem commented

2026-02-27 03:05:44 +03:00

Author

Owner

@scalbox commented on GitHub (Apr 14, 2024):

But you will have to wait for the release of the patch, if you use vanilla servers, if you are not official, then you can use Oxide itself and add this plugin. Otherwise I can make you the same plugin but as a Harmony dll, which does not require Oxide

@scalbox commented on GitHub (Apr 14, 2024): But you will have to wait for the release of the patch, if you use vanilla servers, if you are not official, then you can use Oxide itself and add this plugin. Otherwise I can make you the same plugin but as a Harmony dll, which does not require Oxide

kerem commented

2026-02-27 03:05:44 +03:00

Author

Owner

@scalbox commented on GitHub (Apr 14, 2024):

Vanilla and community servers can run Oxide. just respect the rust guidelines. They use oxide for admin and anti cheat plugins

@scalbox commented on GitHub (Apr 14, 2024): Vanilla and community servers can run Oxide. just respect the rust guidelines. They use oxide for admin and anti cheat plugins

kerem commented

2026-02-27 03:05:44 +03:00

Author

Owner

@scalbox commented on GitHub (Apr 14, 2024):

Guidelines for community servers using plugins / mods
https://support.facepunchstudios.com/hc/en-us/articles/360009062817-Guidelines-for-community-servers-using-plugins-mods

@scalbox commented on GitHub (Apr 14, 2024): **Guidelines for community servers using plugins / mods** https://support.facepunchstudios.com/hc/en-us/articles/360009062817-Guidelines-for-community-servers-using-plugins-mods

kerem commented

2026-02-27 03:05:44 +03:00

Author

Owner

@scalbox commented on GitHub (May 4, 2024):

For those who don't want to use my plugin https://digitalmarketplay.com/product/rust-ping-estimation-lag-stalling-fix-rust-update-04-04-2024/ because they don't have umox/carbon, you can set this server property:
ping.ping_estimation false

@scalbox commented on GitHub (May 4, 2024): For those who don't want to use my plugin [https://digitalmarketplay.com/product/rust-ping-estimation-lag-stalling-fix-rust-update-04-04-2024/](url) because they don't have umox/carbon, you can set this server property: **ping.ping_estimation false**

kerem commented

2026-02-27 03:05:44 +03:00

Author

Owner

@github-actions[bot] commented on GitHub (Aug 4, 2025):

This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.

@github-actions[bot] commented on GitHub (Aug 4, 2025): This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.

kerem referenced this issue

2026-02-27 03:55:52 +03:00

[PR #2836] [MERGED] Release v20.2.0 #3805