cheg

By this time I think that whoever is prioritizing tasks in their sprints should quit.

I agree to your assessment. I feel there is a big focus on new features rather then finishing old things. As well goes the same on the topic of bugs, where some trivial bugs are not fixed for 5-6 months now and are pretty basic game features.

To be honest, I have simply stopped playing the game and just sporadically check if the bug is fixed. And I think this will be the case more and more. They are a small team, and should focus on bugs rather than developing ambitious features. This looks to me that they have a bigger underlying problem.

It's amazing that such a big update was done and such a trivial bug is not yet fixed.

Still not working.

Same experience here

Update: again a new update and still no fix. Really disappointed…

I see this bug as quite relevant to fix. I really fail to understand why it is not addressed now, after 3 updates.

at least that a mod confirms that they know it

So new update came out and this is not fixed even tho its a small but relevant bug Did any moderator noticed this one?

Means that when I'm on a server i see K/D of players set to 0 even though i know they have killed a ground unit or a air target, or their losses are 0. Whilst the score goes up. null

Any plans for the AC 130? Think would be pretty cool to have it! Some version like AC-130U? https://en.wikipedia.org/wiki/Lockheed_AC-130

As the title says, seems like the Kills and Deaths on servers is not working. The score seems to be working.

+1

+1

There is also another issue I have noticed, and that is maybe related with this whole "refresh" thingy with the weapons, that when I boresight a maverick, and then i use PRE mode all is fine, but when I switch to BORE mode, HUD does not display the cross / or better yet to say its outside of the HUD (either way left or right, depending if its the left or right wing pylon selected) so BORE mode is unusable when maverick is boresigted... Except if I'm missing something?

It does but then in a second or two goes back... It seems it cannot keep the target in focus. But maybe it is an alignment issue? I did have that time something like 2/55 (aprox)

Hi there, On random I have noticed that the TPOD (and I believe it's also related to the HARM/HTS Pod) starts losing my target and aiming in some random direction for no reason. I have provided two images. I aim at a target (on WP3) and then press TMS UP, and i get a "target" but then this target changes every few seconds to some random target that is in this case behind me. This stopped when i took a new plane. But there was no reason for this to happen. I have landed and repaired the plane, reloaded it and didn't have it fixed. So I'm suspecting its a bug.

So In regards with HARM not wanting to lock nullAfter firing some harms, landing and reload and repair, get back in the air then it says on the harm BIT even tho master arm is on and i believe the other conditions to fire are met. But I still cannot lock on to any targets (see on the image).

I do agree... I don't use it as much (even tho im fairly new to the game), but sometimes its convenient if i wanna grab a coffee But for new people it is confusing i think. As you said, it is implied that its "taxi ready"... Or maybe add a bit more instructions there and mention to the player that they need to finalize the alignment...

Hi, So I have noticed that when switching (after a cold start or reload) in air or on ground that when I switch weapons from HARM to Mavericks it gets bugged - where it should say VIS - BORE - PRE, it says HARM. And to temporary fix it, i need to click on A-G and then again A-G, then I get the normal selection for Maverick modes. As far as I remember this was not the case before? Also on random I have noticed when using HARM's it can happen that the HAD screen gets bugged that i cannot target anything or that i have invisible targets. I'll record this bug and post it as soon as I repeat it.

Hi, So I noticed after the last update that the autostart script for the F16 has a weird thing where when it comes to INS Knob - NAV it leaves it there (even tho i have noticed it "confirms the LAT and LNG" with an enter, but the knob is left on the ALIGN mode. So I checked the Macro_sequencies.lua and it seems that part is commented out. So I'm wondering is this intended or? null