RealDCSpilot

Yep, this new generation of GPU's is the first one that doesn't struggle with highend VR. If the DCS engine gets optimized for todays CPU gen someday, we can go even further. Nvidia will also release a 3080 with 16GB VRAM, i really recommend waiting.

@propeler Here is the CAD data of the base thread for grips M36x2-6g (by Baur from Virpil): https://forum.virpil.com/index.php?/topic/656-warbrd-base-thread/&do=findComment&comment=6006 Should work for all the compatible grips out there.

Very impressive! Did you already try the force trim options in the Huey, Mi-8 or Ka-50? (default trimming option in special settings)

Maybe, once you start being objective, you will understand my point.

Did some more testing yesterday. I only reduced render resolution settings to 100% which ends up with 2016x2240 per eye. VRAM usage dropped down to ~10.8GB. However, didn't do a longterm test and this drastically reduced visual quality and i still needed to force motion smoothing because CPU frametimes won't allow 90 FPS. Conclusion: the crispy sharpness of high SS settings - once you've seen it, you never want to go back. More VRAM opens up a lot of headroom to enhance your VR experience.

Just two examples what a real Gazelle pilot said, but you need to be able to use translate.google.com: http://www.checksix-forums.com/viewtopic.php?f=465&t=200331&start=50#p1678174 http://www.checksix-forums.com/viewtopic.php?f=465&t=200331&start=50#p1679855

He is talking about collective, not the cyclic. FFB on or off has no influence on that axis. Also, the Gazelle is the only module with broken FFB support and never got fixed, amongst many other issues where ED can't be used as scapegoat.

@The_Nephilim I think aspect ratio is not that important for the VR mirror, but maybe it's helping with something if it's set to 1:1 panel resolution. Usually this is all forced by the VR SDK and DCS settings for res and aspect ratio are ignored. As an update, i also set visibility range to extreme now. No problem for the 3090, it's amazing how far i can push the game settings now.

options.lua ["graphics"] = { ["DOF"] = 0, ["LensEffects"] = 2, ["MSAA"] = 2, ["SSAA"] = 0, ["SSAO"] = 0, ["SSLR"] = 0, ["anisotropy"] = 4, ["aspect"] = 0.9, ["chimneySmokeDensity"] = 10, ["civTraffic"] = "low", ["clouds"] = 1, ["clutterMaxDistance"] = 800, ["cockpitGI"] = 1, ["effects"] = 3, ["flatTerrainShadows"] = 1, ["forestDistanceFactor"] = 1, ["fullScreen"] = false, ["heatBlr"] = 1, ["height"] = 1600, ["lights"] = 2, ["messagesFontScale"] = 1, ["motionBlur"] = 0, ["multiMonitorSetup"] = "1camera", ["outputGamma"] = 2.2, ["preloadRadius"] = 150000, ["rainDroplets"] = true, ["scaleGui"] = 1, ["shadowTree"] = false, ["shadows"] = 4, ["sync"] = false, ["terrainTextures"] = "max", ["textures"] = 2, ["treesVisibility"] = 10000, ["useDeferredShading"] = 1, ["visibRange"] = "High", ["water"] = 2, ["width"] = 1440, autoexec.cfg options.graphics.stereo_mode_use_shared_parser = false disable_write_track = true no_device_hotplug = true

Most of my current settings.

@Extranajero :) Oh, i really hope you attend to that. For you it's free of charge!

Thats what GPU-Z shows. Idle, loading DCS to menu (6GB), loading Through the inferno mission (over 13GB) choosing A-10II (24GB) after that choosing F-14 (2 little spikes for each plane). After that leaving to menu, 24GB kept getting allocated. At the end, quit DCS. Keep in mind that i'm driving very high ingame settings and double panel resolution SS for each eye. A huge part of VRAM is allocated for the display buffers. The last graph shows RAM usage, around 32GB from 64GB.

I'm currently running the 3090 with forced low latency on Ultra and prerendered VR frames at 1. This seems to minimize the side effects of Steam VR's motion smoothing a lot. The 3090 is extremely beefy compared to a 2080ti and seems to have a real advantage here. The strange thing is, i see 40 or 27 FPS in DCS internal FPS info, but the "27" FPS feel much much smoother on a 3090 than with a 2080ti.

About the POSCAP issue, the latest Nvidia driver introduced a better algorithm for boosting clocks to prevent spikes: Atm, my card is stable boosting up to 1980 MHz, but i have no comparison to unstable behaviour because i started with the most recent driver.

How about a workshop? The agenda would be: 1. Public relations: - How to find better ways to communicate with our customers and the community - Who are our customers and potential customers? What do they want? - Professionalism: what to communicate and what not - How to keep always being honest, keep telling the truth 2. About learning and being a professional developer: - Analyzing fails and mistakes from the past 4 years - Deep analyzing other dev's modules: what are their strongpoints? - why are we not able to reach their level, even on core features? - What is DCS? What makes it different from other software/game/simulation platforms? What are our responsibilities if we take part in such a longterm development platform? - What are standards in DCS? How can we meet those standards? - Get an overview of todays available hardware and features that are supported by DCS (huge list) - Leave the bubble we created for ourselves and are stuck into 3. Rebuilding company reputation: Rethinking strategy to regain the trust of customers and the community A. take all we've learned from 1. and 2. B. Fix the Gazelle first? May bring back trust from existing customers C. Invest time and concentrate on marketing this "new" gazelle (from B.), be honest about mistakes and show A/B comparisons in detail: What was bad and why - what is fixed and better now (show proof on youtube, social media...) 4. Release of the Kiowa module - take everything you learned from 1. 2. and 3. - have a good time, finally get the sales you deserve if you release high quality products for DCS

+1 on the collective behaviour This is standard in every other DCS module, the simulation defines how fast you can move primary control inputs, not the user.

I have the same card as in the 8auers's video. Gigabyte 3090 Gaming OC with the "worst" capacitor config, i personally banned Afterburner now from my system because it isn't needed anymore. 10K of CUDA cores boosting up to 1980 MHz, stable with the latest driver. It's a big punch and enough for me for now.

Yep, DCS does not clean up VRAM properly, makes it look like a memory leak. If VRAM is full, your system starts to cache the rest to the harddisk, that additional data transfer activity adds load to the CPU and GPU and kills frametimes. That's no problem for normal single screen usage, i doubt that you can fill up 11GB while playing flat. But VR turns it all around, we are driving it to the extreme with VR. For 2 highres panels and AA + post pro effects, you need larger buffers in VRAM plus enough space for geometry and highres textures.

You can't imagine my big fat smile yesterday when i tested this, i was happy like a little boy. Extreme highres for both eyes, very high visual quality settings + 4x MSAA on top and still a smooth and pleasant flight experience. This GPU generation is the first one that has enough steam to tackle high quality VR for real. Imagine, if DCS's engine wouldn't be that badly CPU bound, what would be possible...

I suspected DCS's VRAM usage for a while now for causing occasional framerate drops and stutters, especially in MP when switching aircrafts. Typical scenario was: entering the server, choosing an aircraft, play a while, choose another aircraft (F14 on carrier for instance) and bamm! VRAM overflow - huge FPS drop. Got my 3090 (24GB) today and this problem is gone. My good old 2080ti with 11GB wasn't enough. Rule of thumb, the higher the panel resolution and/or SS setting, the more VRAM you need on top of textures and geometry filling your VRAM already. Steam VR beta just updated and adapted to this: "Maximum automatic render resolution limit is now calculated based on gpu dedicated memory; it was previously hardcoded to 1.5x the headset driver recommended resolution. This should have little to no impact on existing headset and video card combinations, but will scale better as displays become higher res and gpus more powerful."

Steam VR beta just updated: "Maximum automatic render resolution limit is now calculated based on gpu dedicated memory; it was previously hardcoded to 1.5x the headset driver recommended resolution. This should have little to no impact on existing headset and video card combinations, but will scale better as displays become higher res and gpus more powerful." Perfect timing.

Got my 3090 today and it really makes a difference. The most important feature are the 24GB VRAM for VR in DCS. I had the occasional stutter problem in MP sessions, mostly after switching aircraft where i already suspected that it breaks the 11GB barrier of my 2080ti. Now everything is pretty smooth at 2880x3200 per eye on the Index, most settings maxed out, even MSAA at 4x. No more stuttering, switching aircraft goes pretty fast (geometry and textures load sooo fast!). It's still throwing money at the problem, but this time i'm really happy how it works out.

I'm put off by the Gazelle's unrealistic handling and flying, how bad controls are and even how unrealistic the 3D model is animated during flying and auto hover. Never expected this from a DCS module. If ED's shop system had a refund option, i would have used it a long time ago.

@shagrat I don't get the point of any of your posts, SAS is a subsystem. AP will use it, because it would be senseless not to. Still there is enough real life data and videos that show that the controls + SAS + FM of the Gazelle module are extremely far from everything real.

@Shagrat Autopilot modes are separate systems and make use of SAS, yes. https://en.wikipedia.org/wiki/Autopilot "Many helicopters have pitch, roll and yaw SAS systems. Pitch and roll SAS systems operate much the same way as the yaw damper described above; however, instead of dampening out Dutch roll, they will dampen pitch and roll oscillations or buffeting to improve the overall stability of the aircraft." In a helicopter SAS is basically just a dampening system, it smoothes everything out. The pilot in the video makes a lot of quick movements and the chopper reacts a bit later, so it looks like SAS is active.