All Activity

Hi Qcumber, I am using a Somnium VR1. With my old PC it took so long to open DCS, that I had time to turn off Steam VR when it popped up after I clicked the DCS desktop icon, allowing DCS time to load in flat screen mode, no problems. However, with my new faster PC, DCS loads so quick now that no matter how quick I am to shut down Steam VR when it pops up, I can't win and it then shuts down DCS as it is loading because I have just turned off Steam VR, lol. Result is that I am having to uninstall Steam each time I want to work on DCS in flat screen mode, otherwise I can't get DCS to launch as I want it. LOL Happy landings, Talisman

I am the first to take off, after having carried out the procedure to be directed by the personnel on the flight deck (salute), I wait more than 30 minutes and I still have the message; Awaiting personnel. The problem is related to parked planes, maybe a DCS bug?

Its a map where timeframe wise it was still occupied by the japanese.. Its a ww2 map. I dont see your point. You have the modern variant of it aswell in dcs.

Hi, I just realize that my DCS dedicated server does not have a region while I search my server through the DCS multiplayer screen. I though the region should be based on the IP address that is landed in the specific region, but it seems not. What is the step that I have missed. Thanks.

If it's anything like the Viper it'll be released completely under cooked and then take years to gradually fix and complete (it'll soon be 6 years and we only just got a pilot body)

Hallo miteinander, ich habe eine Frage zum „Verschwinden“ von KI-Flugzeugen nach der Landung. Also: ein KI-Flugzeug soll bis zur finalen Landung überleben, darf nicht abgeschossen werden. Falls doch, löst der „Einheit tot“-Trigger weitere Trigger aus, die NUR bei „tot“ entstehen dürfen. Jetzt passiert es aber, daß das Flugzeug erfolgreich landet und nach einiger Zeit dann einfach verschwindet. Und genau dieses Verschwinden wird vom Mission Editor auch als „tot“ gewertet. Und so werden die Tot-Trigger ausgelöst. Wie kann man dafür sorgen, daß das Flugzeug nach der Landung auf dem Parkplatz bis zum Spielende stehen bleibt? Es soll nicht verschwinden. Wieso tun Einheiten das überhaupt? Danke im Voraus für Vorschläge / Erleuchtungen!

That's right. That's why I'm conveying my wish to ED. The management of ED should stop lying and deceiving customers, selling worthless products and chasing money, and think about making something better. Then my wish for Supercarrier will be easily realized. This is exactly the kind of post that should be on Supercarrier's wish list. I'm not dealing with people who are hired by ED to protect ED and criticize me. Rather, you are the ones who are not worthy of this place and are obstructing the conveyance of my legitimate wish.

Ok. Thanks.

Hello all, I'm a blind gamer who would *love* to dive into DCS World. I'm prepared to invest in real hardware (HOTAS, cockpit panels, head tracking), study the systems, and take this simulation as seriously as anyone else here. But right now, **DCS is effectively impossible to play without vision.** The good news? It doesn’t have to stay that way. --- **Why DCS Is So Promising for Accessibility** Unlike many other flight sims, DCS already has a modular, data-rich cockpit interface via [DCS-BIOS](https://github.com/DCS-Skunkworks/dcs-bios). This ecosystem exposes: * Cockpit states * Gauges and indicator lights * Radios and communication panels * Weapon systems * MFDs, HUDs and more (and [MFD label support is actively being developed](https://github.com/DCS-Skunkworks/dcs-bios/issues/1208)) These values can be used to generate **spoken output, sonification, or braille** — but in practice, that potential is locked behind huge technical barriers. --- **Where Accessibility Hits a Wall** Right now, the available tools are unusable without vision: * Web-based interfaces like `dcs-bios-webinterface` are entirely graphical and not usable with screen readers like NVDA or JAWS * The raw data (e.g. `0x3B7F: 65534`) is meaningless without deep knowledge of each aircraft’s internals * Python connectors exist, but are poorly documented or incomplete * Input/output mapping must be configured *per aircraft*, often manually, with little abstraction Even as a tech-savvy user, I simply can't build a usable interface from scratch without sight. --- **What Would Make a Real Difference** This isn’t a request to redesign DCS itself — just to improve how data is exposed via DCS-BIOS and related tools. **Example: Accessible MFD Output** Thanks to the work now underway by the DCS-BIOS team, we may soon be able to retrieve MFD button labels dynamically. If exposed in structured JSON: ```json { "mfd_left": { "B1": "NAV", "L3": "WP1", "R4": "TGT ACQ" } } ``` This could be spoken aloud or navigated via keyboard — unlocking full MFD usage, including targeting and nav functions. **Example: Radio Panel Readout** Instead of: ``` 0x43A0: 121500 ``` We could have: ```json { "radio1_frequency": 121.5, "unit": "MHz", "mode": "AM" } ``` Spoken as: > "Radio 1: 121.5 Megahertz AM." **Example: Status and Warnings** ```json { "master_caution": true, "gear_down": false, "fuel": 35.2 } ``` Spoken as: > "Warning: Gear is up. Fuel at 35 percent." **Input Mapping** * DCS-BIOS already supports input via serial or UDP * Physical buttons or keyboard keys can be mapped (e.g. G = Gear Toggle) * This could be defined in JSON configs without needing to write custom code --- **Audio Interaction Already Works — Just Not in DCS** Blind players already enjoy: * **MSFS / FSX** using TTS plug-ins * **Elite Dangerous** with audio-based MFD mods * **X-Plane** via structured plugin data * Even **Star Trek bridge simulators** with full voice interfaces But DCS has the **best cockpit data access of all** — and we're not using it for accessibility. --- **What I'm Asking** 1. Expose DCS-BIOS output in structured, documented JSON 2. Provide a schema per aircraft — so values have context 3. Create a CLI or screen reader–friendly monitor for DCS-BIOS 4. Involve accessibility-focused testers — I’m happy to help --- **Why It Matters** DCS is one of the most realistic combat simulators ever created. With only minimal changes in how cockpit data is structured and surfaced, it could become **the most accessible one, too**. The technology is already here. What’s missing is **visibility and intent**. Let’s fix that — together. > PS: This is also posted to the DCS-BIOS GitHub: > [https://github.com/DCS-Skunkworks/dcs-bios/discussions/1207](https://github.com/DCS-Skunkworks/dcs-bios/discussions/1207) --- **One More Thing: `Export.lua` – An Untapped Ally** While DCS-BIOS is an excellent bridge to the cockpit, it's worth noting that `Export.lua` can be used **alongside it** to expose additional flight data: * Speed, altitude, heading * Aircraft state, sensor values * Cockpit lights, warnings, and targeting info * Even some data **not available through DCS-BIOS** This makes it possible to build **custom assistive tools**, voice-controlled UI layers, or sonified interfaces — all without changing the simulator itself. If anyone in the community has explored this route — or is working on accessibility, speech interfaces, or similar solutions — I'd love to connect. Let’s share knowledge, collaborate, and push this forward.

I found a post a few days ago that recommended turning both on, but setting the dead zone to zero on the Special menu page. Then setting a small dead zone for each axis in the Control section. I set a small, 3-5% dead zone on each axis and saw a noticeable improvement on mine.

I take it "Eye tracking off" also implies FR off. Also: no quadviews? Don't think eye tracking in it self does all that.

This is a weird one. Last night I noticed that DCS wasn't reading the full output of TrackIR correctly for pitch. In other words, when I look full up with TrackIR, DCS only sees half of that input. To test this, I chose "tune combo axis", and the square cursor was only showing 45% the movement. I checked TrackIR, and it was putting out the full 90 degrees of up. DCS just wasn't seeing it. I had been playing around with OpenTrack software for a week. So, I then closed TrackIR and used OpenTrack. Looking "full up" in OpenTrack, DCS now sees "full up". My working assumption here is that since OpenTrack is viewed by DCS as "TrackIR", playing around with with OpenTrack again had corrupted the way that DCS "reads/polls" the output of real TrackIR. This is sort of confirmed by clicking on Rescan Devices in DCS while looking straight up with TrackIR. After doing this a few times, DCS started seeing 75% of that pitch, up from just 45%. Does this make any sense? It's hard to explain clearly. Thanks! -Ryan

I too have been interested in OpenXR Toolkit, but this advice on the Github site has stopped me; "AS OF 2024, SUPPORT FOR OPENXR TOOLKIT IS DISCONTINUED. THERE IS NO NEW DEVELOPMENT AND NO TECH SUPPORT OF ANY SORT. THE DEVELOPER DOES NOT RECOMMEND TO INSTALL/USE OPENXR TOOLKIT, AS IT IS KNOWN TO CAUSE ISSUES WITH MANY OF THE NEWER GAMES RELEASED IN SINCE 2024" Any comments on the above statement?

There is a OH-6A in my second "special project". We need the AH-6J now!

Hand raised, here in the UK too!

Hi ! As in the title, I can't contact the LSO after a bolter or a Wave off. How can I do ? Before, I could. Thanks

https://www.goodmorningamerica.com/video/123919720 and the airliner's pilot words:

folks just a pre-emptive message. Please stay away from politics in this thread thank you

I imagine it must have been rough for the man to see what the country he fought for turned into in his final years.

Could you please send a screenshot how it looks for you ingame? Make sure you are looking at the window around the HUD area, not the canopy area.

I cannot select or drag any of the tools around with my mouse ie. The black box when I try to select is the same place that toggles the pencil on and off. the bar at the top , I cannot interact with it

The FF module will model many of this aircraft’s systems very differently from the FC version which many of us have been flying. So there will be a lot to unlearn and, then, relearn. It would be extremely helpful to have the manual released prior to the module. That would decrease the frustration level for folks who haven’t spent time wading through the available Russian language. At least this would give folks a chance to see what’s changed before the module arrives.

I have one more question: How do I activate Turbo Mode? I think there was a catch in older tools. It's missing in the current version. When I activate Turbo Mode on the VR, I get the warning "...prevents ASW." Does it even work? What else do I need to configure? Thanks. PS: Can/do I enable advanced options in the tool? If so, where can I find them?

A Mirage III will be build by other 3rd Party.

Hi all, just a few points, raptor probably touched on them in previous comments, but here we go. 1) The colour of a bugged target tracked by the onboard FCR without datalink contribution can be altered by DTC colour settings, and the current FCR chapter in the DCS manual is from an earlier version of the DCS F-16 that was using a different colour (yellow) than what exists now in the game (white). Neither is incorrect, but it represents a pilot-configurable item within the DTC settings. 2) The Air Target Data Table (ATDT) rules that govern the colour and shape of an FCR symbol as Friendly/green, Unknown/white, Suspect/yellow, or Hostile/red should be the same regardless of whether it is detected by the onboard FCR or not. The only bug that is present is that these rules are being applied for targets detected by the onboard FCR but not for offboard datalink tracks. This is intended to be addressed along with the corresponding DTC feature. The FCR chapter is being revised and updated to the current DCS F-16 state, and future DTC settings in development should provide players with the ability to configure symbology colours and select which rules the ATDT uses to affect the target symbol colour and shape. additionally: When datalink is applied to the FCR display, the scheme of what governs "solid" vs "hollow" target symbols is altered, to include TWS mode. As Raptor stated above in his explanations, you must still have sufficient radar track data to bug a target for an engagement, but if datalink information is applied to the FCR display, using the "hollow" symbol state as an indication of this will not be available due to how the datalink correlation is represented on the MFD. Again, a more thorough explanation will be provided in the revision of the FCR chapter. thank you