DaveTC

Hi, Just a quick update for this issue. I may have found a solution to this issue. I have not encountered any Protocol/stream errors since implementing this solution. Try this out and see if it works for you. The solution: In your network configuration you need to modify the settings of all your network adaptors. As you can see in the image below I have 2 network adaptors (Ethernet and Wifi). In the properties of both these adaptors you need to have only the following options active (i.e. checked) - see images below Client for MS networks File and printer sharing for MS networks IP4 protocol Uncheck (do NOT delete!) all other options, protocols and drivers. Click OK after making these changes to your adaptor properties, then ideally reboot your PC. Hopefully this will work for you. Kind regards

And just to be clear! I have not been banned by the server administrators! I can log back onto the server and play for a while (time varies) and then get disconnected once again with the protocol stream error. I have never previously encountered this. Only after the last patch and only on the newly installed Germany map! Kind regards,

Since the latest update with the Germany map, I have encountered "protocol / stream error" on numerous occaisions whilst on a multiplayer server. The connection to the multiplayer server is lost and I am back at the server list from where I have to reconnect to the MP server again (see attached log file). Can anyone enlighten me as to how I can prevent this from happening, or is this a DCS issue? Thanks. I have also opened a support ticket for this. Kind regards, dcs_prototcol_stream_error.log

That was indeed why I started this thread! Kind regards,

Hi, Thanks for the feedback from everyone! @BIGNEWY Here attached, as requested, is a track replay of a short flight. I have also attached a copy of the log file of this short flight. Here is also a link to a video made of this short flight: https://youtu.be/O6TMF8kphAs Kind regards, 4YA_MAR_PVE_V2.95[02_MAY_FEW]-20250324-154925.trk dcs.log

Hi, I am experiencing very erratic yaw behavior in the Apache since the last DCS update. Prior to this update the apache was much more stable in yaw movements in a hover. Is anyone else experiencing this? I don't have any mods installed except SRS & The Way. Kind regards,

Yes. This is a known issue which has unfortunately not been resolved yet in the latest update. See also this thread:

I head that it was also on other servers. I believe Contention server was one of those mentioned.

As I suspected. Probably will take some time to sort out, because despite all the uploaded trk and log files they are unable to replicate the issue. Don't know what further tests one can do to provide any clues to this problem.

I had it today on 4ya Marianas at a farp, so it's not always at an airbase. If I recall correctly, I was destroying a Shilka, a kub & manpads. This was just before installing todays patch. Will have to see if the patch solves the issue. Didn't see anything specific mentioned on this in the changelog though, so I fear that it has not officially been fixed yet. Kind regards

Just noticed that disconnecting and then immediately reconnecting to the same MP server mission seems to clear up the weird textures. I will have to test this further to see if they then come back.

I take it you saw it in the video.

I have never seen this issue previously, but since the latest update I am getting the weird textures regularly when flying on MP servers. Here in attachments is the DCS log file of the latest session on the 4ya Syria mission when I encountered this issue. I do have the track file but it is too large to upload here. I will therefore provide an URL link to this track file (see link below). URL link to DCS Track file I have also recorded a video of this session (see link below). Fast foward to timecode 44:33 to see the start of the display glitch. At timecode 47:50 you can see I descend through the layer of the texture glitch. Also take note of how the AGL altitude on the ihadss jump when descending through this layer. DCS Textures 2025 01 02 video Hope this is of some use. Kind regards, dcs.log

Sure! Here is the requested TRK file. Kind regards 4YA_MAR_PVE2_DS_V2.89[02_MAY_FEW]-20241227-090425.trk

Sorry to disappoint you, but setting fog to manual will not help. I believe this is how the 4ya missions are setup and George / Petrovich is not giving a list of targets on their missions! Kind regards

Well, I believe that 4ya run their missions with fog on manual like I did in my test (see my previous postings) and not on auto! BTW when I was testing, I did not run the mission from the ME. I went to the missions menu from the main screen (not the launcher), selected the mission and then pressed the launch as multi player server button. Kind regards

Thanks everyone for the feedback! Merry Christmas and I would also like to take this opportunity to wish you all the best wishes for 2025! Kind regards

Hi all, Merry X-mas to you all! Since the X-mas update the JTAG laser beam is no longer visible in the VID page of the MFD. I am wondering if this is intentional of is this another bug that appeared in this latest patch? In the previous version one could see the JTAG laser beam pointing to the target and one could point the apache in that direction before firing. Kind regards

My point is indeed that I am beginning to suspect that the issue has something to do with the dedicated MP server exe and not completely due to the fog settings. Basis of my assumption when running with a mission setup as a server within DCS itself George can find targets even with fog. Kind regards

Hi, I am experiencing the same issue in the Apache. I had this issue on all the MP servers I play on, mostly 4ya. I have also heard on other forums that Petrovich is having simular issues, though I can't verify it myself! Not at all convinced that it has to do with fog because I did a following test: I created and saved a small mission with fog on manual setting (see attached images). From missions menu I launched the mission as a multiplayer server (so that I could use dynamic spawns) Jumped into the apache with Lima hellfires Lifted off and scanned for targets (see attached images) and George presented me a list of friendlies in the target list. This also worked on my own saved mission with fog setting turned off! I am wondering if it has to do with an issue on the stand-alone MP servers, because I am starting a MP server form within DCS itself and not running a separate DCS MP server like the most MP servers do. Kind regards

Well I tried selecting the FCR as ACQ, but that is as far as I know not allowed. At least when I tried it did nothing. I see a ?FCR and therefore it cannot be selected. Possibly that this has not been implemented yet as everything is still WIP.

Big thank you for this work around! Can confirm that this works! As suggested just press RCTRL + Num0 twice and then press NumEnter and your saved view is loaded and restored. This indicates that the cockpit angles (& FOV) are being saved, but not loaded at the beginning of the flight. Thanks once again! Kind regards

Can confirm that this happens both in the Apache as well as in the Huey. Kind regards

Well, I have been able to get George to fire the lima hellfires while I was in the back seat. I did have to remain either in a stationary hover or at a very low speed (i.e. < 20kts) for accurate results. At higher speeds the missiles fired by George would miss the target. Don't know if this is a bug or intended. Kind regards,

Hi Flappie, First I would like to wish you a very happy new year. May 2023 be a year full joy, happiness, peace and good health for you and all who are dear to you! Thanks for your tips. 1) Clear DCS cache: A couple of days ago I deleted the fxo and metashaders2 folders from the saved games folder. I also ran a full DCS repair. On the NVIDIA shader cache, I will have to do some research on this. 2) Pagefile: Currently the windows 11 is set to manage the page file automatically. I have 32Gb RAM, so I will give this a try and set it manually as you suggested. 3) Graphics driver: Current version of the Graphics driver is Nvidia GeForce RTX 3090 v 527.56 which was installed around 8/12/2022. Install is performed by deinstalling the previous version and installing afresh of the new version. I install the latest version regularly. There is probably a new version coming in January so I will wait untill then for uninstall and reinstall of the GPU driver. 4) MemTest: Ran the MemTest today for approximately 2 hours with no errors (see also MemTest86-Report-20230101-124048.html). 5) Bios XMP profile: I have now disabled this in the BIOS 5) Update BIOS: I am going to hold off this step for the moment. Thanks once again for the feedback! Kind regards,