toilet2000

There's a pretty good way to tell if your weapon needs QFE or not. Smart weapon: it doesn't (BK-90, AGM-65) Otherwise: is there a "fin" appearing above the aiming dot on the HUD? Yes -> No need for QFE No -> You need QFE

I think you're absolutely right about that. Makes totally sense, and it corresponds to the description of radar ranging used in the manual. I'll try setting QFE as soon as I'm home and report whether it works or not. Although there is still an issue with the symbology (both in A1 where the symbology is not a cross, but a simple curve like in the RB-04 symbology, and in A2 symbology where it simply does not match at all what is presented). Actually, I think the A2 radar mode isn't what it is supposed to be. As far as the documentation goes, I feel like the A2 mode should be more useful than it is currently and certainly more detailed. It seems like the radar continues to scan at the full 123 deg at 110deg/s pattern instead of the 64 deg at 60 deg/s pattern described on page 112 of the manual. That, and the transformation from A-Scope to B-scope seems to put forward the low amount of rays using for the raycasting simulation of the radar.

This is true for the Nav release (i.e. if you stay in Nav master mode and go trigger unsafe), where you actually need QFE. For RR (radar release), it shouldn't need QFE at all since it is using radar ranging. The problem is, switching to ANF and going trigger unsafe doesn't seem to switch the systems to RR bombing, but instead it keeps everything just as in Nav bombing. That, and the RR symbology from the manual do not match the symbology shown in game at all. In fact, the symbology in A2 (B-Scope) mode is simply wrong.

I had the same problem today. Datalink not working in MP at all. Can't receive or send.

I tried bombing using the RR radar move (master mode ANF). The symbology shown on the radar does not match the manual (both in A1 and A2 mode) and the bomb would not release at all. I've attached a track showing this behavior. Latest open beta patch. ajs37_rr_bombing_bug.trk

That doesn't make any sense. The reason why some airplanes (like the Harrier) cannot "use" the Maverick on certain MFDs is because the video wiring is absent on one or several screens. It should prevent the user from showing the Maverick feed on the right MPCD (as it is not wired), but the user should still be able to control the seeker, as it is still wired to the HOTAS (if the seeker is uncaged). And the Cage/Uncage behaviour (i.e. it shows the feed on the right MPCD) is a bug. From the official RAZBAM manual:

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?