Lord Vader

Hello @dutchili We would need a track replay to observe this behaviour as we're unable to reproduce it using your description. Thanks for understanding.

Hello @SaladinoSaurus Many items need further development on Steerpoint types in our F-16CM Block 50 CCIP, including geographic lines, preplanned threats, etc. Stay tuned for future updates. The current types and distribution are temporary.

Glad to hear you sorted it out. Happy to help.

Hello @moggel I do indeed see what you mean and it does look like a bug. However, when I tried that mission you shared or my own simple mission, that frozen radar issue doesn't occur. This leads me to believe you may have an assignment for that particular OSB button. Perhaps a stuck key? Can you confirm it's that?

Like I said, @Schlomo1933I bound both those keys to my joystick that it is working on my side. I also only have one entry for increasing and decreasing. If you have any modification to the keybinds, I suggest you temporarily remove them and try to bind these keys again. If it's working as intended, then you found your culprit.

Hi, @ACME_WIdgets You can observe the status of this item in the title of this thread. Thanks for your patience. We're investigating this. Edit: Also, that track you shared can't be replayed due to scripting.

Hi @vctpiland repliers. There does indeed seem to be a discrepancy in the TSD coordinate data. I have raised this internally for analysis.

Hey @Schlomo1933 I think you mean the TDU contrast rockerswitch on the TEDAC unit? I know it also controls the HDU contrast when projecting TADS but just making sure. I tried binding it to joystick buttons and it did work as intended. Unless I got the wrong rockerswitch, can you confirm which one exactly are you binding and how?

We are still conducting tests for multicrew syncing issues, including the autopage items reported above. We apologize for the inconvenience and hope to mitigate the issues very soon.

Hello @FalcoGer Thanks for bringing this up. We tested this internally and we see the message persists after crashing or reloading the slot with ALT-B. I've reported this internally for analysis.

It's a simplification, really. A way to be able to create navigation points as well as target points by adjusting altitudes. In the future, some new features will support better mission planning (DTC, for example). But that's still under development currently. Btw, love Darth Revan on your profile. Always appreciate a fellow Sith.

If that's the case, then you need to edit the mission and reduce the waypoint altitude to ground level or edit the waypoint to add the correct ground elevation. That's the rule of thumb for any waypoint to be converted to a target point on any aircraft. The weapon doesn't know the current altitude of the target, as it doesn't know its position until you tell it so. Like you describe, It will fly towards that point in the sky and obviously miss.

Hello @SaladinoSaurus Thanks for bringing this to us. This was reported internally for analysis.

I had asked for a track because I did try to land, load and unload weapons and couldn't reproduce. If you can make this happen then a track is needed demonstrating the steps towards the issue. Thanks for understanding.

I can't see anything done wrong. That doesn't mean something might have evaded my attention. The track is a bit long and I was focused on seeing the bug happening rather than trying to follow your flow. There doesn't seem to be many items to fail anyway.

Please understand we need to sustain such changes with documented evidence. Some items may sound counterproductive but if that's the way the real aircraft works, I'm afraid we can't make a change because it "feels better". If the documents say it, then that's what we'll do. Thanks for understanding.

Hi @NSAdonis85 I can see the behaviour you describe on your track, but for me in the replay the circular area appears small with both assigning via WPT or via TPOD. Something is off. However, when I tried to reproduce this on my own in a clean mission, I wasn't able to. Can you try to reproduce this in a smaller track, like starting hot in Caucasus and send me that newer track? I would appreciate it because I am unsure this is just happening on your side.

Like I said, if you only have guns available what mode other than AGR should be available? Again, we need documented evidence this should work any other way. So, once more, please send your evidence via PM to @BIGNEWYand we'll rectify if needed. I understand what you're saying about "feeling wrong" but we can't change logics without evidence.

Hi @[31st] Spider Like @Hive said, this is correct behaviour, if loading a weapon on the very center pylon, you cannot load any on the pylons beside it and vice-versa. This reflects real life operation.

Hi @merlin851526 Like others have mentioned, there could be an issue with altitudes (currently trying to fix this internally). Other than that, we have no reports of startup inability. This could be a local problem. A good practice when creating a bug report here is to create a short track with the issue occurring and we can analyse what's going on.

Hi @Magic Zach After a brief analysis, we feel that our current model for the canopy is correct. Thank you for your suggestion.

Hi @Matt Glover Can you please supply a track with this happening so we have a look? Thanks.

After review and with @itnfine analysis, it seems there was an error while conducting the Normal alignment procedures. Great to see the community lending a hand.

Hi @dutchili We need some more information on this. In my tests without any weapon available on the pylons, the radar is set to operate the AGR as the only available mode for the gun. If you think this is incorrect, please send non-classified publicly available information to @BIGNEWYand we'll have a look. @Yaga In what conditions does that happen? Can you supply a track for that?

@deltatangoand @Drangoll Try to reproduce the situations individually in a single or multiplayer as short as you can make them in a simple mission, preferably in Caucasus. You are talking about three different issues so maybe compartmentalize them to facilitate our analysis. Like I said, I was unable to reproduce any of those issues on my own.