Johnny_Rico Posted August 11, 2017 Posted August 11, 2017 Hi, Hopefully someone can help If I go to Settings -> Controls -> UI Layer It will not let me set a keyboard button / combo for VR reset or VR Zoom Any ideas on how to work around this bug ? I just want to set these to the same keys as I use for my trackir I use profiles on my X55 so I just want to set the keyboard combos for these 2 functions METAR weather for DCS World missions Guide to help out new DCS MOOSE Users -> HERE Havoc Company Dedicated server info Connect IP: 94.23.215.203 SRS enabled - freqs - Main = 243, A2A = 244, A2G = 245 Please contact me HERE if you have any server feedback or METAR issues/requests
dburne Posted August 11, 2017 Posted August 11, 2017 I could be wrong, but believe those only support button presses at this time. Don B EVGA Z390 Dark MB | i9 9900k CPU @ 5.1 GHz | Gigabyte 4090 OC | 64 GB Corsair Vengeance 3200 MHz CL16 | Corsair H150i Pro Cooler |Virpil CM3 Stick w/ Alpha Prime Grip 200mm ext| Virpil CM3 Throttle | VPC Rotor TCS Base w/ Alpha-L Grip| Point Control V2|Varjo Aero|
Johnny_Rico Posted August 11, 2017 Author Posted August 11, 2017 Damn thats a bit of an over sight from ED :-( METAR weather for DCS World missions Guide to help out new DCS MOOSE Users -> HERE Havoc Company Dedicated server info Connect IP: 94.23.215.203 SRS enabled - freqs - Main = 243, A2A = 244, A2G = 245 Please contact me HERE if you have any server feedback or METAR issues/requests
dburne Posted August 11, 2017 Posted August 11, 2017 They may have thought if using VR one would not really want to be pressing keys. I am glad they added it though, I have assigned to a couple buttons on my throttle and comes in very handy. Don B EVGA Z390 Dark MB | i9 9900k CPU @ 5.1 GHz | Gigabyte 4090 OC | 64 GB Corsair Vengeance 3200 MHz CL16 | Corsair H150i Pro Cooler |Virpil CM3 Stick w/ Alpha Prime Grip 200mm ext| Virpil CM3 Throttle | VPC Rotor TCS Base w/ Alpha-L Grip| Point Control V2|Varjo Aero|
Johnny_Rico Posted August 11, 2017 Author Posted August 11, 2017 Maybe I should clarify I want to be able to set keys eg CTRL + INS = VR Reset view CTRL + HOME = VR Zoom in That way I can use those bindings in an X55 joystick profile I will not be pressing those keys on the keyboard but pressing button on my stick that send those keystrokes METAR weather for DCS World missions Guide to help out new DCS MOOSE Users -> HERE Havoc Company Dedicated server info Connect IP: 94.23.215.203 SRS enabled - freqs - Main = 243, A2A = 244, A2G = 245 Please contact me HERE if you have any server feedback or METAR issues/requests
dburne Posted August 11, 2017 Posted August 11, 2017 Maybe I should clarify I want to be able to set keys eg CTRL + INS = VR Reset view CTRL + HOME = VR Zoom in That way I can use those bindings in an X55 joystick profile I will not be pressing those keys on the keyboard but pressing button on my stick that send those keystrokes Ah gotcha. Don B EVGA Z390 Dark MB | i9 9900k CPU @ 5.1 GHz | Gigabyte 4090 OC | 64 GB Corsair Vengeance 3200 MHz CL16 | Corsair H150i Pro Cooler |Virpil CM3 Stick w/ Alpha Prime Grip 200mm ext| Virpil CM3 Throttle | VPC Rotor TCS Base w/ Alpha-L Grip| Point Control V2|Varjo Aero|
Hippo Posted August 14, 2017 Posted August 14, 2017 I'm getting this issue as well. Since I only got my Rift recently, and from reading other posts, I get the feeling that a bug was introduced into a recent version? I'm using KP5 to recentre, but I would really like the zoom functionality. System spec: Intel i7 12700k @ stock, ASUS TUF Gaming GeForce RTX 3080 Ti 12GB GDDR6X, Gigabyte Z690 UD DDR4, Corsair Vengeance LPX 32GB (2 x 16GB) DDR4 3200MHz C16, Samsung 980 EVO 500 GB NVME M.2 SSD (system drive), WD Black SN 850X 2TB NVME M.2 SSD (games drive), Thermalright Assassin Spirit 120 Evo Cooler, Asus XG43UQ Monitor, Oculus Quest Pro, Thrustmaster Warthog HOTAS Prev System spec (leaving here because I often reference it in my posts): Intel i9 13900KF @ stock, Gigabyte GeForce RTX 4090 Gaming OC 24GB GDDR6X, Gigabyte Z690 UD DDR4, Corsair Vengeance RGB PRO SL 32GB (2 x 16GB) DDR4 3600MHz C18, Samsung 980 EVO 500 GB NVME M.2 SSD (system drive), Samsung 970 EVO 1 TB NVME M.2 SSD (games drive), Cooler Master ML360 Illusion CPU Cooler, Asus XG43UQ Monitor, Oculus Quest Pro, Thrustmaster Warthog HOTAS, MFG Crosswind Rudder Pedals
dburne Posted August 14, 2017 Posted August 14, 2017 I'm getting this issue as well. Since I only got my Rift recently, and from reading other posts, I get the feeling that a bug was introduced into a recent version? I'm using KP5 to recentre, but I would really like the zoom functionality. Do you have an available button on your stick or throttle you can map it to from within the UI layer? As mentioned previously I have both zoom and re-center mapped in there to buttons on my Warthog throttle and they work quite well. Don B EVGA Z390 Dark MB | i9 9900k CPU @ 5.1 GHz | Gigabyte 4090 OC | 64 GB Corsair Vengeance 3200 MHz CL16 | Corsair H150i Pro Cooler |Virpil CM3 Stick w/ Alpha Prime Grip 200mm ext| Virpil CM3 Throttle | VPC Rotor TCS Base w/ Alpha-L Grip| Point Control V2|Varjo Aero|
Hippo Posted August 14, 2017 Posted August 14, 2017 Do you have an available button on your stick or throttle you can map it to from within the UI layer? As mentioned previously I have both zoom and re-center mapped in there to buttons on my Warthog throttle and they work quite well. I do have free buttons, but I don't even get that far. When I double-click the space (for keyboard or joystick) in the options to assign a control, nothing happens - the assignment window doesn't even come up. I have posted in the issues forum https://forums.eagle.ru/showpost.php?p=3221434&postcount=1 System spec: Intel i7 12700k @ stock, ASUS TUF Gaming GeForce RTX 3080 Ti 12GB GDDR6X, Gigabyte Z690 UD DDR4, Corsair Vengeance LPX 32GB (2 x 16GB) DDR4 3200MHz C16, Samsung 980 EVO 500 GB NVME M.2 SSD (system drive), WD Black SN 850X 2TB NVME M.2 SSD (games drive), Thermalright Assassin Spirit 120 Evo Cooler, Asus XG43UQ Monitor, Oculus Quest Pro, Thrustmaster Warthog HOTAS Prev System spec (leaving here because I often reference it in my posts): Intel i9 13900KF @ stock, Gigabyte GeForce RTX 4090 Gaming OC 24GB GDDR6X, Gigabyte Z690 UD DDR4, Corsair Vengeance RGB PRO SL 32GB (2 x 16GB) DDR4 3600MHz C18, Samsung 980 EVO 500 GB NVME M.2 SSD (system drive), Samsung 970 EVO 1 TB NVME M.2 SSD (games drive), Cooler Master ML360 Illusion CPU Cooler, Asus XG43UQ Monitor, Oculus Quest Pro, Thrustmaster Warthog HOTAS, MFG Crosswind Rudder Pedals
dburne Posted August 14, 2017 Posted August 14, 2017 I do have free buttons, but I don't even get that far. When I double-click the space (for keyboard or joystick) in the options to assign a control, nothing happens - the assignment window doesn't even come up. I have posted in the issues forum https://forums.eagle.ru/showpost.php?p=3221434&postcount=1 Couple things come to mind. 1: Do it from the main menu, not from when in your module. 2: Insure you are in true full screen ( alt+enter) before attempting. Barring that, not sure what might be going on there for you. Don B EVGA Z390 Dark MB | i9 9900k CPU @ 5.1 GHz | Gigabyte 4090 OC | 64 GB Corsair Vengeance 3200 MHz CL16 | Corsair H150i Pro Cooler |Virpil CM3 Stick w/ Alpha Prime Grip 200mm ext| Virpil CM3 Throttle | VPC Rotor TCS Base w/ Alpha-L Grip| Point Control V2|Varjo Aero|
Buckeye Posted August 14, 2017 Posted August 14, 2017 (edited) Click in the cell where you want to make the binding (i.e. on the "VR Zoom" row under the "Warthog HOTAS - Joystick" column)...instead of double clicking to enter into the screen/section where you would normally make a new key bind, with the cell still selected, click "Add" at the bottom. This will allow that screen to pop up. Hope this helps? Edited August 14, 2017 by =Buckeye= Rig: SimLab P1X Chassis | Tianhang Base PRO + Tianhang F-16 Grip w/ OTTO Buttons | Custom Throttletek F/A-18C Throttle w/ Hall Sensors + OTTO switches and buttons | Slaw Device RX Viper Pedals w/ Damper Tactile: G-Belt | 2x BK LFE + 1x BK Concert | 2x TST-429 | 1x BST-300EX | 2x BST-1 | 6x 40W Exciters | 2x NX3000D | 2x EPQ304 PC/VR: Somnium VR1 Visionary | 4090 | 12700K
Hippo Posted August 14, 2017 Posted August 14, 2017 Hi, Thank you both for your suggetions, unfortunately none of them has worked. I should add that I am able to bind other commands without issue. System spec: Intel i7 12700k @ stock, ASUS TUF Gaming GeForce RTX 3080 Ti 12GB GDDR6X, Gigabyte Z690 UD DDR4, Corsair Vengeance LPX 32GB (2 x 16GB) DDR4 3200MHz C16, Samsung 980 EVO 500 GB NVME M.2 SSD (system drive), WD Black SN 850X 2TB NVME M.2 SSD (games drive), Thermalright Assassin Spirit 120 Evo Cooler, Asus XG43UQ Monitor, Oculus Quest Pro, Thrustmaster Warthog HOTAS Prev System spec (leaving here because I often reference it in my posts): Intel i9 13900KF @ stock, Gigabyte GeForce RTX 4090 Gaming OC 24GB GDDR6X, Gigabyte Z690 UD DDR4, Corsair Vengeance RGB PRO SL 32GB (2 x 16GB) DDR4 3600MHz C18, Samsung 980 EVO 500 GB NVME M.2 SSD (system drive), Samsung 970 EVO 1 TB NVME M.2 SSD (games drive), Cooler Master ML360 Illusion CPU Cooler, Asus XG43UQ Monitor, Oculus Quest Pro, Thrustmaster Warthog HOTAS, MFG Crosswind Rudder Pedals
Hippo Posted August 14, 2017 Posted August 14, 2017 I suspect that this could be fixed by manually editing the keyboard.diff.lua (like the OP I'm hoping to bind keystrokes, which I'll then assign using my joystick software), or the <joystick>.diff.lua. If it's not too much trouble, would you mind posting the part of the file that references these commands? System spec: Intel i7 12700k @ stock, ASUS TUF Gaming GeForce RTX 3080 Ti 12GB GDDR6X, Gigabyte Z690 UD DDR4, Corsair Vengeance LPX 32GB (2 x 16GB) DDR4 3200MHz C16, Samsung 980 EVO 500 GB NVME M.2 SSD (system drive), WD Black SN 850X 2TB NVME M.2 SSD (games drive), Thermalright Assassin Spirit 120 Evo Cooler, Asus XG43UQ Monitor, Oculus Quest Pro, Thrustmaster Warthog HOTAS Prev System spec (leaving here because I often reference it in my posts): Intel i9 13900KF @ stock, Gigabyte GeForce RTX 4090 Gaming OC 24GB GDDR6X, Gigabyte Z690 UD DDR4, Corsair Vengeance RGB PRO SL 32GB (2 x 16GB) DDR4 3600MHz C18, Samsung 980 EVO 500 GB NVME M.2 SSD (system drive), Samsung 970 EVO 1 TB NVME M.2 SSD (games drive), Cooler Master ML360 Illusion CPU Cooler, Asus XG43UQ Monitor, Oculus Quest Pro, Thrustmaster Warthog HOTAS, MFG Crosswind Rudder Pedals
dburne Posted August 14, 2017 Posted August 14, 2017 Hi, Thank you both for your suggetions, unfortunately none of them has worked. I should add that I am able to bind other commands without issue. Dang that is strange, it certainly should work for you. Ok so bear with me for sounding simplistic here: You are in the actual UI layer correct? Clicking the down arrow by your module listings and scrolling all the way down to UI. You do have your Rift headset connected and running at the time. Don B EVGA Z390 Dark MB | i9 9900k CPU @ 5.1 GHz | Gigabyte 4090 OC | 64 GB Corsair Vengeance 3200 MHz CL16 | Corsair H150i Pro Cooler |Virpil CM3 Stick w/ Alpha Prime Grip 200mm ext| Virpil CM3 Throttle | VPC Rotor TCS Base w/ Alpha-L Grip| Point Control V2|Varjo Aero|
Hippo Posted August 14, 2017 Posted August 14, 2017 Dang that is strange, it certainly should work for you. Ok so bear with me for sounding simplistic here: You are in the actual UI layer correct? Clicking the down arrow by your module listings and scrolling all the way down to UI. You do have your Rift headset connected and running at the time. First question: yes. Second question: have tried both in rift and non-vr. It just doesn't work. I suspect a bug has been introduced in a recent release. System spec: Intel i7 12700k @ stock, ASUS TUF Gaming GeForce RTX 3080 Ti 12GB GDDR6X, Gigabyte Z690 UD DDR4, Corsair Vengeance LPX 32GB (2 x 16GB) DDR4 3200MHz C16, Samsung 980 EVO 500 GB NVME M.2 SSD (system drive), WD Black SN 850X 2TB NVME M.2 SSD (games drive), Thermalright Assassin Spirit 120 Evo Cooler, Asus XG43UQ Monitor, Oculus Quest Pro, Thrustmaster Warthog HOTAS Prev System spec (leaving here because I often reference it in my posts): Intel i9 13900KF @ stock, Gigabyte GeForce RTX 4090 Gaming OC 24GB GDDR6X, Gigabyte Z690 UD DDR4, Corsair Vengeance RGB PRO SL 32GB (2 x 16GB) DDR4 3600MHz C18, Samsung 980 EVO 500 GB NVME M.2 SSD (system drive), Samsung 970 EVO 1 TB NVME M.2 SSD (games drive), Cooler Master ML360 Illusion CPU Cooler, Asus XG43UQ Monitor, Oculus Quest Pro, Thrustmaster Warthog HOTAS, MFG Crosswind Rudder Pedals
Jabbers_ Posted August 14, 2017 Posted August 14, 2017 You cannot use keyboard for this, just your HOTAS or other Controllers. Ill double check tonight, and I'll file a bug about it if one doesnt already exist. Twitch2DCS - Bring twitch chat into DCS. SplashOneGaming.com - Splash One is a community built on combat flight simulation. S1G Discord twitch / youtube / facebook / twitter / discord
dannyq8 Posted August 14, 2017 Posted August 14, 2017 I do have free buttons, but I don't even get that far. When I double-click the space (for keyboard or joystick) in the options to assign a control, nothing happens - the assignment window doesn't even come up. I have posted in the issues forum https://forums.eagle.ru/showpost.php?p=3221434&postcount=1 Which DCS version are you running? The reason I ask is I found this issue with the UI Layer and the Hawk in both beta and alpha DCS 2.1.1.8244 Update 1. Since DCS 2.1.1.8491 Update 2 all is well again https://forums.eagle.ru/showthread.php?t=191407 Wise men speak because they have something to say; Fools because they have to say something. Plato
Hippo Posted August 14, 2017 Posted August 14, 2017 You cannot use keyboard for this, just your HOTAS or other Controllers. Ill double check tonight, and I'll file a bug about it if one doesnt already exist. That's great - thanks. System spec: Intel i7 12700k @ stock, ASUS TUF Gaming GeForce RTX 3080 Ti 12GB GDDR6X, Gigabyte Z690 UD DDR4, Corsair Vengeance LPX 32GB (2 x 16GB) DDR4 3200MHz C16, Samsung 980 EVO 500 GB NVME M.2 SSD (system drive), WD Black SN 850X 2TB NVME M.2 SSD (games drive), Thermalright Assassin Spirit 120 Evo Cooler, Asus XG43UQ Monitor, Oculus Quest Pro, Thrustmaster Warthog HOTAS Prev System spec (leaving here because I often reference it in my posts): Intel i9 13900KF @ stock, Gigabyte GeForce RTX 4090 Gaming OC 24GB GDDR6X, Gigabyte Z690 UD DDR4, Corsair Vengeance RGB PRO SL 32GB (2 x 16GB) DDR4 3600MHz C18, Samsung 980 EVO 500 GB NVME M.2 SSD (system drive), Samsung 970 EVO 1 TB NVME M.2 SSD (games drive), Cooler Master ML360 Illusion CPU Cooler, Asus XG43UQ Monitor, Oculus Quest Pro, Thrustmaster Warthog HOTAS, MFG Crosswind Rudder Pedals
dburne Posted August 14, 2017 Posted August 14, 2017 First question: yes. Second question: have tried both in rift and non-vr. It just doesn't work. I suspect a bug has been introduced in a recent release. You may be right there, I assigned these to my Rift some time ago, and has just always kept on working for me. Don B EVGA Z390 Dark MB | i9 9900k CPU @ 5.1 GHz | Gigabyte 4090 OC | 64 GB Corsair Vengeance 3200 MHz CL16 | Corsair H150i Pro Cooler |Virpil CM3 Stick w/ Alpha Prime Grip 200mm ext| Virpil CM3 Throttle | VPC Rotor TCS Base w/ Alpha-L Grip| Point Control V2|Varjo Aero|
Hippo Posted August 14, 2017 Posted August 14, 2017 Which DCS version are you running? The reason I ask is I found this issue with the UI Layer and the Hawk in both beta and alpha DCS 2.1.1.8244 Update 1. Since DCS 2.1.1.8491 Update 2 all is well again https://forums.eagle.ru/showthread.php?t=191407 Ah - apologies to all - I should have mentioned that I have been using 1.5.7.7741 - which is where I am seeing the issue. I have just tried 2.1.1.8491 - and indeed it works ok in that version. Sorry for any confusion. System spec: Intel i7 12700k @ stock, ASUS TUF Gaming GeForce RTX 3080 Ti 12GB GDDR6X, Gigabyte Z690 UD DDR4, Corsair Vengeance LPX 32GB (2 x 16GB) DDR4 3200MHz C16, Samsung 980 EVO 500 GB NVME M.2 SSD (system drive), WD Black SN 850X 2TB NVME M.2 SSD (games drive), Thermalright Assassin Spirit 120 Evo Cooler, Asus XG43UQ Monitor, Oculus Quest Pro, Thrustmaster Warthog HOTAS Prev System spec (leaving here because I often reference it in my posts): Intel i9 13900KF @ stock, Gigabyte GeForce RTX 4090 Gaming OC 24GB GDDR6X, Gigabyte Z690 UD DDR4, Corsair Vengeance RGB PRO SL 32GB (2 x 16GB) DDR4 3600MHz C18, Samsung 980 EVO 500 GB NVME M.2 SSD (system drive), Samsung 970 EVO 1 TB NVME M.2 SSD (games drive), Cooler Master ML360 Illusion CPU Cooler, Asus XG43UQ Monitor, Oculus Quest Pro, Thrustmaster Warthog HOTAS, MFG Crosswind Rudder Pedals
Hippo Posted August 14, 2017 Posted August 14, 2017 ED: Any chance functionality to assign these commands to keystrokes (and not just joystick buttons) can be added as well? System spec: Intel i7 12700k @ stock, ASUS TUF Gaming GeForce RTX 3080 Ti 12GB GDDR6X, Gigabyte Z690 UD DDR4, Corsair Vengeance LPX 32GB (2 x 16GB) DDR4 3200MHz C16, Samsung 980 EVO 500 GB NVME M.2 SSD (system drive), WD Black SN 850X 2TB NVME M.2 SSD (games drive), Thermalright Assassin Spirit 120 Evo Cooler, Asus XG43UQ Monitor, Oculus Quest Pro, Thrustmaster Warthog HOTAS Prev System spec (leaving here because I often reference it in my posts): Intel i9 13900KF @ stock, Gigabyte GeForce RTX 4090 Gaming OC 24GB GDDR6X, Gigabyte Z690 UD DDR4, Corsair Vengeance RGB PRO SL 32GB (2 x 16GB) DDR4 3600MHz C18, Samsung 980 EVO 500 GB NVME M.2 SSD (system drive), Samsung 970 EVO 1 TB NVME M.2 SSD (games drive), Cooler Master ML360 Illusion CPU Cooler, Asus XG43UQ Monitor, Oculus Quest Pro, Thrustmaster Warthog HOTAS, MFG Crosswind Rudder Pedals
Hippo Posted August 15, 2017 Posted August 15, 2017 Click in the cell where you want to make the binding (i.e. on the "VR Zoom" row under the "Warthog HOTAS - Joystick" column)...instead of double clicking to enter into the screen/section where you would normally make a new key bind, with the cell still selected, click "Add" at the bottom. This will allow that screen to pop up. Hope this helps? And apologies again. This does work; I was sure I'd tried it last night and it didn't. Many thanks. System spec: Intel i7 12700k @ stock, ASUS TUF Gaming GeForce RTX 3080 Ti 12GB GDDR6X, Gigabyte Z690 UD DDR4, Corsair Vengeance LPX 32GB (2 x 16GB) DDR4 3200MHz C16, Samsung 980 EVO 500 GB NVME M.2 SSD (system drive), WD Black SN 850X 2TB NVME M.2 SSD (games drive), Thermalright Assassin Spirit 120 Evo Cooler, Asus XG43UQ Monitor, Oculus Quest Pro, Thrustmaster Warthog HOTAS Prev System spec (leaving here because I often reference it in my posts): Intel i9 13900KF @ stock, Gigabyte GeForce RTX 4090 Gaming OC 24GB GDDR6X, Gigabyte Z690 UD DDR4, Corsair Vengeance RGB PRO SL 32GB (2 x 16GB) DDR4 3600MHz C18, Samsung 980 EVO 500 GB NVME M.2 SSD (system drive), Samsung 970 EVO 1 TB NVME M.2 SSD (games drive), Cooler Master ML360 Illusion CPU Cooler, Asus XG43UQ Monitor, Oculus Quest Pro, Thrustmaster Warthog HOTAS, MFG Crosswind Rudder Pedals
Buckeye Posted August 15, 2017 Posted August 15, 2017 And apologies again. This does work; I was sure I'd tried it last night and it didn't. Many thanks. Perfect! Glad I could help my man, have fun! Sent from my iPhone using Tapatalk Rig: SimLab P1X Chassis | Tianhang Base PRO + Tianhang F-16 Grip w/ OTTO Buttons | Custom Throttletek F/A-18C Throttle w/ Hall Sensors + OTTO switches and buttons | Slaw Device RX Viper Pedals w/ Damper Tactile: G-Belt | 2x BK LFE + 1x BK Concert | 2x TST-429 | 1x BST-300EX | 2x BST-1 | 6x 40W Exciters | 2x NX3000D | 2x EPQ304 PC/VR: Somnium VR1 Visionary | 4090 | 12700K
Recommended Posts