Reaper6 Posted August 7, 2016 Posted August 7, 2016 I am runing multiple monitors. And when editing the kneeboard file to have it as a viewport, it creates a violation of the ingerity check in MP. Is there a plan to fix this or are we just SOL? Reaper6 "De oppresso liber" NZXT Phantom Full Tower, Intel Core i7 4960X Processor(6x 3.60GHz/15MB L3Cache) 20% Overclocking, 64GB DDR3-2133 Memory, NVIDIA GeForce GTX Titan Black-6GB SLI Mode(Dual Cards), Gigabyte GA-X79-UP4 Motherboard, ViewSonic PJD5132 SVGA Multi-Region 3D Ready Portable DLP Projector, Track IR 5, Thrustmaster Warthog, Cougar MFDs.
Zarma Posted December 19, 2016 Posted December 19, 2016 Same problem here. No changes yet. i9 9900k, 64 Go RAM, RTX 4090, Warthog HOTAS Throttle & Stick, Virpil AH64 collective, TPR rudder, MFD Cougar, Trackir 5 Pro, Multipurpose UFC, Alain Dufour's TEDAC and Oculus Rift S (when I want some VR), http://www.twitch.tv/zarma4074 / https://www.youtube.com/user/Zarma4074
Nero.ger Posted December 19, 2016 Posted December 19, 2016 you could try "outsorce" the declare_kneeboard_device.lua and init.lua to the ka50s cockpit script folder changing the device_init.lua dofile(LockOn_Options.common_script_path.."KNEEBOARD/declare_kneeboard_device.lua") to somthing like dofile(LockOn_Options.script_path.."KNEEBOARD/declare_kneeboard_device.lua") of course copy both files in the folder mods/ka-50/cockpit/scripts/KNEEBOARD also you must edit the appropriate line in your copied init.lua. did not tryed it myself(!!), but i thought i share the idea that popped into my head while reading this :) be carefull tho because you can royaly **** up your ka50 (backups are your friend) 'controlling' the Ka50 feels like a discussion with the Autopilot and trim system about the flight direction.
Recommended Posts