Santi871

The 1st one is already reported, the 2nd one I can't reproduce, do you have a track?

Sorry, it's fixed. I must've not noticed it working properly since then and assumed it was still a bug since the report got buried quickly and didn't get a response. Thanks for letting us know though :)

here's another fun one :) sadly impact not visible https://streamable.com/qc4cb

Because the BRU-55 was added to the game without modification of the STORES and JDAM DISPLAY functionality.

Yes, but with the same JDAM variant.

STEP is not used to step between different JDAM types, it's used to step between different stations carrying the selected type - to be precise, between all stations carrying the selected type if QTY is unboxed, and between the selected stations if QTY is boxed and >1. It's perfectly possible to carry several types of JDAMs simultaneously ingame but as you say it's not possible to select them simultaneously. They can, however, be all powered on and aligned at the same time (which is usually the case).

What makes you think this is currently the case ingame? Because so far with everything that's been tested and said, it's not possible.

This is fixed internally.

A/G radar in general isn't a magic bullet that will fix all your problems, but it's just another tool. Using it against ships is the best use case since they stand out a lot. For ground units (especially non moving ones), it depends a lot more on the operator's knowledge/skill + intel since you will have to find a way to recognize what is a target and what is a building or a tree. For instance, airfields should be easier to recognize. However, finding a random target without knowing what to look for or any patterns would be quite difficult.

Perhaps it's a matter of semantics. RWS slewing (radar azimuth following the cursor) is not possible. RWS centering (radar azimuth centered by depressing the cursor) is.

It's not implemented yet.

Thanks, although I tried it in the dev branch and it doesn't seem to happen there, I'll try again just to be sure.

If you confirm then you can't do a stored heading alignment.

Question for mvsgas - have you verified the current INS drift after performing stored heading alignment? Steerpoint LOS indicator on HUD can easily be seen drifting across the HUD at several dozen meters per second while in flight. Seems excessive when docs indicate stored heading alignment quality is very similar to that of NORM. What do you think?

Nope, just clarifying what avrolanc was saying, but I'll try to find out. edit: can confirm this is a capability

The problem is you can only do it if you're carrying bombs and set them to AUTO mode, while avrolanc is pointing out it should be possible always regardless of payload or delivery mode (as long as it's in A/G master mode).

INR refers to the pod being able to remain more or less ground stabilized when masked, not extrapolating a moving target.

Bump, I think this one got buried rather quick a few months ago

This is the most exhaustive list I've seen so far.

There's supposed to be a WIND option in the stores page on the bottom row for conventional bombing calculations, but I'm not exactly sure what selecting it does - to be precise I don't know if it overwrites the current calculation with stored wind data or whether it enables wind to be factored in at all, or something else. Maybe ED can dig into it.

Those were fixed with the big TWS update a month or so ago. This bug seems new.

Edit: didn't read the -1 g part.

This can be done by rendering the MFDs on a 2nd monitor via viewports and recording that - I'm not sure it's possible without a 2nd monitor. That also obviously comes at the cost of performance. HUD recording outside of tracks isn't possible.

I'm away from home right now, but have in mind the mini acquisition raster is neither RWS or LTWS or TWS, it's a special "transition" mechanic to acquire STT, hence why it should (likely) be cancellable with undesignate to return to RWS/LTWS/TWS. You can trigger this mini acquisition raster by depressing the TDC over empty space. The radar also automatically performs this if it doesn't find the target when you attempt to STT over a HAFU. Perhaps inquire the team about this. To clarify, what we're saying is that since the TWS update, we can no longer cancel this mini raster and we have to let the radar perform it for a few seconds which makes the radar unusable until it's done (ie the undesignate L&S functionality takes priority over canceling the mini raster).

My apologies. I've been meaning to update the tool as a whole and get rid of any antivirus flags - my PC is clean but I'll spool up a VM and compile it there to see if that fixes it. Just haven't found the time to do it and I'll be out of the country until late January.