Search the Community

Hi, Not sure if its a known issue but ive had it a few times when doing MP with a mate that after a respawn or rearm George will not lock onto a target, you still get get the solid green box up etc, it all looks normal but he won't fire the laser. Usually another respawn and he's working again. If its not a known issue I will upload a track file once I can replicate it. Thanks.

I found this problem with the AH-64D. The instant action mission “Runway Start” and the training mission Lesson 3 “TSD Navigation” both have this problem. Others may also have it I have not checked every one. The MPD’s and the “IHADSS“ are displayed as the mission starts. Then after a few seconds they all go blank. This happens for the pilot and the gunner at the same time. The training mission continues and high lights the required buttons to be pressed. The training will continue as if the displays can be seen. The complete training can be finished with all displays blank. My screen is 1920 x 1080. Monitors is set to “Screen 1” and full screen in selected. I have also done a full DCS repair using the slowest option. It did not help. I have not uninstalled and reinstalled the module. I do not want to reinstall DCS World. Instead I am writing this in hopes to get a solution. Let me know if there is any more information I can provide. Thanks to all for your help!

From 2:02:17 apache's engine goes from a normal condition to a total crash and shuts down, I can't tell if it's a bug or something else, could anyone say?

Just tried to fly a MP mission on a mate's server. Trouble was the inside of the cockpit was as clear as it would be in daylight despite the mission being set at night. Meant it was impossible to use the IHADSS / FLIR as the reflected lighting inside the cockpit bled out the IHADSS image. Ran into a hill. Not sure what the problem is as earlier today a few of us flew a night mission on my MP server and all was well with the lighting. Screenshot of inside of cockpit attached. The flood lights were off. However there was a full moon (but the mission earlier today also had a full moon and the cockpit lighting in that mission was OK) Also, I noticed once I had the aircraft started and my main MFDs seemed OK that looking over my instrument panel to the CPG's MFDs that all his MFDs were dead.

As title - the stabilator position indicator on the flight page and the shutdown page is not synced between CPG and pilot, nor is the EUFD manual stab advisory. Stab position on the aircraft appears to be synced. Track replay to follow.

DCS BUG F18 The "Stow" control is non-functional from the "Pull" and "Fold" position of the wrist for the wings of the F18. The wrist cannot be pushed back into the locked position using joystick keys.

Let's start with negative G. The maximum negative G I was able to hit was -1.7, which is wrong, and should be -3.2. Another thing during negative G flight, the engine doesn't flameout. Hydraulic/oil pressure does go down, appropriate caution light comes on, and that's it. You can keep flying with negative G as long as you like. According to some document, the limits of negative G flight are: -AB Thrust - 10 seconds, -MIL Thrust or below - 30 seconds

When ground unit is standing in the water, for example in a river or a stream, it's detected by SEA mode as it would be a naval unit.

Hi, I don't know if this has already been reported but since the last update during our multiplayer games, it is impossible for the CPG to slave the TADS on a WP entered via the TSD. Problems encountered by others? Thxxxx

Can't seem to get any SAMs showing up on the HAD page through the HTS. Is this bugged at the moment? Is there a checklist somewhere to make sure I'm not screwing it up? Never had a problem with it before. I can get the SAMs to show up on my harm emitter through the WPN page just fine.

i was approaching the carrier, 135-140 kts 300ft, full flap and i soon as start banking the 18 sink and stall no way to recover also at full power if i iam banked........maybe is a hotas problem, but i am not sure......

As per the title: The configuration of the OA1/2 in the DEST page have an elevation value. This elevation shoul dbe a height and therefore AGL just like VRP/VIP and PUP. However, with the end of april 2022 update, the OA1/2 elevation is the altitude or ASL. Regards Leo

I'm probably doing something wrong, but i noticed in Wags video for landings he had a FPV. I can't seem to bring one up for me (it's probably something simple). Am i doing something wrong?

Was flying along happily as CPG when suddenly I got rotor break lock caution in flight. Pilot confirmed rotor break was off. Toggling on and off fixed it.

Using todays patch, I have 2 pylons with 2xGBU38 each. TOO on both. I use TGP to designate target coords for TOO1 and TOO2. Switching between them, the coords seem ok. Step to the other station. Designate TOO1 and TOO2. Again, seems ok. Step back to the original station, check TOO1/TOO2. They have now changed to the coords from the last designates. That is, TOO1 coords are the same on both stations. TOO2 coords are the same on each station. Dropping all 4 bombs, 2 bombs each hit the same coords. This seems like a bug, or is my process wrong? Thanks. Update: maybe a bug - QTY behaves differently with TOO/PP When using PP drops, you CAN use QTY. Each bomb guides to the coord you enter When using TOO drops, you can NOT use QTY. Multiple bombs will guide to one coord, no matter what you put in the TOO for each one.

flew ok two updates ago or maybe three. In level flight nose keeps rising and can't maintain on speed approach to carrier. On approach the trim won't work and sometimes is stuck in the full nose up position Bobs up and down and is uncontrollable.I've downloaded a new program and did all new bindings but still no joy. Don't know to retrieve tracks,or send. Where is the stabilizer adjustments located?

Flaps up on a cold start causes the wings to un-fold.

So I managed to sneak in beneath radar to mop up a SA-13 at close range with my cannon. Easy, right? Nope. Hatched popped open as I took aim, gunner came out and wasted me with his 7.62 machine gun. What? Apache is armored to withstand up to 23mm but his first few shots were golden BBs and wasted both my engines. Armor not modeled properly yet? I don't think such a feat should be easy at all...

Hello, I've come across this issue in several circumstances. Hot start aircraft, George is commanded to select target, George can have Hellfire WAS or Gun WAS. George menu is UP(displayed) Pilot(player) WAS for GUN, on the MPD the WPN page is selected, MAN RANGE button is pressed, A is typed on KDU, ENTER pressed. In pilot HMD manual range is still indicated. In the track file attached, I run through the AUTO RANGE several times, Then George is commanded to fire on infantry, several targets are selected and destroyed. After this round of target kills, AUTO RANGE is accepted. https://drive.google.com/file/d/1LAXEvZhtlrqjBHviO3Ddkv0wHA1aBAMU/view?usp=sharing

I've seen this bug number of times already. After shooting down multiple bandits, I can still see a radar track (soft lock) or an AACQ cross, usually 5, 6nm away from me, at 0 alt. and running at -400 kts. closure. The target box on my HMD was pointing directly below me though and traveling at the same speed as I was. I wasn't able to get a STT lock on it. I will try to get a short track showing this. All I have is a vid for now. I'm sure there are other folks that have seen this bug.

DCS 2.7.11.22211 Open beta ,Error in flight control system or aerodynamic model or engine thrust data.The plane cannot take off from the land airport.Even if all runways are used, the aircraft cannot accelerate to takeoff speed.The takeoff trim angle of the flight control system cannot be maintained at 12 °. As the speed increases, the trim angle automatically increases and cannot be controlled.This error exists for both no-load and full load.Test airport:kobrej.

When descending using the FPAS calculated optimum descent, the end point is calculated correctly when a waypoint is the reference, but incorrectly when a TACAN is the reference. As it displays the distance a descent should be commenced for your given altitude, if you keep the FPAs calculated number and your actual distance the same, you can fly and monitor the descent all the way down. When using a waypoint, this works well, as shown below. @30nm @20nm @9nm @2nm (slight error is due to getting a little low compared with the profile) When using a TACAN as the reference, the descent is not calculated correctly. As you can see below. @30nm @20nm @10nm @5nm @2nm @1nm As you can see, the TACAN reference leaves you about 5,000ft too high. To illustrate more clearly, this is the two descent profiles compared: Distance - Waypoint Alt - TACAN ALT 30nm ~30K ~33.5K 20nm ~20K ~23.5K 10nm ~10K ~14.7K 5nm ~5k ~10K 2nm ~1.5k ~7K Secondly, the standard descent profile is, use idle power and descend at cruise Mach until 250kts, than 250kts onwards. ie M0.83-->250kts. This roughly correlates into a 2-to-1 descent profile for every 1,000ft, give or take 5nm. Eg, 20,000ft requires ~40nm to descend, 30,000ft 60nm etc. As you can see, this is almost double the distance calculated by FPAS when referencing a waypoint, and even more incorrect when referencing a TACAN. I believe that FPAS descent figures are incorrect, and result in an overly steep descent. They also calculate the wrong final altitude when referencing a TACAN.

3 Vipers got hit, all 3 Vipers leaked fuel, and none had vapor trails behind them. 2 Vipers didn't even know they were shot. No impacts heard or felt, nothing. Don't have a track. Was a user made mission on Persian Gulf. Were shot by a Rapier site. Sent from my SM-G960U using Tapatalk

Recently I've noticed that when I try to lock up a SAM radar using the HAD, I'll get a very large axis error, but a position quality reading of PGM1 (the highest quality). This always results in a miss. Notice in the attached photo I have an axis error of 308nm, but position quality is PGM1. No amount of triangulation will bring the axis error down. I've noticed this mostly with SA10 and SA6 radars, but it doesn't happen everytime I try to go for a lock. Sometimes the radar emitter will be at the edge of the MFD and far outside the HARM footprint and still show PGM1 when I lock it up. The axis error will stay the same and far outside a launch parameter.

1. I was playing online trying to sneak up on an enemy airbase with my RF switch in quiet mode. My CBU-105's were powered on prior. When I reach the target I got one release and realized I was in quiet mode = bad drop (Pre mode). I turn it on and I could not get another pickle. I move off from the target area and switched modes to vis, back to pre, and even switched weapons then back to the cbu = Would not drop. I power cycled them, turn my master arm OFF then back on, cbu's showed RDY and was able to pickle. Next drop in sequence after another pass, cbu's still showing ready would not drop. I followed them same procedure of power cycling, Master arm on and off, then back on resulted in a successful pickle. I had one more CBU-105 left for a pass and it would not drop. I jettisoned the weapon and RTB. I noticed other instances where they haven't released and there won't be a falling cue. Only the weapon in range carrot works. 2. With this being in VR and online multiplayer I don't have a track. I can possibly submit logs? 3- 4- Multiplayer - Caucasus 6- I searched and found a similar report, but not very detailed.