wadman

Yup - same here. Has Heatblur acknowledged this bug???

Some people like to get what they paid for - an unfinished module pretty much abandoned since April with no signs of resolution AND the possibility it will never get the planned updates and expansions doesn’t cut it for many people.

Game developers (as much as you claim otherwise, this is still game - very detailed, but still a computer game) would go bankrupt if they made products targeted to people like you. Gamers might have a hotas, pedals and VR - but even with all of the other things that you mention that you have, you are not even remotely getting the experience that a real pilot has. That said, I’d be OK to allow the unrealistic things to be tuned off for folks like you - but don’t make the rest of us suffer in the name of ”fidelity” when these “sims” can never deliver an experience that is close to real life.

It’s actually a game. Regardless, these “sims” will always lack the physical feedback/cues that a pilot would experience in the real world. So… having things like audible cues that might not be exactly realistic can be a good thing to help make up for the gaps!

Odd - it's working fine for me.

Where do you access/control this new AOA option?

Something significant appears to have changed with this patch and it's not good - F14 radar on TWS with AIM 54 seems "porked". In the Instant Action "Beyond Visual Range" mission on Persion Gulf Map, I could pretty reliably press in at a slight offset while reducing altitude and take out both Mig 29's with Phoenix TWS shots (one at ~30 miles and the second at ~19 miles). Now with ZERO changes on my end, the TWS tracks drop before 30 miles range and do not reappear. So... pre-patch both Migs could be taken out consistently - but... post-patch it's not possible as the tracks drop and do not reacquire for some reason. So something definitely got screwed up here. It's very frustrating as DCS never seems to settle down - I get's it's open Beta, but things that worked keep getting broken!

https://youtu.be/7BQaVbWgf60 Link to video showing this problem - I continue to be amazed at how major stuff like this is not caught in testing before release? I get it's a beta, but this is pretty standard settings for a higher end PC and with zero mods!

I see the same issue! How does something this obvious make it out? Does anybody actually review these updates comprehensively before they push them out? Geez!

And yet he got a very professional response and validation of the issue from Iron Mike. While I don't agree with all of the rhetoric used, the lack of a realistic trap model on this awesome represention of the most ironic naval aircraft of all time, this long into the release, is a little disappointing. It's nice to see that Heatblur acknowledges this and is committed to getting it right before they exit early access.

Yeah - WTF is up with that??? How can ED not fix this? They think it's OK for a sim that stresses realism to behave like this??? I can launch a smokeless AIM-54 from WAY beyond visual range and as soon as the missile is fired, the AI starts dropping chaff??? That is messed up and ED should be ashamed of themselves for not fixing this massive, very obvious flaw!!!

This approach seems odd (and surprising) to me and why there has been a big disconnect on the discussion on AOA indexer brightness - if you don't validate your changes in the actual game, how can you know that you actually addressed the user's issues? At the end of the day, how things work in the actual game we are playing are what matter?

Did some carrier landing practice today - what a pleasure to actually be able to use the indexer to confirm on-speed approach as I could actually see it clearly. Thanks again for the workaround for this bug!

Thank you - great find!!!!. Hopefully, this means that there is no reason that HB should not be able to formally fix this since this workaround proves that the indexer lights can be much brighter in the F14!

If the F14B, it's probably because you are launching in afterburner - which was prohibited in real-life, anyhow. That's the only time I've seen a blackout on cat launches.