toilet2000

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.

Bump again, this is an important issue, still not acknowledged by anyone from Razbam.

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.

According to the pocket guide : While it was like this before, now the EHSD appears on the right MPCD. It's not a big issue but it does make it a bit more complicated to fiddle with MPCDs without taking your hands off the HOTAS.

TDC designator moves too fast/jumps on HUD This bug is described in this thread: https://forums.eagle.ru/showthread.php?t=212633 Basically, the TDC when assigned to the HUD jumps around instead of moving slowly. That, and it moves way faster than when the TDC is assigned to the radar. This happens with the TDC bound to an axis. I don't know if it happens when bound to keys.

Unfortunately this thread got moved into the controller section. As far as I know they're not doing any bug tracking here... I'll make another more general one in the Bugs section.

I've set a curve to make it possible to use the axis TDC for the AA radar. The TDC movement speed on the radar display is fine (not too fast) using this curve. But if I try to designate using the HUD (TDC on HUD when in AUTO A/G release mode), the TDC moves wayyyyy too fast and in a stuttering way. It makes target designation using TDC on HUD almost impossible using an axis. Steps to reproduce: 1. Assign axis to TDC (not mouse axis) 2. Set curve that works well for radar designation (on the ATTACK RADAR page of the DDIs) 3. Now use said curve but with AUTO HUD designation, i.e. designate approximate position using the velocity vector (and pressing TDC Depress) and try to move the TDC to a more precise position. The TDC will just start flying off way too fast in the direction of the axis.

I've got the same behaviour and it's surely a bug. It's just the waypoint number shown that doesn't change, the data does. If you open the HSI on one of the DDIs, you'll see the real waypoint number and it changes accordingly.

It’ll be way better than the Harrier/A-10C. Terrain avoidance radar, TFR, ATFLIR (which includes both the targeting pod AND a navflir on the mount, projectable on the HUD like the Harrier), ground moving target track radar, ground mapping and synthetic aperture radar... The capabilities of the Hornet at night will be far better than what we have known before in DCS.

That's expected behavior in MP. Because of engine limitation, the BK90 acts like a bomb in MP. The new implementation they have been working with ED on should "fix" this and make MP and SP consistent.

There's already a Bas90 like system in DCS. You can create a roadbase that you can ask to relocate. You can rearm and refuel at those bases.

I've got the exact same issue that I reported in another thread, but got no answer. Your video demonstrates it perfectly. Even when the sight isn't jumping around or disappearing, it's simply not working (fixed at a certain angle and not moving as it should).

I have the same question!

Just some stuff I've discovered: For some reason, none of the bombing modes of the Viggen work, but this happens only when playing TTI (on PG). Any other mission on PG is fine. When spawning on the Stennis with an F-18, the F10 map does not show anything (super zoomed in on a part of the ocean, without the ability to zoom out). This happens to both me and a friend playing in COOP.