Raven (Elysian Angel)

See that’s where odd things can happen, since on my system the in-game frame counter claims I’m CPU-bound, while I doubt that it is. When my Reverb G2 died and I replaced it by a Varjo Aero, I was forced to also buy a new GFX card since the Aero doesn’t work on AMD (I had a perfectly fine 6900XT). On AMD the frame-counter said I am indeed GPU-bound, but after switching to a 4080 Super it says “CPU bound” no matter which settings I change - even increasing my headset’s PPD setting from 35 to 39 - which doesn’t make any sense. The only thing I can come up with is that that “CPU-bound” message is purely because of the overhead of nVidia’s software DirectX scheduler (AMD uses a hardware scheduler).

I have done that, actually. I don’t remember if I have the service enabled or disabled at the moment (I know for a fact that for a while I have, though). I’ll check and disable if needed - thanks for the reminder anyway

I am running the Ultimate Performance power plan in Windows 11 (which is not available by default), but even then I have noticed windows updates messing with power settings without my consent (turning usb selective suspend back on for example). Microsoft does some shady backdoor stuff with their updates. Ideally I would configure Windows just the way I want it directly after installation and just leave it there, but it seems M$ wants to interfere with that - and tbh I no longer have the patience for hours of tinkering on a regular basis…

That’s the problem with the extremely simplified AI that we have: in our own modules we have realistic detection ranges and realistic limits on target acquisition, but the AI don’t care and lock you up instantly without any of the limitations we have to deal with…

This looks like something that needs to be addressed no later than the launch day of the official HB campaign

Depends on which one you mean: module-specific Special Option: yes. ED’s Axis Control settings: no.

I was under the impression the default one is more 'game-y', while the alternative Special Option is more realistic. I think that's how it was implemented, and I haven't seen anything that would indicate otherwise

https://forum.dcs.world/topic/354649-phantom-fps-performance/

There is a thread about Jester feedback/venting already:

He's right though, and it's what I have been doing since the Phantom released: use trim to get as close as possible to hands-off level flight as you can, then make the final adjustments with throttle. That will indeed change your speed but for low-effort formation flying it works very well. And I don't have issues with IFR.

I found that out the hard way as well. If I only fly the F-14 within the same DCS session, I have no problems and the autopilot works just fine.

Yes it's purely visual. In the F-14A moving my throttle all the way up parks both engines in zone 5 (you can check in-cockpit), but the reheat visual effect in external view (not just in F2) turns on and off on the right engine.

If we’re going that road, I’d say I’d have preferred an AIM-9D and/or AIM-9G, since both are relevant for the conflict the upcoming Heatblur campaign will be based on

I agree 100%. I even made a comment to that effect on ED’s FB page when the module was first announced (without reply). Bit it’s likely too late already, since ED probably filed all the paperwork to reserve/patent the name “DCS: MiG-29A” before they let us know of their plans to create this module. It’s basically the same as when ED announced their “DCS: F-16C Viper”. A lot of people objected to the use of “Viper” and asked for the module to use the proper “Fighting Falcon” name instead. But ED replied with what comes down to “we can’t because we already filed the paperwork”.

Oh absolutely: since we got the MT client, VRAM demands have gone through the roof. It’s not just the texture size of some modules: while that’s clearly part of it, DCS handles textures differently these days. Hopefully Vulkan will offer improvements in that regard…

Probably not, but during online play a lot depends on the quality of DCS’s network code, the ping to the server from your end, ping to the server from others’ PCs, … It all depends on how that data is routed and synchronised.

I just got the script error myself. I was about to make a post when I noticed this one existed already

It might be. As far as I understand, navy aircraft refuel slower because there’s a risk of overspeeding the probe opening/closing mechanism. Air force aircraft don’t have that restriction. If I remember correctly, the ideal refuelling speed for an F-16 is 310KIAS for example (while an F-18 needs to stay under 270). It might be worth experimenting a bit to see what “feels” best in terms of responsiveness and the lowest risk of overcorrection/PIO. Providing the current FM is reasonably accurate, that should get you close enough

Did you both check VRAM usage? Both the F-4 and CH-47 are new modules and thus use better/more detailed textures. A 3080 in particular doesn’t have a lot of VRAM, and in the current state of the CH-47, not even 16GB is enough. Also, using V-sync is not always the best idea, same as using “full-screen” in the settings menu.

I think that’s a smart approach!

The screenshots look very promising!

I don’t

That’s good to hear: at the very least VPForce gives developers priority in the queue so ED (or a 3rd party) won’t have to wait 6-8 months like the rest of us

I realise this is an old thread, but I'm in the same boat now, as my Reverb G2 died last week - after 4 years of pretty intense usage. I got a good deal on a Varjo AERO and it should arrive in a few days. I'm aware that support is on its last legs but it was the only valid alternative for me as I see it: I'm not ready to take the plunge with Pimax because of the well-known Chinese QC issues (their engineers admit this themselves), and Meta is... well, just no... Also I refuse to entertain anything that doesn't have a DP connection. I hope all goes well

Oh I need to check that then. The combination of MSAAx2 and quad view normally works brilliantly for me. *edit* I just noticed ED removed the “cannot reproduce” tag