alip

I might add as feedback that the encoder gain seems high for various knobs, or at least with my virpil hotas, it is hard to set precise values.

Hello, I cant find the airspeed indicator bug keybinds, are they missing?

I would love for the CCIP Consent to Release bug to be addressed, the CR modes have been broken for many years now. 2 more weeks? @BIGNEWY As always we thank the developers for their great unending work.

I found ASW produced a blurry ghosty image in my attempts. How do I go about locking it to 30hz? I only see options for auto and forcing 45fps with ASW on or off in the tray tool. Would i want the goggles still running at 72hz with ASW at 30hz?

I got a Quest 3 a couple of days ago, and I am new to DCS VR. I am rather lost in with all these settings... I have a 3080 12gb, so far the best experience I've had is attempting to reach a constant 72 fps with ASW off and medium/low DCS settings with DCS pixel density set at around 1.4. This has given me a mostly smooth experience and acceptable image clarity in non demanding missions. Headset set at 72hz and render resolution 1.0 in oculus app. In the debug tool I have ASW disabled. I am using this link cable. I have the OpenXR toolkit installed but have not found any success fiddling with that. Using windows 11 and DCS MT version. So, am I completely off base with this strategy? Should I be using ASW and targeting a lower frame rate? I also have a strange issue of seemingly random severe stuttering and freezing up, especially in the DCS main menu with an hourglass visible, any ideas what might be causing that? My latest settings are attached.

Is compression an issue over the link cable as well? Why? Is that a software issue or just a limitation of using usb?

Am I right in that using the link cable is pretty much always preferrable to a wireless connection? I have a rtx 3080 12gb, is that beefy enough for this headset for relatively clear and crisp cockpits/displays or do you think for a proper experience you will need a 4090?

A question for you guys who have done your research, for those of us getting into DCS VR, is this headset a good buy? What are the primary downsides or benefits as compared to other options for DCS use? This looks relatively inexpensive, versatile and seems like somewhat good specs? I tried the previous quest 2 model in DCS and found it to be somewhat clunky in use and perhaps just below what i would find to be acceptable image quality (for DCS), but it was amazing in other applications. Figured this new version might just be the upgrade it needed for DCS...

I am still getting this bug as of todays version. Blade flies east in full burner high AOA. Edit: did the mission a second time. Did a quick startup and went straight to CAT 2 and waited there until Blade was just about to launch. Flew the mission normally after that, no problems.

Is dual engine flameout modeled? I've been studying F14 and if I understand correctly the electrical generators are backed up by a hydraulically powered electrical generator and the engine driven hydraulic pumps are backed up by an electric hydraulic pump. So, in the event of a dual engine flameout due to say damage or fuel starvation, it should result in losing both generators and hydraulic pumps, leading to total loss of control and complete electrical failure since the both primary and backup systems are inop? However in game you remain in control and under electric power, what am I getting wrong?

I have a similar issue. I like to map the encoder dials to HSI heading/course knobs but it is so slow it is almost unusable. Does anyone know of a good workaround?

Hello, I have a bug report. On the C-101CC HSI, the VERT and NAV flags have reversed behavior. The (left side) VERT flag disappears when the NAV reciever is in use and the (right side) NAV flag disappears when glideslope is in use. (it should be opposite). On the C-101EB the HSI is a different and the flags are on the opposite sides. (Nav left and VERT right). On this model the behavior is correct. I imagine this is the cause of the bug, both aircraft are programmed to behave as if the flags are on the same side.

Hello I've been getting into DCS warbirds. The instant action missions that have flak seem to be very hard to complete. (Even on easy setting). No matter how I fly the flak hits and kills me sooner or later, usually sooner. Even at treetop level, flying fast and erratically. Now I am no expert on WW2 AA/flak effectiveness, but is this realistic? Was it really this effective? Comments/tips appreciated.

I am still experiencing this issue.

Will you try to remember to reply to this when the fix goes live so we can redo the mission?

No, but I think others have. I would just edit the logbook and skip the mission until Baltic Dragon addresses the issue. I think the latest DCS update may have broken the mission.

Me too.

I keep getting shot down by SA-15 on Larak Island during the push. About at the time flight lead inquires into weapon status. It seems the SA-15 shot is scripted and not supposed to track. However, after three attempts to get past it I've given up and am skipping the mission. Tried various radar/jammer configurations. Running the latest open beta.

Yes its harder to reproduce. Seems random. I think I get it most often after doing lots of high bank/high pitch/inverted maneuvers in CCIP mode followed by a steep dive. I could reproduce it by doing that for 5 minutes or so, can't say what specifically caused it though: Edit: I think it might be more likely when diving from a high altitude. (Above 10.000 feet)

Might this be related: I am experiencing the same... Think the bug was introduced at the same time as the one I reported.

Hello It seems that when the HUD was updated some time ago it broke the CCIP CR modes - 3/9 and 5mil - rendering them more or less useless and CCIP bombing with high drag munitions difficult. When using these modes the designation pipper is cut in half by the bottom of the HUD. Furthermore once target is designated the reticle and pipper are also cut in half by the bottom of the HUD. This is not related to viewing angles or head position, the pippers are always stuck to the bottom of the hud and cut in half, see screenshots: Designation Pipper: Reticle: The issue is present with both versions of A10C and in all maps, single and multiplayer. Steps to reproduce: 1) Load A10C with high drag munitions in mission editor. (MK-82AIR og cluster munitions). Any map, fly mission. 2) After start use the IFFCC test menu to set HUD to 3/9 mode. 3) In flight at a couple thousand feet ALT select CCIP mode and start a slow shallow dive with high drag munitions selected. 4) Designation pipper should be cut in half. 5) Once target is designated, reticle should be cut in half. 6) ??? 7) Profit. Ensure you are in 3/9 mode or 5mil mode, bug is not present in manual release mode. Ensure you are not using low drag munitions, at high speed or in a steep dive (then the designator will not appear since bombing solution will be within the HUD).