Replies: 1 comment 2 replies
-
|
Hey @warsang, The logs about rejected inputs and invalid rollback ranges are both caused by the same thing - the host receives inputs that are too old. This can be either because of latency, or wrong time sync. Could you please check both the latency and predicted time? For latency, you can print I do wonder how did you end up setting the Tickrate Mismatch Action to 10, since it's an enum 😄 |
Beta Was this translation helpful? Give feedback.
-
I have no idea... I have been playing with these settings for a while now but I haven't touched the addon files for this project at the very least :p Below is a snippet of my logs with the remote_rtt and tick for one server and two clients; I'm running everything locally right now. (There's multiple uuids for the server because I instantiate the logger before having peerids; one uuid is assigned for each player node represented on the server)
|
Beta Was this translation helpful? Give feedback.
-
|
The following settings seem to have improved it significantly bringing down the remote_rtt (when running locally) to 0.6 < x < 0.9 These settings are mostly from trial and error so I'm not sure if they could cause significant overhead for my game or other underlying issues/trade-offs 
|
Beta Was this translation helpful? Give feedback.
-
Hey!
Can someone provide a bit of additional guidance on tweaking Netfox settings for my game?
I keep getting this spammed in my output with only one or two clients when using the default plugin settings:
[WRN][@6089][#1][_][netfox::RollbackSynchronizer] Received input for 6024, rejecting because older than 64 framesThen it usually is followed by one or two rollbacks:
[WRN][@6097][#1][B@6088|6088>6089][netfox::NetworkRollback] Trying to run rollback for ticks 6025 to 6097, past the history limit of 64I attached performance monitors when using default settings for server and a client:
My rollback synchronizer is syncing the different inputs I use (I can probably stop syncing movement since I no longer use it); My game is 3D with a character moving according to where the mouse is right clicking (and follows the cursor if the right click is held). My set-up may be a bit comlex which could explain the lag? I use Jolt as a physics engine and procedurally generate a Terrain3D map and place different gatherable nodes like trees and stone that are synced wih normal MultiplayerSynchronizer and RPCs (properties only synced onchange). All this stuff is generated server side and synced to the client upon connection to set up their map and node positions+states and then we only update these whenever there's a change.
I use netfox input prediction in my Input.gd file for the player mouse position.
To try and remove the log entries above, I have been playing with settings. The below configuration seems to remove the log entries but now my player's movement is kind of choppy . The character will be running slow then speed up all of a sudden and run super fast ( a bit similar to someone speed hacking with cheat-engine). I did go through https://foxssake.github.io/netfox/latest/netfox/guides/network-time/#tickrate-matching but I could really do with a bit more guidance on how to tweak different netfox settings. Seems like what I shared removes the spam log entries but I would like to try and better understand how I can reduce the choppiness and "speedhack" effect. I'm not building a MOBA so I'm fine with a bit of lag within reasonable limits.
Happy providing any extra info if needed.
Thanks in advance!
Beta Was this translation helpful? Give feedback.
All reactions