dorianR666

i dont know what exactly causes this, but the track reproduces it 100% of the time. i press and hold the emergency jettison button while in 1G subsonic flight. everything is jettisoned - except the rightmost doublerack for amraams. i can try it again and again but that rack still wont get jettisoned. selective jettison works for it, and the rack finally gets jettisoned. jettison_fail.trk

old bug. its the windsock thats wrong iirc

The manual should reflect the ingame behaviour then. Most confusing.

dont select trig it will lase automatically as long as the missile is in flight

i have this problem too.

Its understandable for SAMs like Tor, but manpads are IR-guided and a glide bomb probably wont be particularly hot. Yep, havent seen them shooting at those. I suspect its caused by what category in loadout screen the weapon is in. It seems SAMs simply shoot at anything categorized in the "AG missiles" menu, including tiny APKWS. This thread is about a different bug though - manpads shouldnt have the ability to shoot at any munitions at all. The same way SA-2 doesnt shoot at glide bombs. ED probably forgot to (un)set a flag somewhere in some Lua definition.

interesting, i can no longer replicate it however i do have it on video, from some months ago. here is an LS-6 (GPS-guided bomb) being shot at by MANPADS. it was my own mission.

flir is targeting pod. if you have no targeting pod mounted, flir page wont be available. youre supposed to contact the jtac in the training mission, he will lase the target for you.

this was reported as bug multiple times and ED always keeps marking it as correct-as-is, either repeatedly not understanding the problem or not knowing how to make it work. dont hold your breath. i would also like to see this work.

Hello if you switch radar screen to night mode, there is a pixel in the center thats always on. mig19_pixel.trk

Hello, the afterburner texture inside the nozzle is bugged, upper half of it is much darker than the bottom half. steps to reproduce: just light up the AB and look from behind. mig19_afterburner_bug.trk

Hello, both engines can be started simultaneously, in conflict with what the manual states. mig19_start_bug.trk

Hello, if you enable pitot heat CB before switching on battery, the switch becomes bugged. Its jumping up and down erratically and cannot be moved in either position by the pilot. Until battery is switched on, then it gets unstuck. mig19_pitot_heat_bug.trk

Hi, what is this weird spot flying randomly on the radar screen? its moving left and right completely irrespectively of the scan line. Its there even when looking up the sky. There are no other units in the world, only me. is that some technical limitation of the radar or a bug? mig19_weird_blob.trk

Hello, the radar altitude warning is borderline inaudible. mig19_radalt_volume_bug.trk here you can see me rolling from side to side to trigger the warning off and on repeatedly. Being below set radar altitude should be pretty critical to the pilot, yet i can barely notice it. My DCS sound settings sliders are all to maximum.

I think you misunderstood the problem. If you are in INS mode *and* you use keyboard for TDC, the axes are inverted. TDC left makes designation move right, TDC forward makes designation move down. Should I make a new bug report with track and video?

happens more often than not on caucasus. i have encountered this bug several times during frontlines georgia DLC campaign. some bridges are more cursed than others, some have 100% chance of failure (i may add track tomorrow if i have time). made me learn not to add bridge crossing in my missions.

why was this moved to Resolved Bugs?

just gotta wait until they notice the thread.

ive seen iglas shooting at JSOW/GB-6, tho they never ever hit. they just waste their missiles

attached is the problem appearing entirely on ground power, without touching APU or engines. indeed it is as you say. the time window is extremely narrow. ins_bug_e.trk

great find! thanks that sounds like a realistic cause. i saw this problem once also when aligning on ground power (though i didnt save track), couldnt replicate it again. your explanation would make sense for it too.

With some more testing i found the following: Caution INS ATT will appear, yet HSI shows AINS. Not sure if thats possible. Whats interesting is the velocity vector on HUD is messed up, yet position is tracked and updated perfectly well on HSI - how?

Exactly. Do you think the real aircraft shows OK and then resets the alignment? If simulators should NOT count with pilot doing incorrect things, why do DCS planes have batteries running out of juice (Hornet)? Why do they have engine flameouts (Viggen)? Why do they have radar overheat (MiG-19/21)? The behaviour should be defined, not left to random nonsense appearing on displays.

what were your cautions and advisories?