How does g_nRemoteControlSurfacesInterval work?
-
Hi,
I’m facing some multiplayer issues same as what many people have already reported in this forum.Therefore, I would like to tune some settings to seek best MP settings works for me, not only on bandwidth but also on
g_nRemoteControlSurfacesInterval
which is in falconbms.cfgAccording to the manual it says:
“Time in milliseconds between control surface updates over
multiplayer. Valid range 20-1000. Default is 200, 0 = disabled.”I have several questions here.
1. What is the word “control surface updates” used here means?
Is it Yaw/Pitch/Roll input, Maneuver output, aircraft position information, or all of them (or something other information) that clients and host share?2. If I disable this setting, what will happen?
I guess without any of those information It is not “Multiplayer” any more…is it?3. 200 milliseconds sounds so long interval for me if “control surface updates” means any of those information, only 5 frames per second are allowed to update another players maneuver.
Flying in Multiplayer, It seems my friends aircraft are responding more smoothly. -
Control surfaces are components of the airframe including TEF (Flaps, Flaperons) Ailerons, LEF (Leading Edge Flaps), the tail stadilator (elevator) and Rudder.
Their position is now sent to others. Including Head position.
Its in a manual somewhere.
-
Thanks.
Are they just graphical change interval? or is it also related to other players aircraft movements?
I searched for “Control surface” in Manuals but I could not get it… -
-
I’ve heard disabling the control surface movement won’t save you that much, during a test with 7 clients connected they just saved around 50 KB/s upload overall.
-
Thanks WaveyDave,
Then I don’t have to worry about their movement smoothness in close formation.Regards
Chihiro -
If it won’t save that much, It might not affect that much even I tweak the setting to 20 milliseconds, and able to get more smooth experience when observing my friend and predicting his next movement.
Anyway I will try tweaks in next flight:)