Quax456 Posted December 3, 2017 Posted December 3, 2017 I have the same issue like with the M2k in former times. https://forums.eagle.ru/showthread.php?t=169625&highlight=black+screen+key+binding My Rig: Windows 11 Pro, Intel i7-13700k@5.4GHz, 64GB DDR5 5200 RAM, Gigabyte Z790 AORUS Elite AX, 2TB Samsung 990 PRO, RTX4080, Thrustmaster HOTAS WARTHOG Stick + WINWING ORION 2 + MFG Crosswinds, LG 32" 4K 60FPS, ACER 30" 4K 60FPS GSync Display, HP Reverb G2 V2
Sneak69 Posted December 8, 2017 Posted December 8, 2017 I am now getting the same thing in the 2.2. In the 1.5.8 beta i did not have this problem. Sent from my SM-G930W8 using Tapatalk
Nero.ger Posted December 8, 2017 Posted December 8, 2017 i have that problem in all Razbam modules, only been able to bind keys when i am in a mission. 'controlling' the Ka50 feels like a discussion with the Autopilot and trim system about the flight direction.
Sneak69 Posted December 8, 2017 Posted December 8, 2017 i have that problem in all Razbam modules, only been able to bind keys when i am in a mission.Yep only walk around for me as well. Sent from my SM-G930W8 using Tapatalk
Zeus67 Posted December 8, 2017 Posted December 8, 2017 Folks. I need the following: Your dcs.log file when this happens. The list of keys you were trying to bind. Thank you in advance. "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."
Sneak69 Posted December 8, 2017 Posted December 8, 2017 Heres my log and my joystick settings I was trying to load in. Using the 16000m FCS.harrierhotas.diff.luaharrierjoy.diff.luadcs.log.txt
Jason S Posted December 9, 2017 Posted December 9, 2017 This happened to me as well after initial install twice. The work around I did was to make a mission with the av8b and then fly it. Exit from the mission then go set up your key bindings they will now save. Flying in the quick mission first seems to auto generate the lua files inside the C:\Users\???????\Saved Games\DCS.openalpha\Config\Input\AV8BNA directory, prior to doing this those lua files were missing.
YoYo Posted December 9, 2017 Posted December 9, 2017 The same problem, with Harrier only. Webmaster of http://www.yoyosims.pl 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
Woodsy Posted December 17, 2017 Posted December 17, 2017 I am experiencing the same problem as well, the same as with the Mirage. All key binding changes in main menu leads to black screen, have to rely with changing key bindings in mission. Will attempt to create a DCS log file. Sent from my iPad using Tapatalk
Recommended Posts