LeCuvier Posted November 26, 2015 Posted November 26, 2015 Typically when a mission starts, the gunsight crosshair is visible (brightness sufficiently high by default). But shortly after mission start the crosshair fades and disappears. I can turn it up again with RShift-O but it does not stay bright. It dims away after a time interval which seems random. Sometimes immediately, sometimes several seconds and sometimes even longer. But there is no way you can win an air combat with that behavior. I attach a short track file as an example. PS: There seems to be a problem with tracks too. Sometimes when I watch the track after a mission it shows me some old track rather than the current one. I had to go through the motions several times before I had the right track file. I have seen this sometimes in 1.2.16 and therefore in theory it should not be reported here. But since track files are often required to substantiate a bug report I think it should be noted.Bf-109 Gunsight dims Off Again.trk LeCuvier Windows 10 Pro 64Bit | i7-4790 CPU |16 GB RAM|SSD System Disk|SSD Gaming Disk| MSI GTX-1080 Gaming 8 GB| Acer XB270HU | TM Warthog HOTAS | VKB Gladiator Pro | MongoosT-50 | MFG Crosswind Pedals | TrackIR 5
dooom Posted November 26, 2015 Posted November 26, 2015 hmmm i wonder if you have a button dual mapped to turning it down... That is is random is odd and others have not reported this yet that I have heard of. Check your RShift - O mapping line and see if there is another keymap that you are using (trigger etc.) that is turning it down little by little each time? Bonne chance! ASUS Tuf Gaming Pro x570 / AMD Ryzen 7 5800X @ 3.8 / XFX Radeon 6900 XT / 64 GB DDR4 3200 "This was not in the Manual I did not read", cried the Noob" - BMBM, WWIIOL
Sporg Posted November 26, 2015 Posted November 26, 2015 Check if you have an axis assigned to the gunsight brightness. That could give the behaviour you describe. System specs: Gigabyte Aorus Master, i7 9700K@std, GTX 1080TI OC, 32 GB 3000 MHz RAM, NVMe M.2 SSD, Oculus Quest VR (2x1600x1440) Warthog HOTAS w/150mm extension, Slaw pedals, Gametrix Jetseat, TrackIR for monitor use
LeCuvier Posted November 26, 2015 Author Posted November 26, 2015 hmmm i wonder if you have a button dual mapped to turning it down... That is is random is odd and others have not reported this yet that I have heard of. Check your RShift - O mapping line and see if there is another keymap that you are using (trigger etc.) that is turning it down little by little each time? Bonne chance! Hi, I checked but... 1. there is no double-mapping of Rctrl-O 2. no joytick or throttle button is mapped to that row 3. Not running TARGET software which could cause this kind of issue And when the mission has started the brightness dims away before I have touched any game control or keyboard button. LeCuvier Windows 10 Pro 64Bit | i7-4790 CPU |16 GB RAM|SSD System Disk|SSD Gaming Disk| MSI GTX-1080 Gaming 8 GB| Acer XB270HU | TM Warthog HOTAS | VKB Gladiator Pro | MongoosT-50 | MFG Crosswind Pedals | TrackIR 5
Sporg Posted November 27, 2015 Posted November 27, 2015 Did you check axis? System specs: Gigabyte Aorus Master, i7 9700K@std, GTX 1080TI OC, 32 GB 3000 MHz RAM, NVMe M.2 SSD, Oculus Quest VR (2x1600x1440) Warthog HOTAS w/150mm extension, Slaw pedals, Gametrix Jetseat, TrackIR for monitor use
Art-J Posted November 27, 2015 Posted November 27, 2015 After watching the track, at first I though it might be circuit breaker related issue, but after second look, it's obvious something's flipping the dimmer switch on and off. I'd still say it might be some controls related problem. Second option - do You use game flight mode? This is know for causing all sorts of strange issues in different modules. i7 9700K @ stock speed, single GTX1070, 32 gigs of RAM, TH Warthog, MFG Crosswind, Win10.
LeCuvier Posted November 27, 2015 Author Posted November 27, 2015 Check if you have an axis assigned to the gunsight brightness. That could give the behaviour you describe. That was a good shot! Yes in fact the slider of my Warthog throttle was mapped to the brightness, and the slider was in the minimum position. 100 points for Gryffindor! LeCuvier Windows 10 Pro 64Bit | i7-4790 CPU |16 GB RAM|SSD System Disk|SSD Gaming Disk| MSI GTX-1080 Gaming 8 GB| Acer XB270HU | TM Warthog HOTAS | VKB Gladiator Pro | MongoosT-50 | MFG Crosswind Pedals | TrackIR 5
Sporg Posted November 27, 2015 Posted November 27, 2015 That was a good shot! Yes in fact the slider of my Warthog throttle was mapped to the brightness, and the slider was in the minimum position. 100 points for Gryffindor! ;) For me, I set that axis for zoom, it's good for shooting accurate. :) (Tip from a friend I admit.) System specs: Gigabyte Aorus Master, i7 9700K@std, GTX 1080TI OC, 32 GB 3000 MHz RAM, NVMe M.2 SSD, Oculus Quest VR (2x1600x1440) Warthog HOTAS w/150mm extension, Slaw pedals, Gametrix Jetseat, TrackIR for monitor use
Recommended Posts