PawlaczGMD Posted October 29, 2023 Posted October 29, 2023 As per the title. In VR, sometimes, going to the map and back causes the overall brightness to increase significantly for a few seconds - very uncomfortable. I only experience this in Ka50, on both Pico 4 and Pimax Crystal headsets.
v2tec Posted October 29, 2023 Posted October 29, 2023 (edited) Agree. I can confirm this behaviour. It is very annoying. Please fix. Using HP Reverb G2 Edited October 29, 2023 by v2tec ________________________ ________ ______ ___ __ _ Win10 64 Pro, i7-6800K 3.4Ghz, 32 GB (DDR4), Asus Aorus 1080 TI WF, TrackIR 5 / RIFT, Thrustmaster Warthog, Fanatec Pedals, 55" oled 4k TV, Modules:A10C, KA-50, Huey, AV-8B, FA-18, F-16, NTTR, Persian Gulf _ __ ___ ____ _____ ______ _______ ____________
Kappa-131st Posted October 31, 2023 Posted October 31, 2023 (edited) Same, this bug is much older than 2.9 This is not a "KA-50" bug, it is the same for other aircraft (Apache, Mi24....) Edited October 31, 2023 by Kappa-131st
Ready Posted May 23, 2024 Posted May 23, 2024 (edited) Same here. The bug is still alive. A-10C using Varjo Aero. Edited May 23, 2024 by Ready I fly an A-10C II in VR and post my DCS journey on | Subscribe to my DCS A-10C channel Come check out the 132nd Virtual Wing | My VR Performance Optimization (4090/9800X3D/Aero) SYSTEM SPECS: Ryzen 7 9800X3D, RTX4090, 64GB DDR5-6000, Windows 10, ROG STRIX X870E-E Gaming WIFI, Varjo Aero, VKB Gunfighter MKIII MCG Ultimate with 10cm extension, VPC MongoosT-50CM3 Throttle, VPC Control Panel #2, TM TPR Rudders. Buttkicker, Gametrix Jetseat, PointCTRL, OpenKneeboard, Wacom Intuos Pro Small.
MoleUK Posted December 5, 2024 Posted December 5, 2024 (edited) Bug still persists, couldn't find the old thread to bump it. Been a couple years now I think, affects all modules but is much more noticeable in helos. Edited December 6, 2024 by MoleUK
Recommended Posts