All Activity

I just started this campaign and after shooting down 10 bombers between my wingman and myself I RTB'd to Anderson to find a bomber dropping bombs. No additional dialog from anyone after I started engaging the bombers. When I reported inbound to Anderson ATC told me to go to my alternate. I ended up diverting to Saipan and ended with a draw for a result.

Wondering whether pilot are able to direct control radar in the upcoming new plane, or it could still be controlled only by RIO?

I just received my replacement TQS after some of the switches failed on my previous version. My issue is that none of the switches work in the off position, and this also applies to the Gear switch as well; for example, in DCS, I can bind the gear up position, but not the gear down position. I can bind the CAT 1 position, but not the CAT 3 position. This applies to all buttons and switches on the throttle. Although with some of the switches, I can select the button off option for binary functions, I cannot do this with the OFF option in the MODE switch or the BIT option on the Program switch. I had no issues with my previous the version of the Viper TQS and I didn't even need to install any drivers for it. It just worked perfectly out of the box. I thought it might be an issue with Thrustmaster switching to virtual buttons, but I could not find any options in Windows 11 , or in the TARGET software to enable virtual buttons. Any suggestions?

ED has a lot to do,

Thanks for the heads up! [emoji1303] Sent from my SM-A536B using Tapatalk

Idk they just moved it here for some reason

Are these planned for public release? I spent a few weeks in Czechia and love their aircraft paint schemes.

I'll check out your vid when I have time. Typically I avoid videos since I need written text and ctrl+F capability to find the info I'm looking for; also cellular data consumption

I flew this mission twice to verify that these are not just random, but repeatable as of version DCS 2.9.20.15384 (September 2025). The loadout (x2 AGM-65F, x4 MK82) still does not match the briefing (4 AGM-65F). The Hummer turns off taxiway before leading Stryker to Runway 05 as ATC directions state. Wingman will never engage the dam targets, but claims credit when I hit them for him (your welcome!). I finally get the opportunity to F10 order everyone to hit the airport after I've already taken out all three helicopters. Lastly, when returning to base, wingman goes to a different parking spot than we started at. I just drove through our original parking area (parking spot 95) and then all the aprons trying to get some sort of message. Eventually I just parked next to my wingman (who is stopped in hanger 03, which is not where we started), and lost 10 points for not parking in the correct place.

Polly, It's been a while. Would you like to have a drink with me sometime, just to catch up? Orni

If ED gets new info and changes the modeling in 6 months-5 years I expect an extra gift!

Many other aircraft have the same HUD...'bloom'...is perhaps not the right term - but where increasing brightness (or even mild FOV changes) corresponds to fatter/fuzzier fonts. The Mig-29 isn't the worst offender but like most other green HUDs I find myself reducing the brightness to sharpen the image immediately on entering the cockpit. I hope ED will one day give some love to the HUD elements - they look like overlays rather than projections on glass (Razbam's Harrier I quite like though). The WW2 reticles in particular look like something out of a 90's era flight sim. There must me some fancy new GFX card trickery available to up the realism?

From the most recent wags video https://youtu.be/HyiWR8UYfS4

so FFB is working correctly now?? excellent. i can try this bird out again

So. There are multiple problems with this idea. The core problem is its not NVGs. its the fact the COCKPIT, that has to be modified to work with them. 1: Soviets didn't have gen2 or much less gen3 NVG's operational anywhere in the relevant time frame of the 9.12 like not even remotely 2: Cockpits have to be modified for NVG's to even work at all in them. ED has historically done a terrible job in this regard, failing on every level to acknowledge this basic fact. Its well documented. 3. Even if you had some "western modified" "9.12" it wouldn't really be a 9.12 anymore and even then there is no evidence of NVG mods of that.

AH-64 (the whole reason I got into DCS all those years ago), A10CII, F-16. Recently discovered the new UH-60L v2.0 mod and been really enjoying that.

The chart is in my video above There really aren’t many for Fulcrum “fuel flow per speed and altitude” charts, though there are more for “fuel used for climb/descent with xx payload”

I don't have force feedback but I just checked & the force feedback option was checked. I unchecked it & will see if it has any effect.

I've been struggling with AA recently, my solution which looks hugely better is using reshade and the TAA shader along with MFAA 4 and turning MFAA related stuff on in nvidia panel.

The real-world Luftwaffe manual has much more understandable wording for explaning this system: In TAC the remaining flight distance is calculated based on current fuel flow and ADC data. In OPT the remaining flight distance shows the max possible range "with an optimized calculated fuel flow." I believe this would be referenced through charts, however my manual is incomplete and missing said charts.

About our beloved sim, seems to reveal a distinct lack of game design on behalf of ED. This is perhaps obvious but is there any discussion around this topic? Why not allow the community to build the 'game part' of this sim? As much as i love DCS i find that my experience on it today is much the same as it has always been going way back to lomac. Pretty disheartening. Regards

Two of those logs show you've added Quad-Views-Foveated, recommend removing OpenXR Toolkit if you're running that in general. The logs don't show a crash itself so it's more likely that Windows is killing the process. Can you run the Windows DxDiag tool, save the output, and then attach it here as well. I'd highly recommend you remove your mods, run a repair, and delete your Saved Games\DCS\fxo and metashaders2 caches. Mods can cause issues so may be something conflicting with that module and not others. Additional items: You can remove the "force_OpenXR" parameter from your shortcut as the game is entirely OpenXR. I'm assuming your other params are so you can have both VR and 2D shortcuts? You have core parking enabled. You can use the ParkControl software to disable core parking for your power management profiles. Having this enabled can cause stutters. I'll wait for the DxDiag report as that will likely have more info re: system issues and if/why Windows is terminating this.