Search the Community

Spitfire Spinner disappears when up close in F2 view then reappears when you zoom out. In fact I also notice an issue with the spinner on the FW190 Dora, where (presumably) the LOD changes when up close to a general black one, and further away its striped or spiralled. Pre-2.7 I never noticed the spiiner disappearing, or is it just a detail setting on my end?

does target pod mostly drift on bridges. doiung a operaton pontus mission and its difficult to lase target

I tried a million configurations, but, no matter what, the fuse is never triggered and the bomb never opens (VT1). cbu99.trk

Affected aircraft: F-16, A-10 (C & C II), AH-64 Setup: Using radio call menu, all variations of easy comms/assisted comms/regular comms Multiple bands, multiple radios; all radios tuned correctly, buttons mapped (no conflicts). I've used the drop down menus and ensured radios in each aircraft is on, up, unsquelched, non-blocked, and in-range. Behavior: I'll attempt a check, but pilot doesnt transmit. I'll attempt same JTAC on different radio/freq, but at most will get static for ~1 sec. If I start making drops in his AO anyway, He'll finally respond, but will only call an abort. No other comms are possible. Anyone else having this issue? Many thanks in advance... when doing single player, sometimes its the only life on there besides george during mission.

I don't know how I managed this, and track is multiple megabytes as usual. But I got stuck with TADS symbology as pilot. No matter what I did to resolve this, I couldn't get it back to flight symbology. I tried symbology select, and even turning off IHADS in the WPN/UTIL page. I also had the gunner chance sights and symbology, but that didn't help either. I know that a display processor failure would duplicate the HMD, but I don't think that's implemented? Also we just took off from the airfield and I'm pretty sure there was no damage.

This is an interesting phenomena. So, at night, in a moonless night scenario, if you look at different angles your image darkens by a lot for a few seconds. From my testing, the angle at which this phenomena occurs seems to be related to the time of night and maybe even location. Also you can get this thing even from third person if you look at the right angle. Here is a video i took of the thing happening. Also i have 3 tracks, one where this thing happens when you look straight up, another track with changed location and a different hour where the angle changed and another one with a little light when the "bug" is absent. (i only get it on moonless nights, pure black so far) Another person i could test this with also has this happening. WhatIsGoingOn.mp4 dimming 12am.trk different angle required.trk little light, no dimming bug.trk

As you can see, there seems to be something wrong with the fuselage or the part of the wing that is hit by the sun. Is it the game's fault or is my graphics card broken?As you can see, there seems to be something wrong with the fuselage or the part of the wing that is hit by the sun. Is it the game's fault or is my graphics card broken? nullOr is it game settings?

The HMCD is very shaky when using the Quest 3, making it difficult to set a good marker point. A feature that makes movement smoother and more stable would be a real improvement for the A10C II.

Hi everyone, For whatever reason, I cannot seem to get the AI F-4E-45-MC to use Paveway II and Paveway III series laser guided bombs against points on the ground. Upon reaching the waypoint with the bombing task, the aircraft simply turn around, follow the rest of their waypoints and land. I've tried numerous options on the weapon to use (AUTO just ends up using the internal cannon, I've also tried guided bombs, guided and bombs) to no avail, override AI attack avoidance decisions also doesn't appear to change the behaviour (and in any case, this mission is empty apart for the AI aircraft - there's no threats). It also doesn't seem to matter if the task is set to CAS and whether or not you use the CAS, Attack Group/Unit or Search then Engage tasks, none seem to work. The issue seems to be fairly exclusive to Heatblur's F-4E-45-MC (though the F-5E-3 also failed to drop the bombs, but then, there wasn't anything to provide designation). Attached is a track showing what happens with the GBU-12, the issue is also present on the GBU-10 and GBU-24B/B (the latter should actually be an A/B, but that's for HB to fix). EDIT: The problem is also happening with a few other weapons as well, it seems mostly isolated to guided air-to-surface weapons, with exceptions (so far the AI is fairly reliable when engaging with the AGM-12). In AI_F-4E_AGM-65D_nofire.trk, you can see that the AI won't fire Mavericks at a tank platoon, the same is true for every other Maverick the F-4E-45-MC has available. It also happens regardless of what the Maverick is mounted on (be it the LAU-117, the LAU-117 on the special weapons adapter or the LAU-88). In AI_F-4E_AGM-45A_nofire.trk, you can see that the AI won't fire an AGM-45A at the SON-9 (the guidance section is set appropriately), I have got it to fire at the Big Bird and the P-19 however - it seems a bit inconsistent. I also can't get it to fire at the Fan Song or Low Blow. EDIT 2: The AI will only fire AGM-45A if the SEAD advanced waypoint task is active, it doesn't work if you only have an Attack Group/Unit or Search then Engage task set. The GBU-8 is as with the Paveway II and III described above, see F-4E_AI_GBU-8_nodrop.trk. Both Walleyes however are unaffected. F-4E_AI_LGB_bug.trk AI_F-4E_AGM-45A_nofire.trk AI_F-4E_AGM-65D_nofire.trk AI_F-4E_GBU-8_nodrop.trk

Importing a profile (an exported dtc file) overwrites the current profile on the DTC screen instead creating a new one in F/A-18C multiplayer. Have not tested F-16 for this issue.

It's the cold start mission in quick start. I found that coordinates of points I added in the TSD never matches what I typed into the KU. The coordinate is 38T GG 4515 7680. I typed in. Then the coordinate in the TSD become 39U UB 6789 7191. Track's here. wrong coord.trk

for some time i have noticed that when designating a ground non moving target with the HMD ,as soon as you look away from it the designation diamond will not stay locked on it and will be miles away. you must quickly move the senser of priority to the flir Demon-702

I only get the radar to get the sweeping animation or the picture when I press RSET, especially on A/G MAP mode and then it stops sweeping. F-18 MAP mode radar bug.trk

When not caged, my understanding is that the dial should move to reflect the range to a target based on radar returns. I've messed around with this for an hour and have yet to see the dial move off of 1800'. When I cage it, it goes right to 600', but right back to 1800' when uncaged again, regardless of how far away the target is.

Every time I click release slot from front seat, DCS crashes. Will add log and track file after we clean up this mission. SSSR (2)-20250311-211217.trk.writing SSSR (2)-20250311-211217.trk dcs.log

right and front wheel were damaged. both sinking into ground.

Pretty please with extra sugar on top, could the WebGUI interface (aka DCS Server Dashboard) get some attention? There is a very long delay when adding, removing, and changing maps in the DCS Server Dashboard. The amount of lag between making a change and seeing the result makes a user wonder if the server crashed and would need to be restarted. Even restarting the server can take up to 10 minutes!

Since the latest update, when spawning in or recentering the camera FOV in the A-10CII, it centers the camera off to the right of the cockpit. It worked without issue the day before the update as well. Additionally, I use TrackIR but I don’t think that is the issue. There are no stray IR sources distracting the IR camera, etc. TrackIR works flawlessly with all my other modules currently and including the regular A-10C since the last update. I have tested this on Syria, Marianas, Caucuses, PG, Kola, and Afghanistan. All the same issue. This issue is present in old missions and newly created ones. This picture shows what it believes to be the “centered” position. Any help is appreciated!

there is behavioral difference between damage models of a10c vs a10cii. the former model behaves somewhat believable. when shot with 37mm cannon of mig15 from rear aspect, damage is catastrophic. the latter model eats 37mms like miki sudo eating hotdogs. a10c2_dm.trk

Yesterday I decided fire up the L39C doing the cold start training in dcs Cleared all joystick bindings. Mapped my throttle axis to joystick as slider. Also mapped set throttle to idle But the in game virtual throttle does not move, nor does it show movement in show controls indicator. Also when training asks me to set throttle to idle, nothing happens, ralt + home does nothing and the mapped joystick button for throttle to idle no worky also...

On several of our missions I noticed the Patriots and Hawks are not reloading any more on a base or with an ammo truck. I even tried in the mission editor to just put 1 hawk launcher with all the hawk parts present. It fired off all it's missiles, I turned up the speed of the mission to see when it would reload and over an hour it didn't get 1 missile. Nasams appeared to take about 10 minutes to get one missile. This always worked before but I think a recent update did something to it.

Even if he is ask to laser a target. He never does. Bug or not? See uploaded .miz Any help is welcome. PG - NEW - JTAC-Test.miz

When using the TADS to lase and store a target, and then slave back to that stored target, the TADS will no longer point at the initial location. In the following video, notice how the TADS indicated LOS on the TSD correlates with the location of the target (T04) when it is stored, but when slaved to T04 the TADS indicated LOS on the TSD shifts noticeably away from the point. This is also seen in the TDU itself where the LOS shifts several hundred meters to the right and closer. I do not have a track at this time, because I've so far only experienced it during 3 hour sorties. I shall be attempting to reproduce in the coming days and will update here.

I'm seeing floating hold-back bars and light wands held in hands of the crew. The models are not stationary in their hands. The minimum movement is more visible the farther we are from the crew. This is true for both 2D and VR. SC floating objects.trk

I've encountered this for months, and I've finally figured out exactly what causes it. As per the title, binding middle mouse to "Force cursor to show, toggle" causes a red exclamation mark to appear next to "Camera transpose mode (press and hold)", making it unusable. This is quite irritating as DCS requires an awkward double click on middle mouse by default so if this keybind worked you could make it just one press. I'm sure the people here with carpal tunnel would appreciate it if this was fixed.