Jump to content

Server update timeout


SilentWarrior
 Share

Recommended Posts

With the new Viggen update, i am having constantly "Server update timeout" and being kicked.

 

I have tried several servers, same thing.

 

Kick reason:

 

"Connection timed out.

 

Server update timeout"

 

What could this be?

 

Yesterday when the Viggen was released I played for like 2 hours with no problems. Then went to Training and went through all the training missions, now i cant re-join MP servers.

 

 

Edit: I tested in multiplayer with Mi8 and I dont get kicked. Switched back to the Viggen and I get kicked within 20 seconds with this message.

Edit2: From teamspeak, it seems its a common problem. There are at least 5 other people with this problem i have spoken to.


Edited by SilentWarrior

Proud owner of DCS: FC3, A-10C Warthog, F-14A/B Tomcat, F-5E Tiger, Mig21bis Fishbed, Mirage 2000C, Nevada Test Site, Normandy, Ka-50 Black Shark, Mi-8MTV2 Magnificent Eight, UH-1H Huey, SA342 Gazelle, Bf 109 K-4 Kurfurst, FW 190 D-9 Dora, Spitfire LF Mk. IX, P-51D Mustang Combined Arms, Hawk T.1A, L-39 Albatros, NS 430 Nav System, F-86F Sabre, MiG-15bis, AV-8B Night Attack V/STOL, F/A-18C Hornet, Yak-52 and the mighty AJS-37 Viggen! :music_whistling:

Link to comment
Share on other sites

We've been having this issue quite a bit with the guys I've been doing missions with. We also get this on the AO server. I think it's definitely a Viggen issue, but as to what is causing it, we are not sure. Two guys tried taking out their autoexec but hasn't seemed to help.

[sIGPIC][/sIGPIC]On A Wing & A Prayer - In Memory of my Father who was my instructor, pilot, and co-pilot

 

NZXT H440 Blue | Windows 10 Pro | Intel i7-4790k | Gigabyte G1 Gaming GTX 970 OC | G.Skill Ripjaws X 16GB | WD Caviar Blue 1TB | Samsung 840 EVO 120GB | ASRock Z97 Extreme 6 | Corsair H100i | Corsair HX750i | Saitek X-55 Rhino | Saitek Pro Flight Pedals | Track IR 5 w/ Proclip

Link to comment
Share on other sites

Almost every server i join with the Viggen Iget in like 10-30 secs, really wanting to fly this bird online but all seems hopeless at this point, very frustrating. Have done a repair have tried the auto exec thing from another thread, all short of uninstalling an re-installing.

Screen_170130_163628.thumb.jpg.245fe68a1393d5d292b44a61c27396ff.jpg

Link to comment
Share on other sites

Had the same issue two nights ago. First flight on Aerobatics Online was fine for some 15 minutes, then got the same kick, and after that never lasted longer than 30 seconds before getting disconnected again. Didn't try any other aircraft besides the Viggen, though.

Link to comment
Share on other sites

I'm having the same problem in the Viggen. Yesterday it worked after some time and a couple of reconnects, today it's not and the connection times out in under a minute.

 

EDIT: I was now able to connect to the Aerobatics Online Public Mission server. Only 5 people connected, compared to 20+ on the other ones I tried.


Edited by Gate-5
Link to comment
Share on other sites

Whatever it is, it's very intermittent.

 

On Aerobatics Online I've gotten booted off before my canopy closes at least a dozen times now, but I've also had 3 or 4 sessions that lasted 30-120 minutes with no issues. I didn't notice any apparent correlation between timing out and server uptime/client count but I could be wrong.

DCS modules are built up to a spec, not down to a schedule.

 

In order to utilize a system to your advantage, you must know how it works.

Link to comment
Share on other sites

Repeated Server Time Out on several Servers here too with 20+ pilots in various aircrafts including 2 Viggens. This occured just after T/O in the Viggen. Rejoined and everyone else still there as if nothing happened to them or the server.

 

I hosted a Viggen mission myself for several hours with one other pilot with no issues.

 

Flew another mission with 6 pilots in A10Cs, F5s and one Viggen for a couple of hours with no issues.

 

I know, this tells us nothing really. Serve timeouts have been a rare occurrence for me historically.

 

Have not had this occur in Stable or NTTR.


Edited by MegOhm_SD

 

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

Link to comment
Share on other sites

Same problem here. I've had this every time I flew online with the Viggen (on the 104th). Haven't tried any other aircraft since then. It worked fine before the Viggen came.

 

I'll give the fix jakebwallace mentioned a trie.

Intel i7-12700K @ 8x5GHz+4x3.8GHz + 32 GB DDR5 RAM + Nvidia Geforce RTX 2080 (8 GB VRAM) + M.2 SSD + Windows 10 64Bit

 

DCS Panavia Tornado (IDS) really needs to be a thing!

 

Tornado3 small.jpg

Link to comment
Share on other sites

yeah, I'm also getting this problem, on multiple servers, and that fix didn't work.

My youtube channel Remember: the fun is in the fight, not the kill, so say NO! to the AIM-120.

System specs:ROG Maximus XI Hero, Intel I9 9900K, 32GB 3200MHz ram, EVGA 1080ti FTW3, Samsung 970 EVO 1TB NVME, 27" Samsung SA350 1080p, 27" BenQ GW2765HT 1440p, ASUS ROG PG278Q 1440p G-SYNC

Controls: Saitekt rudder pedals,Virpil MongoosT50 throttle, warBRD base, CM2 stick, TrackIR 5+pro clip, WMR VR headset.

[sIGPIC][/sIGPIC]

Link to comment
Share on other sites

The autoconfig-fix solved the problem for me.

Intel i7-12700K @ 8x5GHz+4x3.8GHz + 32 GB DDR5 RAM + Nvidia Geforce RTX 2080 (8 GB VRAM) + M.2 SSD + Windows 10 64Bit

 

DCS Panavia Tornado (IDS) really needs to be a thing!

 

Tornado3 small.jpg

Link to comment
Share on other sites

 Share

  • Recently Browsing   0 members

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