RealDCSpilot

Atm the mainrotor doesn't produce simulated air pressure for lift. The collective is just an anti-gravity lever, so the skids on ground behave magnetized as long as their collision detection says "true" for contact with ground object. As soon as you use the anti-gravity lever, it shoots the gazelle-thingy straight up and the skids say "false" for any ground contact and completely ignore that there ever was a ground object.

Despite the bad description of the problem, it is a fact that especially in MP something like a memory leak appears and causes a huge drop in fps. It may be triggered by choosing a new plane or different type of plane or by another player entering the server and choosing a plane that wasn't choosed before in the session. But that is only me guessing, DCS is still not handling memory very well (video memory and RAM). The thing is, sometimes the problem goes away after a few minutes, but it sucks however. The only thing that seems to mitigate this, is to lower the visibility range (lowering memory usage). But that's all guessing... What i don't get is why the "extreme" option exists, because there is no hardware that can tackle it (unless you set everything else to extremely low and ugly).

A much more efficient method would be support for Variable Rate Shading for supersampling in DCS. This MSAA mask feature is kinda neat, but would have much more potential in combination with VRSS.

I have a Valve Index and i use Steam VR for custom SS for DCS. I pushed it up to 2880x3200 pixels per eye at around 90% GPU usage. I don't know enough about oculus, i think you have to use the tray tool. Disable MSAA, SSLR, SSAA and motion blur. Set terrain shadows to flat and eyeball how your fps change.

In VR, DCS is running better than ever on my system at very high settings. From what i see in your settings, a PD value of 1.5 is quite high (DCS internal SS is very costly!) - it's better to use external SS settings and leave PD on 1.0. Use Oculus settings to raise SS for DCS, this shifts the SS workload over to your 2080ti which is hungry for work while running DCS's CPU bound tasks. The most actual driver optimization comes from this guide: Make sure your CPU runs DCS at high clock speeds 4.6+ GHz without any energy saving options. Don't use VR shader mod, ignore older optimization guides - DCS constantly changes, we have to keep up with it.

Hmmm, so the real Gazelle's stick does have a huge dead zone and as soon as you are moving a couple millimeters out of it and hold there it goes into a continuous roll?? Why does it fly like by-wire instead of direct stick to main rotor? And the real collective can be moved like crazy fast without friction for instant jump starts? Why does everyone have to tinker extremely with control settings to make it even a bit flyable, while other DCS modules just work out of the box?

Hi, just got a realtus forcefeel and tested SSA with DCS. Feels great! Adds another level to VR flying. I couldn't find a way to enable full support for all 8 motors of the forcefeel, did i miss anything? I can't use the Forcefeel Control Center app when SSA is running, it has this little checkbox (6 to 8 conversion).

The Rift OLED panels are clamped in bandwidth. Because switching times of OLED cells from OFF (full black) to ON where not fast enough, they decided to let them not switch completely OFF. Instead they just go into a very low energy state that looks like nearly black. However, VR HMD with OLED's aren't per se better regarding Blacks or color space, they also suffer from "black smear" "black crush" which shows as less detailed display of detail near black or dark scenes in general. I've seen that in several VR titles, where my old VivePro just showed pitch-black-nothing and my Index now still shows details and objects that i couldn't see before. The 100% perfect panel tech still doesn't exist.

Great post, thanks!

I upgraded my frankenstick with smooth low friction oil dampers. They compensate the weight of the heavier grip and counteract the mechanical deadzone of the G940 base. https://www.thingiverse.com/thing:3849592

The Gazelle is DCS's worst helicopter module, i would recommend to start with the Huey or Ka-50. Polychop did nothing to fix this since release in 2016, all we get are excuses like: https://forums.eagle.ru/showpost.php?p=4373660&postcount=51

I had to do this, FFB is so essential :) https://www.thingiverse.com/thing:3849592 The base delivers the FFB and X+Y axis, the grip delivers buttons buttons buttons... @fat creason Afte the latest OB update i have a bug with FFB switching off in the F14 in MP. If i change from another aircraft to the F14, FFB gets disabled :(

I checked the cockpit in modelviewer, it's not the shader maps... Must be something with the lighting or the 3d model that makes the gi lighting go nuts.

I'm on 445.98, don't have the issue...

+1

Thanks for looking into it. I had the problem in MP, don't know if it also occurs in SP. The tail wheel always tries to turn itself facing backwards, like on a rubber band.

Maybe i was wrong on gusts support in DCS, but i've never seen it working on your server. Look at chimney smoke or smoke pods or burning engines, the particle system is always a straight long line at 90 degrees from the emitter, showing a constant wind direction at constant extreme speed.

The problem is back! (DCS 2.5.6.49314) :huh:

https://nvidia.custhelp.com/app/answers/detail/a_id/5022/~/geforce-hotfix-driver-version-445.98

There is a significant difference between gusts and wind speed. DCS doesn't simulate temporary random changes of wind speed aka "gusts" yet. Wind in DCS is just a static value from a static direction. With adding gust speed to real "normal" wind speed you always end up with unrealistic storm conditions. There is a reason why weather stations publish 2 separate values for wind speed and occasional gusts. Makes the use of the METAR system senseless on your server. I don't get it, it is such a neat feature, but used in a wrong way.

The wind bug is back again, Senaki weather station says 14 Km/H which is around 4 m/s. Server is set to storm conditions at 14 m/s, thats 50 Km/H!!!

It's better to disable it, the new update seems to work well without it.

Best aviation skillz i've ever seen in DCS!

Yep, huge performance increase. Don't forget to revisit/remove prior performance "tweaks" of any kind (VR shader mod etc.), because they might interfere with the latest changes to the graphics engine. Do not forget to disable SSLR, this one is a big performance killer.

First make sure Windows isn't running in any energy saving modes, then try this: https://forums.eagle.ru/showpost.php?p=3411425&postcount=1