Jump to content

Recommended Posts

Posted

Hi,

 

I seem to get constant disconnects from all 1.6 servers when in the Viggen. Seems to be happening to a lot of others also. Not sure if its a DCS World 1.6 bug or Viggen?

 

Anyone else getting this?

Posted

Hi, in MP when i picked Viggen, i got extreme ping around 400.

Happening it at all servers.

Also i can't choose other aircraft or spectator after i was in Viggen. I can only disconnect from the server.

 

FPS are fine, no dopping.

MB2 Czech DCS server. Youtube české Tutorialy youtube-logo.png
Discord MB2 1.Flight  | =UVP= Czech school of TOP GUN | DCS at Airshow - Aviaticka Pout

thumbnail_email.jpg
4K player | ASUS B760-F | i7 13700KF 5,4Ghz | MSI 4080 SUPRIME X | 64Gb G.Skill 6000MHz | 2TB M2.PCIe4 for DCS | Corsair RM1000e | (build 2023)

 

Posted (edited)

same here, getting disconnected shortly after spawning in the viggen - tested to see if it only happens in the viggen & already discussed in this thread - https://forums.eagle.ru/showthread.php?t=181640

the odd thing is that ( to mee) it seems to start totally randomly ( theres no specific action that triggers the disconnecting) , but once you got the disconnect-problem its like a blockade / a stable session cant be forced by trying again and again.

 

Yesterday i started my pc go to multiplayer and flew without problems, then took a break and returned an hour later ( same server/mission & slot ) and it disconnected me seconds after spawning. Then i tried 10 or more times to fly the viggen on the same server and always got disconnected after spawn, rebooted multiple times, tried different servers, always the same - two hours later started dcs tried again and still couldnt fly the viggen, watched a movie, then flew the viggen in singleplayer and just before shutting down the pc i though i might give it one more try, so tried again and could fly online for two hours. Today i tried three times and had no luck.

 

at first it seemed that flying singleplayer before entering multiplayer helped, but it was only coincidence as i tried to fly solo to end the "blockade" multiple times, further stuff that had no effect:

rebooting, repairing dcs, setting terrain preload to minimum ( seems to be a problem with it in 1.56) , making sure port 10308 tcp/upd is open, autoexe fix described in the thread linked above, removing mods ( i only had simple radio and reshade ), closing background programms & praying.

 

well its a beta module in a beta world...

Edited by tob.s
  • Recently Browsing   0 members

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