Search the Community

Hi everyone, this is certainly not a new request – it has been raised several times by the community – but I would like to submit it again here in a more structured and reasoned form, as it would be a real benefit for many users. The main idea is to decouple the HMCS/HMD display so that it can be used together with head tracking. This would especially help DCS users flying aircraft like the A-10C II who have built advanced home cockpits, but do not use VR – instead relying on large projection screens or multi-projector setups. The core problem: For cockpit builders without VR, the physical environment (screen, cockpit structure) remains static relative to their head position, while the HMCS should move dynamically with the head, as it would in a helmet-mounted system. In these setups, the symbology is often difficult or impossible to see, especially when spread across a large screen area. This could likely be addressed via a relatively straightforward head tracking–based rendering of the HMCS in a separate, exportable viewport. I'm aware this would require a native implementation by the developer, and that workarounds are either non-functional or too complex. VR is one way to solve this – but not a viable option for all users. I’m sure I’m not the only one with this request – and it would offer great value for many in the DCS community. So to all users who would also benefit from this: please join in and add your support here. Other affected modules include: F-16C, F/A-18C, F-15E → all with HMCS systems AH-64D Apache, and others In all of these modules, having an exportable HMCS/HMD would be extremely helpful – especially for cockpit builders and more advanced setups. Since MFCD and sensor displays already support viewport export, the HMCS should be no exception. Thanks again for your ongoing work and the continued development of this outstanding simulation!

Hi. I'm currently working on my Home Cockpits. Since I'm not trying to use VR for several reasons, so I decided to imitate Warthog Project method. So - I'm working on Panels, and Switches.. These are doing good so far. But My problem is... I'm thinking of using TrackIR or Eyetracker for HMCS. And at the same time, I'm trying to use a projector for screen. The question is... Can I allow DCS to render HMCS display according to my head movement while overall camera orientation unchanged?

1 to turn on the hmcs scorpion system 2 uncategorized the backup adi when in cold start. 3 mirrors toggle I'm sure there is some more . But I just csnt think of them atm . Would like to be able to fully start and operate the A-10C II with out ever touching a mouse.

After coming back from a small hiatus, I noticed that my HMCS screen isn't centered on my main screen anymore and that the horizon line in the HMCS isn't static anymore as well. When I roll my head left or right with my TrackIR, the horizon line and any other HMCS symbology move around, making it almost impossible to use. This is all being used with a custom monitor lua that I set up to have my lt and rt MFCDs on my second screen to the left. When I go back to just using one screen and it's native resolution, the HMCS works as advertised though. My native resolution is 1920x1080, and as said before, HMCS works as advertised at that resolution. My custom monitor lua that includes the MFCDs on the secondary screen, the resolution is 2480x1080. I have attached pictures as a reference as well, those with the MFCDs on the right is my custom lua showing the horizon line moving up and down "floating" along with the SPI as I roll my head. The others that don't have the MFCDs on the right are native resolution and showing that the horizon line doesn't move while rolling my head. Would anyone have any idea on how to get the HMCS to stay static while also keeping my custom lua? Thank you in advance for any and all help.

JDAM 2000 gets shot down by enemy anti-air. Radar locks onto enemy/friendly missiles very easily, can't lock helo behind missiles. HMCS is not showing when on the ground, have to be in the air to calibrate JDAM Time in Trk: 01:22:30 Foothold_Caucuses_Extended_1.0-20231101-204021.trk Tacview-20231101-194939-DCS-Host-Foothold_Caucuses_Extended_1.0.zip.acmi