MBot Posted October 15, 2017 Posted October 15, 2017 The manual chaff programs do not dispense when putting the switch into INT or KONT.
QuiGon Posted December 22, 2017 Posted December 22, 2017 (edited) This bug is still not fixed. Has it been acknowledged? Edited December 22, 2017 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!
MBot Posted December 29, 2017 Author Posted December 29, 2017 The KB pod seems to be working again, at least if you set INT with a keybind (KONT with a keybind or INT/KONT by clicking the switch doesn't work). Also it seems that the jammers do not work at all.
QuiGon Posted December 29, 2017 Posted December 29, 2017 Yes, keybinds work, clicking does not. Also, see this thread: https://forums.eagle.ru/showthread.php?t=182367 There might be something wrong with the countermeassure release programms. I used the jammer 3 days ago and I think it was working for me. The MOTVERK indicator light up to indicate active jamming. But maybe that was because of countermeassures beeing released from the KB pod, which I had with me as well. Haven't payed close attention. But jamming was definately working in the past. 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 December 29, 2017 Posted December 29, 2017 Are you sure that the fast release switch is set in the right mode? It is located on the left side pinned to the canopy, just a bit back of SPAK and the autopilot buttons. Also you have to select the pods too if you're using any. Otherwise, this is a Heatblur-level problem. They're probably the only ones who would know how to fix it. Best of luck towards you anyways! It doesn't work if you click on the switch. Nothing happens. If you assign keys instead and press them it works. 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 December 29, 2017 Posted December 29, 2017 Sounds like it isn't modelled correctly in the cockpit, or it may be a HOTAS function. I guess for now you should probably just use the keybinds and bind them to your HOTAS. It's not a HOTAS function. There is a special CM fast release button on the throttle, which is a HOTAS function, but not the normal CM release switch on the canopy frame. 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!
MBot Posted December 31, 2017 Author Posted December 31, 2017 I used the jammer 3 days ago and I think it was working for me. The MOTVERK indicator light up to indicate active jamming. But maybe that was because of countermeassures beeing released from the KB pod, which I had with me as well. Haven't payed close attention. But jamming was definately working in the past. I think the MOTVERK light is due to the KB pod. If I only load the jammer without the KB pod, I no longer get a MOTVERK light. It did work some months ago.
QuiGon Posted December 31, 2017 Posted December 31, 2017 I think the MOTVERK light is due to the KB pod. If I only load the jammer without the KB pod, I no longer get a MOTVERK light. It did work some months ago. I did now fly a combat mission with this configuration again and this time I payed closer attention to it. I could not get the MOTVERK indication by switching the pods on (modes B/F-E/K as I was using the U22/A pod). So I checked the manual again and saw this: Pods will automatically emit when illuminated by a radar from the frontal aspect. So the pods can't be switched on to just emit by request and instead have to be illuminated from the front to start emitting. In this sortie I had threat radars to my left, but not to my front, so that might be the reason why the pod has never emitted in this case. I will have to check with frontal threats again. 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!
MBot Posted December 31, 2017 Author Posted December 31, 2017 I did now fly a combat mission with this configuration again and this time I payed closer attention to it. I could not get the MOTVERK indication by switching the pods on (modes B/F-E/K as I was using the U22/A pod). So I checked the manual again and saw this: So the pods can't be switched on to just emit by request and instead have to be illuminated from the front to start emitting. In this sortie I had threat radars to my left, but not to my front, so that might be the reason why the pod has never emitted in this case. I will have to check with frontal threats again. I did check it approaching a SA-6.
QuiGon Posted December 31, 2017 Posted December 31, 2017 I did check it approaching a SA-6. Alright, then I guess it's really broken, although it did work in the past after the Viggens release :( 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 December 31, 2017 Posted December 31, 2017 I just tested it again in a testing sortie. I turned the U22/A pod on, which gave me a KB-H/ KA SL indication as it warmed up. The indication disappeared after a while. I approached a A-50 Mainstay AWACS on my left, and my RWR indicated it was emitting, while the jammer stayed silent. I then turned left to face the A-50 and the jammer started jamming automatically, indicated by the MOTVERK light started blinking. So it worked as it should, at least in this test. 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!
MBot Posted January 1, 2018 Author Posted January 1, 2018 I just tested it again in a testing sortie. I turned the U22/A pod on, which gave me a KB-H/ KA SL indication as it warmed up. The indication disappeared after a while. I approached a A-50 Mainstay AWACS on my left, and my RWR indicated it was emitting, while the jammer stayed silent. I then turned left to face the A-50 and the jammer started jamming automatically, indicated by the MOTVERK light started blinking. So it worked as it should, at least in this test. Perhaps it is a version 2.2 thing, but it doesn't work for me.
MBot Posted January 1, 2018 Author Posted January 1, 2018 Well, I found the problem. In fact there seem to be multiple issues with the jammer. 1. For the U22/A pod, the program, B-E + F is not emitting. B-E + G-K is working. According to the manual, F should also emit. Since F is the default position on the second knob, this is an easy bug to walk into. 2. In an air-start, the selector is on A per default (which is pre-heat for U22/A). If you actually want pre-heat to work, you have to manually cycle the switch to 0 and back to A again. 3. U22 doesn't seem to pre-heat in either A or B with or without any cycling. 4. U22 doesn't emit in its sole mode A.
QuiGon Posted January 1, 2018 Posted January 1, 2018 That makes sense, as it fits my observations, because: 1) I usally use B-K instead of -F, although I don't have any particular reason for doing so. 2) I never make air starts. I do cold starts only. 3 + 4) I never tried the U22. 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!
RagnarDa Posted January 2, 2018 Posted January 2, 2018 (edited) Thanks for the reports! Hopefully fixed the problems. Not sure it will make it into next release but maybe the one after that. The issues was that setting mode F with U22/A would always set it to listening mode, the U22 wouldnt light the MOTVERK-lamp and one of the payloads was named U22/A but contained a U22 which might cause confusion. Also made it preconfigured for whatever pod you carried on a hot start. Edited January 2, 2018 by RagnarDa DCS AJS37 HACKERMAN There will always be bugs. If everything is a priority nothing is.
QuiGon Posted January 2, 2018 Posted January 2, 2018 Thanks for the reports! Hopefully fixed the problems. Not sure it will make it into next release but maybe the one after that. The issues was that setting mode F with U22/A would always set it to listening mode, the U22 wouldnt light the MOTVERK-lamp and one of the payloads was named U22/A but contained a U22 which might cause confusion. Also made it preconfigured for whatever pod you carried on a hot start. Thanks! 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 Thanks for the reports! Hopefully fixed the problems. Not sure it will make it into next release but maybe the one after that. The issues was that setting mode F with U22/A would always set it to listening mode, the U22 wouldnt light the MOTVERK-lamp and one of the payloads was named U22/A but contained a U22 which might cause confusion. Also made it preconfigured for whatever pod you carried on a hot start. Is the countermeassure release switch on the canopy frame fixed as well (see first page of this thread) or is just the jamming? 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!
RagnarDa Posted January 7, 2018 Posted January 7, 2018 I think I fixed that as well yes DCS AJS37 HACKERMAN There will always be bugs. If everything is a priority nothing is.
QuiGon Posted January 8, 2018 Posted January 8, 2018 (edited) I think I fixed that as well yes Awesome, thank you very much! :thumbup: Sweet! Does that include the text on the switch as well (see below)? Current: https://forums.eagle.ru/showpost.php?p=3063544&postcount=5 NORMAL - Normal MOTTAG - Receive SAND - Transmit What I think it's supposed to look like from the real plane: http://www.aircraftresourcecenter.com/awa01/501-600/awa519-Viggen-Toll/29.jpg https://i.pinimg.com/originals/cd/20/40/cd2040ced4406367c043bc0dcbe8c335.jpg https://forum.keypublishing.com/showthread.php?114029-Newark-Air-Museum-Briefing-2012&p=1869418#post1869418 KONT - Continuous? FRÅN - Off? INT - Interval? The DCS Viggen manual even refers to the positons of the switch as KONT, FRAN and INT, although the text in the cockpit is different as you pointed out. Edited January 8, 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!
renhanxue Posted January 8, 2018 Posted January 8, 2018 Yeah, the texture is from a JA 37 cockpit at the moment.
Recommended Posts