Dogman

Thanks for that however I have been advised that the Protocol Error issue is affecting many other players and that it has been acknowledged by the Devs as a DCS issue that will hopefully be fixed in the next update. I along with many others are looking forward to that.

Yes I did misunderstand. Will see what the pros and cons are for the enabling of the new IPv6 and see where I go from there thanks

Thanks for the reply silverdevil but I checked and my system only runs IPv4 so the issue must be getting caused by something else. I can't believe that there is so little information about this extremely annoying problem .. I must just be lucky

Hi Guys Recently I have had increased DCS game crashes and after the game crashes I get box that comes up saying Protocol Error. I have searched that in this forum but did not see reports of the same problem with other users. Have played DCS for many years and have had the occasional crash before where a crash report is generated however this Protocol Error only started in the last few months and is becoming more frequent and I have had no major change to hardware or software during that time. Unfortunately a formal crash report is not created but I did find the attached files in the Logs folder which may have some clues in them. Greatly appreciate any suggestions on what the root cause of this new issue is and what actions I can take to resolve it. Many thanks debrief.log dcs.log

Hey Phantom as Homer would say DOH!!! So now I feel really stupid... thanks for pointing out the obvious.

Hi Guys Recently I discovered a strange issue with the nose wheel steering on my FA/18. When starting cold I am unable to engage NWS even though the bind I have used. It works when activated in the controls screen I can even see the Paddle behind he joy stick move in the cockpit when I use the assigned bind but I get no NWS display in the HUD. When I enter a single player mission and start the simulation in a started plane the NWS displays in the HUD and works normally, however as soon as I use the bind the NWS display is gone and I no longer have NWS function. If I take off and then return to land the NWS is displayed in the HUD and works when the plane has landed but again as soon as I use the bind it stops working again. I have searched this issue on line and in this forum and can't find any other user having this specific problem. Would certainly appreciate any thoughts on what I can do to resolve this issue which affectively stops me from using the module in MP servers. Many thanks

So I have had similar issues to the ones posted in this thread. In my case 13 modules were affected including some jets and prop planes no helicopter modules were affected. In all cases where two thrust binds were available it was always the left thrust bind that had the conflict issue. In a modules where only one thrust bind was available it was the only bind that had the conflict. Thankfully what was looking like a big problem was easily resolved by clearing all conflicted binds noting that the red exclamation badge still showed against the affected bind and a new bind reassignment would not be accepted. I then closed DCS and restarted and found to my great relief that all the red exclamation marks had now gone and I was able to reassign all thrust binds correctly verifying that they worked in game. Bullet dodged... PHEW!!!!

Hi Guys For some time now I have noticed that when loading profiles onto different modules from saved input config files a red exclamation badge that I believe means that multiple inputs have been assigned to that command shows up on random commands. The screen shot attached shows what the issue looks like with the Weapons Fire command that after clearing a duplicate input command in Throttle Category only the one Joystick is input is now being applied but the badge persisting and the bind does not work. There is no rhyme or reason as to what commands will be affected in the different modules it is random. I would greatly appreciate some support solving this very annoying problem. I have done some research on the issue but can't find any satisfactory resolution apart from reloading the module and assigning each command individually which is a prospect that I can hardly imagine considering the number of modules that I have. Very much look forward to hearing from anyone who may have had this problem and has determined root cause and solution. Thanks in advance...

Thanks Max first thing I did was to check the joystick settings in the settings app and there is no issue with the joystick inputs. Also other FS programs are not affected so it is certainly DCS. I feel a full reinstallation is on the cards

Hi Guys I have just recently been having a worsening issue with intermittent input problems from my controllers to DCS modules. I have a TM Warthog stick and throttle that I have been using without issue for years. A couple of days ago I noticed that some key binds that included a modifier were being commanded without the modifier being used. Then things got worse when other input commands with and without modifiers started to work sporadically as well. The problem started during a session and has now persisted for a number of days. As an interim work around I then started to use corresponding keyboard commands but then discovered that they too were not working consistently. Note that the issue happens with multiple modules and is random happening anytime during the session but appears to becoming worse over time. Would greatly appreciate hearing from anyone else that may have experienced similar problems and what I might try to resolve the issue. Thanks in advance

I have got a problem mapping the Rudder axis in the pilot position on the AH-64. The Rudder action has a red exclamation icon next to it and won't allow the rudder input to be recognised. I have no problem setting up the rudder for the CP/G position. The screen shot below shows the problem to which I would appreciate any feedback. Thanks in advance

Hi Guys I tried tanking with the Hornet in MP for the first time since updating to 2.7 and was quickly aware that the degree of difficulty has increased significantly performing what has been for me a very simple and straight forward process. I have tried with all tanker types and have had the same problem which is some strange kind of pressure wave/turbulence when approaching the basket. I have tried from all angles to see if that made any difference but each time the same thing happens, when I get close to connecting the plane suddenly drops by the nose and then has to be firmly recovered which then ruins the approach line and requires me to try again. I watched several other players also trying to plug and they also seemed to be having similar problems to what I experienced. I am very interested to know if others have noticed the same issue because if its now this hard to refuel in the Bug there is absolutely no hope for other air frames like the F-16 and Harrier. Hopefully this is some kind of bug that will be fixed in due course.

Nice to know it's just not me @admiki I also discovered that some modules have the issue and some don't.. hopefully this issue has been noted by ED and they are aware.

Hi Guys When I am in MP the load out screen has not been updated to the new larger model version that is available in SP not sure if this is how it is supposed to be. Also whilst I can select different skins I am unable to select hardpoint loadout options, I can select the hard point but there is no drop down pick list. This issue occurs in different servers and I have had not had the problem in previous versions of DCS. Any suggestions about how to resolve this frustrating problem would be most appreciated. Thanks

Thanks Megalax.. so much to learn..