Dinasty

Agreed, this has happened multiple times to me as well, instant mode reversion to RWS causing lost of track on both the target and missile guidance. The worst part is, you try to get jester to switch back to TWS mode to re engage the bandit, but its stuck in RWS. However i notice it happens more towards targets that have not been IFF, but we know its a bandit. Hopefully, Heatblur will come out with a fix asap.

Hi Doormouse, i concur with some of the bugs you are reporting. In short the tomcat radar system is very bugged at the moment. Just to share my recent experience, i am also experiencing: 1. In TWS mode, once a phoenix is fired at a TWS target, radar mode instantly reverts to RWS causing immediate lost track of target as well as missile guidance. However i notice this occurs more often towards targets that have not been IFF but are positively identified earlier by pilot. On top of that, unable to return to TWS mode and stuck in RWS mode when this occurs. 2.After launching a phoenix, there are times where the radar system refuses to exit auto tracking mode even after target tracking is lost, or missile is trashed ie hitting the ground,or spamming the PAL or PLM mode. When this occurs, no scan elevation at distance will be allowed, therefore disabling the pilot from beginning a new search for bandit. I dont fly with a human RIO, so i can say for sure this affects the solo tomcat jockeys. Its really depressing to deal with these bugs, but im positive that Heatblur will come up with a fix, its just a matter of time. Lets be hopeful. Cheers.

Lepas tu nak cakap pasal engineering awg9 radar dengan ustio tu buat apa? Hang ingat sarcasm hang tu sangat lucu? Orang tengah post pasal bug hang pula ejek, bila kena sakai cakap saya childish? Siapa yang lebih childish? Hang diam lah ki ma!

Or perhaps they should allow us the option to break track when we need to so that we can aquire other targets that are deem a bigger threat? Oh sorry, perhaps you like not being able to target something else after launching a missile. Weird, first ive ever seen. Kepala buto engkau mat saleh bodoh, sohai.

Yes Ustio, i have already reported it to Heatblur but im not sure if they will look into it because they havent responded. I also brought up this issue and started a thread about this tittled Jester TWS A. Its really stupid because you cant break the auto tracking mode, sometimes you can, sometimes u cant, by spamming the PAL mode. I feel you and i hope Heatblur will do something about it. It cause alot of problem when we are trying to search for a bandit via jester scan elevation function. Atleast allow us to break the auto track. Ever since the TWS Auto track function was implemented its been causing so much problems for us who use jester. Before this was that switch flicking party at the back seat.

Hi Heatblur team and fellow tomcat jockeys. This bug is a little more complicated to explain. As we all know when we fire a phoenix missile, the radar mode will automatically revert to TWS A with auto tracking within gymbal limit. When this occurs ofcourse the scan elevation at distance option will go missing from Jester menu as the radar is tracking a fired upon target. This is fine but however after turning cold and extending away from the enemy, sometimes the TWS A refuses to reset itself even after losing track, ie "lost tws lock", when this happens the scan elevation at distance remains not available. Also radar mode sometimes switches to RWS and no firing solution, and cannot be overrided. Ive triend re-engaging TWS mode with jester menu but to no avail. Spamming the PAL mode sometimes gets the radar mode to reset again but sometimes it doesnt and remains in TWS Auto tracking mode or sometimes RWS. This causes a serious problem when turning back hot to re-engage hostile bandits. Could anyone else provide feedback to this issue? I am pretty sure that i am not the only one experiencing this bug.

Yes it happens when TWS A goes bonkers if you previously asked jester to change azimuth or elevation scan. To avoid this for now, do not ask jester to manually scan both any elevation or azimuth, just leave it as it is. You can ask jester to set TWS mode during initial startup, but thats about it, otherwise he will conflict with TWS A once a phoenix is fired. We shall wait for a fix from heatblur.

Yes i am experiencing this bug on a constant basis since the TWS Auto update, the TWS auto is really messing up the gameplay as well the weird AWACS system. But i realize that this TWS auto bug happens when you get jester to adjust scan elevation or azimuth even before or during an engagement. It has caused me to lose engagements many times and also disables your pilot ability to PAL, VSL or PLM accompanied by that crazy non stop switch flicking noise . I already e-mailed heatblur twice and also sent them a message on facebook. I really hope they will fix this bug and also give us the option to use TWS manual as per before this update as i personally prefer less interference from the auto system.