Jump to content

[CAN NOT REPRODUCE]Selective jettison button not activated by key binding


Recommended Posts

Posted

I have this bug in OB only. In the Stable it works fine. The binding is highlighted in the settings ok, but in the cockpit I must push the button with mouse.

12900KF@5.4, 32GB DDR4@4000cl14g1, 4090, M.2, W10 Pro, Warthog HOTAS, ButtKicker, Reverb G2/OpenXR

Posted

yeah, i seem to remember having trouble getting stores to JETT just using TM-WH

i7-4790K | Asus Sabertooth Z97 MkI | 16Gb DDR3 | EVGA GTX 980 | TM Warthog | MFG Crosswind | Panasonic TC-58AX800U

 

[sIGPIC][/sIGPIC]

Posted

I was thinking about it, but how in the track I can show that I do actually press the bound button??

12900KF@5.4, 32GB DDR4@4000cl14g1, 4090, M.2, W10 Pro, Warthog HOTAS, ButtKicker, Reverb G2/OpenXR

Posted
I was thinking about it, but how in the track I can show that I do actually press the bound button??
Include the log as well. Alternatively, what I do is that I hover the mouse cursor over the button and circle or wiggle it, to show that right now I'm pressing it.

The vCVW-17 is looking for Hornet and Tomcat pilots and RIOs. Join the vCVW-17 Discord.

CVW-17_Profile_Background_VFA-34.png

F/A-18C, F-15E, AV-8B, F-16C, JF-17, A-10C/CII, M-2000C, F-14, AH-64D, BS2, UH-1H, P-51D, Sptifire, FC3
-
i9-13900K, 64GB @6400MHz RAM, 4090 Strix OC, Samsung 990 Pro

Posted

@Impalor: did you verify that the switch you use for the selective jettison isn't bound to something in the UI_LAYER?

LeCuvier

Windows 10 Pro 64Bit | i7-4790 CPU |16 GB RAM|SSD System Disk|SSD Gaming Disk| MSI GTX-1080 Gaming 8 GB| Acer XB270HU | TM Warthog HOTAS | VKB Gladiator Pro | MongoosT-50 | MFG Crosswind Pedals | TrackIR 5

Posted (edited)

The mouse cursor is not recorded in the track, but I still attached it with my log. I pushed the button with a mouse click in the end. Curiously, assigning another button (J) to this control triggers it, but what I have (LSHF-V) does not. The button is held, not pressed (see screen 2). I have this mapping in all my other modules, and it works fine with F-18 in DCS Stable, so I am not keen to re-program in TARGET. This is not a VR-only bug...

sj.trk

Screen_200427_141747.thumb.png.9801412ac7e463a645e59c5012fe31c7.png

Untitled.png.e37d19ee4d72755e7b9c403d2725e7ce.png

dcs.log.rar

Edited by impalor

12900KF@5.4, 32GB DDR4@4000cl14g1, 4090, M.2, W10 Pro, Warthog HOTAS, ButtKicker, Reverb G2/OpenXR

Posted

The problem is that by default, LShft + V is bound to a command in UI_LAYER. See attachment. DCS lets you bind LShft +V in other modules, but the binding in UI_LAYER overrides everything else. I would just delete the binding in UI_LAYER which in my opinion is as useless as a hump on your back.

UI_LAYER.jpg.9a8b978731aaa4cfd2e8c39178a39111.jpg

LeCuvier

Windows 10 Pro 64Bit | i7-4790 CPU |16 GB RAM|SSD System Disk|SSD Gaming Disk| MSI GTX-1080 Gaming 8 GB| Acer XB270HU | TM Warthog HOTAS | VKB Gladiator Pro | MongoosT-50 | MFG Crosswind Pedals | TrackIR 5

Posted

Hi LeCuvier, good catch! Must be a new thing in OB compared to Stable. This is still a bug in that DCS does not warn us when the binding is already taken!

12900KF@5.4, 32GB DDR4@4000cl14g1, 4090, M.2, W10 Pro, Warthog HOTAS, ButtKicker, Reverb G2/OpenXR

  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...