ArtOfStuttering

Can the included User Manual be updated to include info on this Dynamic Cargo button? Currently, the section on Warehouses and their Resource Manager shows screenshots without this feature.

This seemed to be it! I had it turned on, the others not so much. Thanks for the workaround and in the future the fix.

Pilot dcs.log WSO desync spam antenna controller 2.9.5.55918.logWSO dcs.log desync spam antenna controller 2.9.5.55918.log Little later than promised but here you go. Different pilot this time around, different mission but same server (although this is server-agnostic). Touching the radio knobs is merely to show that it's only the antenna stick (that I know of, so far). Pilot POV: WSO Pov (touching the antenna stick is around 4:30):

Unfortunately, it still seems to be there. I'll try to get some video of both perspectives tomorrow if desired.

In multicrew, whenever the Pilot or WSO enables or disables the in-cockpit body, it also does so for the other player/seat. If the Pilot likes flying with the body on, it forces the WSO to also fly with a body and vice versa. Ideally for me, it shouldn't be synced and be only locally so the pilot and WSO can have their body active or not independently. Edit: Added Known Issue to title.

Tried this and it didn't help. As soon as I touch the antenna stick it causes desyncs. Of note is that as a WSO I don't have the pilot stick and/or throttle bound. Unbinding Pitch & Roll (pilot stick) in the F-4 Pilot section didn't change anything either. Sorry to hear that you're having the same/similar issues! At the same time, kinda glad I'm not the only one. Seeing your other post, it seems you're also having performance issues. I'm having a solid 50+ fps no matter what (with a theoretical 200+ FPS as my GPU is a known bottleneck). My gameplay is hampered because effectively I can't use anything that interacts with the antenna stick. I can ride along and interact with everything else just fine.

Absolutely. Attached are both my (WSO) and Pilot logs from the Cold Start video above. I've since isolated the issue to me touching the antenna stick and interacting with any system through moving with it, whether it's the radar screen, Pave Spike pod, or Maverick slewing. As soon as I move the stick it desyncs but things like IFF interrogation doesn't. This is fully reproducible for me alone, cold start and hot start, in the WSO seat while others have no problem. Below is a recording of my PoV on a hot start flight where I showcase the errors with the radar screen, pave spike, and mav. This is on a different server than the Cold Start video I posted earlier. Also attached is both my Pilot and WSO dcs log file of this flight. Of note is that I can replicate this independently of the multiplayer pilot, I just happened to use the same pilot twice. Apparently it didn't record Discord voice on my Pilot's side but highlights are at 1:50 for hot start radar, 11:50 for the Pave Spike, and 14:20 for the Mav (which I am unable to do anything with at that point it seems like). dcs-pilot-log-HotStart.log dcs-pilot-log-Cold Start.log dcs-WSO-log-Cold Start.log dcs-F4-WSO-HotStart.log

Cold Start WSO PoV: Cold Start Pilot PoV:

Whenever I join the F-4 WSO seat in the back of anyone, the pilot has a good chance on getting the full sync error spam in their top right messages and my controls keep 'lagging' or reverting, effectively making it impossible for me to do anything in the backseat. I've reproduced the full sync error spam by basically interacting with anything in the back seat whether it be a hot or cold plane, especially by moving the antenna stick. It does this in 4 separate people their jets on command when I'm in the back, in different servers, on different maps, and different missions (including empty ones). I can ride along just fine as long as I don't touch anything and I can still pilot for other people to sit in my back. From my point of view when interacting with the radar/antenna stick it forcibly resets it, while in the radar screen it often keeps resetting or just keeps going for a second well after I've let go of my antenna stick. I've since deleted all my mods ((A-4 or C-130) and UH-60L mod (unarmed)) other than SRS, ran a full repair, and it still does it. Both in ST and MT, although I run MT by default. DxDiag included. Will try to get video of both my side and pilot side this weekend. DxDiag.txt

Thanks for taking the time to check on your own machine and see if--oh, wait. Not that it changes anything. Cold-War-Caucasus-v108_DME1-20230426-162022.trk

Could this at least be acknowledged in some way, shape, or form? Incidentally, similar degraded performance behavior (although to a lesser extent) has been seen for me in Enigma's Cold War server when on the F10 map view, even with or without having any mods installed (other than SRS), showcasing that it's not limited to ST, MT, or mods and reproducible on multiple (distinct) MP servers. If required, I can provide track files, recordings, etc. of this once more.

Version 2.8.4.38947 GrayFlag Persian Gulf server Not sure when this was introduced but in multiplayer missions, both 'ST' and 'MT', having the F10 menu open with lots of shapes that are drawn plummets the framerate to unplayable levels. Pressing Escape to open the menu makes the framerate skyrocket, while the F10 map continues to update, seemingly only the drawn shapes being hidden. Occassionally, there seems to be some kind of garbage disposal happening in the background as the FPS shoots up again while still showing everything, before it grinds back to a halt. This has been reproduced by several players on both GrayFlag servers. I'm aware that the server uses two mods (C-130 Anubis mod and UH-60L mod), however, a quick test in the Mission Editor with the track-file renamed as a .miz caused it to be sub 5 FPS when opening, and as shown in the video below, >180 FPS can be achieved with everything but the shapes stuff. dcslog.log Grayflag Persian Gulf A-20230413-194759.trk DxDiag.txt DxDiag.txt dcslog.log Grayflag Persian Gulf A-20230413-194759.trk

As much as this is a SRS thing, the underlying bug is that the Hornet doesn't turn off the MIDS component after shutdown like it does the Datalink part.

Using SRS, after an autostart and setting up my MIDS channel and turning it on, when doing an autostop it doesn't turn off. Not using SRS, doing another autostart after the Hornet retains its settings of MIDS.

Addendum: Unfortunately, this seems nearly impossible to troubleshoot in SP, as on impact both HE as well as MPP exploded every time. One thing I did notice with the Harrier is that doing a hot start either in the air, LHA-1 Carrier, or airfield, the APKWS are designated 20S in the STRS page. Doing a cold start (and then auto starting it with Lwin Home) at any position, it seems to be 20R.