Jump to content

Recommended Posts

Posted
Ok too many numbers bouncing around now. Is a bit confusing.

So what are the exact lines to enter for the Autoexe.config file now?

 

Is this something we have to create? If not, where is it? Did a search on .config and found nothing in my DCS folders.

Dogs of War Squadron

Call sign "HeadHunter" P-51D /Spitfire Jockey

Gigabyte EP45T-UD3LR /Q9650 3.6Ghz | 16GB DDR3 1600 RipJaws | EVGA GTX-1060 ACX3 FTW | ThrustMaster 16000m & G13 GamePad w/analog rudder stick | TurtleBeach EarForce PX22 | Track IR5 | Vizio 40" 4K TV monitor (stuck temporarily with an Acer 22" :( )

Posted
Is this something we have to create? If not, where is it? Did a search on .config and found nothing in my DCS folders.

Yes, you create it using notepad and save it as autoexec.cfg then put it in your saved games dcs open beta config folder.

Posted
So to host 50 players you would need 40Mbit? As in nearly half a 100mbit ethernet connection? I am not doubting you just astonished.

40Mbit at the end of 4 hours on a 2000+ unit mission with 45+ players was seen. And above. That's just the nature of the beast. There is an exponential type of component. 20 players will use much more than twice the network of 10 players.

I am going to be selfish asshole here but ask, I am in Asia and see ~225ms to your server. I would like to get back to it once the beta calms down a bit. I understand pings have to be for the benefit of all people but warping that I could see was caused much more by packet loss than simple high ping. If the limit could be set 'considerately' that would be appreciated. No matter what connection I pay for I won't get that ping below 225 due to physics.

Our ping limit was 330. It was until recently reduced to something lower on busy peak EU evening times.

 

Ping, packet loss, causes multiple side effects. Warping causes CPU spike as well as network throughput spiking. Not to mention being undesirable for gameplay. CPU starting to consume 1+core starts to increase the likelihood of an early DCS server crash. Also, the tools available to us (ingame ping calculations are often based off an average) An average that, sometimes is not really useful for us. Some guy jumping from 150ms to 400ms to 150ms all the time is a server killer... he can remain under the average ping limit, yet his jitter is wrecking the gaming experience and pushing throughput and CPU usage, and in turn server reliability towards a bad direction. So we have a cascade effect... Higher Warping effects due to the game engine = more throughput network wise = pushing other clients with weak connections (2Mbps) to also warp = CPU spiked and overloaded = warping...... etc....

 

Also: have you seen any reduction in b/w due to the beta? Or just due to fewer clients?

I can't comment on that just yet with great authority, as I don't have an Apples vs Apples comparison just yet. Will wait until more hotfixes and patches come out (so runtime gets longer), and then we can make a judgement on it (need a more stable server with higher numbers) I'm going to guess that the network usage, from what I have seen, going on preliminary observations is ballpark the same as 1.2.x, all things being equal.

[sIGPIC][/sIGPIC]

Posted
Has there been a consensus of opinion as to just what the best entries should be for the autoexec file for both server and client? I thought I had it right with

net.download_speed = 1310720

net.upload_speed = 1310720

but now I'm not so sure considering the various numbers I have seen. Coff, should the entries for everyone be exactly like this?

 

net.download_speed = 256*1024

net.upload_speed = 128*1024

 

So what is the answer? Which is it?

 

Verbatim

 

Cooler Master HAF XB EVO , ASUS P8Z77-V, i7-3770K @ 4.6GHz, Noctua AC, 32GB Corsair Vengeance Pro, EVGA 1080TI 11GB, 2 Samsung 840 Pro 540GB SSDs Raid 0, 1TB HDD, EVGA SuperNOVA 1300W PS, G930 Wireless SS Headset, TrackIR5/Wireless Proclip, TM Warthog, Saitek Pro Combat Pedals, 75" Samsung 4K QLED, HP Reverb G2, Win 10

Posted

anybody know, did this get fixed with today's hotfix 3, or do we still have to manually fix this as per instructions in various posts in this thread?

[sIGPIC][/sIGPIC]

 

Intel Core I7 4820K @4.3 GHz, Asus P9X79 motherboard, 16 GB RAM @ 933 MHz, NVidia GTX 1070 with 8 GB VRAM, Windows 10 Pro

Posted
anybody know, did this get fixed with today's hotfix 3, or do we still have to manually fix this as per instructions in various posts in this thread?

 

Still not adjustable in the settings. :ermm:

[sIGPIC][/sIGPIC]

Posted
Still not adjustable in the settings. :ermm:

 

but are the hardcoded numbers at least now the correct numbers, or do we still need to change those by hand?

[sIGPIC][/sIGPIC]

 

Intel Core I7 4820K @4.3 GHz, Asus P9X79 motherboard, 16 GB RAM @ 933 MHz, NVidia GTX 1070 with 8 GB VRAM, Windows 10 Pro

Posted
but are the hardcoded numbers at least now the correct numbers, or do we still need to change those by hand?

 

There are no "correct numbers" per se, at least not for DCS. You still gotta adjust them unless ED reworks the network code of DCS.

[sIGPIC][/sIGPIC]

  • 1 month later...
  • 5 weeks later...
Posted

So the old 1.2 network.cfg file settings were entered as "bits" per second but now the new 1.5 autoexec.cfg file settings need the values entered as "bytes" per second, is this correct?

  • 1 year later...
  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...