elcoo

Still no luck. Things I tried after hearing it's working for you again: - Updated GPU-Drivers - Completely uninstalled DCS, backed up and removed the configuration files in "my saved games" - Freshly reinstalled DCS, without any modules (apart from the SU-25t and TF-51) Even in this absolutely fresh and standard configuration, I am unable to join larger servers. My system specs are as follows: - CPU: AMD Ryzen 9 5900X - GPU: AMD RX6800 (16 GB VRAM) - RAM: 64 GB I had no problems joining larger srevers prior to the new spawn system update.

Hmm, I also tested after the update but the issue persisted. I wonder if it might be a configuration issue, because the servers I'm testing on are quite populated so I guess it works for a good amount of players. I did a repair of course but i didn't reset my configuration files yet. Edit: I see a lot of posts about a similar issue connecting it to the supercarrier module. I don't have that module though, so that's not the cause.

Same issue here. I'm unable to join most servers without the game completely freezing up. I think it may have to do with the number of available slots, as it still seems to work for servers with lower maximum allowed players. Patchlog says Known issue: Performance drop in some populated multiplayer servers when the “Select Role” window is displayed. But in my book this is not a performance drop - the process just eats up all available memory and freezes until killed by the task manager. I'd like a moderator or developer at least to acknowledge that there is a more major issue than just a performance drop and that they are looking into it.

I could only find one "video" of an alleged Shilka engaging a Su-25, and it's obviously a fake: https://www.youtube.com/watch?v=3ZNhLNOGfyA

Did you set the afterburner cutoff switch to off by any chance?

Any news or maybe a workaround for this issue? We tried out multicrew today after a little break from the Gazelle and couldn't get the TV Slewing to work correctly as well.

Kreisch hat völlig recht, ohne GPU bringt dir der PC für DCS herzlich wenig. Wenn der Rechner nicht viel teurer werden soll würde ich eher Empfehlen eine günstigere CPU (z.B. i5 8600K) zu verwenden und stattdessen mehr Geld in die Grafikkarte zu investieren. Unter einer Nvidia 1070 oder einer Vega 56 (Dank Cryptomining derzeit hoffnungslos überteuert) solltest du für VR nicht einsteigen. An deiner Stelle würde ich derzeit noch etwas abwarten bis Nvidia hoffentlich bald seine neuen GPUs released - momentan kauft man sich nämlich 2 Jahre alte Karten zum selben Preis wie damals. Edit: War zu langsam :P

Hello, first of all, I'm very excited that we got the multicrew update today, great job! :) I tried it with a buddy and he had a very hard time aiming. The picture on his viviane screen was shaking very hard. He sent me this video of it: [ame] [/ame] He's aiming using a Saitek x52, if that makes a difference... Just wanted to know if anyone else is experiencing this or if it's a known issue.

But the changes are not in todays update log for 1.5 :(

Eine Möglichkeit wäre es Bereiche der Achsen in Tasten umzuwandeln. Das geht z.B. mit GlovePie (http://www.heise.de/download/product/glovepie-40061) Dann hast du zwar keine echte analoge Eingabemöglichkeit, aber 2-3 Stufen sind damit bestimmt machbar.

It says in the changelog, that multicrew and mistral missiles have been added. :smilewink:

I think this is the same issue as described here: http://forums.eagle.ru/showthread.php?t=165198 And here by me: http://forums.eagle.ru/showthread.php?t=172067 I can confirm it affects the sliders more than the joystick itself.

This is great news! Your progress on this module has been much faster than I would have expected. I'm looking forward to some fun co-op flying!

Yes, that's exactly what we encountered! I searched the forums for that iisue but it was hard to find, as I didn't know what keywords to search for. BTW, I was now able to reproduce the bug on my system as well, by twisting the joystick to its limits very fast.

Hi, a friend of mine has a weird problem using any joystick with DCS. The joystick axes get stuck at an offcenter position when he quickly recenters the joystick. When he moves the joystick again after that, it will reposition correctly - so it doesn't get decalibrated. Still this is a big issue, because it often leads to a stuck aileron or elevator. We tried it with different controllers (thrustmaster flight hotas x and Xbox 360 gamepad) - it's the same for both controllers on every axis. The axis position shows correctly in the windows gamecontroller settings and other games, apart from DCS, so we are certain it is not a hardware issue. There were no other controllers plugged in, that could interfere with the controls. We only used one controller at a time for testing. The update rate on the hotas flight controller seemed to be much slower than with the xbox controller. This seemed to increase the effect drastically. It looks like DCS stops to update the axis position as soon as the joystick reaches the center position and shows the last known position instead. We also tried resetting the input settings, by deleting the input configuration folder. We used DCS version 1.5.4.55584 on a Windows 10 64 bit system. I was not able to reproduce the bug on my Computer using a X52 Pro flight stick. Anyone with an idea what could cause this and how we could fix it? :huh: Thanks in advance!