DrGonzo94

I also have this problem. Antenna elevation keys work, but only with keyboard keys. Even if I unbind all bindings, antenna elevation CW/CCW are still marked by a red exclamation mark. No button on my hotas will work on antenna elevation. All other bindings works, including with hotas buttons. edit: Was able to rebind after restart.

I don't know In the end, I reinstalled my virual machine and redid it following this instructional: It's sort of the same as I've done things before, but with the debloating and diabling of unused network features in windows. Now it works! And I'm not changing anything ever again

Sorry for answering in and old thread, but I wanted to say many thanks!, as this completely solved my issue of having different "RIGHT_MFCD" for different modules, F-16 was the one making the most fuss. I just thought I'd point out that the MFD-init files are located in \DCS\Mods\aircraft\F16\cockpit\Scripts\Displays\MFD\indicator and that the config.lua file is located in \DCS\Mods\aircraft\F16\cockpit\Scripts\. This wasn't apperent to me initially. edit: Apologies, I spoke too soon. I have the same problem as described earlier in thread with the main cockpit LCDs going fuzzy and dark. Has anyone found a fix for this? edit2: Got everything working now, good looking MFDs on both secondary monitor and in cockpit. Here's what I did: 1. Change viewport names in MFD_*side*_init.lua. 2. Change viewport names in \DCS\Mods\aircraft\F16\cockpit\Scripts\Displays\MFD\indicator\LCD\MFD_LCD.lua 3. NOT change config.lua setting to false.

Just wanted to say, excellent thread guys! Solved all my Mirage dual screen and viewport problems!

I run into this problem no matter what I do. Running a dedicated open beta server from desktop works fine, but when I try to start one from my server, it will not list in-game, and mostly will not be accessible from outside my network. I've tried running in a VM inside Truenas, a VM inside TrueNAS running on Proxmox and now a instance running on Debian with Wine, inside a LXC container in Proxmox, all with the same result. I've checked and double-checked ports in router, checked versions, opened ports in Iptables, disabled proxmox firewall, tried different ports, tried different DCS acounts - nothing helps. Looking at the log file I see "ConflictInMappingEntry" fails for both ports 10308 and 8088, but I cannot analyze the significance of this. dcs.log

Just wanted to say THANK YOU! This has been low-key bugging me since I got the throttle, and your solution is exactly what I was looking for!

I'm inclined to agree with this. With CA disabled the bug appears much less often.

Yup, the bug appears as meltingSnowdrift describes it, every time. It's the same bug described in this thread. edit: spoke too soon again, it worked the first two times, but now I cannot reproduce it anymore. Instead the wallpaper disappeared from the main screen, unclear if related.

Can CONFIRM that this issue disappears when disabling Combined Arms. Maybe it would be constructive to have someone with a AMD gpu investigate this issue, seeing as 100% of people affected have AMD gpus? Can also confirm that this bug seems to disappear if you disable Combined Arms. edit: Apologies, spoke too soon. This bug still exists with Combined Arms disabled.

I get this too, trim is always slightly off, and different to all other helos in "Central Position Trimmer Mode". Feature or bug?

I got latest version of game and latest version of AMD drivers. Problem persists. And the log file.. dcs.log

I can confirm this bug on every multiplayer server I played on. They all have CTLD. I have not tried it in singleplayer. I have not tested exhaustively, but general feeling is that some waypoints added are ignored. I usually get reasonable results if I create two waypoints close to each other, where I would usually use one.

Same issue, AMD Radeon 6800. dcs.log

Hi, did you find a fix for this? I got the exact same thing.

I have this exact thing, too. Server says it's up, it shows up on "My Servers" list when logging on to https://www.digitalcombatsimulator.com/ server page. It can be accessed and administered thru webgui. But it does NOT show up on server list in-game. Had server with exact same setup before, then it worked without problems. Server is on a Windows VM in a TrueNAS-server.

Hi, not sure if this is feature or bug. I haven't seen it mentioned in changelog or on forums, so I thought I'd mention it. When using AIM-9 (mostly X, but true for M as well) the BORE functionality with HMCS has turned from functioning both horizontally and vertically to functioning horizontally only in one of the last betas (I'm currently using 2.5.6.58125). To be clear, when using HMCS to lock AIM-9X to enemies, looking sideways still works well, but missile seeker ("missile diamond") does not follow HMCS sight when looking up or down. I've tried different setups and modes, and behaviour is completely reproducible.

Then you probably have a different problem, my friend.

Hallo, thanks for a great mod! I trying to find a full and current unit list for DCS, with technical names included, for use with the CTLD config file. Found an old one on a steam forum, but haven't been able to find a current one.

I followed this guide, it worked before, and it works now. Clear mouse axises Set a modifier Set each axis with modifier and then use axis tune to invert each one. Then set mouse axis without modifier for each axis for regular in-cockpit use.

Yup, the method I described above works again in openbeta 200930 update, and also 201002 update. edit: Sorry, didn't properly read your question. It works for all modules I'm using (AJS37, F-16, Mi-8, FC3, Ka-50, among others). If I remove mouse look settings, mouse look is disabled. Default mouse look settings are the same as they were before 200930 update.

Functionality seems restored in open beta update 2.5.6.55743 (200930). Thankyouu ED

I concur. I have had settings for mouse look to invert all axis with a modifier (because DCS has these settings backwards in external views, compared to every other game I play). This does not work anymore, and furthermore the settings for the mouse axis seems to make no difference whatsoever. No matter what I put in there, the game uses default settings. I tried resetting the settings for "General" and "UI Layer" as well, but to no avail. edit: Just to be clear, this is for the Open Beta 200923 update. Release version is unaffected.

Mouse look binding got broken in 23/9 update. I used an inverted external look by setting mouse look with a modfier, and inverted axis. Can't get it to work now, no matter what I try.

I think I have this issue as well. Not completely sure about the new modes yet, but trying to do CCRP bombing can result in HUD marking and CCRP guide pointing to some point that is definately not the target, even though target is properly set in the TGP.

You're quite right, thank you.