Raven (Elysian Angel)

The Rhino software is brilliant and am still discovering new things that improve quality of life I have no idea how the FFBeast software works, but it should only be allowed to overwrite effects for modules that don't support FFB natively (the Hornet for example: I find the default stick forces far too stiff for comfort so I set the Rhino software to reduce the spring forces by 50%). Like MAXsenna said you need the telemetry from DCS so the FFB software knows what to do with it. Something to remember is that DCS generally has an issue with axis inversion. People who have been around for a while know that lots of us need to invert throttles and toe brakes especially or they won't work as you'd expect. Sometimes pitch/roll needs to be inverted as well (VPForce already knows that so does it for you).

Victory said the F-4E both IRL and in DCS is a fingertip aircraft.

It is a great module as-is, and I personally wouldn't mind if the current WIP-items were removed if the situation doesn't get resolved: I don't need JDAMs for example so am completely fine with "just" dumb bombs and LGBs: then we can have a complete '90s version of the aircraft.

A real-life pilot has a much better grasp on what the aircraft is doing (and often about to do), because they can 'feel' the aircraft and thus react (proactively) a lot quicker than us armchair pilots - since we have to wait until we 'see' the effect. But even we can learn to anticipate certain behaviours given enough virtual flight hours and muscle memory

INS drift? Isn't there an options somewhere that lets you simulate how long you've been in the air already when you spawn in, and thus the accumulated INS drift up until that point? I don't usually air spawn so I don't know for sure

What are you using? The Mirage works just fine with my Rhino: in fact I lowered the minimum forces again in the special options after the update. It is sensitive yes but perfectly flyable with precision

That’s pretty much what it is called in the Group Policies editor as well. I don’t see why this registry edit wouldn’t work

No. What I am saying is that you should test if your trim works properly (trimming up actually trims up, trimming down actually trims down). In the Rhino software, pitch is inverted by default so I don't need to touch anything. It just works. Not necessarily. There has been someone else who commented on this very thing months ago already in another thread. I can't remember on the top of my head what HB's reply was, but I'm sure you'll find it if you read the other FFB threads on this F-4 subforum. Issues can arise if you have both a FFB stick and a non-FFB stick connected and use both for DCS, but for different aircraft. I don't have any problems myself: I use the RealSimulator R3L for the F-16, and the Rhino for everything else and it works just fine...

Go to your F-4 controls, select "assign axis", select either pitch or roll and then click "FF tune". Personally I don't need to bother with that, but I use a Rhino, so the FFBeast might be different. You might need to invert your pitch axis in the FF settings too (if trimming works properly for you, you don't need to invert axis).

You can lock a specific feature update too, using Group Policies (it requires Windows Pro or Enterprise however). That way you can still get security updates.

See this is why I wonder why people keep suggesting to install that, when mbuccia himself recommends not using it if you have Varjo Base 4.3+: https://github.com/mbucchia/Varjo-Foveated/releases [quote]UPDATE JULY 2024: AS OF VARJO BASE 4.3, THERE ARE NOW SETTINGS DIRECTLY IN VARJO BASE THAT ALLOW YOU TO ACHIEVE THE SAME EFFECT AS THIS SOFTWARE PREVIOUSLY DID. IT IS RECOMMENDED THAT YOU USE THESE NEW SETTINGS INSTEAD OF USING VARJO-FOVEATED. PLEASE SEE THE BLOG POST FROM VARJO. LOOK FOR THE ForceFoveatedRendering KEYWORD SPECIFICALLY.[/quote]

So basically you're asking me to revert to an older version of the software to undo the performance hit from enabling options I don't need to enable? If I simply ignore those 2 new options, the sim runs just fine and performance is the best it has ever been...

Thing is, I don't have the mbucchia script installed atm, and I have disabled OpenXR Toolkit (it is still installed, but disabled in settings). When I tick the "quad view" and "use eye tracking" options in DCS, my framerate drops by around 40%. That tells me there's something weird going on, and perhaps QV was active but is disabled when ticking these boxes because of a conflict with the Varjo API layer? *edit* I am using the latest Varjo software: v4.4.010

That doesn't make any sense. Why am I not seeing a massive performance degradation in DCS then? The only way that could happen, is if quad view never worked in the first place, but if that is the case then why did so many people in other threads say the github script for quadview is not needed since the Varjo software has it built-in? I was using the github script on my Reverb G2 (before it died), and I noticed a substantial performance increase after switching to Varjo (granted, I also changed gfx card from 6900XT to 4080S, but that doesn't explain the higher framerates if quadview hasn't been working since: the new card is not THAT much faster). None of it makes any sense... We'd need someone at ED to clarify what those new options actually do, and when (not) to use them

Does this happen with other aircraft too, or just the F-4? Perhaps it’s hardware-related, such as a USB cable that’s not seated properly? I take it you double-checked your bindings?

You mean the new tickboxes in the DCS VR menu? I recommend leaving them off: we Varjo users don't need them as both are already included in the Varjo software. I think this is meant as a replacement for user-created solutions so people are no longer reliant on other software from github. not just trees: mountains too for example.

ED doesn’t do that: they only release hotfixes for game breaking bugs - aka stuff that can actually crash the game or make it impossibly to fly a certain module. Sadly we’ll have to wait 6 weeks or so for the next major patch

It’s still the same as it’s been for the last 18 months or so: - If you fly something else first then switch to the F-14, the TCS display works correctly; - If you fly the F-14 as the first aircraft in your current DCS session, the TCS display is black until you restart/reload the mission.

Do you consider Western Europe to be “east”, then?

I'd suggest reading the in-game tooltips that are displayed when you hover over those options. They explain it very well

Support for FFB pedals needs to be implemented on a DCS-level by ED first, I'd think

Same here: I tried the NTTR runway start IA mission yesterday (mainly to adjust head position now that we have pilot models), and I noticed I was just 500MB under my VRAM cap. And that’s just in NTTR with nothing else in view. On a recent map such as Afghanistan I’d be multiple GB over the 16GB limit of my graphics card Funny that Orbx developers mentioned earlier that ED enforces strict VRAM limits and that’s why the Kola map looks so much worse than people expected, and yet don’t abide by their own rules for the CH-47…

Yes that annoyed me too: now there's a (relatively) huge black square in the sky whereas normally there would be a faint actual aircraft visible...

null