Search the Community

Hi I noticed some problems with the HUD display since the 2.9.18.12722 release. As you can see there are some "holes" in the lines.

Hi, I noticed different engine sounds during flight. Engine 1 idle, engine 2 at AB and vice versa. Same on ground

If I set the mission to a 2 ship F-16 I can only seem to communicate with my wingman on 127.00 frequency, if I set it to anything else I get silence. To be clear, this has ALWAYS been the case for me but I decided to ask the community why, I'm sure there will be a simple explanation... F-16 radio freq test.miz F-16 radio freq test.trk

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.

Is it a bug or a feature? It's kinda frustrating. I look for targets with the TGP while the maverick is in PRE mode. If the maverick can't see the target it often (or always?) switch over to VIS mode, and then I lose track of where I am with the TGP. Is it possible to tell the maverick to NOT switch over in VIS mode, even though it can't see the target? My workaround atm is to switch over to another weapon, like a GBU12 or something, search for target, and dont switch back to the maverick before I know the maverick seeker can see it. This cannot be the right way, obviously I've added a track file if it is any help. f16_agm65_going to VIS while in PRE.trk EDIT : I did some testing in a self made mission where I started airborne, and then it worked normally, ie : no annoying automatically switching to VIS while using the TGP and agm65 PRE mode. So my hunch right now is that I'm doing something wrong under startup (since this mission is a cold start). I know I didn't boresight my mavs, but that can't be the case?

I am experiencing significant latency issues with the mirror rendering in VR on the Meta Quest 3. When I move my head or adjust my pilot position, the mirrors exhibit a delay of approximately 0.5 seconds or greater before reflecting the movement. This lag renders the mirrors effectively unusable. This mirror latency significantly impacts gameplay immersion and tactical awareness, as real-time mirror feedback is essential for situational awareness during combat operations. I have tested this issue across different connection methods to isolate potential causes. The latency persists both when using Virtual Desktop over wireless connection and when connected directly via cable without Virtual Desktop. This consistency across connection types suggests the issue is related to the mirror rendering implementation rather than the connection method or bandwidth limitations.

the cockpit-zoom leaps into higher levels of zoom without touching the axis. it's only a mig29 issue.

Hello, In the most recent patch notes there is a line for: 3D models enhancements in progress: Improved pilot model. But does that include the default seating position of the pilot? Because when you look down, it becomes apparent that the default F1 viewpoint is too much forward, and when looking behind you the pilot's shoulders clip through the ejection seat. The former issue can be fixed by editing the default camera position (with the included Camera Cockpit keybinds), but the latter requires ED intervention. For now I put the new default F1 view in-between the current default position, and where it would be if I align my head with the in-game pilot's head, but what can we expect in the (near) future? Are the upcoming improvements to the pilot model going to address both of these issues? Thanks!

Tried making myself an unlimited spawn training mission with infinite fuel and ammo on the mig-29A and no matter where I set the option, be it via script, waypoint action or mission options I cannot get it to to work. The override box is unchecked in the gameplay tab.

Amazing work! The pilot camera FOV has a strange fisheye thing going on. It's cooked into the module, as none of my other DCS modules do this (and I own all of them). I'm getting nauseous just sitting in the plane on the ground. Can we get an option to change this? Thanks! -Ryan

This is my Center Pilot view always off and down in Track IR

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

The Sniper Pod is not showing in the loadout screen for me. The only thing showing is an unskinned Litening Pod. I did a repair and tried again, but the same thing is happening. Anyone else experiencing this?

Dont know if this is a bug but I only see aircraft symbols on the SA page if I have the TACAN turned on. Is that correct? This is on an MP server with AWACS on eplrs turned on.

Hi, My osb displays button text are missing which I use the AAQ-33. nullWhat can I do?

Hi, I created a custom Laser Guided Bombing mission on the Afghanistan map that uses the older Litening TGP. I get the jet ready to rock with a hot start from the ramp, and when I go into A-G Mode, and select the TGP it shows on Standby, but when it seems like it's about to show the video my screen freezes and the game exits. I am including the recent logs (Looks like errors around MFD textures and possibly loading terrain textures). I have also attached the log and mission files. This is happening right at the beginning before I even get moving. dcs.log Afghanistan Ground Attack Practice.miz

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

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

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 tried the new Northeast Afghanistan map last night. I never got off the ground cuz my FPS was unplayable. Just to make sure I didn't have any other issues, I ran the exact same aircraft and mission in Iraq, and it ran flawless. Anyone else have FPS issues with this new map? I had southwest Afghanistan before and I don't remember having any issues with it. Only started when I went to the northeast map.

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