Jump to content

Recommended Posts

Posted

Hi guys.

 

I had never had to modify UI layer bindings but recently i bought a second hand Oculus Rift to try the VR and binded some keys from UI Layer. I have a Warthog and use a combination of modifier from throotle key and and a button to, for example, right and left mouse clicks.

 

The problem is when i start DCS on VR, sometimes the bindings work and sometimes not and for work i had to remove and add again the modifier while in non VR launch it works always ok.

 

Any idea?

 

NZXT H9 Flow Black | Intel Core i5 13600KF OCed P5.6 E4.4 | Gigabyte Z790 Aorus Elite AX | G.Skill Trident Z5 Neo DDR5-6000 32GB C30 OCed 6600 C32 | nVidia GeForce RTX 4090 Founders Edition |  Western Digital SN770 2TB | Gigabyte GP-UD1000GM PG5 ATX 3.0 1000W | SteelSeries Apex 7 | Razer Viper Mini | SteelSeries Artics Nova 7 | LG OLED42C2 | Xiaomi P1 55"

Virpil T-50 CM2 Base + Thrustmaster Warthog Stick | WinWing Orion 2 F16EX Viper Throttle  | WinWing ICP | 3 x Thrustmaster MFD | Saitek Combat Rudder Pedals | Oculus Quest 2

DCS World | Persian Gulf | Syria | Flaming Cliff 3 | P-51D Mustang | Spitfire LF Mk. IX | Fw-109 A-8 | A-10C II Tank Killer | F/A-18C Hornet | F-14B Tomcat | F-16C Viper | F-15E Strike Eagle | M2000C | Ka-50 BlackShark III | Mi-24P Hind | AH-64D Apache | SuperCarrier

Posted

I know the "UI Layer" category doesn't warn you (at all) when you choose a keybinding already used in any other category.

You should give ths a try: select any unuseful command of the aircraft you're usually flying, start binding one of the keys you're using for "UI Layer" and see if DCS says it's already taken by another command of this aircraft.

---

Posted
I know the "UI Layer" category doesn't warn you (at all) when you choose a keybinding already used in any other category.

You should give ths a try: select any unuseful command of the aircraft you're usually flying, start binding one of the keys you're using for "UI Layer" and see if DCS says it's already taken by another command of this aircraft.

 

Thanks for the response.

 

I already check all my modules and theres no double binding on any of then.

 

Something new i discoveres is, to fix then, i dont have to remove and adding again the modifier, i only have to go to the UI layer controls and push Ok, then they will work (until the next time), it looks that theres some problem loading the UI layer controls maybe?

NZXT H9 Flow Black | Intel Core i5 13600KF OCed P5.6 E4.4 | Gigabyte Z790 Aorus Elite AX | G.Skill Trident Z5 Neo DDR5-6000 32GB C30 OCed 6600 C32 | nVidia GeForce RTX 4090 Founders Edition |  Western Digital SN770 2TB | Gigabyte GP-UD1000GM PG5 ATX 3.0 1000W | SteelSeries Apex 7 | Razer Viper Mini | SteelSeries Artics Nova 7 | LG OLED42C2 | Xiaomi P1 55"

Virpil T-50 CM2 Base + Thrustmaster Warthog Stick | WinWing Orion 2 F16EX Viper Throttle  | WinWing ICP | 3 x Thrustmaster MFD | Saitek Combat Rudder Pedals | Oculus Quest 2

DCS World | Persian Gulf | Syria | Flaming Cliff 3 | P-51D Mustang | Spitfire LF Mk. IX | Fw-109 A-8 | A-10C II Tank Killer | F/A-18C Hornet | F-14B Tomcat | F-16C Viper | F-15E Strike Eagle | M2000C | Ka-50 BlackShark III | Mi-24P Hind | AH-64D Apache | SuperCarrier

Posted

Then it would be interesting to compare the content of the"C:\Users\your_name\Saved Games\DCS...\Config\Input\modifiers.lua" file before and after you click "OK".

---

Posted
Then it would be interesting to compare the content of the"C:\Users\your_name\Saved Games\DCS...\Config\Input\modifiers.lua" file before and after you click "OK".

 

Modifiers and joystick lua file from UI layer last modification was yesterday when i was binding the keys, the last time i tested was a pair of hours ago so it looks that when i push Ok the file is not modified

NZXT H9 Flow Black | Intel Core i5 13600KF OCed P5.6 E4.4 | Gigabyte Z790 Aorus Elite AX | G.Skill Trident Z5 Neo DDR5-6000 32GB C30 OCed 6600 C32 | nVidia GeForce RTX 4090 Founders Edition |  Western Digital SN770 2TB | Gigabyte GP-UD1000GM PG5 ATX 3.0 1000W | SteelSeries Apex 7 | Razer Viper Mini | SteelSeries Artics Nova 7 | LG OLED42C2 | Xiaomi P1 55"

Virpil T-50 CM2 Base + Thrustmaster Warthog Stick | WinWing Orion 2 F16EX Viper Throttle  | WinWing ICP | 3 x Thrustmaster MFD | Saitek Combat Rudder Pedals | Oculus Quest 2

DCS World | Persian Gulf | Syria | Flaming Cliff 3 | P-51D Mustang | Spitfire LF Mk. IX | Fw-109 A-8 | A-10C II Tank Killer | F/A-18C Hornet | F-14B Tomcat | F-16C Viper | F-15E Strike Eagle | M2000C | Ka-50 BlackShark III | Mi-24P Hind | AH-64D Apache | SuperCarrier

Posted (edited)

Then maybe DCS doesn't read the files contained in the "C:\Users\your_name\Saved Games\DCS\Config\Input\UiLayer\joystick" folder at startup, like it should?

 

EDIT: I tried to reproduce your issue with my Warthog throttle (modifer) and Warthog joystick (button). I restarted the game and had no need to get back in the controls options to make it work in a mission. Your issue seems linked to the VR gears.

Edited by Flappie

---

Posted

Yes, looks like it has to be VR related, some on DCS or Oculus software, tried again on Non-VR DCS and works fine

NZXT H9 Flow Black | Intel Core i5 13600KF OCed P5.6 E4.4 | Gigabyte Z790 Aorus Elite AX | G.Skill Trident Z5 Neo DDR5-6000 32GB C30 OCed 6600 C32 | nVidia GeForce RTX 4090 Founders Edition |  Western Digital SN770 2TB | Gigabyte GP-UD1000GM PG5 ATX 3.0 1000W | SteelSeries Apex 7 | Razer Viper Mini | SteelSeries Artics Nova 7 | LG OLED42C2 | Xiaomi P1 55"

Virpil T-50 CM2 Base + Thrustmaster Warthog Stick | WinWing Orion 2 F16EX Viper Throttle  | WinWing ICP | 3 x Thrustmaster MFD | Saitek Combat Rudder Pedals | Oculus Quest 2

DCS World | Persian Gulf | Syria | Flaming Cliff 3 | P-51D Mustang | Spitfire LF Mk. IX | Fw-109 A-8 | A-10C II Tank Killer | F/A-18C Hornet | F-14B Tomcat | F-16C Viper | F-15E Strike Eagle | M2000C | Ka-50 BlackShark III | Mi-24P Hind | AH-64D Apache | SuperCarrier

  • Recently Browsing   0 members

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