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.

Win 10 21H2, 2.7.10.19402 OB, AV-8B Harrier, MPP M282 APKWS in a MP server. I'm not sure whether this is the correct bug section but hey, better to report than not to at all. During a MP mission I engaged multiple infantry duos on separate occassions, consisting of the SA-18 Igla and the associated support/commander guy, with the APKWS MPP (M282 warhead) variant flying the Harrier. What happens is that I lased either one of the two, or split the difference on the ground between them. At most they had 5 meters between them in every engagement. On rocket/missile impact, it would kill the commander but left the guy holding the launcher unscathed, with no visual explosion at all occurring. I'm aware that the M282 is not an HE warhead but a shaped charge, but if you look at this APKWS M282 shot, it's pretty clear a less than ~5 m separation should not be a problem. Sure, an argument could be made that because sometimes it physically hit the infantryman, it doesn't detonate or something due to delayed fusing. However, impacting the ground would create a cone of shrapnel, not to mention the explosive charge itself, that would have a very high probability of lethally wounding. Unfortunately, due to this happening in a ~2 to 3 h mission and exceeding the 5MB file size I cannot upload the server track, although I do have it. What I can show, is it happening multiple times in a recording. Currently the video is still processing to HD res but here are Engagement #1, Engagement #2, and Engagement #3. There are more engagements that did get explosions as viewed in Engagement #4, and after that I'd be willing to find but I hope I made my point. I stutter, so feel free to mute. I've confirmed in the server Tacview that all shots shown were M282.

Thanks everyone for participating!

Shadow, please pick only one.

Art First choice: MiG-28 Second choice: MiG-21bis

Dear HB, In the 2nd mission overall, the RIO cold start mission, there's a possible bug: If you start the mission, it tells you to call up the ground power. After you do that, you're supposed to press 2 and switch to the RIO seat. However, if you don't switch and press spacebar you'll be booted out of the Tomcat and bodies will fill the cockpit. Not something I've been able to turn off so far. p.s. wooooooho, it's here! p.p.s. You know that part where you make a system as idiot proof as possible? I'm an absolute idiot. I will break everything. For fun. Art

Art - F/A-18C

Art - F5/MiG-21

The state of the manual and some feedback Manual typos: I've been reading through the manual as I just bought the module and finding some errors here and there. Not exactly a bug but hey, it might help :) Page 7: Top down view states the width at the landing skids it states 2.750 meters whereas right below it in the Front view it says 2.040 meters for the exact same measurement. All in all, I'd really recommend the devs to have another go at the manual and include things such as basic helicopter operation, checklists, and also review everything that's written so far. I've found several typos (such as 'witch' instead of 'which') and numerous occasions of questionable grammar. Referring to a training mission in the manual is unacceptable for subjects such as weapon deployment. The manual is supposed to be a reference which is accessible at any time (from a second screen or secondary PC/Laptop). In the current state of the manual, if I haven't flown the SA342 in a while and I find myself in a situation where in my group I'm flying the SA342 I have no way of easily getting myself up and running. The exact same goes for start up, which is even MORE important. This alone ensures the SA342 will NOT be a widely used helicopter as it CAN NOT be started up without either some luck OR excellent knowledge of the aircraft. And quite frankly, I do not possess either as I can not invest hours and hours of my free time in every single module. Perhaps more importantly, this sets a precedent of which I'm unhappy with the quality of (some important parts of) the developers' module. This makes me doubt whether I'll buy another module of them again if the SA342('s manual) will remain in its current state. And that saddens me greatly, seeing a possibly excellent module being deteriorated by simple things such as useless manuals. This changed from a Bug report to more of a Feedback post. I hope you can appreciate it and will address some of the things I stated as they're incredibly important for the module's success! Closing, a module that can't be flown because of a lack of knowledge is a useless module, not because it is bad but because it is inaccessible to those who can not invest their lives into DCS. And there are many of us that can't. Cheers Art

Thank you everyone for the responses, but this doesn't fix the bug I posted. On the flaps, I was already aware there's a work around however since this is made by Eagle Dynamics, this isn't a "third party dev". I'd appreciate a dev's assurance it'll be fixed, especially since they changed the topic and removed "[bug]" in the topic. It was there to get the Dev's attention. Mods, please, at least reply you've read it and forwarded it. Small communications such as those are important to your users and doesn't take long! It only increases the appreciation we have. Changing topics and not responding does the exact opposite usually. Again, thanks everyone for the flaps suggestions but I do not accept messing around the lua myself as the solution. Kind Regards, ArtOfStuttering

Dear Eagle Dynamics, First of all, I'm sorry if this is in the wrong place. I tried finding a Bug Tracker but couldn't find it anywhere. I recently bought the L-39 on Steam and was setting it up with my Thrustmaster Warthog HOTAS Joystick & Throttle. When I tried binding the "Engine Start Button" it opens the Emergency Switch Cover. I bound the key on my Throttle to the Left ENG OPER IGN switch (momentary left upward switch, JOY_BTN31). When pressing Home (the default keyboard binding) it however works fine. And when binding the switch to the Emergency Fuel Switch Cover, it opens and closes the correct Switch Cover. Also, when I've bound the "Turbo Switch Cover OPEN/CLOSE" to my Right ENG OPER MOTOR switch (toggle right downward switch, JOY_BTN19), it doesn't do anything. The momentary switch works for the 'Turbo Start Button' when via the mouse opening the cover. Version: 1.5.3 via Steam. P.s. Why doesn't the throttle's middle flap indentation work? I know I can program them via Thrustmaster TARGET's software but knowing these work in other ED's modules without a hassle, why not now? Kinds Regards, ArtOfStuttering.