FoxTwo

I just tried taking off in mission 9 of raven one without issue. What mission specifically are you noticing the issue with?

Are you resetting the FCS and take-off trim? Are you set to +15-17 trim for carrier takeoff by weight?

I think the problem that most of us are having is that on cold start jester sets the ECM to standby, which is incredibly dim, so while people were saying it was incredibly hard to see in the daylight, that's because it was, based on the position of the DECM switch. The current brightness may in fact actually be FINE and would explain the inconsistency in the reports you're seeing. At the very least, I know mine was. With the switch in the ON (highest brightness position) it looks fine to me on the latest open beta version (as of today). You probably want to reevaluate whether or not, post DECM switch fix, it needs to be brighter in the first place. I'm not sure it does.

You can get rid of your curves with an extension, particularly of that length.

Make sure you have Advanced Super Sample filtering disabled in SteamVR if you have MSAA enabled in DCS. They are not compatible.

Eureka. Can we get a fix asap? This explains everything.

Holy. $*&%. Welp. Guess we found out why sometimes I can see the indexer and sometimes I can't. Holy crap, good find. Can we get a hotfix boys?

Windows 7 send telemetry data to microsoft as well. For years now. Live with it.

Stop using an out of date END OF SUPPORT operating system that's no longer receiving security updates when you can STILL upgrade to Windows 10 for free. Problem solved.

https://www.nvidia.com/en-us/geforce/forums/game-ready-drivers/13/425911/geforce-46109-game-ready-driver-feedback-thread-re/2967675/

Yup. Just happened to me. Climbed up to around 40,000ft in full AB, just above mach 1.0, leveled off, engines caught fire. Engine temps weren't excessive.

I think it's just very hit or miss. I ordered and received a CM2 base and 200mm extension in less than two weeks.

You can use afterburner with the gpu.dll plugin to see how much it's ACTUALLY using. Top tip, it's not 17GB. In multiplayer I rarely see more than 7.5GB used, although the full 10GB is allocated.

It's in the driver version right there. You're runing 432.00 (26.21.14.3200), which is way before 481.48.

I'm not sure if this is a DCS bug, steam VR bug, or Windows Mixed Reality bug, but the only fix is to exit DCS, CLOSE steamvr and windows mixed reality, and then restart it and start DCS back up. It's something to do with the mouse cursor in DCS losing track of focus. At any rate, as I said there's a workaround which is close out windows mixed reality and restart it.

The Reverb G2 fixed a lot of the color accuracy and lack of contrast issues I was having with the G1. I'm not recommending you buy one I'm just saying I was going through the same problem in VR and it was basically all down to the Reverb G1s poor contrast and color accuracy.

Never had a problem flashing over a powered USB hub, I do it every update. That said the software SPECIFICALLY says to NOT do that so I don't know why you're trying to force the issue.

you shouldn't have oculus software running, do you mean windows MR? Otherwise, uninstall that software it's not necessary with the reverb. Check your steam VR scaling, 100% is double what it should be with the reverb g2, so you'll want to set it at around 50%.

Not sure if something changed recently, I haven't been in the F-14 for a while and hopped back into the A model and it feels like the default head position is way too far forward. I mean I know how to move it back some and save it but I'm trying to figure out how high/far forward my eyes should actually be and currently the starting position doesn't feel right.

And here I am trimmed out and on speed, which you can barely tell. It's TOO dim during the daylight. So are the instrument backlights but whatever, those are significantly less important. I get it "realistic" lighting has been a challenge since 2.5.6 mucked everything up but this seems like one of the things that really, really needs to be fixed. They fixed all the other lights, why hold back on this one?

Confirmed, super dim. Unrealistically so. I'm at 2.2 gamma you can barely see the damn thing. It would have been a hazard and unqualified for flight if the real one was this bad.

Then, quite frankly, you're doing something wrong. Loading into the spitfire channel cold start in VR spikes to 7.5GB and then settles around 6.8GB of VRAM.

Load up afterburner, look at committed versus in use. I'm using 6-8GB in multiplayer on the hoggit servers, no stuttering.

This is not the case, the 3080 is fine. I have one. This whole VRAM thing is like a meme at this point.

The A is a new model, f4l0 will have to add it and update the beta. Patience.