BlueAngel

Thanks for the clarification. From your explanation of the AIM-120 usage, it would appear it's not that "holy grail" missile people talk about. When pursuing a cold target (going away from me) I was only able to get a SHOOT prompt close to 12 nm. That's not a great mark. In order to replicate de pylon bug, pick the INNER pylon double AIM-120Cs and fire them in any order. I found they remain on the pylon, but just the visual model. Stores indicated zero available. As for the AIM-7, I'm gonna try the MH variant. Do I select the LOFT mode on the stores page? I also found that once you enter the AIM-120 visual mode, you can't exit it. Or I need to read the manual again.

In the last video made by Mr. Wagner, I noticed he had a flashing "SHOOT" prompt, somewhere in the vacinity of 20nm. He fired the missile and described when the missile went pitbull with the propper indications both on the HUD and Radar scope. I cannot, for the life of me, replicate this. Everytime I pick either the C or B versions, I only get a "SHOOT" prompt within 10nm or less, just like a AIM-7 or similar. I do get the TTI indication and the radar scope delta icon. Shouldn't I get a "SHOOT" prompt in the limits of the AIM-120 maximum range? If I fire the missile without the prompt it'll just fly to the interception point but never goes pitbull. ALSO - There's problem with the model shooting from a two missile pylon. The missile goes off, but a copy remains in the pylon (zero units in stores, though). As for the AIM-7, I'm having a hard time understanding the LOFT mode. It places the interception dot above the target and I fire it, but the missile loses thrust and just drop slowly missing the target. I need to know how you guys do it and if you're getting better results with these weapons. Thanks for your input.

I am using a cable connection but I changed my router door as it seems I was using a maintenance door or something. Packet loss is now almost mitigated. Still getting the infamous crashes and rubberband lag, though. I going to try the following: Move DCS to yet another Harddrive. This SSD also contains other games, dunno if DCS is touchy that it can't have any other programs around it. Perform a fresh install. This will be a pain, probably lasting a whole day just to download from EDs torrent system. We'll see. After these, I'm all out of ideas.

Been some time since I posted this. Still no specific help for my issue. Last time I contacted customer support, I talked with Andrey Fillin and Konstantin Kharin they told me to create a post on the forum. Here I am, no official help given. I wonder if only I am experiencing this. And if I am, why can't I get this solved.

Thanks for the e-hug. This is utterly frustrating, but even more frustrating is the silence coming from those who should be making the replies and sending out solutions. I love DCS. I have no reasons to deslike Eagle Dynamics. But I am very frustrated with all this. I did it a few times. They aren't an issue. I did notice that the host will always have some packet loss, about 10% over 10 queries, no biggie. I did this three times already. At first I would just delete the metashaders and fxo folders. Nothing seems to change to be honest. Like I said, I have no scripts or mods. Just a few skins.

This is supposed to be a support forum right? Where is the support?

Any other suggestions? c0ff? Anyone?

This is obviously subjective. Everyone has their vision of what DCS is. But I honestly think the vast majority believes DCS is all about multiplayer. Hundreds of different communities were created around the possibility of a bunch of guys flying together. Right now, this is close to impossible to a lot of people, not just me. It's even more unbelievable if you know that others have zero issues, and even more alarming is the lack of effective solutions to solve this. Before you guys send us AMRAAMs to the Hornet, before you deploy another campaign, before you send us an aerobatic plane, please, PLEASE fix your multiplayer Eagle Dynamics. But don't just send out fixes and patches. TEST THEM! I volunteer to join any testing session you may want to create and give you my variables.

I always had it, I just keep it out of lazyness to disconnect it. I will try nevertheless. I never had to mess with the pagefile. I will give it a go too, regardless. It's how desperate I am.

Hi. I am writing this out of pure despair. Me and my friends usually host a few games a week. Since update 4 or so, this weekly routine became impossible. We tried almost all "fixes" and suggestions. Port forwarding UDP/TCP 10308 on router. Run Process Lasso program to stabilize process performance. Created Norton Security Firewall rule also for UDP/TCP 10308. Shutdown every non necessary program. Updated all Nvidia and network drivers. If I host the server, the users will experience severe rubberband lag and eventually crash to the menu. If I join another user hosting, the situation is reversed, only it EXCLUSIVELY happens to me. Only I crash all the time, randomly and all other users report their game runs smoothly and without any issues. Before you ask, no we don't run complicated scripts. This happens with any type of mission, including just one on one missions. We all live near each other and our pings are minimum (30/40 tops). I can join most major servers like 104th or Aerobatic with little issue. It's only when I try to join one of our missions that this happens. I deleted the User/DCS folder, I ran Repair, I ran Clean, I even reinstalled DCS World. We also run the same verision of 2.5 Open Beta, almost all the same modulers. No mods whatsoever, just a few paintjobs. The only variant is that the usual host has the Steam version and I run the Standalone. Other than that, we're all similar. What am I doing wrong? Why was this thing working previously and now it doesn't? Why is this so selective? The log file of one of the latest crashes is attached. dcs.log.txt

Rubberband lag is not only back, it's actually worse. Server disconnections are just intolerable now. PLEASE FIX THIS! Multiplayer is erratic at best.

I got the same issue. And tried all "fixes". Game is unplayable in MP. Which is a big let down. I don't understand why this became such a big mess after a couple of updates. Fix some, lose some?

One step at a time, c0ff. We'll take this first one. Thanks.

Thanks c0ff Another quick question. Will this update just fix the rubberband or will it also fix the constant crashes and inability to join servers?

Any word this update will come this week?

Great news, c0ff. Please make it happen as soon as you guys can. I understand this week you are planning the merge with Stable, but please consider a minor hotfix for this specific game breaking issue.

It's now obvious there's no apparent solution for this. I tried it all, including running Process Lasso, turning on and off anti-virus, running tools for memory optimization. It's beyond me what I can do any further. Tried simple missions, complex, loads of planes, just a couple, I cannot enter a multiplayer server and remain there without severe rubberband lag and constant crashes to the menu.

And crashes to menu. Nothing on the log other than 2018-07-21 22:19:25.645 INFO NET: client has stopped It seems that rubberband just becomes more and more severe, then this happens. Seems to be much worse since update 7, tbh.

This situation returned to me in full strength. I think it was never this bad.

I just remapped my HOTAS. No big deal. It kept the Axis and both MFDs.

Known issue, should be patched in the next update or so.

I would say the data is just inverted. Remember the exaggerated negative angle of attack when deploying flaps on approach? Also looked like inverted data, as the expected result should be exactly the opposite. Maybe all it takes is turning negative numbers to positive or vice-versa.

I am now getting many situations where both the speed vector on the hud and on the radar scope are pointing in the wrong way or even going nuts all over the place. I say it's broken.

So, after all this reading, I'm not sure to take this as a bug or just a poorly implemented feature. I would just like to know how ED considers this be an actual flaw or not. It should only occur under specific circumstances, because flying in the Persian Golf at 5000ft and getting this warning when OAT is 30ºC sounds wrong to be honest. And it happens at random during the flight, by the way.

I too am getting a hard time locking targets. The speed vector seems way off too. I am steering away from sparrows right now. I can't be bothered with being killed head on because I can't lock anything within reasonable ranges.