Search the Community

Hey Everyone, I've seen a few posts about this problem, but none of them have helped me. I'm fairly new to DCS and the F-16C and I'm not really sure what happened. I was doing mission 2 of the Dragon's Fury campaign for the second time (First time I landed at Anderson when I wasn't supposed to) and after completing the mission objective I was on autopilot towards waypoint 4 and I decided to accelerate time to get there a little quicker (tired of doing it again). A few seconds into the time acceleration my plane went into a spin diving towards the ground. I took control back, but I could not get full control. There was random full rudder and continuous full aileron both to the left. I turned on pitot probe heat since I saw a few posts about that (even though I was in a warm environment) and deployed landing gear. The landing gear seemed to help the rudder a little bit, but not the constant roll. I also could not trim it out. My stick was calibrated and DCS was not showing any input on any axis in the axis tuner. I could see the rudder pedals moving occasionally in the cockpit. I managed to touch down, but then lost control on the runway and crashed. The track file is just over the size limit, so it is not attached. After the mission ended I hopped into a free flight and no issues were present. This makes me think I did something when using time acceleration, but I can't figure it out. I thought maybe I mis-clicked a command on the keyboard when blindly reaching for ctrl+z with my VR headset on. Is there any sort of command that messes with the flight control surfaces? Watching the track with the inputs showing I can see the rudder going from neutral to full left repeatedly, but yet in the axis tuner it was not moving at all. Does time acceleration cause weird things to happen in game like it does watching tracks? I am playing in VR and using a Thrustmaster Warthog throttle and a Virpil WarBRD base with a Virpil MongoosT-50 CM2 stick. I don't yet have rudder pedals (saving up) and I am using the slider on the Warthog throttle to control rudder. I have only been using it on the ground. I'm currently on version 2.9.16.10973 of DCS. Cheers, thanks for any help/suggestions.

I configure my Virpil dual throttle as sliders and add a -10 curve to match physical detent with in-game AB detent, but with every restart DCS reverts to the old settings. Axis inversion remains though. This seems to be related to the same issue in the MiG-29

DCS works fine as long as I don't cold start the F-16. Whenever I move from off to idle detent, DCS crashes. Sometimes it crashes. It's as soon as I click the start 2 switch. It works fine as long as I do not cold start. I tried to repair multiple times. I have never experienced this issue before. Any assistance you guys can provide would be greatly appreciated. dcs.log.old (5) dcs (2).log

L118 Light Artillery falls through the ground when loading/unloading.

I observed that the the Radar Elevation Zoom function does not work with the Litening Pod if the HOTAS control is bound to an Axis. It does work if it the HOTAS control is bound to a button press. The HOTAS axis zoom function does work with the ATFLIR pod if bound to an Axis. If the Emergency Jettison is used the center mounted Litening Pod appears to be ejected in the 2D view but the Pod still functions on the jet for targeting, etc. Can anyone confirm these observations? Thx!

I am flying in Afghanistan the only code that works with the ATFLIR on the left cheek is 1688. Any other code the rounds (500lb LGB) are impacting about 100 meters off the target. The only other laser codes I've tried so far are 1686 and 1687, both are a no go. A friend and I also tried to buddy lase for one another with 1686 and 1687 and same issue, rounds impact off the target. I placed a JTAC on the ground lasing targets with 1686 and the LST won't even pick up the laser. Haven't tried the JTAC on 1688 yet, but will here soon. So far the only code that works in Afghanistan is 1688. Haven't tried any other maps yet either so I cannot speak to those. Thanks!

track ir is slaving to the tdc in the a10 c when using HMCS and when i press the slew it also follows my head tracking...should it be this way??? shouldn't it only follow my tdc input and not where i look?? as it is now my head movement is being in-puted which has consequences and can throw the targeting off by mistake.

When you start a mission cold and dark the laser isn't working despite the aircraft being armed. This is in DCS 2.9.18.12722

Hi everyone, since the latest two patches my hud seems low res in normal FOV: When I zoom in it come back to normal res: Does anyone ghaving this problem? Anyone manged to solve or is reported already? my PC: -Ryzen 5600x -AMD 7700XT -32gb RAM DDR4 DCS config:

A-10 C and A-10C II mod became unplayable after DCS July update. It does no longer respond to pitch/roll/rudder axis. Even complete reinstallition of A-10C/A10C II module did not change anything. Other mods work fine. Any ideas?

After starting up, Rearming and then turning on the TGP with GBU12s and CBU 105s (no other ordinance works but in the video this is what i was using). The pod begins to flicker or rapidly switch states where using the slew switch will not let you move it and it will not let you set an area or target track. The issue persists even if the pod is removed and reattached mid-mission. It can only be resolved by switching to NAV mode or respawning the jet even when its switched to nav mode it will revert if you go back to air to ground mode. It also will fix when i set my Laser bombs to CCIP instead of CCRP. The issue does not occur in other frames and will happen on any terrain. Will also occur in the ground or air when you switch from A-G to A-A back to A-G. I've tried playing around with the dogfight and missile override and neither can fix it. Steps to Reproduce Cold start F-16C with a loadout containing TGP and any A-G weapons Set Weapons to CCRP Enter A-G mode via ICP Make TGP SOI Observe the TGP: it will now flicker and be inoperable unless you set your bombs back to CCIP or click NAV on ICP IMG_1903.mov f16bug.trk

It's always out to the right for me. Even with a boot full of rudder or full right trim.

Doing a mission on Kola there are mortars, shooting and mayhem going on at the airfield, yet no sounds are heard at all in the cockpit, except if an aircraft booms over head.

Hey, if you hop into Syria map quick start missions there are no liveries on the Hornet. Use the Free Flight mission and then click F2 for external view. It switched back to default livery. If there are some more liveries around, please include them into the module, that we can see the liveries wich are meant to be seen in this syria map quick start missions. Thanks and stay healthy.

ciao I noticed that F18 ext lights are not illuminated, despite all the knobs on 100% internal lights works perfectly, and also taxi lights any idea on how to resolve this bug? Am I doing something wrong? ciao

I have many ground units set to basic movement, but only a handful move, I don't know if this is a general ground unit bug, or a bug with the Kola map, where the ground AI thing the ground is impassable. But it seems AI related as it random of the move, whenever I start a mission, sometimes some units move, some times no units move. I've tried to have the ground units start at 5knot or at 0knots, but it doesn't seem to have any effect. Valley of Death.miz

In the runway start Afghanistan instant action mission, as soon as you spawn into the CH-47, the AI CH-47 on the runway behind you immediately taxis into the back of your aircraft. Not great. Just a heads-up.

After the last patch the ground steering is worser as before. I'm not able to to steer to the right. Left no problem. Maybe I'm doing something wrong. Is there someone who has the same feeling?

Unable to use the command "autostart" with the F/A-18C after the latest upgrade for DCS Stable. After about two minutes, "autostart" stops with the following message displayed "Right engine parameters failure". It occurs consistently with all DCS missions-- including mine. Any ideas? Thanks. LastMissionTrack.trk Debriefing #1.log

Got a weird one. I'm assuming I somehow broke something by mishandling her, but I don't know what or how. Starting off at Andersen, taxi out a bit and take off normally. Do some practice approaches on the North Field runway with LHA deck markings. On first landing maybe I hit too hard? Power lever full down, torque reading 13, reset trim. Struts are extended fully and aircraft bobbles. Second approach, same thing, but this time I ease the stick forward thinking my trim reset didn't work. I somehow lift the tail and stand on my nose. Come back to Andersen and land on the taxiway I took off from. Struts still stay full extended, bobbling. I add power (about 16 torque-ish?) to taxi and the tail comes up. Forgot to turn of the AFCS, so I turn it off and try to taxi again. Now I'm spinning anti-clockwise and don't understand what's going on. Track is a bit long but should show the problem. https://we.tl/t-5TrpMx8iGM

@BIGNEWY This is an old bug returned. When loading mission, the game freezes at the same place every time. Terrain Graphics init : 96. "name of map" .ng5 EDIT, Additional thoughts: I left it for 20 minutes and had to end task to close. I have already done a cleanup and repair with no result. Do you think I should do the fresh Saved Games trick? Thanks in advance, Ray

Steps to reproduce I am not completely sure about how to reproduce this issue. It does not occur very consistently. Similar things have occurred occasionally when using various AI-controlled SAMs, including SAMs launched by ground units, with no clear pattern. The case shown in the attached track file is one of the simplest ways I was able to make it happen. Expected behaviour Missiles launched by the ships should either continue in flight or self-destruct. Their models should be visible. Actual behaviour Sometimes, a missile, when launched, does not begin flight or visually appear, though its label indicates that it is present. Instead, the missile, invisible except for the label, remains stationary in midair, apparently at the location where it was initially created when launched. After some seconds, it self-destructs with a visible explosion. See the attached track file. standard missile 2 in midair.trk

I've been experiencing this bug for couple of times now in MP. The stores page will "freeze" somewhat. It usually happens after I finished a sortie and come back to re-arm. But it also happened a few times with the fresh respawn as well. Here is a video explaining the issue: https://youtu.be/4GoELOsEtH0 I still don't know the exact procedure to reproduce it 100% of the time~. Thanks.

https://www.dropbox.com/s/4yq6gkmos270im7/JTF-13_NTTR_TrainingV1_C_3-20210518-121423.trk?dl=0 link to my trackfile... This is what Im doing and what I am getting Master Arm ON /A-G mode / ATFLIR SOI Using ATFLIR, designate a target, laser is armed, 1776 code confirmed LGBs AUTO/EFUZ Inst/Code 1776 confirmed Cross hits on the bomb fall line, pickle held down and no bomb release. Laser fires, LTD/R displays in the HUD, TTI displayed Did this multiple times with similar passes, tried different aimpoints and still had similar results. The ONLY way I was able to drop any iron at all was to select the quantity from 1 to 2. I was able to successfully drop 2 bombs at the same target at once, but not a single bomb. From what I am seeing, I think its dropping in simulator mode, but troubleshooting told me thats incorrect as my master arm was set to arm, and im certain I put the correct settings in the bomb. Again, the only way I was able to get some off the racks was to select more than one...No, I do not ever try to select quantity when I launch more than one, but this is what I found while troubleshooting. Any suggestions welcome, but Ive never had this problem before.

Happened to me on multiple occasions in MP with squad mates reporting the same. Launch params fine, master arm on etc, missile won't fire! Aim 120c/b and 9x/m. If I have time, pressing MSL STEP helps. Are missile motor failures modelled? Joystick button is fine physically. Not sure how a track file can help. Anybody else had this?