d0ppler

Same for me. It only works in 2D, not in VR. Anybody knows how to fix this? (I'm using reshade v 5.6)

You are totally right! I learned something new. Thank you!

IRL you would need a space suit if you're going over angels 50ish, otherwise your blood will start to boil. That sounds a bit painful.

I believe the IFF in and out switches are not simulated in DCS because what they actually do is classified.

Happens on mine as well. The RWR display is fine, but the DIM switch to dim the button lights is either on or off.

I have had problems with this before, but not in a very long time. Could you provide a short track illustrating your problem? It _can_ be an user error. But like Machalot is saying, if you're already using your TGP, just create a mark point directly. No need to enter those coordinates manually. Bear in mind that there's always some slight inaccuracy when you slew your TGP to a steerpoint. That's at least what I'm experiencing when I "reset" the TGP position with TMS down. You'll get some slight deviation every time you TMS down. Don't know if that's what the real jet does, but the deviation is so small that it's not any problem.

Update : When I restarted the campaign, I could continue by clicking "End mission".

Yep, I agree 100%. People wants to see F-22 and F-35 beating up Su-57 and J-22 and what have you. All classified planes made for DCS with guesswork. Not my cup of tea.

I can't believe there's a difference between starting the mission within mission editor or not. It should be the exact same thing.

I'm doing a user campaign now (made in the previous open beta release) and nothing happens when I click "End mission" in the mission debrief window. I am only able to close the window and therefore I'm stuck at the same point in the campaign.

What's stopping you from doing this in the DCS Viper? Just type it in..

You can hone your skill with this mission: https://www.digitalcombatsimulator.com/en/files/3328442/

When I try to fire mavericks on multiple targets in the same run, it seems like the mavericks are hitting/destroying each other rather than their targets, unless I wait uncomfortably long between the shots. Is this a 'feature' or a bug? On the replay file I fire 6 mavericks at 6 different targets. Once the first maverick hits the first target, it seems like that explosion kills 4 other mavericks in the air, however the last maverick gets the last target. maverick_explosion_kills_other_mavericks.trk The mission I used: maverick.miz

Happens to me as well. I think it's a feature, like a shortcut to get back to RWS

ED - Send me a PM and I'll get you in contact with Viper pilots that can confirm the pedals in an F-16 are moving parallel.

It's good you wrote it in all capitals, that way ED knows it's really important.

How is it that it's very clear that they rotate? Especially when it's just a fraction of an inch? It's kind of confusing. I have first hand information from two ex-viper pilots (now F-35) that they don't rotate at all.

I can confirm by speaking with two Viper pilots that the current pedal animation is wrong. The pedals move straight in and out without turning.

I have nothing against Growling Sidewinder as a person, but I really don't understand why it's so interesting watching dogfight after dogfight after dogfight after dogfight after dogfight after dogfight... I like Grim Reapers when they do these "scientific" videos, and carrier landing challenges and such, but lately there just too much modern mods such as the F-22, F-35, AIM-260, etc made of guesswork which I don't find particularly interesting. My favorite channel is Redkite (when he does DCS) and Bogey Dope

Thank you! All your comments make very much sense! I just needed to edit a tiny error: trigger.action.outText("You have been spotted by " .. enemy .. ". Method : " .. det, 10) to trigger.action.outText("You have been spotted by " .. enemy:getName() .. ". Method : " .. det, 10)

I have a repetitive script running to check whether the player has been detected by any enemy unit. Either by radar, visual, optic, etc. This works fine until an enemy unit gets killed. Then I get this error: Here's my script: local function ScanZone(category, coalition, zoneName) local foundUnits = {} if trigger.misc.getZone(zoneName) ~= nil then local searchZone = trigger.misc.getZone(zoneName) -- new sphere searchVolume from searchZone local searchVolume = { ["id"] = world.VolumeType.SPHERE, ["params"] = { ["point"] = searchZone.point, ["radius"] = searchZone.radius, } } -- search the volume for an object category world.searchObjects(category, searchVolume, function(obj) if obj ~= nil and obj:getLife() > 0 and obj:isActive() and obj:getCoalition()== coalition then foundUnits[#foundUnits + 1] = obj end end) end if #foundUnits > 0 then return foundUnits end return nil end local function isPlayerDetected(enemy) if Unit.getController(Unit.getByName(enemy)) then local con = Unit.getController(Unit.getByName(enemy)) local target if Unit.getByName("Player") then target = Unit.getByName("Player") else target = Unit.getByName("PlayerTest") end local m = {} for det, enum in pairs(Controller.Detection) do if con:isTargetDetected(target, enum) == true then trigger.action.outText("You have been spotted by " .. enemy .. ". Method : " .. det, 10) return true end end end return false end local enemyZone = ScanZone(Object.Category.UNIT, coalition.side.RED, "themap") -- simple check to print the found units or no found units if enemyZone ~= nil then for _, object in pairs(enemyZone) do if object:getName() then if isPlayerDetected(object:getName()) == true then trigger.action.setUserFlag("6", true) end end end end Can anybody point me in the right direction?

Thank you, and nice flying!

Ahh... Thank you! So it's a kind of a mixture between user error and software bug. I've never killed myself so far when I was testing from mid air, but in real life I suppose you would do a high drag bomb run when flying so low. Again, thanks!

This happens so many times when I start cold, or hot from runway/ramp. Sometimes it works. If I test from midair just before bomb attack it always works. Master Arm is on, GBU's are powered ON, everything as far as I know is within parameters with the CCRP symbology Please look at this track file. Is it a bug, or is it something I miss? Sorry for the long track, but I can't recreate this if I spawn midair in front of the target. EDIT : And yes, I'm pushing the weapon release button. At the end of the parameter range on this track, I even held the button down several seconds. Viper_GBU-31_wont_release.trk

Who is creating the Chinook?