dorianR666

indeed. somebody found this out on the forum about half a year ago, thanks to that guy and his info i was able to play comfortably without bricking my radar half the time ever since. you simply mustnt switch to guns while already having locked a target from rws/tws.

close up

if this is gonna be ignored yet again.... the_goddamn_axis_flip.trk

unfortunately, despite all the GACQ bugfixes, the yesterday OB update still has this bug.

you can have 3 preconfigured settings of radar (using SET function). that minimizes button presses on radar screen to minimum.

Happened only once and in multiplayer, tracks are problematic there. However i have a screenshot of another suspicious HAFU behaviour. On radar page, target locked in STT, onboard half of HAFU says unknown, datalink half of HAFU is missing. Yet on SA page the target is datalinked as friendly. How come the bottom half of the HAFU is missing on radar page? Its not just attack radar page, but az/el page too. HAFUs cannot be trusted and are WIP. Or is this a misunderstanding on my part?

Last patch i managed in multiplayer to get into a state, where the softlocked target was displayed as confirmed hostile HAFU on radar page, but friendly HAFU on SA page. Its still a mess. I suppose HAFUs and MSI are kind of inseparable, cant really blame one without the other.

HAFUs are terribly broken since TWS was added, so its probably WIP.

not only undesignate, lock lost by gimbal limits does it too. to avoid this bug, do not do the following: lock a target in rws/tws and then switch to gun. if you avoid doing this, the bug will not appear in my experience. unlock the target while in rws/tws with reset button on radar page before switching to guns. this bug was reported multiple times over the past year, with tracks added - i myself provided tracks, steps to reproduce and video recordings. it always gets ignored for some reason. the old threads got merged recently too.

bindings are separate for each plane, so it working in su-25 is meaningless. you probably accidentally deleted the mapping.

i see. it is annoying as hell.

yes, i see this bug (?) too. brightness sometimes resets to original level (dim at night), after switching mastermodes or pages. is that how its supposed to work?

ive seen this too. i think its manually edited mission file in text editor. mission editor doesnt allow it.

perhaps this function could be used. it should return what entity is being tracked by radar. i havent tested it though. https://wiki.hoggitworld.com/view/DCS_func_getRadar

ignore trains, there are so many things not working in them. not sure why ED spends time and money developing such things when they cant even be used. wasted resources.

liveries can be packed with campaigns tho, so you can try that

i confirm this bug. tracks cannot be promoted sometimes and you have to leave and reenter tws for it to work again.

late activated ships or ships spawned from lua dont work right in multiplayer IIRC that might be your problem

you must boresight the mavericks if you cold start

yep, it doesnt work in override modes.

unless something changed recently: there is only one ECM type in the game, and all aircraft with ECM have that same ECM. its only a boolean flag - ecm on or off. there is no difference in types, there is no difference in strength/range. jf-17, f-14, viggen, mig-21 in the game all have the same ECM so to speak.

they dont magically know about you. actually you can even fly in formation with them if you are below and behind, they wont see you. however beware that enemy units share information. if enemy ground radar sees you, all enemy aircraft will become aware of you too.

+1

speaking of altitude warnings - is it just me, or is the break X on MFCDs absolutely spastic? i sometimes get it even while several hundred feet above ground, pitching up, over flat terrain. is it bugged?

i have seen this happen a few times (sudden shutdown of both engines in dive), but i dont know the exact cause either. might have been messed up input bindings, who knows.