toilet2000

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.

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.

I agree! Any news?

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.

I have the same issue.

Are we getting this on next OB patch this Wednesday?

You're in the wrong forum buddy. This is the F/A-18C wish list subforum. You should have posted in the NTTR map subforum.

For LTWS, IFF and Datalink need to be working. My guess is simply that they're working on that before they can actually work on LTWS (which makes extensive use of IFF and most importantly Datalink).

You're doing the same thing wrong as in this video: I commented on that one explaining what's wrong: And some more info that I commented on why this is happening: As a simple rule: if you're not planning to pull-up, use Bomb Plan (even for dive bombing). If you want to do that pull-up release (for accuracy), use Bomb Dyk.

For the RR bombing mode in A2 (the plan and not the polar radar mode), I did report the missing functionality back then. The radar cue is simply not working in this radar mode (it's just the same symbology as the A1 mode, whereas it should be a straight line and at a different position).

If it is not already something done in DCS, I suggest sharing the depth buffer with the Oculus SDK. The upcoming ASW 2.0 tech uses this depth information and prevents at lot of the artifacts that ASW 1.0 causes. See: https://uploadvr.com/oculus-rifts-asw-2-0-could-greatly-reduce-artifacts-on-low-end-systems/

I would really like to see a fix for this issue.

The whole reason for zoom both in VR and 2D is because our screens aren't high resolution enough to be on par with human vision. Therefore to compensate, we get zooms. It's not cheating at all.

Concerning the bombing system, I know of 3 things that are not implemented properly: - CCIP-to-AUTO delivery: when the CCIP is not within the HUD FOV, a cross is still shown. Pressing pickle designates the target under the cross as an AUTO delivery target, giving steering cues and automatically releasing the bombs when the parameters are met. - ARBS moving targets: ARBS does not (at least did not, I don't know if this has changed but I believed not) follow moving target, but it should. RAZBAM didn't have the info before, so assumed it could not. Someone sent a manual describing that it could and RAZBAM has said they would implement it. - ARBS AA targets: a bit like the previous point, the ARBS should be able to follow AA targets and provide aiming cues. This is currently not implemented.

Nobody that worked on the Mig-21 works for Heatblur, apart from Cobra which, IIRC only worked on the art. HB isn't to blame for anything. My guess stands true for most 3rd party DCS dev teams: they've got shovels of artists, yet next to no programmers. Feels like M3 only has half of a programmer (probably working part time). Same thing applies for Razbam. They've got a ton of announced modules with artwork being done, but system programming goes at a slow pace. Anyway, there's way too many long standing issues with the -21. People praise them when they release their bi-annual patches because it fixes 2-3 problems just because we're not used to seeing any updates from their part.

MSAA is just absolutely bad for performance especially in DCS with deferred shading. You could probably get better results by dropping MSAA to 0 and adding a bit of PD, or using the tweak posted somewhere in the forums which applies MSAA only to a central circle (making it a lot less expensive).

Thanks for the update! The updated manual is lovely! Just a quick question: I see the image in the manual for the BK90 is the new implementation that was presented in a video some time ago. Any update on that front? :)

Indeed, these buttons should all be bound to a controller as those are part of the "HOTAS" controls. The AJS37 is exactly like any other high fidelity module to this regard. As for the unanimated bit, HB said there is new art coming for the Viggen, like a pilot body for example, so these things are surely going to get added. And just to get OP off his high horses, let’s see some of the things missing (or added well beyond 1 and a half year of early access) from other high fidelity module: - Huey EGT (added recently, but there are big issues with it currently) - Huey multicrew (still in the feature list when you buy it) - Mi-8 multicrew - M-2000C navigation and SA modes for the radar - M-2000C FM got changed pretty drastically since the 2 years it released - AV-8B took 8 months to get basic navigation features out - Ka-50 cockpit lightning is broken So OP, this isn’t the case only for the Viggen. Learn to enjoy it instead of getting stuck on small worthless details. The Viggen is a blast and definitely my favorite module.

Be advised, there's a bug currently that "limits" the range of the laser to approx. 8 nm. For example, the "end point" (ie the point the bomb/lmav goes after) is limited to around 8 nm, even if the actual target you're looking at is more than 8 nm away. This makes "long shots" or long range buddy lase impossible.