dresoccer4 Posted October 1, 2024 Posted October 1, 2024 (edited) I've asked this before but solution. I have the dreaded red explanation mark for the CH-47F for only a singe command: camera transpose mode. As you can see there are no key bindings, and yet it's still red. What I'm trying to do is add mouse_btn2 to the command, but it's giving a red mark too. There are definitely no other commands tied to mouse_btn2. How do I fix this? Edited October 1, 2024 by dresoccer4 Acer Predator Triton 700 || i7-7700HQ || 512GB SSD || 32GB RAM || GTX1080 Max-Q || FFB II and Thrustmaster TWCS Throttle || All DCS Modules
scommander2 Posted October 2, 2024 Posted October 2, 2024 I was used to have these red marks because I was on ST and switched over MT (May not be same as yours), then I went back ST once and switched over MT and it was cleared. Personally, I do not think that mime is the solution since ST is gone. I posted the same issue in the previous ED release. No answer since... I need to check if I can find a red mark in my current DCS and I can try the ED tech support... I am not sure... Spoiler Dell XPS 9730, i9-13900H, DDR5 64GB, Discrete GPU: NVIDIA GeForce RTX 4080, 1+2TB M.2 SSD | Thrustmaster Warthog HOTAS + TPR | TKIR5/TrackClipPro | Total Controls Multi-Function Button Box | Win 11 Pro
scommander2 Posted October 2, 2024 Posted October 2, 2024 I have created a ticket "How to clear red exclamation marks in the control keybindings" with the ED tech support... let's see... 1 1 Spoiler Dell XPS 9730, i9-13900H, DDR5 64GB, Discrete GPU: NVIDIA GeForce RTX 4080, 1+2TB M.2 SSD | Thrustmaster Warthog HOTAS + TPR | TKIR5/TrackClipPro | Total Controls Multi-Function Button Box | Win 11 Pro
scommander2 Posted October 2, 2024 Posted October 2, 2024 ED tech support got back to me for my screenshot: Quote Do the red exclamation marks you're seeing affect the functionality of the assigned buttons? If you're still able to use the keys or buttons tied to those actions, it might be a display issue. However, if the exclamation marks are disabling the actions, they may indicate conflicts or issues in the control bindings that need resolving. I never use this item for any button assigning... how can it be a conflict there?! Interesting.... 1 Spoiler Dell XPS 9730, i9-13900H, DDR5 64GB, Discrete GPU: NVIDIA GeForce RTX 4080, 1+2TB M.2 SSD | Thrustmaster Warthog HOTAS + TPR | TKIR5/TrackClipPro | Total Controls Multi-Function Button Box | Win 11 Pro
virgo47 Posted October 2, 2024 Posted October 2, 2024 Is there no tooltip on it? I've seen these in a couple of situations: Binding uses a modifier that was not configured - this is likely not your case. When this happens the offending binding is not even shown, so it can appear on an empty cell as well. Conflicting binding. This happens to me when I import a diff file (Input config) that does not remove the default binding for the plane and uses the same binding for something else as well. If it is in the same config, just try to press that combo repeatedly (click on the table first to focus on it) - it should cycle through all the bindings for the same combo. Conflicting binding with another layer, e.g. UI Layer. Obviously, different aircraft configs don't conflict with each other, but some config layers are used at the same time (plane + UI Layer, not sure about others). Strange cases. Sometimes I see it, restarting the game helps, or saving/loading the input config, etc. This can be caused by loading a diff file for another config (by accident or with a good reason) or when the changes in the system/aircraft defaults binding suddenly (e.g. after the DCS update) collide with your existing stuff in Config/Input. 1 L-39, F-4E, F-5E, F-14, F/A-18C, MiG-15, F-86F, AJS-37, C-101, FC2024 Yak-52, P-47, Spitfire, CE2 UH-1H, Mi-8, Ka-50 III, SA342 NTTR, PG, SY, Chnl, Norm2, Kola, DE Supercarrier, NS430, WWII, CA VKB STECS+Gladiator/Kosmosima+TPR DCS Unscripted YouTube "Favourite" bugs: 1) Object local camera fast/slow inverted, 2) Yak-52 toggles not toggling, 3) all Caucasus ATC bugs
scommander2 Posted October 2, 2024 Posted October 2, 2024 Hi @virgo47, thanks for all hints... I found the tooltip does complain what the conflicts are: Personally, I never change the keybindings in General and UI layer. But the tooltip tells me that it is a conflict in the UI layer.... Since no tooltip and no binding is set... Not sure how to reproduce it. 1 Spoiler Dell XPS 9730, i9-13900H, DDR5 64GB, Discrete GPU: NVIDIA GeForce RTX 4080, 1+2TB M.2 SSD | Thrustmaster Warthog HOTAS + TPR | TKIR5/TrackClipPro | Total Controls Multi-Function Button Box | Win 11 Pro
virgo47 Posted October 2, 2024 Posted October 2, 2024 This one is notorious since some update. Some things were moved to UI Layer (which was a good unifying change). Some were left in other layers. I just fixed it on my end and moved on. I always treat the UI Layer as the highest priority. 1 L-39, F-4E, F-5E, F-14, F/A-18C, MiG-15, F-86F, AJS-37, C-101, FC2024 Yak-52, P-47, Spitfire, CE2 UH-1H, Mi-8, Ka-50 III, SA342 NTTR, PG, SY, Chnl, Norm2, Kola, DE Supercarrier, NS430, WWII, CA VKB STECS+Gladiator/Kosmosima+TPR DCS Unscripted YouTube "Favourite" bugs: 1) Object local camera fast/slow inverted, 2) Yak-52 toggles not toggling, 3) all Caucasus ATC bugs
MAXsenna Posted October 2, 2024 Posted October 2, 2024 Hi @virgo47, thanks for all hints... I found the tooltip does complain what the conflicts are: Personally, I never change the keybindings in General and UI layer. But the tooltip tells me that it is a conflict in the UI layer.... Since no tooltip and no binding is set... Not sure how to reproduce it. More and more identical mappings across modules are moved to the UI Layer. I believe that's the issue. Make sure it is in the UI Layer and you can safely wipe it from any module. Sent from my SM-A536B using Tapatalk
Mike_CK Posted October 2, 2024 Posted October 2, 2024 I get it sometimes. On those occasions where there really isn’t a conflict and I can’t figure out what the issue is, the problem corrects itself if I restart the game. 1
MAXsenna Posted October 2, 2024 Posted October 2, 2024 I get it sometimes. On those occasions where there really isn’t a conflict and I can’t figure out what the issue is, the problem corrects itself if I restart the game.Does it stay corrected, or does it reappear? And if they reappear, will that be the first time you started DCS after an update?Cheers! Sent from my SM-A536B using Tapatalk
Solution BeforeBroadband Posted October 2, 2024 Solution Posted October 2, 2024 (edited) 'Camera transpose mode' has been doing this to me for a long time on every aircraft, regardless if I have anything bound to it or not. Hovering over it tells me nothing (see pic). It also renders 'camera transpose' non functional. The only thing that fixes it for me is to go to 'DCS World>Config>Input>Aircrafts>Common>Mouse', and edit the 'default' .lua file. This is what it normally says under 'keyCommands' in there: {combos = {{key = 'MOUSE_BTN2'}}, down = iCommand_ExplorationStart, name = _('Enable visual recon mode'), category = _('View Cockpit')}, {combos = {{key = 'MOUSE_BTN3'}}, down = iCommandViewTransposeModeOn, up = iCommandViewTransposeModeOff, name = _('Camera transpose mode (press and hold)'), category = _('View Cockpit')}, {down = iCommandCockpitClickModeOnOff, name = _('Force cursor to show on/off'), category = _('General')}, }, I notice it has mouse button 3 (middle click) listed for camera transpose, even though essentially every aircraft/crew position in the game uses a double middle click by default for 'Force cursor to show, toggle'. If I edit this lua by adding a third '{combos' like so: {combos = {{key = 'MOUSE_BTN2'}}, down = iCommand_ExplorationStart, name = _('Enable visual recon mode'), category = _('View Cockpit')}, {combos = {{key = 'MOUSE_BTN4'}}, down = iCommandViewTransposeModeOn, up = iCommandViewTransposeModeOff, name = _('Camera transpose mode (press and hold)'), category = _('View Cockpit')}, {combos = {{key = 'MOUSE_BTN3'}}, down = iCommandCockpitClickModeOnOff, name = _('Force cursor to show on/off'), category = _('General')}, }, the red exclamation mark goes away and restores camera transpose functionality. Slightly annoying that I need to do this after every update or if I run a repair. Edited October 4, 2024 by BeforeBroadband 3
MAXsenna Posted October 3, 2024 Posted October 3, 2024 'Camera transpose mode' has been doing this to me for a long time on every aircraft, regardless if I have anything bound to it or not. Hovering over it tells me nothing (see pic). It also renders 'camera transpose' non functional. The only thing that fixes it for me is to go to 'DCS World>Config>Input>Aircrafts>Common>Mouse', and edit the 'default' .lua file. This is what it normally says under 'keyCommands' in there: {combos = {{key = 'MOUSE_BTN2'}}, down = iCommand_ExplorationStart, name = _('Enable visual recon mode'), category = _('View Cockpit')}, {combos = {{key = 'MOUSE_BTN3'}}, down = iCommandViewTransposeModeOn, up = iCommandViewTransposeModeOff, name = _('Camera transpose mode (press and hold)'), category = _('View Cockpit')}, {down = iCommandCockpitClickModeOnOff, name = _('Force cursor to show on/off'), category = _('General')}, }, I notice it has mouse button 3 (middle click) listed for camera transpose, even though essentially every aircraft/crew position in the game uses a double middle click by default for 'Force cursor to show, toggle'. If I edit this lua by adding a third '{combos' like so: {combos = {{key = 'MOUSE_BTN2'}}, down = iCommand_ExplorationStart, name = _('Enable visual recon mode'), category = _('View Cockpit')}, {combos = {{key = 'MOUSE_BTN4'}}, down = iCommandViewTransposeModeOn, up = iCommandViewTransposeModeOff, name = _('Camera transpose mode (press and hold)'), category = _('View Cockpit')}, {combos = {{key = 'MOUSE_BTN3'}}, down = iCommandCockpitClickModeOnOff, name = _('Force cursor to show on/off'), category = _('General')}, }, this simple modification results in not only the 'camera transpose' red exclamation mark going away, but I also can then just middle click once instead of twice to toggle between cursor and looking around the cockpits. Slightly annoying that I need to do this after every update or if I run a repair. Make it a mod and use a mod manager? Sent from my SM-A536B using Tapatalk
BeforeBroadband Posted October 3, 2024 Posted October 3, 2024 I hadn't thought of that. I have so few mods that I never bothered with mod manager, but maybe it's time to look into it. 1
MAXsenna Posted October 3, 2024 Posted October 3, 2024 I hadn't thought of that. I have so few mods that I never bothered with mod manager, but maybe it's time to look into it.I make these small "mods" all the time. It's really handy, pre/post updates, and for testing!I'm using Open Mod Manager, as it's still in development, for the small stuff. For larger like texture replacement and sounds, with lots of files and writes. I have started using SLAM, which just "replaces" the files in seconds with symbolic links.Cheers! Sent from my SM-A536B using Tapatalk
Emacs Posted October 3, 2024 Posted October 3, 2024 I have that dreaded exclamation mark now at the "Throttle" command for the P-51, Spitfire and the Dora. P-47, 109, and Anton are fine. The axis are no longer used at all. The exclamation mark even stays when I assign nothing to the Throttle action at all. I haven't changed anything, neither hardware nor configs over the last months. Just the updates from the last few days. A bit frustrating I must admit...
Emacs Posted October 3, 2024 Posted October 3, 2024 (edited) Ok, found a solution in another thread: "use clear command on the "red" assignments, reboot DCS, only then reassign them as you wish. That should fix the issue." That worked for me. Cheers, Emacs Edited October 3, 2024 by Emacs 2
dresoccer4 Posted October 3, 2024 Author Posted October 3, 2024 16 hours ago, BeforeBroadband said: 'Camera transpose mode' has been doing this to me for a long time on every aircraft, regardless if I have anything bound to it or not. Hovering over it tells me nothing (see pic). It also renders 'camera transpose' non functional. The only thing that fixes it for me is to go to 'DCS World>Config>Input>Aircrafts>Common>Mouse', and edit the 'default' .lua file. This is what it normally says under 'keyCommands' in there: {combos = {{key = 'MOUSE_BTN2'}}, down = iCommand_ExplorationStart, name = _('Enable visual recon mode'), category = _('View Cockpit')}, {combos = {{key = 'MOUSE_BTN3'}}, down = iCommandViewTransposeModeOn, up = iCommandViewTransposeModeOff, name = _('Camera transpose mode (press and hold)'), category = _('View Cockpit')}, {down = iCommandCockpitClickModeOnOff, name = _('Force cursor to show on/off'), category = _('General')}, }, I notice it has mouse button 3 (middle click) listed for camera transpose, even though essentially every aircraft/crew position in the game uses a double middle click by default for 'Force cursor to show, toggle'. If I edit this lua by adding a third '{combos' like so: {combos = {{key = 'MOUSE_BTN2'}}, down = iCommand_ExplorationStart, name = _('Enable visual recon mode'), category = _('View Cockpit')}, {combos = {{key = 'MOUSE_BTN4'}}, down = iCommandViewTransposeModeOn, up = iCommandViewTransposeModeOff, name = _('Camera transpose mode (press and hold)'), category = _('View Cockpit')}, {combos = {{key = 'MOUSE_BTN3'}}, down = iCommandCockpitClickModeOnOff, name = _('Force cursor to show on/off'), category = _('General')}, }, this simple modification results in not only the 'camera transpose' red exclamation mark going away, but I also can then just middle click once instead of twice to toggle between cursor and looking around the cockpits. Slightly annoying that I need to do this after every update or if I run a repair. thanks for the detailed response. sounds like you had the exact same issue as me. i will try out your solution Acer Predator Triton 700 || i7-7700HQ || 512GB SSD || 32GB RAM || GTX1080 Max-Q || FFB II and Thrustmaster TWCS Throttle || All DCS Modules
BeforeBroadband Posted October 3, 2024 Posted October 3, 2024 Interesting how it usually seems to be Camera Tranpose that's the problem for most people when you search "DCS red exclamation mark" in google. The few other binding conflicts I had were kind enough to tell me what the exact problem was (all UI layer), but Camera Transpose has to make a nuisance of itself. 1
dresoccer4 Posted October 3, 2024 Author Posted October 3, 2024 (edited) 19 hours ago, BeforeBroadband said: 'Camera transpose mode' has been doing this to me for a long time on every aircraft, regardless if I have anything bound to it or not. Hovering over it tells me nothing (see pic). It also renders 'camera transpose' non functional. The only thing that fixes it for me is to go to 'DCS World>Config>Input>Aircrafts>Common>Mouse', and edit the 'default' .lua file. This is what it normally says under 'keyCommands' in there: {combos = {{key = 'MOUSE_BTN2'}}, down = iCommand_ExplorationStart, name = _('Enable visual recon mode'), category = _('View Cockpit')}, {combos = {{key = 'MOUSE_BTN3'}}, down = iCommandViewTransposeModeOn, up = iCommandViewTransposeModeOff, name = _('Camera transpose mode (press and hold)'), category = _('View Cockpit')}, {down = iCommandCockpitClickModeOnOff, name = _('Force cursor to show on/off'), category = _('General')}, }, I notice it has mouse button 3 (middle click) listed for camera transpose, even though essentially every aircraft/crew position in the game uses a double middle click by default for 'Force cursor to show, toggle'. If I edit this lua by adding a third '{combos' like so: {combos = {{key = 'MOUSE_BTN2'}}, down = iCommand_ExplorationStart, name = _('Enable visual recon mode'), category = _('View Cockpit')}, {combos = {{key = 'MOUSE_BTN4'}}, down = iCommandViewTransposeModeOn, up = iCommandViewTransposeModeOff, name = _('Camera transpose mode (press and hold)'), category = _('View Cockpit')}, {combos = {{key = 'MOUSE_BTN3'}}, down = iCommandCockpitClickModeOnOff, name = _('Force cursor to show on/off'), category = _('General')}, }, this simple modification results in not only the 'camera transpose' red exclamation mark going away, but I also can then just middle click once instead of twice to toggle between cursor and looking around the cockpits. Slightly annoying that I need to do this after every update or if I run a repair. here's what mine is showing: keyCommands = { {combos = {{key = 'MOUSE_BTN2'}}, down = iCommandViewTransposeModeOn, up = iCommandViewTransposeModeOff, name = _('Camera transpose mode (press and hold)'), category = _('View Cockpit')}, {down = iCommandCockpitClickModeOnOff, name = _('Force cursor to show on/off'), category = _('General')}, }, This seems to be correct as I want mouse button 2 to be the transpose (as shown in the first post). Any idea what I should do in this situation now? Edited October 3, 2024 by dresoccer4 Acer Predator Triton 700 || i7-7700HQ || 512GB SSD || 32GB RAM || GTX1080 Max-Q || FFB II and Thrustmaster TWCS Throttle || All DCS Modules
BeforeBroadband Posted October 3, 2024 Posted October 3, 2024 You're saying that's what yours shows before or after you modified the lua? Comparing yours with mine, I notice you're missing the 'Enable visual recon mode' combo, which is what my file lists as mouse button 2 by default.
dresoccer4 Posted October 3, 2024 Author Posted October 3, 2024 (edited) 2 hours ago, BeforeBroadband said: You're saying that's what yours shows before or after you modified the lua? Comparing yours with mine, I notice you're missing the 'Enable visual recon mode' combo, which is what my file lists as mouse button 2 by default. i haven't made any changes to the default cfg. i ddin't even know one was there. this is untouched. weird, eh? only thing i've ever messed with was module-specific keybindings. in fact i just updated DCS so all of these files would have been overwritten anyway if they were modified Edited October 3, 2024 by dresoccer4 Acer Predator Triton 700 || i7-7700HQ || 512GB SSD || 32GB RAM || GTX1080 Max-Q || FFB II and Thrustmaster TWCS Throttle || All DCS Modules
BeforeBroadband Posted October 4, 2024 Posted October 4, 2024 (edited) I just ran a repair and modified my default lua to match yours. Lo and behold, I got the red exclamation mark. Playing around with the lua, I believe I've found a fix for you. In your lua example, I then tried deleting only MOUSE_BTN2 so that it says {combos = {{key = ''}}, etc. When I booted DCS back up, no red exclamation mark, and assigning mouse button 2 worked flawlessly. Try that. Edited October 4, 2024 by BeforeBroadband 1
Rammi Posted January 15 Posted January 15 On 10/3/2024 at 1:11 AM, BeforeBroadband said: 'Camera transpose mode' has been doing this to me for a long time on every aircraft, regardless if I have anything bound to it or not. Hovering over it tells me nothing (see pic). It also renders 'camera transpose' non functional. The only thing that fixes it for me is to go to 'DCS World>Config>Input>Aircrafts>Common>Mouse', and edit the 'default' .lua file. This is what it normally says under 'keyCommands' in there: {combos = {{key = 'MOUSE_BTN2'}}, down = iCommand_ExplorationStart, name = _('Enable visual recon mode'), category = _('View Cockpit')}, {combos = {{key = 'MOUSE_BTN3'}}, down = iCommandViewTransposeModeOn, up = iCommandViewTransposeModeOff, name = _('Camera transpose mode (press and hold)'), category = _('View Cockpit')}, {down = iCommandCockpitClickModeOnOff, name = _('Force cursor to show on/off'), category = _('General')}, }, I notice it has mouse button 3 (middle click) listed for camera transpose, even though essentially every aircraft/crew position in the game uses a double middle click by default for 'Force cursor to show, toggle'. If I edit this lua by adding a third '{combos' like so: {combos = {{key = 'MOUSE_BTN2'}}, down = iCommand_ExplorationStart, name = _('Enable visual recon mode'), category = _('View Cockpit')}, {combos = {{key = 'MOUSE_BTN4'}}, down = iCommandViewTransposeModeOn, up = iCommandViewTransposeModeOff, name = _('Camera transpose mode (press and hold)'), category = _('View Cockpit')}, {combos = {{key = 'MOUSE_BTN3'}}, down = iCommandCockpitClickModeOnOff, name = _('Force cursor to show on/off'), category = _('General')}, }, the red exclamation mark goes away and restores camera transpose functionality. Slightly annoying that I need to do this after every update or if I run a repair. I have the same issue as the autor mentioned. I've found out that the transpose mode keybind breaks when i set anything on middle mouse button I tried your fix but unfortunately it does not work, it fixes transpose mode binding yes, but I still have to setup the buttons myself and after a game restart it breaks again. I just want to click MMB to toggle cursor on/off and hold mouse side button (MOUSE5) to use transpose mode. ED support said they can't reproduce the issue.
dresoccer4 Posted January 15 Author Posted January 15 2 hours ago, Rammi said: I have the same issue as the autor mentioned. I've found out that the transpose mode keybind breaks when i set anything on middle mouse button I tried your fix but unfortunately it does not work, it fixes transpose mode binding yes, but I still have to setup the buttons myself and after a game restart it breaks again. I just want to click MMB to toggle cursor on/off and hold mouse side button (MOUSE5) to use transpose mode. ED support said they can't reproduce the issue. good to know i'm not the only one with this big issue Acer Predator Triton 700 || i7-7700HQ || 512GB SSD || 32GB RAM || GTX1080 Max-Q || FFB II and Thrustmaster TWCS Throttle || All DCS Modules
scommander2 Posted January 15 Posted January 15 I am wondering what the tooltip says if the mouse cursor is on top of the red exclamation mark. Spoiler Dell XPS 9730, i9-13900H, DDR5 64GB, Discrete GPU: NVIDIA GeForce RTX 4080, 1+2TB M.2 SSD | Thrustmaster Warthog HOTAS + TPR | TKIR5/TrackClipPro | Total Controls Multi-Function Button Box | Win 11 Pro
Recommended Posts