Rhayvn Posted June 3, 2020 Posted June 3, 2020 So far: 1. HUD and HMD brightness is very low at max brightness. It's virtually impossible to see against light backgrounds. 2. Radar Antennae elevation controls do not work. Keyboard or bound. 3. New Steerpoints show HUD symbology and are usable by the autopilot. Preset steerpoints show no HUD symbology and are not steerable by the autopilot. 4. TGP designation vs CCRP target is ~100 yards offset. Point track on the TGP does not correspond to the actual ground targeted location for the CCRP cues. Possibly using the wrong altitude for the coordinates? The 16 is FAR more broken than it was two hours ago. But hey, we can manually add steerpoints!!
Eagle7907 Posted June 4, 2020 Posted June 4, 2020 F-16 Bugs in today's patch Oops. Just saw someone made a thread about missing tadpole. 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
deadpool Posted June 4, 2020 Posted June 4, 2020 Some of the defects were known in advance to ED and yet they still went ahead with it: See Wags video and you can already spot them if you look. Lincoln said: “Nearly all men can stand adversity, but if you want to test a man's character, give him power." Do not expect a reply to any questions, 30.06.2021 - Silenced by Nineline
Santi871 Posted June 4, 2020 Posted June 4, 2020 2, 3 and 4 are reported (4 in particular wasn't introduced in this update, it was there before). For 2, the antenna elevation does work, it's just the TDC altitude numbers not updating. 1 is a general DCS issue, so hopefully it'll be fixed across the board and not just for the Viper
Rhayvn Posted June 4, 2020 Author Posted June 4, 2020 It's not just the altitude numbers on the FCR, it's also the elevation indicator and while it wasn't many tests, the tests done showed no indication that elevation or depression were happening. Targets outside the listed altitudes on the FCR marker were not detected no matter how the settings were manipulated.
Santi871 Posted June 4, 2020 Posted June 4, 2020 It's not just the altitude numbers on the FCR, it's also the elevation indicator and while it wasn't many tests, the tests done showed no indication that elevation or depression were happening. Targets outside the listed altitudes on the FCR marker were not detected no matter how the settings were manipulated. Checked again, it slews in RWS but not in TWS, I'll update the report
timber29 Posted June 4, 2020 Posted June 4, 2020 F-16 Issues After 6/3 Update 1.HUD is very light on the brightness even when turned all the way up as well as HMCS. 2. Steer point does not show on HUD when selected. 3. TGP: BHOT and TV modes are too bright and unusable. 4. CCRP bomb fall line does not line up in HUD and no drop cue or timer. P.S. Please add key bind for ejection safety lever.
TheBigTatanka Posted June 4, 2020 Posted June 4, 2020 5. El Strobe does not display changes in altitude scanned in FCR. Dances, PhD Jet Hobo https://v65th.wordpress.com/
fullwoody Posted June 4, 2020 Posted June 4, 2020 i agree, the hud is very difficult to see now, the quality of the video on the TGP is terrible. same observations about bhot and whot. i noticed the same thing on the hornet as well yesterday. the flir quality was not nearly as good as it was.
jppsx Posted June 4, 2020 Posted June 4, 2020 same problem whit the tgp is to bright and have weird line in it
Pixelhead Posted June 4, 2020 Posted June 4, 2020 I found a fitst bug with f 16 before 10 min a new patch(bug with autocopy stirpoints) I dont know what are they doing with plane, every putch worst and the worst [sIGPIC][/sIGPIC]
Smoked Posted June 4, 2020 Posted June 4, 2020 6. Radar Elevation cursor does not show altitude change when moved (RWS) 7. Elevation cursor does not move in TWS. [sIGPIC][/sIGPIC] V55th FS | 55th DiscordViper pit Discord
CobaltUK Posted June 4, 2020 Posted June 4, 2020 Must assume Grip Reapers reported such issues but released anyway ? Windows 7/10 64bit, Intel i7-4770K 3.9GHZ, 32 GB Ram, Gforce GTX 1080Ti, 11GB GDDR5 Valve Index. Force IPD 63 (for the F-16)
falconzx Posted June 4, 2020 Posted June 4, 2020 6. Radar Elevation cursor does not show altitude change when moved (RWS) 7. Elevation cursor does not move in TWS. I confirm those bugs RDR Elev knob STUCK on middle position. :( It was working like a charm before :(
Recon21288 Posted June 4, 2020 Posted June 4, 2020 Must assume Grip Reapers reported such issues but released anyway ? Before or after charging ED for the privilege? :P Can confirm all of the above issues. AMD Ryzen 7 5800X3D @ 3.4GHz (Turbo's to over 4.0GHz) ¦ x2 32GB LPX Corsair 3600mhz ¦ Eagle 4070 OC 12GB ¦ Asus prime X370-Pro ATX AM4 ¦ Thrustmaster Warthog / AVA Base / FA18C Stick ¦ MFG v3 Rudder Pedals ¦ Track IR SYRIA | PERSIAN GULF | NORMANDY | SINAI | AFGHANISTAN | KOLA | NEVADA | FC3 | F5E | AV8B | F15E | F16 C | F18C | F4E | M2000 | A10C | MOSQUITO | FB VI | MIG29A | GAZELLE | UH1H | AH64D | CH47F | MI8 | KA50 | OH58D | SUPERCARRIER | http://www.twitch.tv/uncappingbadger
SCPanda Posted June 4, 2020 Posted June 4, 2020 I hope they can hotfix this soon. The radar elevation bug will make f-16 useless in A-A.
Bog9y Posted June 4, 2020 Posted June 4, 2020 Just had a little flight and yes, I also get all of the above issues. So annoying, got a flight planned tonight but won't be able to now. Is it possible to roll back to previous patch?
Briggz Posted June 4, 2020 Posted June 4, 2020 (edited) "1. HUD and HMD brightness is very low at max brightness. It's virtually impossible to see against light backgrounds. 2. Radar Antennae elevation controls do not work. Keyboard or bound. 3. New Steerpoints show HUD symbology and are usable by the autopilot. Preset steerpoints show no HUD symbology and are not steerable by the autopilot. 4. TGP designation vs CCRP target is ~100 yards offset. Point track on the TGP does not correspond to the actual ground targeted location for the CCRP cues. Possibly using the wrong altitude for the coordinates?" +1 Edited June 4, 2020 by Briggz
raptor909 Posted June 4, 2020 Posted June 4, 2020 Confirmed all above issue. A-10C | A-10C II | F/A-18C | F16C | AV-8B | FW-190 A-8 | MB339 | A-4E | CA [sIGPIC][/sIGPIC] https://simitaliagames.com/dcs/
Pwgilbert Posted June 4, 2020 Posted June 4, 2020 Response to New Patch 6-3-20 Does ED even look at the changes they've made before they release a patch? They should be embarrassed for putting out such crap.
Steph21 Posted June 4, 2020 Posted June 4, 2020 (edited) Just had a little flight and yes, I also get all of the above issues. So annoying, got a flight planned tonight but won't be able to now. Is it possible to roll back to previous patch? Yes it is, or fly on the Stable. I haven't updated the Open Beta yet, but how the hell this: DCS F-16C by ED Added ability to create new waypoints. Low altitude, Low fuel, High speed wobbling - fixed can cause everything listed in this post....amazing Edited June 4, 2020 by Steph21
Steel Jaw Posted June 4, 2020 Posted June 4, 2020 Well I dunno, I continue to believe the weak link is lack of beta testers. From a virtual point of view via BMS I know the F16C quite well and have offered my help in testing but it always falls upon deaf ears. "You see, IronHand is my thing" My specs: W10 Pro, I5/11600K o/c to 4800 @1.32v, 64 GB 3200 XML RAM, Red Dragon 7800XT/16GB.
Recommended Posts