Dirkan Posted June 11, 2017 Posted June 11, 2017 (edited) Tested the weapon status display by selecting TAKT. For those of you who don't know, you can see if a weapon is loaded on a pylon or not by looking at the numbers. There's no number for the centerline drop tank. |x|x|x|x|x|x| x can be either "-", "1" or "0" A 1 indicates a weapon is on the pylon and is ready to be used. A 0 indicates a pylon is empty. A - indicates the weapon is inoperable. The bugs: The far right number (for the outer right wing pylon) is broken, since it always displays 0, no matter if you have a sidewinder loaded there or not. The number 1 doesn't change to a 0 on any of the stations when firing: RB05 RB04 RB15 BK90 RB24 RB24J RB74 [*]FÄLLD LAST doesn't light up after having fired: RB04 RB15 Even though the game manual states that FÄLLD LAST should light up when firing the BK90, the declassified manual states that the only indication is of a successful release is through the CK37 display, or if you move the master mode selector to SPA and then the FÄLLD LAST should flash, indicating that weapons are still on the pylons. Furthermore, only IMPULS mode for dropping them should available. Currently, we can drop them with SERIE mode as well, which contradicts the declassified manual. These bugs are reproducible by loading up the mission editor and trying out the different weapons and attacking according to the checklist. UPDATE 2018-06-10: Bug number 1 is fixed. Bug number 2 is still reproducible. All the numbers change to 0 after pressing the emergency jettison button though, if that helps. Bug number 3 is still reproducible Edited June 10, 2018 by Dirkan One of the bugs are fixed. 1 1
RagnarDa Posted June 11, 2017 Posted June 11, 2017 I've noticed and fixed the TAKT thing just minutes ago! Thanks for reporting on the FALLD LAST issue! DCS AJS37 HACKERMAN There will always be bugs. If everything is a priority nothing is.
Rudel_chw Posted June 11, 2017 Posted June 11, 2017 I've noticed and fixed the TAKT thing just minutes ago! Thanks for reporting on the FALLD LAST issue! I'm glad to see that Heatblur does check these bug reports, the Viggen is such a nice product ... its actually the plane that I enjoy the most of all those currently in DCS, and it deserves to be finished. Best regards. For work: iMac mid-2010 of 27" - Core i7 870 - 6 GB DDR3 1333 MHz - ATI HD5670 - SSD 256 GB - HDD 2 TB - macOS High Sierra For Gaming: 34" Monitor - Ryzen 3600 - 32 GB DDR4 2400 - nVidia RTX2080 - SSD 1.25 TB - HDD 10 TB - Win10 Pro - TM HOTAS Cougar Mobile: iPad Pro 12.9" of 256 GB
Cobra847 Posted June 12, 2017 Posted June 12, 2017 I'm glad to see that Heatblur does check these bug reports, the Viggen is such a nice product ... its actually the plane that I enjoy the most of all those currently in DCS, and it deserves to be finished. Best regards. We read every single post, we just don't have enough time to respond to everyone. Sorry! :( Nicholas Dackard Founder & Lead Artist Heatblur Simulations https://www.facebook.com/heatblur/
TomCatMucDe Posted June 12, 2017 Posted June 12, 2017 We read every single post, we just don't have enough time to respond to everyone. Sorry! :( Yes please, keep working on the Tomcat! :)
some1 Posted July 29, 2017 Posted July 29, 2017 I've noticed and fixed the TAKT thing just minutes ago! Thanks for reporting on the FALLD LAST issue! Pics or didn't happen. TAKT is still broken in 1.5.7, does not change to 0 after firing missiles, FALLD LAST light is broken too. Hardware: VPForce Rhino, FSSB R3 Ultra, Virpil WarBRD, Hotas Warthog, Winwing F15EX, Slaw Rudder, GVL224 Trio Throttle, Thrustmaster MFDs, Saitek Trim wheel, Trackir 5, Quest Pro
QuiGon Posted December 31, 2017 Posted December 31, 2017 (edited) I don't know if I'm doing something wrong or if the TAKT indication is totally broken, because I've never seen it displaying anything else than 111111? I usally fly multiplayer, starting cold and clean on the ground, loading the BK90 and when I drop them on the target the TAKT indication remains unchanged at 111111. FALLD Last light does not work either in this case. Edited January 4, 2018 by QuiGon Intel i7-12700K @ 8x5GHz+4x3.8GHz + 32 GB DDR5 RAM + Nvidia Geforce RTX 2080 (8 GB VRAM) + M.2 SSD + Windows 10 64Bit DCS Panavia Tornado (IDS) really needs to be a thing!
QuiGon Posted January 7, 2018 Posted January 7, 2018 Can someone confirm that weapon status display in TAKT mode is not working and always shows 111111 no matter what? Intel i7-12700K @ 8x5GHz+4x3.8GHz + 32 GB DDR5 RAM + Nvidia Geforce RTX 2080 (8 GB VRAM) + M.2 SSD + Windows 10 64Bit DCS Panavia Tornado (IDS) really needs to be a thing!
unknown Posted January 7, 2018 Posted January 7, 2018 Can someone confirm that weapon status display in TAKT mode is not working and always shows 111111 no matter what? I did a quick test in 1.5.8 OB, air start from mission editor. High drag, low drag, HE rockets and the RB 75(at least the one i could launch before my targeting cross started to jump around) was all fine, TAKT showed 100001 after firing, before shoed 111111. I didn't test anything else. 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, F-4E Phantom II 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
grunf Posted January 7, 2018 Posted January 7, 2018 I know for sure that TAKT shows proper values for high and low drag bombs. It does not update value for RB04, RB05, BK90 and air to air missiles - it always shows 1. I don't know about the other weapons.
QuiGon Posted January 7, 2018 Posted January 7, 2018 I know for sure that TAKT shows proper values for high and low drag bombs. It does not update value for RB04, RB05, BK90 and air to air missiles - it always shows 1. I don't know about the other weapons. Thanks, that fits my observations! So, what's the status on fixing this @Heatblur? Intel i7-12700K @ 8x5GHz+4x3.8GHz + 32 GB DDR5 RAM + Nvidia Geforce RTX 2080 (8 GB VRAM) + M.2 SSD + Windows 10 64Bit DCS Panavia Tornado (IDS) really needs to be a thing!
QuiGon Posted February 10, 2018 Posted February 10, 2018 Just noticed this bug again, this time with RB05s. Intel i7-12700K @ 8x5GHz+4x3.8GHz + 32 GB DDR5 RAM + Nvidia Geforce RTX 2080 (8 GB VRAM) + M.2 SSD + Windows 10 64Bit DCS Panavia Tornado (IDS) really needs to be a thing!
some1 Posted June 9, 2018 Posted June 9, 2018 And a year later, it's still broken. Sigh... Hardware: VPForce Rhino, FSSB R3 Ultra, Virpil WarBRD, Hotas Warthog, Winwing F15EX, Slaw Rudder, GVL224 Trio Throttle, Thrustmaster MFDs, Saitek Trim wheel, Trackir 5, Quest Pro
QuiGon Posted June 9, 2018 Posted June 9, 2018 Indeed :( Intel i7-12700K @ 8x5GHz+4x3.8GHz + 32 GB DDR5 RAM + Nvidia Geforce RTX 2080 (8 GB VRAM) + M.2 SSD + Windows 10 64Bit DCS Panavia Tornado (IDS) really needs to be a thing!
Dirkan Posted June 10, 2018 Author Posted June 10, 2018 Tested them again. Bug 1 is fixed, but the others are still reproducible.
RagnarDa Posted June 10, 2018 Posted June 10, 2018 Hi everyone! I've fixed the issue now. Thanks for the reports! The reason it took so long is because the issue is of pretty low severity compared to other issues I've been working on like the gun-sight issue. See for example here: https://www.softwaretestinghelp.com/how-to-set-defect-priority-and-severity-with-defect-triage-process/ DCS AJS37 HACKERMAN There will always be bugs. If everything is a priority nothing is.
Dirkan Posted June 10, 2018 Author Posted June 10, 2018 Thanks Ragnar! You're awesome! Understood and good to know. Is there a way to see what bugs you guys are working on or what have been reported? Like a bug tracker?
some1 Posted June 11, 2018 Posted June 11, 2018 Hi everyone! I've fixed the issue now. Thanks for the reports! The reason it took so long is because the issue is of pretty low severity compared to other issues I've been working on like the gun-sight issue. I wonder what the uproar would be if the Stores MFD page in the Hornet was broken like that for a year :) Hardware: VPForce Rhino, FSSB R3 Ultra, Virpil WarBRD, Hotas Warthog, Winwing F15EX, Slaw Rudder, GVL224 Trio Throttle, Thrustmaster MFDs, Saitek Trim wheel, Trackir 5, Quest Pro
QuiGon Posted June 13, 2018 Posted June 13, 2018 Hi everyone! I've fixed the issue now. Thanks for the reports! The reason it took so long is because the issue is of pretty low severity compared to other issues I've been working on like the gun-sight issue. See for example here: https://www.softwaretestinghelp.com/how-to-set-defect-priority-and-severity-with-defect-triage-process/ Thank you very much! While it hasn't been a critical issue indeed, it was still pretty annoying. I'm glad this is fixed now :thumbup: Quick question: Is the TAKT weapon status and the FÄLLD LAST light working for all weapons or are there some weapons where this does not apply (as in real life)? Intel i7-12700K @ 8x5GHz+4x3.8GHz + 32 GB DDR5 RAM + Nvidia Geforce RTX 2080 (8 GB VRAM) + M.2 SSD + Windows 10 64Bit DCS Panavia Tornado (IDS) really needs to be a thing!
Dirkan Posted June 13, 2018 Author Posted June 13, 2018 Thank you very much! While it hasn't been a critical issue indeed, it was still pretty annoying. I'm glad this is fixed now :thumbup: Quick question: Is the TAKT weapon status and the FÄLLD LAST light working for all weapons or are there some weapons where this does not apply (as in real life)? There are a few weapons where the weapon status and lights don't apply, like for rockets and gunpods as far as I know.
QuiGon Posted June 14, 2018 Posted June 14, 2018 There are a few weapons where the weapon status and lights don't apply, like for rockets and gunpods as far as I know. That's why I'm asking, as i would like to know for sure if this is actually the case and if so with which weapons? Intel i7-12700K @ 8x5GHz+4x3.8GHz + 32 GB DDR5 RAM + Nvidia Geforce RTX 2080 (8 GB VRAM) + M.2 SSD + Windows 10 64Bit DCS Panavia Tornado (IDS) really needs to be a thing!
Dirkan Posted June 14, 2018 Author Posted June 14, 2018 (edited) Well, I had to go through the entire part 1 and 3 of the scanned Viggen manuals. Sources: Viggen manual part 1, section "Flik 25, "Beväpning" Viggen manual part 3, section " Flik 7, Attackuppdrag" This post is how it should be, and may or may not be what actually happens in DCS. Note that you can do a weapons check of the pylons by moving the Mode Selector to SPA. FÄLLD LAST will flash if certain ordnance remains on the pylons. For some ordnance, FÄLLD LAST will flash even though only the pylons remain. The AKAN gunpods, ARAK rocket pods, RB05, RB04, and M71 bombs are classed as "old" weapons, and will not update themselves with the new electronic logic to the CK37. Thus, their status will always be static (1 or 0 no matter if fired or not) on TAKT. FÄLLD LAST light will sometimes indicate that you launched any of those (according to the spreadsheet below), and sometimes setting the Mode Selector to SPA make FÄLLD LAST flash (spreadsheet). Ordnance launch failure and emergency jettisoning is not something I bring up here. I assume normal, successful and complete launches of all ordnance. For Impuls or Serie concerning the Anti-ship missiles, FÄLLD LAST should light up either after the first missile is fired in Impuls mode, or after both have been fired in Serie mode. FÄLLD LAST: Is the light ON or OFF after firing the weapon? TAKT: What number shows on the relevant pylon if the CK37 selector is set to Takt? Two numbers=Before/After firing SPA flash: if the mode selector set to SPA, the FÄLLD LAST light flash if the weapon(s) is/are still on the pylon (W), or with the pylon remaining (P) no matter if the weapon is hanging on it or not. ORDNANCE FÄLLD LAST TAKT SPA Flash ARAK, AKAN NONE 0/0 NONE RB 04, M/71 HD, LD, Illu ON 1/1 W RB 05 NONE 1/1 NONE RB 24, RB 24J, RB 74, RB 75 NONE 1/0 NONE RB 15 ON 1/0 P BK 90 NONE 1/0 W Edited February 12, 2021 by Dirkan Corrected some errors with the new table 1
QuiGon Posted June 16, 2018 Posted June 16, 2018 Thank you vry much Dirkan! That's exactly what I needed. Looks like there is still some work to do on the weapon status indication then, as I'm pretty sure there are still differences on how it works ingame atm and how it should work. I might do some testing and add the results to your table. Intel i7-12700K @ 8x5GHz+4x3.8GHz + 32 GB DDR5 RAM + Nvidia Geforce RTX 2080 (8 GB VRAM) + M.2 SSD + Windows 10 64Bit DCS Panavia Tornado (IDS) really needs to be a thing!
Dirkan Posted June 16, 2018 Author Posted June 16, 2018 Thank you vry much Dirkan! That's exactly what I needed. Looks like there is still some work to do on the weapon status indication then, as I'm pretty sure there are still differences on how it works ingame atm and how it should work. I might do some testing and add the results to your table. You're welcome QuiGon. I look forward to it.
Recommended Posts