Jarlerus

I have experienced this too, and it's really annoying. Needs a fix! I am pretty sure this is a problem on other maps too - at least the PG map. And maybe also effects the IR-TGP. I feel like it's time to upgrade the whole "lock" feature on mavs and similar weapons The processing power need to do actual contrast locks can't be _that_ large?

For the (inevitable?) "UH-1H Remastered"-upgrade, please make the M23 Armament Subsystem an option.

Ok, if this doesn't only concern "dead drops" but also live ones, I think it's actually an issue.

My guess is that they have a template formula for "dead" items falling, and that the formula is stupid Faster falling-> hitting ground faster-> Getting despawned faster can also be a factor. Generally, my guess is that they simplify it to not draw server/client CPU for trivial things

Noticed that I've missed to add the La-7! Fixed //Jarl

Updated with CH-47 as released 42 modules in game! //Jarl

Problem fixed with the update to Release version of the server. //Jarl

Yeah, I've had this issue for a long time Just had enough energy to try to fix it now xD Hadn't seen any info about any change, so I just assumed the Updater would update to a relevant version Ok, I don't remember, but I've probably started with a non-dedicated version, and thought I successfully converted it when the Dedicated Server was released. Probably followed some instructions for how to do that back then I'll try that update command, thanks.

Attached the Server autoupdate.cfg, as it is after an update. No log is present is created when trying to start the server with this file in the directory, as the startup process is aborted. (showing the error message I've attached as well.) I do get a "autoupdate_templog.txt" file, that isn't saved with " 00000.049 --- Log file: C:\Users\MASTER~1\AppData\Local\Temp\DCS.openbeta_server\autoupdate_templog.txt 00000.000 === Log opened UTC 2024-06-15 11:54:44 00000.014 INFO : DCS_Updater/2.16.3.18 (Windows NT 10.0.19045; Win64; en-US) 00000.014 INFO : src-id: f697eb0b6959f621dddfde672932cdb00d183f23, lib-id: b88ea51ae2210987a3865f77cc1802548216d7a8 00000.014 INFO : cmdline: "D:\DCS World OpenBeta Server\bin\DCS_updater.exe" 00000.047 STATUS: Initializing... 00000.048 INFO : basedir: D:\DCS World OpenBeta Server 00000.048 INFO : variant: openbeta_server 00000.048 INFO : DCS/2.9.5.55918 (x86_64; EN; DEDICATED_SERVER,MARIANAISLANDS_terrain,SINAIMAP_terrain) 00000.048 INFO : branch: openbeta 00000.051 STATUS: Checking for updates... 00000.265 INFO : Got reply from www.digitalcombatsimulator.com 00000.506 INFO : Got reply from www.digitalcombatsimulator.com 00000.508 INFO : DCS/2.9.5.55918 (x86_64; EN; DEDICATED_SERVER,MARIANAISLANDS_terrain,SINAIMAP_terrain) 00000.508 INFO : branch: openbeta 00000.510 STATUS: Can't run D:\DCS World OpenBeta Server\bin-mt/DCS.exe: (2) The system cannot find the file specified. 00001.665 === Log closed. " And the error seems to be as simple as the bin-mt folder not existing on the dedicated client. When I do a (small) repair, the autoupdate.cfg file is not "reset" to the one with -mt in it. It only resets to that on an actual update/patch. (Testing a full/detailed repair now) Yes, a full repair of all files re-adds the "-mt" in the autoupdate.cfg file. //Jarl autoupdate.cfg

Hi. (tried looking for a post about this, didn't find it) After every patch my Dedicated Server can't start, as a "-mt" tag appears in my Autoupdate.cfg and presumably tries to start the server in Multi threading mode. So I have to go in and manually remove that "-mt" after each patch. Am I doing something wrong? if not, why the hell is that -mt thing appearing after each patch? <.< Can't that be fixed on ED's end? //Jarl

Updated with F-4E as released, as well as added some new weapons now available because of this release

I hope many other devs find your SDK useful and start using it! I love this initiative!

I noticed this recently. Made 2 test mission with this bug on both Syria and PG. Recorded the issue. Could be a render bug for the moon reflection. BUG TEST MISSION-PG.miz BUG TEST MISSION-Syria.miz

MiG-29 on the list again! xD

It all depends on them actually identifying the issue, and finding a solution - It's very difficult to make a time estimation on issues like this in software development. Ya'll just have to sit back and cross your fingers.