dorianR666

Whether you can be shot at depends on your altitude, direction and speed. The circle on SA page is just a circle with static radius. Its approximate. You can be in range while being outside circle and be out of range while being in circle. But some circles might need a bit of adjustment by ED.

after getting hit, the tower turns green and has no collision box.

in fact, it gets even worse. @Flappie some objects lose their collision boxes and can be repeatedly shot through (T90, soldiers, BMP3). and the guard tower becomes green when hit. the T90 later regains collision box for 30mm cannon. i suspect this whole bug cuts far deeper than it seems at first sight. memory writes into wrong locations, scrambling both physics and graphics? or some incompatibility between weapons and static objects? 2.trk this whole mission, or maybe this particular CA vehicle, or its weapons, behave insane.

it isnt fixed f_shape.trk

like this? please make a post there.

Ive had a track fail within 2 minutes. It didnt record my keyboard press-and-hold of rudder input on taxiway, resulting in me going full afterburner 90 degrees perpendicular to runway during replays. It seemingly forgot to insert that input into the trackfile. There are software bugs in the trackfile functionality that simply are less probable to manifest in short trackfiles. But they fail too sometimes, rarely, but they do.

is something like this intentional ED? seems a bit excessive to me. they also tend to fly perfectly horizontally while all other smokes go more up (can be seen in these screenshots).

i have seen this too. sometimes vehicle smoke is extremely wide or long, it looks like an oil refinery is on fire instead of a truck. no idea how to replicate it.

Did you try running DCS repair?

Ah, I get it now. I got confused by your screenshot pointing at the mission editor ETA field. Thats there mostly to setup TOT with the checkbox on the right. What you describe is weird indeed and sounds like a bug.

that looks like chucks guide to me. its unofficial community-made guide, not module manual. its contents are derived from observed gameplay, not prescriptive of how the game/aircraft should behave. TOT cannot be automatically calculated for F10 marks because there isnt a way to specify airspeed or time for them, unlike mission editor waypoints. you must enter TOT manually for these waypoints in cockpit.

The 5MB file limit is absurd in 2021. It sometimes doesnt even fit official campaign .miz files, let alone the track data. ED pls bump this limit to something actually usable.

Dont forget EMCON and its HOTAS logic. Edit: WobblyFlops already mentioned this. IIRC, ED said that they wont do this one.

cant wait for this. is there a good chance for release this summer?

yes, this stopped working.

The DCS F-16 is CCIP version, which is avionics tape M4.2 if im not mistaken. Those publicly available MLU tape M1 to M3 manuals should apply, unless explicitely overriden by later tapes' manuals.

The manual explicitely says the knob is two-position, not three position. So the bug is: 1) player cannot return the knob to center position 2) manual is wrong yes?

I see. Its not explained in the manual. Thanks.

hi not much to explain here: the afterburner effect is also wider than the nozzle: m2000_ab_bug.trk gamma 2.3

hi, if you set VTB brightness to minimum, almost all of the symbology disappears as expected. but some of them dont. these remnants are, i assume incorrectly, wired to contrast instead of brightness. expected behaviour: brightness of all symbology is controlled by the brightness rotary. m2000_brightness_bug.trk

hi if you select magics with CNM, select horizontal radar mode with WSC - this happens: m2000_mag_bug.trk

hi EDIT: Misunderstanding on my side, bug exists but is something else default position of this knob is impossible. in can either be in HG or BD positions. it cannot be in the middle. once player moves it into HG or BD, it can no longer be put back into (impossible) center position. quote from manual: The two-position outer rim knob rotates to select Haut - Gauche (HG) or Bas - Droite (BD) test positions. Player should be able to put the knob in center position. This isnt possible after selecting HG or BD. m2000_ils_bug.trk

hi if you select cannon for AG, there is *always* one rate of fire (LEN or RAP) selected. RAP being the default one. its not possible to make both of them be unselected. for AA cannon, this is borked. when you select AA cannon, neither LEN or RAP are selected. once you select one, it works correctly and you can never again make both of them be unselected. example situation: you select AG cannon, leave AG cannon, enter AA cannon - a rate of fire will be selected. but if you havent entered AG cannon before, none would be selected in AA cannon. surely this cant be right.

hi. with target locked with PIC in B-scope, there is this short line that very rapidly flies left and right with even tiniest banks of players plane, but usually is off-screen. m2000_weird_line.trk

Im not entirely sure this is a bug, but it is suspect. m2000_inverted_house.trk when you look at this picture. the current waypoint is roughly at my 4 o'clock. you can see that on the HSI/IDN. yet HUD is telling me to turn left? i'd be doing a 270 degree turn instead of 90 degree. when the house is roof-up, so to speak, im supposed to chase it. when its roof-down, im supposed to turn in the opposite direction of it (???), with current implementation. is this how its supposed to work? shouldnt i be chasing it in both cases? its confusing and counter-intuitive for no reason.