Raven (Elysian Angel)

I use a trackball with a scroll ring: it works well for me and is immersive: turning the scroll ring is similar enough to turning a dial in the cockpit

We already have a remastered Caucasus map, so your proposal would make it Caucasus 3.0, not 2.0 . Other than that, you should use the forum's search function and read the existing threads about this exact same topic. Feel free to reply there to give it more traction so it stands out more to ED.

Yes that’s what I think as well. There’s a ridiculous amount of AI “content” on YouTube and social media these days. It's up to us to be discerning…

Yes, or simply selectable sea state 1-9 (as in those pictures above) as that seems to be officially recognised and thus more likely to be approved by ED I’d think…

I haven’t used my ForceFeel in a few years: two of the motors stopped working, and sitting on that pad for prolonged periods of time was starting to become too painful for my scrawny behind

In 2D, easily. In VR, I doubt it: even my 9800X3D is 100% “CPU bound: rendering thread”. Most likely there’s nothing we can do about that until we get Vulkan - and a decently advanced implementation at that.

F I N A L L Y ! Everyone with less than 24GB VRAM rejoice!

Nope.

Thanks, YoYo. I’ll download and try it as soon as the temperatures where I live drop below boiling and it’s safe to turn on my PC again

It’s a proper use for keyboard macro buttons. I’m sure “When we have news to share we will” is also there somewhere

Fair enough. It’s not a huge dealbreaker since restarting DCS fixes it, but this and the black TCS are IMO the 2 major annoyances with the F-14 atm. We all hope it does get fixed, obviously Oh perhaps that’s the reason Hearblur never picked up on that bug before release, since IIRC the MS stick you have was used to code the FFB for the F-14

Sorry if it wasn’t clear: this is about the F-14 FFB that stops working if you fly anything else before it in your current DCS session. So if you start DCS and load any Tomcat mission, FFB works properly. If you fly any other aircraft first, exit that mission and then start any F-14 mission, the FFB stick goes limp and FFB doesn’t do anything until you restart DCS. This has been reported a few times already, and has been a problem for years now. —->

Yes indeed! In fact I use the same hat for George/Petrovich/Polychop AI/communication menu and it works very well AND is easy to remember that way

That’s a bit harsh I think, but in the end what matters for FFB is the software, and the Rhino software is brilliant. My Rhino is on the floor between my legs so I don’t see it anyway.

They already said they are not going to do that: it’s the main reason why we won’t get a full-fidelity SH-3.

Not that I ever heard about. R-77s were carried by Su-35s in Syria but as far as I know never actually fired.

There’s also the small but not insignificant issue of the version that we have in DCS never actually being used by the Russians. Did *anyone* actually ever use them? Ukraine perhaps, as they were produced there?

Why would you create 3 threads on the exact same topic? You’re aware that you can just reply to an existing thread, right? Less bloat that way, and easier to find relevant information. Simply reply to the existing thread here: @NineLine Perhaps these threads can all be merged? Thanks!

Yes, *THAT* competition: I was trying to choose my words carefully to avoid naughty points

The new trailer for the competition showed sea states that look better than the ones we have in DCS, and you likely won’t need to set 50-60 knot winds at 500m for those to happen…

Terrain streaming and memory management are most likely governed by the terrain engine ED uses, and it seems for ED maps at least this is the way forward. I personally use the F10 map as little as possible for this exact reason. And yes that’s annoying when you want to quickly check tower frequencies and TACAN for nearby airfields for example.

Yes, in VR I am CPU bound as well (even though my CPU is quite a bit more capable), and in 2D I am GPU bound. DX11 is horribly inefficient in VR and we all hope Vulkan will change that sooner rather than later.