Arma Dedicated Server – ArmA: Armed Assault Talk
Jump to navigation
Jump to search
JerryHopper (talk | contribs) (→Netlog) |
Lou Montana (talk | contribs) m (Lou Montana moved page Talk:Arma Dedicated Server to Talk:ArmA: Armed Assault: Arma Dedicated Server: Name standard) |
||
| (7 intermediate revisions by 6 users not shown) | |||
| Line 1: | Line 1: | ||
==Netlog== | ==Netlog== | ||
| Line 8: | Line 5: | ||
and is it possible to request certain 'netlogoutput' wishes from bis? | and is it possible to request certain 'netlogoutput' wishes from bis? | ||
Maybe an option to make the netlog( or other universal log mechanism) available for the scripting module? | Maybe an option to make the netlog( or other universal log mechanism) available for the scripting module? as an universal logging mechanism would be a better solution than memory hooks at the server. | ||
--[[User:Jerryhopper|Jerryhopper]] 04:36, 7 March 2007 (CET) | --[[User:Jerryhopper|Jerryhopper]] 04:36, 7 March 2007 (CET) | ||
---- | |||
-privateslots= | |||
As yet unknown functionality. Possibly already working as of 1.05, but have not tested. | |||
Maybe for 'locking out' a certain number of positions in MP for a specific group of players? | |||
I dunno. | |||
-- [[User:Sy|Sy]] 17:50, Wed, April 4th 2007 (NZST) | |||
== Disclaimer? == | |||
Is there a specific reason why there's still a disclaimer on top of the page? The dedicated server looks pretty much released to me ;-) -- [[User:Manny|Manny]] 17:03, 3 May 2007 (CEST) | |||
---- | |||
I've got a sneaking suspicion that... | |||
MaxSizeNonguaranteed=<limit>; | |||
Maximum size of non-guaranteed packet in bytes (without headers). | |||
Non-guaranteed messages are used for repetitive updates like soldier or | |||
vehicle position. Increasing this value may improve bandwidth requirement, | |||
but it may increase lag. | |||
Default: 256 | |||
should be... | |||
MaxSizeNonguaranteed=<limit>; | |||
Maximum size of non-guaranteed packet in bytes (without headers). | |||
Non-guaranteed messages are used for repetitive updates like soldier or | |||
vehicle position. '''Decreasing''' this value may improve bandwidth requirement, | |||
but it may increase lag. | |||
Default: 256 | |||
Anyone else think so? --[[User:Sy|Sy]] 13:18, 12 June 2007 (CEST) | |||
: Definitely not. You will save bandwidth by increasing this parameters, but you'll raise the latency between sent updates, resulting in a bit more lag. See http://www.flashpoint1985.com/cgi-bin/ikonboard311/ikonboard.cgi?act=ST;f=68;t=63479 , extensive explanation on second page --[[User:Whisper|Whisper]] 14:49, 13 July 2007 (CEST) | |||
---- | |||
Latest revision as of 17:07, 26 July 2024
Netlog
is there any explanation for the netlog output? (besides the obvious)
and is it possible to request certain 'netlogoutput' wishes from bis?
Maybe an option to make the netlog( or other universal log mechanism) available for the scripting module? as an universal logging mechanism would be a better solution than memory hooks at the server. --Jerryhopper 04:36, 7 March 2007 (CET)
-privateslots=
As yet unknown functionality. Possibly already working as of 1.05, but have not tested. Maybe for 'locking out' a certain number of positions in MP for a specific group of players? I dunno. -- Sy 17:50, Wed, April 4th 2007 (NZST)
Disclaimer?
Is there a specific reason why there's still a disclaimer on top of the page? The dedicated server looks pretty much released to me ;-) -- Manny 17:03, 3 May 2007 (CEST)
I've got a sneaking suspicion that...
MaxSizeNonguaranteed=<limit>; Maximum size of non-guaranteed packet in bytes (without headers). Non-guaranteed messages are used for repetitive updates like soldier or vehicle position. Increasing this value may improve bandwidth requirement, but it may increase lag. Default: 256
should be...
MaxSizeNonguaranteed=<limit>; Maximum size of non-guaranteed packet in bytes (without headers). Non-guaranteed messages are used for repetitive updates like soldier or vehicle position. Decreasing this value may improve bandwidth requirement, but it may increase lag. Default: 256
Anyone else think so? --Sy 13:18, 12 June 2007 (CEST)
- Definitely not. You will save bandwidth by increasing this parameters, but you'll raise the latency between sent updates, resulting in a bit more lag. See http://www.flashpoint1985.com/cgi-bin/ikonboard311/ikonboard.cgi?act=ST;f=68;t=63479 , extensive explanation on second page --Whisper 14:49, 13 July 2007 (CEST)