Shot

Did two tests just now with all Mods removed (I hope) and a clean logs folder. I've measured from the moment I clicked on the join server button: 1) Server "[PL] Gildia.org - Dynamic Range Germany (Cold War) PvE": DCS loads 2:40 minutes until "New sim post start" appears. This time it took ~2.5 minutes this time before it proceeded and i can select a coalition. Logs are attached as 1st_run.zip 2) Server "105th SSF | [GER] COMMUNITY SERVER": Same Germany CW map. After 45 seconds, the "New sim post start" appears. After a total of 1 minute, that's done and i can select a coalition. Logs are attached as 2nd_run.zip. Why does this sometimes take 2-3 minutes and sometimes (I assume) a normal few seconds only? The only thing I found in the logs which takes ~2.5 minutes is that one here: 2025-08-05 20:09:02.443 INFO WEATHER (Main): reset fog animation 2025-08-05 20:11:19.742 ERROR ED_SOUND (18140): can't load wave: "effects/weapons/automatic/warrior_distant_1.wav" That a mission thing? Thanks for any help! 1st_run.zip 2nd_run.zip

I'll do another clean connect the next days and will provide the DCS.log. At one occasion, I had waited 10 minutes before I killed the app. My buddy who was already on the server has seen my connect but I obviously never made it. Waiting 3 minutes might be annoying, waiting 10 minutes is impossible I'll provide the log...

Well after giving up for some time, I can now report that the issue still kind of exists although it got better again. The symptom however still remains: On some servers (e.g. "[PL] Gildia.org - Dynamic Range Germany (Cold War) PvE", my machine is stuck at "Net sim post start" for around 3 minutes. I can join any other servers (also with the Germany CW map) but none takes that long. The issue just appeared since the last patch, before I never even had observed that message during the loading process. My machine is a i7-10700K with 64 GB Memory and a 5090.

Since I updated to 2.9.18.12722, I can't connect to any server anymore. The game is stuck, DCS is using ~20 GB memory and 15 GB GPU memory but does never complete the loading process. My buddy saw that I'm connecting on the server... but that's it, I'm seeing the loading screen with that message. Any ideas? I've repaired the installation, removed all mods, restarted my router, rebooted my PC and cleared the fx and metashader files...

I'd really be interested how things like this can that easily be broken again. It was not working for months I guess and only just recently fixed. For sure not the most critical feature in DCS, but I really can't get my head around how such things break... Especially since there was no functional change in this area.

Understood that it's difficult or impossible to reproduce without a track file. The thing is that I only enjoy flying on large servers. Just wanted to see if other people also have seen it. Then maybe someone wants to do isolated tests. As I haven't read anywhere else that repair is broken, I'd assume it's two cases only so far.

Tried a repair now 3 times, always with the same result. As it was on a larger server (Rotorheads), no track file available. ah64_repair.mp4

Hi Shaka, I was just on the Syrian server flying with the Apache for 50 boring minutes to Al Qusayr, landed, refilled & rearmed and then continued to Sharyat and got killed. The DYN slot at Al Quasyr then however still said that I did not land there before. Anything I need to type in the chat for that? My nickname in the game is VicMackey. The server is super cool, I guess whatever changes you apply, it'll make it even better! Sorry for the English in the Italian forum. Ciao! Shot

Hi there, would it be possible to also add some DYN slots also for the F15E? Thanks! Shot

Had the same or similar issue last week in the F15E. After losing half of a wing, I was no longer visible on the map. I managed to land and repair but did not become visible on the map again. Did not try whether the AI is seeing me or not, but not being visible on the map might be related to that issue?

Thanks for the workaround. Didn't try it yet myself but it seems very reasonable

Hello, another occasion in which I can't repair my AH64. This time because the engines supposedly were still running: Engine indications were all at 0 Before I asked for repair, I made sure the APU is off, cockpit open (this worked before on the same server plenty of times) After I could not repair, I tried all kind of combinations with APU on, door closed, whater... nothing worked. Not being able to repair is really very frustrating as you try to save your life/vehicle, crawl back to a FARP and then ... just to press the respawn button? Last week I had similar issue, I could repair but not start the engine anymore. Isn't it just possible to RESET the whole thing during a repair in a similar fashion to when I'd respawn? This would solve all related issues at once. Link to track file is here: https://www.primusnetz.de/cloud/index.php/s/c9Jvfik10vVb9co Regards, Shot

I just did a flight, got shot at and lost my George in the front seat. After landing at a FARP, I hit repair and was surprised that: 1) I could actually repair (no more of those bugs) 2) A got a new George! When I was just feeling to get on my 2nd trip... I found that I couldn't start the APU. After trying whatever I could there was no chance of getting the APU fired up. Screenshot shows quite some FAIL messages... after the repair?!

Aaaand it happened again to the harrier. Only a single GBU54 is now possible when u also want to carry a sidewinder. I appreciate the realism... But cutting it down from 12 to a third of bombs is not what I had purchased back then.

So the published loadout is final? I bought the harrier and have seen the loadout shrink over the years.

Cause other things get fixed instead. I had a look at the changelog today and can only shake my head...

Same here, seeing this behavior every single time I hop into the AH64. I've observed the following: George never ever fired >2000m away from target, not even once George seldom to never fires with the "consent to fire" button, only by using the long-press-up (free to engage?) he might fire some rounds Tried all kind of concepts, going higher, slower etc. - none worked. I can fly directly over a soldier who is shooting (and hitting my aircraft) while George is doing exactly nothing. Most of the time just before overflying the target, George starts shooting and released a ton of rounds although the target might be already physically not reachable anymore (as it's behind the gun by then) An SA-8 200m-400m in front of me (or other things)... I'm sick of waiting for George to get some rounds out, it's quicker and more efficient to WAS the gun myself (as pilot) and then just spray it into the direction. It's impossible how badly the gun (with George) is implemented right now. I'm not expecting George to be a sniper with it (like the MI-24 on some servers) but at least he could get some rounds out and towards a target which is clearly visible while the helicopter is in a very stable flight (or even hover!). Waiting for a fix, flying something else in between...

Same here.

The bug that you can't repair as soon as an engine was hit was reported in April or May already... I'm really wondering if this is ever taken care of. It ruins any fun of bringing this bird back as anyhow you already know that you might as well respawn immediately when being hit.

I really tried everything. Also giving George the gun, I had selected the hellfire and changed between RF and SAL but this also didn't do the trick. It's frustrating as it is right now, especially if it's really because he's selecting RF which is not implemented yet. What's the point of even giving the AI that feature if its not there? Will try to provide a trk file, sure I can reproduce by using down or long-down for George. I understand that it's beta.. But if multiple people report the same issue I'm not sure why the community needs to debug the issue

Just had it again, George can't shoot any missile anymore. The "MSL TYPE?" is shown in TADS. Tried everything, switching LOBL, LOAL, weapons safe, even landed to get him back to normal again. Nothing helped. WASing the gun while having the same target locked makes him fire the gun immediately. Range is ~2300 to ~2500m and the target was not masked. I did not include a TRK file as it was after hours on a server. There must be a bug however, I'd guess linked to Gorge DOWN or LONG DOWN as especially the LONG DOWN I've not used recently and did not have any issues. I

Had the same yesterday for the 2nd time. It's quite disappointing after flying the bird back to a base with a single engine only, then struggle to shut off everything with that shaking cockpit and then finally... you find out that you can't repair it due to an engine still mysteriously spinning. Hopefully there's a fix for both issues soon!

Is there any workaround (e.g. lua binding available) to create those bindings ourselves? I'd need all volumes to be available as axis, and so far I've failed creating the bind myself as there is only "Step" (up/down) commands available. Is this somehow doable?

I've read it somewhere in the forum that you need to press SSS (Sensor Select Switch Down) twice within 0.8s to set the TPOD as active (for slewing etc.). Once you do this the controls are working OK again. Weird as I'd expect if the TPOD is not active that the slew controls would do nothing instead of showing this weird behavior.

The slewing is broken since the previous upgrade for me. It only works (left=left, up=up, ...) when flying directly towards the target. Once your target is on your 9 o'clock position it gets difficult as the slewing still seems to be based on the direction of your aircraft. Absolutely unusable, even the DMT I think showed the same behavior. Will fly F18 until this is fixed or someone can tell me which magic button I need to press to get things back to normal again.