Mezsh

I have exactly the same issue. For the last 2 years, I have used my hand controller to reset my cockpit view. Yes, yes, yes, I know you can do the same thing by pressing "5" on the Numpad, but then you have to lift up your visor to see the keyboard, whereas previously I could just reach for my controller to reset my view WITHOUT having to lift my headset up. PLEASE can we get this resolved, and the original functionality restored WITHOUT having to enable hand controllers in VR.

Still broken...

I can't even do a VT now with 19,000lbs, water on, at sea level, and ambient temp of 25C. The engine should produce 23,8000lbs, so the fact that it can't get more than a few inches above the ground with nearly 5,000lbs in the bag is a joke. This module is nowhere near as much fun to fly anymore. I don't think I'll ever buy a Razbam module again, except maybe for the Falklands map.

I know there's been a lot of controversy over the nerfing of the AV-8Bs engine power recently, but can someone explain to me why I can't take off vertically with an aircraft that's loaded to 19,000lbs and has an engine with 23,800lbs, with water on, just above sea level (70ft.). ambient temp of 25C and I can only get a few inches above the deck. Where's the ground effect?! Also, I've read many, many, many books on the various Harrier types, and every single pilot says that the Harrier has ridiculously fast acceleration at low level, but the Razbam Harrier is so sluggish, it's really spoilt my love for this jet, so I barely fly it any more (I used to fly it all the time). All the missions that I've made with Harriers taking off from Oil rigs are redundant now, because it just doesn't have the power, despite nearly having 5,000 in the bag. I have to take off with less than 2,000lbs of fuel, which just castrates the Harrier completely.

Carrier comms with the Tarawa are broken again. Ship responds to initial call, but then gives a "runway heading", and when you approach ship, radio goes dead. No carrier comms, just eerie silence.

New bug or am I missing something? When you try and turn off the map on the EHSD (for low-light conditions) the "Map" button acts as a momentary switch, i.e. it momentarily turns it off, but when you take your finger off the mouse button, it comes back on again. Trying to fly a dusk mission and it just won't turn off. Any ideas?

We need it as a toggle switch in F10 also, nothing complicated, just a single button.

Please, please, please can we have a toggle switch in the F10/Mission editor toolbar so we can instantly switch betwen using Nautical miles and Kilometres, AND another button to instantly switch between Magnetic and True headings, please?! both of these would be insanely useful, especially when using the ruler for distances and bearing! 2 extra buttons on the top toolbar would be all it would take!

same issue

The cockpit panel and instrument lighting knobs don't do anything until the dial is at one o clock, and then they come on instantly, super bright, washing out NVGs and generally blinding you at night, there's no way to dim them. Please look into this.

Exactly. It's the exact same issue that I am experiencing.

The Fuel probe toggle switch is the only key binding I have encountered that is causing issues so far, but I've not been flying much in the last week or so due to being too busy, But I read that the pinkie lever on the stick also no longer works (same issue as the fuel probe toggle)

Whilst trying to refuel the other day, I noticed that since last week's OB patch, the key binding for my fuel probe toggle no longer works. Going into the controls settings menu, there are various probe key bindings available, all of which can be changed with the exception of the "fuel probe toggle" binding. It can be highlighted, but it won't allow me to bind it to any of the switches on my Warthog HOTAS, it worked fine until last week's update. Anyone else having this problem?

I'm pretty new to the Mig-21, I've had no problems doing the startup over the last few days. Today I was on the Cold War server and when I was starting up I kept getting compressor stalls. It happens either during, or just after the engine is spooled up, it must have done it 7 or 8 times to me today, but has never happened on the ground before, and as far as I know, I'm doing the same startup routine that I always do (Chuck's guide). Any ideas what's causing it? and why it started happening just today?

I'm running the latest Open Beta. Since the latest patch, when I click on the "Multiplayer menu" it takes 3-5 minutes for the server list to load. It used to take 3 or 4 seconds until the latest patch. I actually had time to go outside, have a cigarette, come back in and it was still searching... anyone else experiencing this?

I'm using VR (Rift-S) and I concur that the HUD is a bit blurry, especially the lower half, it makes it really hard to pick out targets. Also, the HMD is also out of focus (yes, I adjusted the reticle settings), but it still seems far too close to my eye making it fuzzy and out of focus. This is made even worse by the HUD glass being a bit blurry, and just compounds the problem. The view either side of the HUD, and the rest of the cockpit glass, the view seems fine and in focus.

Cheers, that seems to work! It's not perfect, but it's better than it was. j0nx, yes, I have the exact same problem with the A-10 since the new update. Somebody mentioned changing something in the settings for the A-10, but I've not tried it yet. I practically had to have my chin on my desk, and then look up to see the gunsight reticle in the HUD. I'll play with that tonight and get back to you if I find the solution to it.

First of all, the new cockpit looks great! The only issue I'm having is with the HMS. In a nutshell, it's not in line with my eye. I'm flying in VR (Rift-S) and because of where it's placed in my vision, I have to tilt my head down, and then look up with my eyes to see the target, this means that because I'm looking near the edge of the lens on my headset, the image is slightly blurry, making it hard to see the target I want to designate. moving the seat up or down is not a realistic option, becuase that would change my perspective relative to the HUD and the rest of the cockpit and the outside world. Neither is messing with settings in my headset, I have no issues with head position in any other of the 25-30 modules I have. AFAIK, in real life, the target reticle would be over the centre of the eye. Is there a way to move the reticle? if not, it would be helpful to be able to move and re-focus the HMS reticle to where it it works best for the operator.

*i9-9900k

In the new DCS manual, I was reading up on graphics settings, and trying to understand them better, because even with an i9990K and 32GB Ram and a 2080RTX card, I'm lucky to get 30fps in VR (Rift-S) Anyway... Page 24, under "SSA" it says: "...The heaviest, but also the most qualititive and eerily loading a video card..." Can somebody make any sense of that and what it's supposed to mean? cheers in advance.

Mine looks fine in VR (Rift-S)

Just a quick question: should both the collective and the throttle be mapped to the HOTAS Warthog throttle? for some reason both are mapped to my throttle. Is this correct, or should it just be the collective, and then throttle is automatic and not needed to be bound to the warthog throttle? cheers in advance.

That's what I thought. Just to double check, it's doing it in my VR headset (Rift-S) and on my monitor. So it's definitely a bug.

In every video I've seen on this subject, i.e. setting up the ripple and spacing selections on the bomb page, the numbers appear in the middle of the screen as they're actually being punched in on the LSKs, but when I tried tonight, they remain blank until I actually hit the "Enter" key. I've not seen this before, even in Matt Wagner's videos on the subject, so I assume it's an issue somewhere (2.5.5.6 Open Beta) I made a quick 30sec video to show what I'm trying to explain:

Is there a way to turn down the brightness of the gear indictor lights? they're dazzlingly bright when flying at night time, even without NVGs, or have I missed something?