Alphamale Posted December 8, 2018 Share Posted December 8, 2018 If this isn't a bug, what is it...besides a WIP? Video and Track included IR PAGE FLICKER.trk Link to comment Share on other sites More sharing options...
Donut Posted December 8, 2018 Share Posted December 8, 2018 I have not seen flickering to that extent, but I did have the the IR screen flicker and stay green when the sun was at my 6'oclock high and would go back to normal when I turned slightly so the sun was not directly behind me and shining into the cockpit. I don't know if our issues are related... i5 7600K @4.8GHz | 1080 Ti | 32GB 3200MHz | SSD | DCS SETTINGS | "COCKPIT" Link to comment Share on other sites More sharing options...
Alphamale Posted December 9, 2018 Author Share Posted December 9, 2018 (edited) I have not seen flickering to that extent, but I did have the the IR screen flicker and stay green when the sun was at my 6'oclock high and would go back to normal when I turned slightly so the sun was not directly behind me and shining into the cockpit. I don't know if our issues are related... Yeah, but I don't think this is "works as intended"...it's annoying as hell Edited December 11, 2018 by Alphamale Link to comment Share on other sites More sharing options...
docWilly Posted December 10, 2018 Share Posted December 10, 2018 Have seen this occasionally as well but I am not able to nail it dwn to a specific situation. [sIGPIC][/sIGPIC]my rig specs: i7-4790K CPU 4.50GHz, 32GB RAM, 64bit WIN10, NVidia GeForce GTX 980 Ti, SSD+ A10C, UH-1H, M2C, F5E, Gazelle, KA 50, F18C, DCS 2.5x OB Link to comment Share on other sites More sharing options...
ED Team NineLine Posted December 10, 2018 ED Team Share Posted December 10, 2018 If this isn't a bug, what is it...besides a WIP? Video and Track included I tried your track, when I watched it I was able to see what you saw mostly, didnt seem as bad. But when taking over your track, or flying another mission with the F I was not able to reproduce at all. Forum Rules • My YouTube • My Discord - NineLine#0440• **How to Report a Bug** Link to comment Share on other sites More sharing options...
Flagrum Posted December 11, 2018 Share Posted December 11, 2018 If this isn't a bug, what is it...besides a WIP? Video and Track included What controller setup do you use? Do you use any of the manufacturers config tools (i.e. TARGET or similar)? I ask because I wonder if this issue might have to do with some sort of constant inputs that come from the controllers, maybe a button is "auto-fireing" constantly, overloading the input queue of DCS or something like that. Link to comment Share on other sites More sharing options...
Alphamale Posted December 11, 2018 Author Share Posted December 11, 2018 (edited) What controller setup do you use? Do you use any of the manufacturers config tools (i.e. TARGET or similar)? I ask because I wonder if this issue might have to do with some sort of constant inputs that come from the controllers, maybe a button is "auto-fireing" constantly, overloading the input queue of DCS or something like that. I see where you're going, but I never got this with the MAVG and/or MAVD IR...remember, they did change that for the F version...in any case, I have CH Fighterstick, Pro Pedals, Logitech TQ, Razor Tartarus input kybd... Edited December 11, 2018 by Alphamale Link to comment Share on other sites More sharing options...
BitMaster Posted December 11, 2018 Share Posted December 11, 2018 Could be a nasty NV driver as well. I'd try a newer NV driver if you do not run it yet. I have had a similar tho not the same issue this last weekend. Updated the driver, rebooted and it went away. No clue if it was the driver, a bad hair day or whatelse but a new driver is always a good start ;) Gigabyte Aorus X570S Master - Ryzen 5900X - Gskill 64GB 3200/CL14@3600/CL14 - Asus 1080ti EK-waterblock - 4x Samsung 980Pro 1TB - 1x Samsung 870 Evo 1TB - 1x SanDisc 120GB SSD - Heatkiller IV - MoRa3-360LT@9x120mm Noctua F12 - Corsair AXi-1200 - TiR5-Pro - Warthog Hotas - Saitek Combat Pedals - Asus PG278Q 27" QHD Gsync 144Hz - Corsair K70 RGB Pro - Win11 Pro/Linux - Phanteks Evolv-X Link to comment Share on other sites More sharing options...
Alphamale Posted December 11, 2018 Author Share Posted December 11, 2018 (edited) Could be a nasty NV driver as well. I'd try a newer NV driver if you do not run it yet. I have had a similar tho not the same issue this last weekend. Updated the driver, rebooted and it went away. No clue if it was the driver, a bad hair day or whatelse but a new driver is always a good start ;) Thanks for the suggestion but I always have the latest drivers (417.22) since I have the Notifications on in GeForce Experience...I'm thinking this has to do with the new IR page that came along with the F MAV since everything was fine with the MAVG and MAVD IR page... Edited December 11, 2018 by Alphamale Link to comment Share on other sites More sharing options...
Alphamale Posted December 11, 2018 Author Share Posted December 11, 2018 Here are two videos at night showing this happens all the time...and not only does it happen all the time, but I can also get the background to change polarity just by hitting the FOV button as the second video demonstrates Link to comment Share on other sites More sharing options...
Alphamale Posted December 11, 2018 Author Share Posted December 11, 2018 Ok I think it has something to do with the horizon...as you can see in these videos, once I begin to pitch up, you can clearly see a change in the background polarity... it starts with the velocity vector level and thru the IR page, you can see that the mountain range is dark and the atmosphere is light...then as I pull up, the sky turns dark...both videos show this Link to comment Share on other sites More sharing options...
SDsc0rch Posted December 13, 2018 Share Posted December 13, 2018 yeah.. i was going to say i get some flickers as the mav seeker is sweeping through the horizon i7-4790K | Asus Sabertooth Z97 MkI | 16Gb DDR3 | EVGA GTX 980 | TM Warthog | MFG Crosswind | Panasonic TC-58AX800U [sIGPIC][/sIGPIC] Link to comment Share on other sites More sharing options...
Alphamale Posted December 13, 2018 Author Share Posted December 13, 2018 yeah.. i was going to say i get some flickers as the mav seeker is sweeping through the horizon Well, it doesn't matter if you see it, if they can't reproduce it, it will probably be dismissed Link to comment Share on other sites More sharing options...
Alphamale Posted December 13, 2018 Author Share Posted December 13, 2018 (edited) Ok, if anyone's still looking into this, watch this track...there's no doubt that it is reproducible...the polarity of the sky and horizon switches when you bring the MAV seeker up in between 0 and 5 deg pitch angle. Master mode set to ARM, A2G weapon mode on, MAVF selected from stores, and you can also go from Wide to narrow FOV (this doesn't matter)...FWIW, here's the track Edit: System specs ASUStek TUF Sabertooth 990FX mobo; AMD 8350 8-core; nVidia GTX-1060 6GB; 32 GB DDR3 SDRAM; CH Fighterstick, Logitech TQ, Pro Pedals, Razor KBIR PAGE FLICKER_4.trk Edited December 13, 2018 by Alphamale log files and specs Link to comment Share on other sites More sharing options...
Alphamale Posted December 13, 2018 Author Share Posted December 13, 2018 Wont let me upload log files...so what else do you need Link to comment Share on other sites More sharing options...
unknown Posted December 20, 2018 Share Posted December 20, 2018 I don't have that flickering but a "green screen" as soon as the Mav seeker is slewed above the +2/3(?) degrees pitch ladder mark. Win10 1809( was like this with version 1803 too ) latest nVidia driver 417.35 (was the same with 417.22 ) Modules: KA-50, A-10C, FC3, UH-1H, MI-8MTV2, CA, MIG-21bis, FW-190D9, Bf-109K4, F-86F, MIG-15bis, M-2000C, SA342 Gazelle, AJS-37 Viggen, F/A-18C, F-14, C-101, FW-190A8, F-16C, F-5E, JF-17, SC, Mi-24P Hind, AH-64D Apache, Mirage F1 System: Win 11 Pro 64bit, Ryzen 3800X, 32gb RAM DDR4-3200, PowerColor Radeon RX 6900XT Red Devil ,1 x Samsung SSD 970 EVO Plus 2TB NVMe, 2 x Samsung SSD 2TB + 1TB SATA, MFG Crosswind Rudder Pedals - VIRPIL T-50CM and VIRPIL MongoosT-50 Throttle - HP Reverg G2, using only the latest Open Beta, DCS settings Link to comment Share on other sites More sharing options...
Alphamale Posted December 20, 2018 Author Share Posted December 20, 2018 Yeah, I don't think they really care...It has already been "stamped" as "Not Able to Reproduce" which means it will disappear unless a lot of people start reporting the same problem....and when they tell you that something is not a bug...they should tell you why, because some things you report, you know they're not "as intended" Link to comment Share on other sites More sharing options...
SDsc0rch Posted December 20, 2018 Share Posted December 20, 2018 here's my video... seems to be reproducible to me! this was from this morning, 20dec2018, right after updating to 2.5.4 i7-4790K | Asus Sabertooth Z97 MkI | 16Gb DDR3 | EVGA GTX 980 | TM Warthog | MFG Crosswind | Panasonic TC-58AX800U [sIGPIC][/sIGPIC] Link to comment Share on other sites More sharing options...
Alphamale Posted December 20, 2018 Author Share Posted December 20, 2018 here's my video... seems to be reproducible to me! this was from this morning, 20dec2018, right after updating to 2.5.4 Yep, that's it. You actually had the flicker at about 0:37 in your video...I think the flicker is due to the triangle dipping above and below the "event horizon", shall we say, rapidly...you definitely have what I was reporting...and you can tell that it's wrong because first, you see the land as light (White hot IR) and the sky is dark (Cool IR) and that's ok until you lift the MAV seeker (triangle) a few degrees up, then all of a sudden, the sky in the MAV page switches to light colored which was supposed to be hot...anyway it's screwed up and they need to address it...but really, I'm at the point where DCS can find their own bugs as far as I'm concerned...they just don't give your report any credence anymore...they automatically assume that you're wrong, not them Link to comment Share on other sites More sharing options...
Eagle7907 Posted December 21, 2018 Share Posted December 21, 2018 Seen that too. Only happens when there isn’t any thing to contrast with in the image. Also when FOV is narrow. Sent from my iPhone using Tapatalk Pro Win 10, AMD FX9590/water cooled, 32GB RAM, 250GB SSD system, 1TB SSD (DCS installed), 2TB HD, Warthog HOTAS, MFG rudders, Track IR 5, LG Ultrawide, Logitech Speakers w/sub, Fans, Case, cell phone, wallet, keys.....printer Link to comment Share on other sites More sharing options...
Wizard_03 Posted December 21, 2018 Share Posted December 21, 2018 Yep, that's it. You actually had the flicker at about 0:37 in your video...I think the flicker is due to the triangle dipping above and below the "event horizon", shall we say, rapidly...you definitely have what I was reporting...and you can tell that it's wrong because first, you see the land as light (White hot IR) and the sky is dark (Cool IR) and that's ok until you lift the MAV seeker (triangle) a few degrees up, then all of a sudden, the sky in the MAV page switches to light colored which was supposed to be hot...anyway it's screwed up and they need to address it...but really, I'm at the point where DCS can find their own bugs as far as I'm concerned...they just don't give your report any credence anymore...they automatically assume that you're wrong, not them Or Maybe since the whole IR rendering model is about to get a major overhaul they don’t want to waste time fixing the old one DCS F/A-18C :sorcerer: Link to comment Share on other sites More sharing options...
captflyby Posted December 23, 2018 Share Posted December 23, 2018 (edited) On the mission this evening, AGM-65F, definite screen flickering. Don't really used the Fs anyway. Targeting logic is not reliable yet. Edited December 24, 2018 by captflyby Link to comment Share on other sites More sharing options...
Py Posted December 23, 2018 Share Posted December 23, 2018 I noticed this issue in the previous version, but it appears to be fixed (for me at least) after the latest release. Link to comment Share on other sites More sharing options...
Eldur Posted January 11, 2019 Share Posted January 11, 2019 Definately still there, but I'd go for this: Or Maybe since the whole IR rendering model is about to get a major overhaul they don’t want to waste time fixing the old one Link to comment Share on other sites More sharing options...
Recommended Posts