CoBlue Posted August 22, 2020 Posted August 22, 2020 I see you didnt read the FM paper... https://forums.eagle.ru/showthread.php?t=281651 The answer was supposed to be posted here by NineLine, in the relevant thread, so much for keeping us informed :doh:. All Hud's still showing KEAS though! i7 8700k@4.7, 1080ti, DDR4 32GB, 2x SSD , HD 2TB, W10, ASUS 27", TrackIr5, TMWH, X-56, GProR.
bkthunder Posted September 29, 2020 Author Posted September 29, 2020 EAS vs CAS bug The bug was reported here (which isn't just an F-16 bug but affects all modules) https://forums.eagle.ru/showthread.php?t=276363 I see it has been marked as [NO BUG] even though it was acknowledged officially. I just checked in game and it is [sTILL A BUG]. Windows 10 - Intel i7 7700K 4.2 Ghz (no OC) - Asus Strix GTX 1080 8Gb - 16GB DDR4 (3000 MHz) - SSD 500GB + WD Black FZEX 1TB 6Gb/s
ED Team BIGNEWY Posted September 29, 2020 ED Team Posted September 29, 2020 (edited) Hi It seems the title was changed in error, I have changed it back to reported. the team do have tweaks coming. Please feel free to PM me next time. Thank you Edited September 29, 2020 by BIGNEWY Forum rules - DCS Crashing? Try this first - Cleanup and Repair - Discord BIGNEWY#8703 - Youtube - Patch Status Windows 11, NVIDIA MSI RTX 3090, Intel® i9-10900K 3.70GHz, 5.30GHz Turbo, Corsair Hydro Series H150i Pro, 64GB DDR @3200, ASUS ROG Strix Z490-F Gaming, PIMAX Crystal
bkthunder Posted May 21, 2021 Author Posted May 21, 2021 Ok so, it's been a while and unsurprisingly this bug is still affecting all modules. I don't know, maybe it's just me, but I thought having the correct speed reading on your hud is kinda important in a high-fidelity study-level sim... While I understand there are many bugs to squash, I truly find it astounding that a thing as basic and literally in your face as a speed reading is left bugged for years on end. 2 Windows 10 - Intel i7 7700K 4.2 Ghz (no OC) - Asus Strix GTX 1080 8Gb - 16GB DDR4 (3000 MHz) - SSD 500GB + WD Black FZEX 1TB 6Gb/s
WHOGX5 Posted May 21, 2021 Posted May 21, 2021 3 hours ago, bkthunder said: Ok so, it's been a while and unsurprisingly this bug is still affecting all modules. I don't know, maybe it's just me, but I thought having the correct speed reading on your hud is kinda important in a high-fidelity study-level sim... While I understand there are many bugs to squash, I truly find it astounding that a thing as basic and literally in your face as a speed reading is left bugged for years on end. IIRC Eagle Dynamics doesn't have any speedometer-programmers assigned to the Viper atm, only weapon-programmers, so I wouldn't expect a fix until the F/A-18C is out of early access. 2 -Col. Russ Everts opinion on surface-to-air missiles: "It makes you feel a little better if it's coming for one of your buddies. However, if it's coming for you, it doesn't make you feel too good, but it does rearrange your priorities." DCS Wishlist: MC-130E Combat Talon | F/A-18F Lot 26 | HH-60G Pave Hawk | E-2 Hawkeye/C-2 Greyhound | EA-6A/B Prowler | J-35F2/J Draken | RA-5C Vigilante
bkthunder Posted May 23, 2021 Author Posted May 23, 2021 On 5/21/2021 at 10:20 PM, WHOGX5 said: IIRC Eagle Dynamics doesn't have any speedometer-programmers assigned to the Viper atm, only weapon-programmers, so I wouldn't expect a fix until the F/A-18C is out of early access. Too bad this is not a Viper problem, but a problem in every single DCS aircraft with a HUD... Windows 10 - Intel i7 7700K 4.2 Ghz (no OC) - Asus Strix GTX 1080 8Gb - 16GB DDR4 (3000 MHz) - SSD 500GB + WD Black FZEX 1TB 6Gb/s
Recommended Posts