Raven (Elysian Angel)

Sure but if it was your system you'd see the same behaviour with other modules too. It's odd really... The only thing I can think of right now is to try and decrease/remove other potential bottlenecks, such as PCIe bandwidth (check bios and make sure it's running at gen5 x16), memory bandwidth (check BIOS to make sure EXPO2 is selected - EXPO1 is there only for compatibility), disk speed (again check BIOS but for Samsung NVMes you also need to keep Samsung Magician running in Windows for optimal drive health), ...

Yes of course because a 2070S only has 8GB of VRAM. 4080S and 5080 have 16GB which is plenty for everything except the Chinook.

Whoopsie, my bad then... Anyway, the way I understand it is that Gigabyte's turbo mode basically just turns off SMT (and disables the 2nd CCD if present) and based on what I have seen of DCS's core management, I'm not sure that's a good idea. Over the years there have been forum posts about people who turn off SMT in DCS (either in BIOS or by using Project Lasso) and haven't seen any performance boost. I think DCS is pretty good at spreading the workflow across available cores, and identifying which cores to use for render tasks and IO and stuff.

I haven't noticed any issues, but I have only done a quick free flight so far on the Normandy map. Compared to the P-47 it uses more VRAM (still fits perfectly well within a 16GB frame buffer) but framerates are about the same - on my end anyway. It's a brand new module so I expect further optimisations along the road I'm not seeing that, and my system is very similar to yours

I'd also like to see more flap bindings than just "+" and "-".

That depends on how you land. It's tricky to keep the nose up and do proper aerobraking (it's tricky in the F-5 too for example) but you can certainly do it: I have done so on multiple occasions.

It's tons better than ED's warbird pilot models though At least this one has the correct proportions for a human being

I'm hilariously unqualified to talk about flight model, but I can share my views on FFB. Mind you I have only done a quick free flight so far, and the only effect I noticed was a stick shaker when the stall warning comes up. The aircraft is incredibly sensitive in pitch (and yaw) and there doesn't seem to be an artificial feel system. There also isn't a default TelemFFB profile yet so I copied the P-47 one then loaded my own warbird configuration file. That helped a ton!

Happy to hear that fixed it!

Do you have FFB disabled in the "misc." options menu?

Virpil grips are probably closest to Russian /Soviet aircraft, though they are meant to be a representation and not a 1-to-1 copy. The T-50CM2 and the new FLNKR grip are both nice products.

Less drag is a major advantage when it comes to DCS, and it’s not a Frankenstein pod like our current pod is.

Yes they can - it just might take a bit. It took 6 weeks for my R1-Falcon pedals to arrive and that’s a brand new product, so this is likely a worst case scenario. My Rhino took 8 months between order and delivery: it doesn’t mean it’s not worth ordering.

Jester still quite often puts a smile on my face

Terrain stutters have been happening forever. I can’t remember a time when the terrain *didn’t* stutter, if that ever happened - especially when looking to the sides (looking out front is fine). It stutters even when the game is locked at 90fps Lots of people have been complaining about it over the years, and started to believe it’s a limitation of ED’s terrain engine. Perhaps the introduction of Vulkan will fix it, who knows…

Yes, because we're 2.5h past the normal time a patch lands. And on top of that, there's nothing new here:

Is it related to any particular map or module, or is it a general issue? I have a very similar system to yours. Perhaps you could share a mission file that gives you the most problems, and I can have a look? There are issues with stuttering that were introduced a few patches ago so that would be up to ED to fix, but I think that's a different issue than what you are experiencing... In any case, if you want I can take a look (tomorrow as it's bed time now ).

That would make sense, as I often get those stutters (see graphs above) when looking down. Funnily enough, I get no stutters when flying inverted, but when I roll back to a normal attitude they start again: the frametime graph shows the green line (simulation) increasing in frame time to match the white line, and I get CPU BOUND MAIN THREAD (red) displayed. Btw this is still happening after switching to a new PC with fresh Windows installation, so this is not bound to the specific hardware setup I was using.

Did you check if it's perhaps something that's running in the background, that's not needed for DCS?

ED apparently "fixed" the polling rate issue, but regardless of that it's always a good idea to set it pretty low especially in VR. I'd check your windows power plan, or even disable the Power service altogether: there's a lot more that those power plans do behind the scenes that isn't shown on the default Windows UI, and it is known to sometimes cause stutters (but it depends on which module, as not all of them seem to suffer from it).

Yes, there is. An official manual is an important resource and part of the module, therefore we paid for it, therefore it's far from unreasonable to insist ED provides one. Their logic is probably that it's a waste of time and resources to write a manual while features are in flux and thus the manual would need to be re-written every time they change something. But that logic falls flat on its face when you consider how 3rd parties do things. If a particular feature is WIP, simply leave it blank in the manual, stating it's WIP and add it later. This leaves plenty of opportunity to write the parts of the manual for stuff that won't see significant changes and/or is considered complete Besides, it's probably a lot easier for developers to explain a feature when they just finished developing it and is thus fresh in their minds. Compare this to writing about something years later after you have been working on other modules as well...

This has been discussed in depth already in other threads on this subforum. Have a read there :-)

Correct me if I'm wrong, but I believe "nothing" is still a leftover setting from the older sprite clouds, which is why it looks the way it does. The only way to use the new weather system is to enable one of the existing templates.

Yes and it also depends on if you're playing other games too, and which options you want to be enabled. Apparently Frame Generation *requires* HAGS to be enabled. I also found that disabling HAGS drops the framerate in Cyberpunk by 50% Game Mode is also something I keep left enabled. I see no performance penalty... Also, core isolation / memory integrity / VBS has very little if any performance penalty for modern CPUs as they have hardware accelerators for it. So it really depends on what you have (on my system on or off falls within margin of error).