All Activity

HARM seems to be able to see targets even when at the side of it. It should not have such a wide FOV LastMissionTrack.trk

nullHi, I hope you enjoy the summer as much as I do. When you select BORE mode in dogfight/ACM mode, what range are you seeing or using in your sim or reference? Is it supposed to be 10nm like HUD and vertical scan, or 20nm as some manuals claim? Because looking at the HSD its looks like it's 20nm. Can anyone please confirm if its 20 or 10. Thank you for you assistance in this matter.

Yes it was a typo on my part M2 _4 & M2_5 Still a bit pissed my Ram won't be here till next Wednesday. Every Laptop I buy has always been Intel and for PC it's AMD.

Against IR missiles also consider cutting the throttle while pulling Gs and dumping flares.

Lossless Scaling does not work with VR. For upscaling in VR there is DLSS and FSR. Generation of additional frames in VR is done by the respective compositor reprojection methods.

ParkControl shows no effect! But strange: I could avoid massive freezes while taxiing on airbases on Iraq-map with an old trick I noticed in the freezing-thread: Task manager/DCS.exe/Set processor affinity/Activate only 1 core (No. 1)/Ok/Then activativate all 4 cores/Ok! Result: No freezes anymore, strange! Any way to automize this process?

Demands and requests are very different things. A demand is accompanied by a threat, implicit or explicit. No such thing as a friendly or polite demand.

No problem and I understood. Are we seeking more FPS in VR by this app generates more artifacts also?

Dear all, during the last DCS update we had a build mishap and the DCS: OH-58D Kiowa was returned to a previous state. We apologise for this mistake and will ensure it is corrected in the next update. The following changes will be included in the next update: DCS: OH-58D Kiowa Warrior by Polychop Simulation Fixed: All digital data on dash detaching from dash on NAV SETUP page Fixed: Perf Page CALC button requiring two button presses Fixed: Hog menu CLASSIFICATION, PRECEDENCE, ACKNOWLEDGE lead to an endless loop Thank you for your understanding. ED Team

Kind of wish they worked it out, but if VEAO was using docs they weren't allowed to share with a foreign company (ED is officially Swiss, but the Russian connection had caused trouble before), we might have dodged a liability there. This is a gray area and the Brits are notoriously cagey about their military hardware. In any case, it's better if ED has all that stuff in case the devs disband for any reason.

Didn't read that in a changelog, but then, it wasn't a placebo effect. Nice

Tried it and now i can fire 2 or more rocket pods in pair.. thanks!

This is invaluable feedback of what the customer wants. Not necessarily what he actually needs. Those things don't always overlap. Customers want a lot of things, but that doesn't mean these things are good uses of dev time, or even particularly useful. This is especially acute when we're talking business apps and the request is about buzzword compatibility with something an exec read in a pamphlet at a conference (implement blockchain in the CRM system? We'll get right on that...). Take Vulkan, for instance. Compared to things like the F-35, it's not particularly shiny unless you already know a thing or two about rendering. It's only even being asked for because DCS is a notorious performance hog and people hope it'll help with that. However, it is necessary for both improved visuals and ongoing performance improvements, so we need this change more than most people think.

There seem to be very different understandings here as to what the word 'demand' means.

This is just a joke I would like to make it perfectly clear that this was a joke.

Anyone has idea (some tools) how to figure out what could be hole's diameter. Picture frame (focus) was not taken very happily and I think diameter is not so small as it looks on first view. R-77-1 of course is on picture. Actually I don't even know nozzle exit diameter so that info would be also appreciated

That seems to have done the trick. Microswitch logic set to auto off and bound a toggle switch on my throttle quadrant for the microswitch on/off. Using the physical toggle switch lets me know the on/off position. It is much better now, thank you all.

I have experienced this in the past as well. I'll see if I can get a track this weekend.

Crash Again dcs.log-20250731-140650.zip

there is no optical guide in DCS SAMs

Yeah, except:

Missed that, thanks.

I buy all components at the local hardware shop (walking distance from where I live), and then build the system myself. They don't care about branding: as long as the item is within legal warranty, you get another one But then again we all have our preferred brands, and brands we tend to avoid...

I didn't want to start my own thread, so if you don't mind me adding something here- it seems the update removed 'mouse' as bindable in a few categories. In every module that supports it, I have my kneeboard toggle set one of the mice side buttons, as well as the comms menu. flying after the update, comms menu wouldn't open. So i checked and the mouse can no longer be bound in the communications category. Strangely enough the kneeboard toggle is still bound and the mouse binding hasn't been removed from it. Only a minor inconvenience but thought I'd inform you

That's what I gathered. But I was specifically referring to radio triggers and random conversations with Petrovich: if you take the long route, you never get told to switch to the Bagram Tower frequency. I just did the mission again (3rd time), this time taking the short route and the trigger to switch to tower was there.