Jump to content

Red lines in Key config


Recommended Posts

Posted

I got some red lines in the key config after last update.. But none of the red lines are in confllict with other keys ??

 

I have a vaste mapping, so I dont want to delete my entire keymapping..

 

Any solutions form others ??

Intel Core i7-6700K Cpu 4.00 GHz OC 4.8 GHz Water Cooled|32 GB DDR4 ram OC| Nvidia RTX 2080Ti| TrustMaster Warthog|Saitek Battle Pro Pedals | Logitec G13| Oculus Rift S :joystick:

 

I´m in for a ride, a VR ride:pilotfly:

https://www.youtube.com/channel/UCBX_-Hml7_7s1dggit_vGpA?view_as=public

Posted

Remove the red keys and rebind them then restart the game

 

Works for me

 

It happens when the default keybind that gets set with the new patch overlap with one of your other keybinds

 

It's annoying but easy fix

[sIGPIC][/sIGPIC]

Youtube

Reddit

Posted
Remove the red keys and rebind them then restart the game

 

Works for me

 

It happens when the default keybind that gets set with the new patch overlap with one of your other keybinds

 

It's annoying but easy fix

 

It dosent work for me. Still I see the red line after this test (I deleted shortcuts):

 

DCS-2016-_sesrsse.jpg

 

Perhaps the problem is repeated default key and this module always remember it (lights problem: Nav Lights and Form lights = the same key (its a bug).

If You touch it = red line.

Webmaster of http://www.yoyosims.pl

Yoyosimsbanner.gif

Win 10 64, i9-13900 KF, RTX  5090 32Gb OC, RAM 64Gb Corsair Vengeance LED OC@3600MHz,, 3xSSD+3xSSD M.2 NVMe, Predator XB271HU res.2560x1440 27'' G-sync, Sound Blaster Z + 5.1, TiR5, [MSFS, P3Dv5, DCS, RoF, Condor2, IL-2 CoD/BoX] VR fly only: Meta Quest Pro

Posted
It dosent work for me. Still I see the red line after this test (I deleted shortcuts):

 

DCS-2016-_sesrsse.jpg

 

Perhaps the problem is repeated default key and this module always remember it (lights problem: Nav Lights and Form lights = the same key (its a bug).

If You touch it = red line.

 

Can you please send us your Keyboard.diff file?

It is on Saved Games\DCS.openbeta\Config\Input\M-2000C\Keyboard\

"Programming today is a race between software engineers striving to build bigger and better idiot-proof programs, and the Universe trying to produce bigger and better idiots. So far, the Universe is winning."

"The three most dangerous things in the world are a programmer with a soldering iron, a hardware type with a program patch and a user with an idea."

Posted
Can you please send us your Keyboard.diff file?

It is on Saved Games\DCS.openbeta\Config\Input\M-2000C\Keyboard\

 

Btw Zeus, I just noticed that when I was making binds for Slats I've put 0 , 0.5 , 1 values for down, middle , up position

 

So when you press those keybinds they're in awkward position

 

They should be like -1 , 0 , 1 for them to be in correct position

 

If you don't mind fix that mistake for me

[sIGPIC][/sIGPIC]

Youtube

Reddit

Posted
Btw Zeus, I just noticed that when I was making binds for Slats I've put 0 , 0.5 , 1 values for down, middle , up position

 

So when you press those keybinds they're in awkward position

 

They should be like -1 , 0 , 1 for them to be in correct position

 

If you don't mind fix that mistake for me

 

Thanks, we will.

"Programming today is a race between software engineers striving to build bigger and better idiot-proof programs, and the Universe trying to produce bigger and better idiots. So far, the Universe is winning."

"The three most dangerous things in the world are a programmer with a soldering iron, a hardware type with a program patch and a user with an idea."

Posted
Can you please send us your Keyboard.diff file?

It is on Saved Games\DCS.openbeta\Config\Input\M-2000C\Keyboard\

 

TY. Sent (in PM)!

Webmaster of http://www.yoyosims.pl

Yoyosimsbanner.gif

Win 10 64, i9-13900 KF, RTX  5090 32Gb OC, RAM 64Gb Corsair Vengeance LED OC@3600MHz,, 3xSSD+3xSSD M.2 NVMe, Predator XB271HU res.2560x1440 27'' G-sync, Sound Blaster Z + 5.1, TiR5, [MSFS, P3Dv5, DCS, RoF, Condor2, IL-2 CoD/BoX] VR fly only: Meta Quest Pro

Posted

In my case I had to delete the input folder for the M2000C in the saved data directory, then restart DCS World. Upon restarting, DCS will repopulate the bindings with the default values, and the red lines are gone. The downside to this procedure is that you have to completely redo all you custom bindings.

[sIGPIC][/sIGPIC]

 

Intel Core I7 4820K @4.3 GHz, Asus P9X79 motherboard, 16 GB RAM @ 933 MHz, NVidia GTX 1070 with 8 GB VRAM, Windows 10 Pro

Posted
In my case I had to delete the input folder for the M2000C in the saved data directory, then restart DCS World. Upon restarting, DCS will repopulate the bindings with the default values, and the red lines are gone. The downside to this procedure is that you have to completely redo all you custom bindings.

 

Hmmm. I remeber this reset procedure

 

[ame]

[/ame]

 

but in M2000C Module folder is only lua (old) file format.

Webmaster of http://www.yoyosims.pl

Yoyosimsbanner.gif

Win 10 64, i9-13900 KF, RTX  5090 32Gb OC, RAM 64Gb Corsair Vengeance LED OC@3600MHz,, 3xSSD+3xSSD M.2 NVMe, Predator XB271HU res.2560x1440 27'' G-sync, Sound Blaster Z + 5.1, TiR5, [MSFS, P3Dv5, DCS, RoF, Condor2, IL-2 CoD/BoX] VR fly only: Meta Quest Pro

Posted
TY. Sent (in PM)!

 

Ok, it works, TY Larry for Your help. I deleted it manually from Saved Games\DCS.openbeta\Config\Input\M-2000C\Keyboard\ Nav lights and Form lights and in settings looks like this (no red line, back to repeated but default keys):

 

http://s10.ifotos.pl/img/Nowy-1JPG_seewasa.jpg

Webmaster of http://www.yoyosims.pl

Yoyosimsbanner.gif

Win 10 64, i9-13900 KF, RTX  5090 32Gb OC, RAM 64Gb Corsair Vengeance LED OC@3600MHz,, 3xSSD+3xSSD M.2 NVMe, Predator XB271HU res.2560x1440 27'' G-sync, Sound Blaster Z + 5.1, TiR5, [MSFS, P3Dv5, DCS, RoF, Condor2, IL-2 CoD/BoX] VR fly only: Meta Quest Pro

Posted

JUST DO A COLD BOOT OF THE COMPUTER AND THAT FIXED IT PERMANENTLY FOR ME. MAKE SURE TO LEAVE POWER SUPPLY OFF FOR SEVERAL MINUTES UNTIL ALL MOBO LIGHTS ARE NOT LIT WITH ANY RESIDUAL POWER.

Posted
JUST DO A COLD BOOT OF THE COMPUTER AND THAT FIXED IT PERMANENTLY FOR ME. MAKE SURE TO LEAVE POWER SUPPLY OFF FOR SEVERAL MINUTES UNTIL ALL MOBO LIGHTS ARE NOT LIT WITH ANY RESIDUAL POWER.

 

wut

[sIGPIC][/sIGPIC]

Youtube

Reddit

Posted
wut

 

Someone had good party in Friday ;D.

Webmaster of http://www.yoyosims.pl

Yoyosimsbanner.gif

Win 10 64, i9-13900 KF, RTX  5090 32Gb OC, RAM 64Gb Corsair Vengeance LED OC@3600MHz,, 3xSSD+3xSSD M.2 NVMe, Predator XB271HU res.2560x1440 27'' G-sync, Sound Blaster Z + 5.1, TiR5, [MSFS, P3Dv5, DCS, RoF, Condor2, IL-2 CoD/BoX] VR fly only: Meta Quest Pro

Posted

erase user/saved games/dcs open beta folder and remap controls again. this happened to me and I did this and it worked. no more red lines

AWAITING ED NEW DAMAGE MODEL IMPLEMENTATION FOR WW2 BIRDS

 

Fat T is above, thin T is below. Long T is faster, Short T is slower. Open triangle is AWACS, closed triangle is your own sensors. Double dash is friendly, Single dash is enemy. Circle is friendly. Strobe is jammer. Strobe to dash is under 35 km. HDD is 7 times range key. Radar to 160 km, IRST to 10 km. Stay low, but never slow.

Posted
erase user/saved games/dcs open beta folder and remap controls again. this happened to me and I did this and it worked. no more red lines

We all know deleting the save config folder solves the problem. But its not a selution for me.... I have made a heck off a mapping to fit it for my X55, and its a living hell to do it again...

Intel Core i7-6700K Cpu 4.00 GHz OC 4.8 GHz Water Cooled|32 GB DDR4 ram OC| Nvidia RTX 2080Ti| TrustMaster Warthog|Saitek Battle Pro Pedals | Logitec G13| Oculus Rift S :joystick:

 

I´m in for a ride, a VR ride:pilotfly:

https://www.youtube.com/channel/UCBX_-Hml7_7s1dggit_vGpA?view_as=public

Posted
We all know deleting the save config folder solves the problem. But its not a selution for me.... I have made a heck off a mapping to fit it for my X55, and its a living hell to do it again...

 

You don't need to delete the entire config folder.

Open the keyboard_diff.lua file and search for the command that creates the red line and delete it. That will get rid of the red line.

"Programming today is a race between software engineers striving to build bigger and better idiot-proof programs, and the Universe trying to produce bigger and better idiots. So far, the Universe is winning."

"The three most dangerous things in the world are a programmer with a soldering iron, a hardware type with a program patch and a user with an idea."

Posted
You don't need to delete the entire config folder.

Open the keyboard_diff.lua file and search for the command that creates the red line and delete it. That will get rid of the red line.

 

Great !!! thanks a lot....

 

I have been playing games since Vic20, and I have never meet any developers, so helpfull as you guys from Razbam...

Intel Core i7-6700K Cpu 4.00 GHz OC 4.8 GHz Water Cooled|32 GB DDR4 ram OC| Nvidia RTX 2080Ti| TrustMaster Warthog|Saitek Battle Pro Pedals | Logitec G13| Oculus Rift S :joystick:

 

I´m in for a ride, a VR ride:pilotfly:

https://www.youtube.com/channel/UCBX_-Hml7_7s1dggit_vGpA?view_as=public

Posted

My red lines had to do with a mode key originally being assigned and not there after the upgrade.

 

I re-assigned the key and the red disappeared.

  • Recently Browsing   0 members

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