patpatpowercat

Hey @Admiral189, hope your recovery is going well. Just wanted to report an issue with the Admiral Ushakov, specifically the SA-N-7 missiles. Everything I can find says the Sovremenny-class has 2x 3S-90 Uragan single rail launchers, bow and stern, and either a magazine depth of 42 or 48 missiles (obviously this could change). However your mod seems to have unlimited ammo, and launches at a rate of far FAAR too fast. I modified the Admiral Ushakov.lua and added two lines (one for each launcher). GT.WS[ws].LN[1].ammo_capacity = 24; I also commented out all the connector_names with the exception of one per launcher. By performing these two things, it has a limit of 48 missiles in the magazine, and the RoF seems much more appropriate to what myself and other unit members have found, with ~2 missiles (1 per launcher) every 8-9 seconds. This is a rough approximation of a Mk13 launchers rate of 1 missile per 8 seconds, so seemed like a good estimated guess. If you want to take a look and let me know what you think. Thanks for all your mods, and best of luck with your recovery! Admiral Ushakov.lua

Would you be willing to share your complete .kmz?

Is that a typo that it is supposed to be 46.3km? I see you're using some of the same sources as me (CMO). That, wiki, and other sources I could find designate the range for the 9M38 as ~25nm (46.3 km). I see in the .lua the range is 46000, and active radar lock 56000. Although I dunno the difference between those two parameters. Thanks so much for your quick response with this stuff! Oh, and I think you have to update the Admiral Ushakov.lua file as well to reflect the lower threat ring in the map correct?

@Admiral189Can you look at the Admiral Ushakov as well? It is supposed to be a Sovremenny-class destroyer is it not? In which case it should have SA-N-7 Gadly missiles. It currently fires "SANSA11", with a SA-11 model, but to a range far beyond what it should be, with the threat range being 160nm, this should be ~25nm instead. Or am I mistaken?

Awesome thank you!! @Admiral189

Hey @Admiral189! I was just wondering if the LSD Oak Hill had been updated for the dancing missile guidance problems? I saw there was not an active link on your website for an update.

I do believe there is an SM-6 that was added to the base game files, although not implemented, so it seems clear that thinking ahead is in someone’s mind.

Awesome thank you!

@currenthillWith the change of ED’s core now having Arleigh Burkes that have selectable ammunition, will your future releases of the flight IIa and III from the USA assets pack include this as well?

+1

We've removed *all* scripts and this crash still occurs. Always related to the transport.dll. dcs.log-20241015-192648.zip dcs.log-20241017-191650.zip

Crashes occurred in clients occupying multiple different modules from multiple different module makers: F-18, 16, AH-64, F-15, F-14 were all effected the same way at the same time.

Our group had a couple large client crashes this weekend during an event. In both cases, the server did not crash. Members in gamemaster/spectator slots did not crash or disconnect. There were no lag spikes or issues prior to the client crashes. We did not add any new scripts/mods that we have not been using in the past. In all cases, the clients froze up, then crashed. In all cases, the client's crash log points to an access violation from the transport.dll. As you can see, they all occurred at the same time. No large event/battle occurred at this time. Attached are 3 client crash logs all showing the same thing, however I can happily produce more client crash logs showing the same. There is also a full log from another client. The server log showed nothing of note. This mission was run through multiple times in SP, and never had any issues. It seems to be only in MP that there are issues, and only for clients that are occupying module slots. pat_dcs.log-20241013-015641.zip matth_dcs.log-20241013-015641.zip cblou_dcs.log-20241013-015641.zip OGA04 Client Crash.log

We’ve had issues with S-3s in my group as well, getting stuck on catapults and not launching. Works fine in SP, but in MP they get stuck on cat and do not launch. It seems to be that if a player/client aircraft uses the catapult first the AI then gets stuck on it. If the AI uses the catapult before a client (beginning of mission say) there are not any issues.

This seems not to be just older static templates. It seems importing static templates renames the units off the GROUP name, rather than carrying in the UNIT name.