Eldur

I've seen people overclock that thing in excess of 4GHz, but that needs a decent cooler and you shouldn't volt it past 1.45 if you'd considering OCing yours.

This must be the reason my performance in the CV1 at 1.5 (in DCS) improved vastly a while ago. Now I know why, even though I was under the impression the quality still differs. Having massive performance diffs in the Quest though.

What's your system specs? I've been flying DCS in VR with a Rift CV1, PD 1.5 on a 3570k and a 1080 non-ti with med-high settings just fine, at least offline. MP was a different ballpark due to most servers running lots of great scripts that eat the few CPU cycles that old thing had, making the fps drop hard. Should even be doable with a 1060 / 1660 6G. If you've got something like that or better, you could try getting a used Rift CV1 or OG VIVE, should be fine. Rift S might also work. Agreed. VR makes you be there and especially in simming, it's having a good user base already. 1/3 is quite a lot actually. And never forget: If it runs well enough in VR, you don't even have to spend a second thinking whether it would run on Pancake. It simply does, and it does it very well since many optimizations will impact Pancake as well, except for things like Single Pass Stereo that are specific to VR. Edit: And I've seen quite some improvements on my end during the last 2 years, even though it all went through ups and downs. As for the new map - it is new. And even when having moved over to Stable already, it's still new and uses the most recent technology for terrains that ED has up their sleeves. There's lots of room for improvements though optimizations still, it just takes time. I wouldn't judge anything here yet. If I'll experience noticably lower performance compared to other maps, I'll just stick to the others and have a glance at the new one every now and then until I can run it decently, just like I did with Normandy and Syria. We'll be getting there and our feedback helps ED and their 3rd parties to improve things.

I'd love to see them removable as well, and that's a general wish for obstructive things. As an unrelated side note, but presenting a similar issue, I've flown the MiG-15 through some Lebanese valleys a few weeks ago and couldn't see ship due to the lighting conditions already, but I wished I was at least able to see out of the cockpit just in front of me, without having that massive gunsight right there. Some planes like the L-39 allow for removing the sight, some allow for removing the guncam thing. These things should be generalized if it makes a massive difference. As for the Mi-24 mirrors specifically, the minimalist thing to do would be having the mirrors tilted so they'd obstruct the view the least as seen from the default viewport when they're switched off. Some mirrors in other planes are tilted away already in DCS, so this should be the easiest way to make people happy here.

Man, that sucks. Been there (for over a decade due to various health things), so I can perfectly understand... don't let things take you down. DCS and your roadmap are one thing that will keep your chin up, keep that resource.

Thanks, I'll retry it anyway on my new rig. The old one was updated from Win 7 and it was impossible to install foreign Languages back then, but I only retried with 10 a few times since I didn't have lots of time to delve deeper into everything. If I need help, I'll get back to that forum section. Just as a side note, it might not like having cockpit noise coming from the speakers while I speak into the CV1 mic for some reason. At least that was my first thought - but it didn't work with muted speakers either.

Never worked for me in the first place. Completely unable to pick up what I say. Win 10 voice recognition does work however. It's a bit sad to have paid up for something that is useless...

I'm still on the CV1 and there isn't even remotely any possibility to tune the display settings there. I'm having that issue with all the collimated sights and HUDs though. But at least they are visible. In that other sim they're completely gone unless I sit directly at the sweet spot with µm precision which is why I hardly ever fly that one since I moved to VR. Could be related to the res as I think it's a tad better with the Quest. Can't speak for any LCD or generally more recent high res HMD.

The original one is already almost invisible in VR, I guess this mod will remove it completely then...

I'd be happy to be able to do that as well by getting a Mi-24 upgrade pack that brings the V and maybe also the VP that has a GSh-23-2 turret. After shooting the 2A42 in VR I can only imagine this being a total blast. At least I will be able to do that in the Apache once it's there, but I'd love to have that feature in the Mi-24 as well. And TBH there's enough "soft" targets that we could engage well enough even with the YakB.

I just had 2 sessions testing the rockets so far, both with the UB-32 pods. Also noticed different length of bursts, regardless if I just tap the thing or hold it down for up to 5s+. Never had exact amounts of rockets, but the burst length selector did have an impact. Often, they wouldn't shoot at all BTW and I was wondering if I did something wrong, only to see it just working the next approach, but even with the burst length setting untouched, the burst length always would vary a little. Since the rockets aren't being rendered in the pods as per known issues, I never have been able to validate the remaining amount. Certainly there's something still "WIP".

I've been proposing a new thread for the 2.7 updates when 2.7 dropped that the notes went into the 2.5 thread... Updating my bare naked DCS right now / getting the new map on my new rig while not being at home which is why it still lacks a decent GPU. 5800x, 64GB of 3600, ASUS B550-A board, 1TB 980 Pro for Win, DCS and MSFS, another 2TB 980 Pro (was the same price as the 970 Evo+because there was rebate on it and it was available, second slot isn't PCIe 4.0 though, so it's still slower), SBX AE-5 Plus and currently an old 660 2G with broken fans (= passively cooled only, hitting 100°C under load, somewhere around 40°C on idle) that will be replaced by my 1080 8G when I get back home. Can't wait to try DCS in VR on that beast. I'll probably be able to use my Quest then instead of having to run the CV1... and I'll try out the new map, of course, even though I haven't been to Cyprus yet as I wanted to do some pew pew pew with the Hind which I did in my Caucasus miz

There's probably a safety margin as well. I guess the rotor won't directly strike the tail boom as soon as you pull back a little with low collective. But having the actual possibility in DCS would just be realistic, maybe consider adding it as a special option.

I have had his channel subbed and belled, but as always, never got any notifications due to their rotten algorithms (thx Google). Thanks for fixing that for me at least on this particular occasion, will watch later

My idea would be to get rid of the double tap thing (but keep as an option for those who like it, but I've had accidentally reset my trim severa times when trying to trim with short button presses in quick succession) and make the rudder untrim (recenter pedals with yaw AP channel off or retrim so the H channel needle is centered with it on so it gets the same amount of authority in both directions) slowly (so it won't kick you around instantly) when using the trimmer button (start untrimming on down, stop doing that on up) if rudder trimming is disabled in the options. That way we could gradually get that trim offset from the yaw AP channel out with the trimmer button (nothing wrong pressing it for a second or two) which is anyway a good idea to do after a turn.

ED should give him actual HOTAS controls, he literally is flying the thing with keyboard only

For flying fun, I'd recommend the Huey. For having a great thing I'd go for the Hind. For ease of use (flying included) und combat efficiency I'd go for the Shark. Also, do watch those vsTerminus tutorials, they're pure gold. And I can't emphasize it enough: If you can, get yourself into VR. I've been flying DCS in VR on an old 3570k (OC @ 4.4) with a 1080 non-ti through a CV1. Anything like a 1060 or 1660 6G, 1070, 2060 or 5700 should do similarly well. Either get a relatively cheap Quest 2 or try grabbing a used Rift CV1 / S or VIVE (Pro) or Samsung Oddyssey+ for the entry if you're on a budget. It's worth it absolutely, especially when flying helos. Also keep in mind that the Ka-50 is still the old price. Later this summer the Upgrade BS3 will come and ED will handle it similarly to the A-10C. You'll be able to get the upgrade for 10 bucks probably within the first month, later on you'll only have the full package for 80 then. So get the Shark now ideally so you can still save on the old price tag with the sale rebate and get the upgrade for not too much once it drops.

They'Re basically un-aimable since they even shoot upwards (I actualyl wonder how so). Can't even use the manual range thing since it just doesn't work once those things are selected...

Ball flying in DCS helos has always been off. When you step on the ball you might imagine flying coordinated, which is the thing goes where it points at, but that's definately not the case and never has been in any helo in DCS, back to the Ka-50. Uncorrected translating tendency should be indicated by the slip indicator as it basically is sideslip.

Had it happen yesterday out of a staight and level flight at just around 250kph and it felt absolutely weird from that on. It did roll to the right and push the nose down hard, not reacting to any controls except for collective which (lowered completely) didn't change anything in flight behaviour. But on that same flight I had myself stuck in a RH pirouette turn right on the groung with my pedals hardlocked to full right and it took like a minute or so until it began reacting on my rudder inputs. Guess the same happened with the cyclic and something weird (I'm namecalling you, Satya Nadella!) probably just locked the stick in the forward right corner, I just never looked down at it since I wanted to see if any of my inputs had an actual effect on the thing. It just was one weird sortie...

Just on a totally unrelated sidenote: I've tried the 466.77 DCH drivers and literally everything kept crashing right under DCS's plot (with it crashing as well, especially when Oculus dies). UJR, Thrustmaster TARGET, Oculusware, OBS and even my friggen Notepad++ went south. I even had my stick and/or rudders stop reacting at all for a while several times before that happene. Not gonna lie, I was never happier to roll back to an older driver, just to have my stance proven hard. Back on 465.89. The new one just does one thing well enough, and I'm not gonna tell because of "language"

Not a fan of the double tap thing. Hit it accidently several times (like when "that wasn't enough, just another notch", yeah I can use the hat now as well here)and it wasn't exactly a great experience. My suggestion if it's not realistic (which I think): Make it an option for those who like it. I mean, it saves them a button.

Just noticed that this also fixes the doppler gauge being aligned to north instead of the airframe.

Just chiming back in. FPS are up and running again and I can even switch the mirrors on after leaving the Senaki area (which in general is tough on fps) without dropping below 45 in the Rift. I didn't just readjust the sensors, but went through the whole setup procedure of that thing. Luckily it succeeded at tracking on the first try, as I still don't know the criteria for that. So it "just" was the Riftware again, hogging up exactly that one single CPU core completely that DCS is running on. Weird thing is, that it actually had effect on pancake fps as well, they're back to almost 200 in the menu. Weird stuff being weird... next time I see any performance issues, I shall do that first and foremost, period.

Because experience taught me a lot especially with DCS it not being a good idea mostly. But I'll try the most recent one (that gets outdated probably within a few days), not expecting any differences though TBH. On a side note, I had ATis for a long time when they actually had a monthly driver and not just like twice a year like it's now. Before that I ran my GF3Ti200 on 23.11 for ages simply because every single driver after that sucked balls unless you ran into a shiny new game that just wouldn't run on 23.11s... Oh BTW, totall forgot to mention: I ran the previous versions (basically all 2.7.0 and 2.7.1) on the same driver, and they ran just brilliant (not sponsored). Now the 2.7.2 even tanks the fps within the menu. Mostly around 70-80 there whereas it always had been topped out at 90 (CV1) before and being in the 180-200 region in 1200p(ancake). But well, let's go down that Windows 10 rabbit hole again and try every possible configuration with HAGS, Game Mode, XBox mode and what not. I hate that eternal pre-alpha "OS" for a reason... in the end, just another patch on DCS will fix it and I'll again have wasted hundreds of hours troubleshooting for nothing, as always; BTDT (can't blame ED for the complexity of their great product though, I see that on others as well)