toilet2000

Then change the bug to: IRMV image shows on right MFD (where it shouldn't). I just pressed Uncage and it showed on the right MFD. So that's a bug. :)

Got this bug yesterday. If the Maverick image is on the right MFD, there's no way to select IRMV via the SS Forward switch. EDIT: In fact, the video feed should not show at all on the right MPCD. Pressing Cage/Uncage shows the feed on the right MPCD (where it is impossible to reach IRMV via the SS Fwd) whereas it should show on the LEFT MPCD (as per the official RAZBAM manual).

Um, HB did it, so did the community A-4E team, so it's totally possible and both the AJS-37 and the A-4E have really good performance. EDIT: Changed A-6E for A-4E

Is it supposed to be static like that? Even while the aircraft is moving, the ground returns are static and there's not "update" scan and fade (i.e. persistance).

Quoting the Facebook post: Basically translates too:

You're in the wrong forum section. You're probably asking too many AI to take-off at the same time anyway.

No, it is a collimated sight, which means there's a lens collimating the sight and creating the chromatic aberration.

Number 4 and 5 are already reported.

1. Can you post videos on a more know source, like Youtube or Vimeo? "bilibili" looks pretty shady. 2. You're using a modded version of the A-10C to fire an RB-75 in that first video. Expect strange behaviors. As far as I can understand from your pretty bad english, you seem to be saying that there's no gymbal/tracking angle limit to the RB-75. As far as I know, it is a known issue that others have reported before.

Are you entering the waypoints with Longitude first and then Latitude (opposite of every other module)? Are you entering the waypoints in this format: DDMMSS? (and not DDMM.MM)

+1

Put the HUD to the Night position (under the HUD screen). Then, press the Scene Reject/FLIR button on the HOTAS. The FLIR should appear on the HUD.

Winter ends between the 20th and the 22nd of March in the Northern hemisphere, hence why Winter is often said to be ending on the 21st. Certainly not in February. Nobody refers to February as the last month of Winter. They actually never said they were releasing it before Christmas. They said, and that’s a quote: "We aim for Christmas, but we promise during Winter". Reasons for delay? Like anything: more work than planned, work items take more time than planned and more features added. You can most surely PM Nicholas if you want a refund for your preorder. He’s always been super lenient and helpful for those things. Since you seem entitled just because you preordered something, I really suggest you ask for a refund, so you don’t continue to act like an entitled kid.

I was just wondering if I'm the only one with this problem with the radar picture: In VR, it feels like the lower contrast compared to the DCS 1.5 makes it much harder to see details. Everything looks more washed out than in 2D. Am I the only one with this problem? Could it be because of my gamma settings?

+1, I’ve got the same issue.

I have the same issue as OP. +1

The GBU-12 is not supposed to be dropped at all. When loading a TPOD on a wing station, a GBU-12 (which has a similar weight to the pod) has to be kept at all time on the other wing's corresponding station. The loadout on that photo is a pure FAC(A)/Designator loadout or an "expended" loadout after a sortie (if the Harrier is landing, which it does seem to be doing). TL;DR That GBU-12 should never be dropped. It has to stay there.

+6

I agree! Any news?

That's for sure not how it works. At least according to Zeus' post, it is clear it's not like that. It's probably because it requires the dashed line to be multiple small non-dashed lines. With how things are drawn and move around, it might be a bit more trouble to make the coordinate transforms/linear transforms to keep every tidy. At least that's my guess. There's no way this is a "complex" problem like Zeus makes it up.

Yeah, the 11111111111111111111111111111111 kind of bug appears quite often too. I've seen it appear on time values and coordinate values.

Haven't yet tested the new changes, but you can use radar mode A2 to get a zoomed in view on the currently selected waypoint. Should give you a bit more details.

It is not the system described in the manual. Conversion to auto happens on the fly with a "ghost CCIP", really similar to the 3/9 or 5 mils A-10C consent mode. What you described is basically a "Z mark point" in A-10C terminology. Not the same. To be frankly honest, I happen to work a lot with graphics in general and C++. This is typically not a really complex task. I do understand that I do not know the limitation of DCS' API, but there's a lot of literature on said kind of task and I just can't figure how this could be a complex task. EDIT: To give more info on the CCIP-to-AUTO conversion. This is linked to complaint 1, where the CCIP cue should stay on the HUD even though the actual impact point is below the HUD. This makes it so you can designate "on the fly" a AUTO attack point AND convert directly to AUTO release, meaning it will give you the AUTO cues to release the bomb so that they impact at said point. Like I said, really similar to release consent modes on the A-10C.

I have the same issue.

Are we getting this on next OB patch this Wednesday?