squirrelmeister

You can add these options in the "me_route.lua" in your DCS World directory: see here: https://forums.eagle.ru/showpost.php?p=3601319&postcount=8 Cheers

@Rockerverb08: Regarding your OC on your GPU: I had crashs all over the place with just a 50MHz overvlovk on my card. Allthough the temps were all good the game like many other games just didn't like that oc. Cleared the oc and everything was back to normal. Do you use any monitoring software? Something like HWINFO64...

Which module? Cheers

So this didn't work unfortunately. No matter what affinity I am using, no matter the priority set for HWINFO64, it still gives me these drops from 90FPS down to 70 for a splitsecond every 2000ms. Very sadly I have to admit that the long beloved program HWINFO seems to have a very big problem that shouldn't exist. Why I am saying that? Well MSI Afterburner is also monitoring my GPU without any drops or something similar. So the problem lays on the side of HWINFO64. It could be a sensor problem but I won't bet on that. But what do I know?!? Cheers

Just to be clear: In my case it gave me frame drops even if monitoring was set to off but HWINFO64 was still running. It has to be closed completely to get rid of these stutters/drops in frames. What I tested a moment ago, since I had a possible workaround for this problem or so I thought at least, was to set the affinity to a single thread. But still got these drops. I should mention that I didn’t set the affinity for DCS accordingly - which is actually a little dumb from my side. Will test it with core 0-6 for DCS and number 7 (this is a virtual core so it shouldn’t matter for DCS) for HWINFO64. Will report back if it is a workaround! Cheers

I don't have a clue unfortunately. But I am wondering about your frames - it states that you have around 27 FPS (Tacview is reporting it at the end of the log file). You are in VR, right? What is the resolution of the Reverb (I have the Rift S, so don't know a lot about the Reverb)? I am just asking because it is strange that you are only getting these kind of frames. Are you running any PD on the Reberb, I mean any higher PD than original?

Are you asking me? I am kind of getting confused from time to time :helpsmilie: Cheers

Thought I post it here too: For everyone having stutters like every two seconds - in my case it was HWINFO64 which caused the stutter/framedrop/frame loss on any settings! Closed it and the stutters went away - tested it again with starting it again while in flight, and stutters came back, turned it off and stutters went away again. Strangely it didn't even matter if I was monitoring anything or nothing at all. The reason why I had it every two seconds was because HWINFO64 logged/monitored everything every 2000ms. Hope this helps someone else too! Cheers

Speed-of-Heat version! the normal one with the water.fx! This one: DCS VR Shaders mod for 2.5.6.50321.zip (no link due to copyright...or I just don't know if I am allowed to, that's why no link!)

One more thing: turnes out that I have to activate the Turbo Modus in the bios again - so the OC works as intended - to know something doesn't mean I know everything:smartass:.

Figured it would be good to post my system specs: Happilly presented by HWINFO64, the stutter causing bad boy ::doh::lol: I am using a water cooler for my CPU! Ram is 48gb. Does not show all the ram modules!

So, now that I tested everything, I can confirm it is working again without any crashes, without any sort of stutter (2d and VR- solid 40fps, rock solid), just beautiful! So I am getting constant 40fps (due to ASW - but it is okay since it is on AUTO and switches back to 80fps when I am hitting those numbers) on all occassions: SC, in air, everywhere. I am using the shader mod and this little shadow tweak: { --high 4096, {0.02, 25.0, 100.0, 400.0, 1500.0, 7000}, {0.02, 0.5, 0.6, 0.7, 0.8, 7000} --the 7000 is for cascading your planes shadow on the ground }, Graphic settings ingame (just copied it out of the options.lua - faster than a picture): ["DOF"] = 0, ["LensEffects"] = 0, ["MSAA"] = 2, ["SSAA"] = 0, ["SSAO"] = 0, ["SSLR"] = 0, ["anisotropy"] = 3, ["aspect"] = 1.7777777777778, ["chimneySmokeDensity"] = 0, ["civTraffic"] = "", ["clouds"] = 1, ["clutterMaxDistance"] = 0, ["cockpitGI"] = 0, ["effects"] = 3, ["flatTerrainShadows"] = 1, ["forestDistanceFactor"] = 1, ["fullScreen"] = false, ["heatBlr"] = 0, ["height"] = 1440, ["lights"] = 2, ["messagesFontScale"] = 1.25, ["motionBlur"] = 0, ["multiMonitorSetup"] = "1camera", ["outputGamma"] = 1.3, ["preloadRadius"] = 150000, ["rainDroplets"] = true, ["scaleGui"] = 1.25, ["shadowTree"] = false, ["shadows"] = 4, --keep the custom settings in mind here! ["sync"] = false, ["terrainTextures"] = "max", ["textures"] = 2, ["treesVisibility"] = 50000, ["useDeferredShading"] = 1, ["visibRange"] = "Medium", ["water"] = 1, ["width"] = 2560, I am now very happy with that performance especially that I could make out the bad boy who was causing these terrible frame drops - HWINFO64 and its monitoring (tested it again - just started it as I was ingame and not a second later the frame drops were back. turned it off/closed it and back to no stutters and no drops in frames!). EDIT: Did forget to mentioned that the cause for the crashes was a slight overclock to the core clock of my GPU! (just a 50MHz overclock! - temps were completely fine) Cheers

Yeah, had a look at this and it is what I was doing. On Steam it is just called "validate game files/data". So I did that. But thanks anyways - much appreciated!

Thx for the quick reply but it seems I won't need it. I am now like 5 minutes into my mission and I am not getting a crash. And the winner for causing it is.....: A simply OC on my GPU of about just +50MHz on the Core Clock (seems like MSI Afterburner is doing it on its own/standard - just installed it yesterday for better overview and more control) was causing these crashes. Will install the mod again and report back as soon as I have tested it.

I still get a crash. This is strange. One more thing for me to test. Will report back. Just wait two minutes ^^

That repair thingy...can I do it via Steam? Because I am on Steam.

Why do I have over 223 files that failed to validate? That makes no sense at all. I mean the mod doesn't put 200 or more new/same files into the game. And I did delete it and and used my backup shader folder. And yes, this backup is from a new validated install. Can someone enlighten me?

Okay. Strangely the first test resulted also in a CTD or at least in a crash. Gonna validate the install and test again. This is now getting strange. I just did one thing yesterday and that was just to disable the Turbo Modus in my bios since I am not using it anyway due to the oc I ran. I am getting confused here now I just remebered what else I did: made a registry change so that DCS has always HIGH priority. Deleted it too. Still waiting for the validation.

Just saw that there was a new folder in saved games dcs metashaders folder called "metafx". Is this new? Never saw that one before. Will delete mod and all shader folders for all terrains and all folders in saved games metashaders and fxo. Will report back if CTD is still present.

I am sadly on the same CTD train with the new version (without water.fx!). Yesterday it just crashed, today it gave me a "metashader" compile error. CTDs occur on PG and Caucasus (only maps I got). But on the other hand I think I solved MY stutter problems/dropping frames every 2 seconds from like 180 down to 90 for a splitsecond every two seconds (doesn't matter what fps even if you cap it at a certain number - the drops are always present). Turns out it correlated exactly with "a flickering" on the monitoring window of HWInfo64 and I mean exactly! Closed HWINFO64 completely and I think my framedrops are gone! Have to test further but until now I would confirm that it was indeed HWINFO64 which caused massive drops for me! Maybe this helps someone out too. Never would have I imagined that monitoring software could be such a problem in certain games (it does not happen in other games or at least that is my impression) Cheers

Hey all! So here is the thing what confused me a moment ago: I set up controls for the F/A-18, saved it for each controller and column. I then bought the good old Huey and made sure that my profile was loaded before I set up some controls for the Huey. Saved the column as the same profile. All nice and good. But: Today I loaded up the F/A-18 and wondered why my controls won't work... - got into the control settings and loaded up the profile, pressed save as profile and there I go...well, actually NOPE. Back into the control settings and just flipped a switch to see where it was mapped and to my surprise...nothing was mapped. My question: Is it normal behaviour that I can't map my controls to two different modules in the same session in the control setting (adjust controls) menu and then press save as profile and only the last control bindings for the last module are saved? :helpsmilie::joystick:

Hey! Just wanted to let you know what you can eventually expect with this setup: I myself have a 1080ti and an i7 7700k overclocked to 4.9Mhz with water cooling, 48gb of ram. So my setup is roughly around 15-20% (due to the oc - standard would be 15% for the 7700k vs the 4790 alone) better performance - just on paper - ingame I would suggest more like 10-15% more fps. My fps on the SC are, well how should I put it...very much dissapointing. In 2d no problems because fps stays way above 60fps on 1440p with high settings. In vr....well that is another story. No way to play DCS with 80fps (Rift S) all the way through. You have to use ASW, or if you like to play a vr game that looks like a prototype from the nineties (yeah a little bit over the top - but it kind of is true when you lower your settings to the point where you can maintain 80+fps), then you don't need ASW. Yeah that was very much a sarcastic comment ;-). DCS is very very demanding in every aspect on your rig. And I yet have to see someone who has the rig to play dcs in vr at 80+fps with high settings. My frames are locked at 40fps with asw on because of the jitter you're getting with forcing 40fps without asw enabled. In air with nothing around and no terrain in sight I get steady 80fps but that is the only time I am getting those numbers. On the sc it depends a lot on what is present too - on and off the sc. If there are a few/handful of statics on deck and ai starting and flying around (I have to say that this also depends on what module is flying around or starting or landing) I am getting around 25-40 fps, which would actually not bother me if there wasn't the problem with ghosting when high speed objects fly by. When I am the only one on the sc and no ai plane anywhere, then my frames go up to 30-40fps. I found out that some of the settings like shadows have a huge impact...but the gain in fps with no shadows is in my case not worth it - just because it just looks terrible, completely destroys my immersion. I do only use shadows in the cockpit and my own shadows outside - every other shadow is set to off, no ai will cast a shadow, no trees, no static map objects, nothing else but me, myself and I. And one of the worst things with the sc are (and I think in general it is performing as expected due to the complexity of this module) the framedrops every 1-2 seconds. And these are in between 15-50% (yeah you read right, 50! percent). These drops happen no matter where you look. The only difference is the intensity of the drops. Looking at the isle is the worst of framedrops you can imagine - and that every 1-2 second. Even in 2d I get these massive drops from like 140 down to 60-80 (just for a tenth of a second but very much noticable). So I would suggest that you wait a little bit longer, get all cash you can get together and go for something way bigger and better than what I for example have what is actually a good gaming rig (at least for all games at 1440p with maxed out settings). Well that is a long read but maybe I can prevent someone from doing something they will, with a very high chance, regret afterwards. And for better comparisons here are my settings out of my head: Textures: high (medium, low won't give me more fps) terrain textures: low, just because the difference between high and low is in my eyes negligible civ. traffic: off water: medium visib range: medium heatblur: off shadows: high (tweaked for cockpit only shadows) res.: doesn't matter in vr (2d would be 2160x1440 in my case) res. cockpit: 1024 every frame (fps wise I didn't notice a jump when setting this lower MSAA: 4x (no difference in performance for me if it is 2x or 4x) everything else on the left side: off Clutter/Grass: 0 Tree visibility:60 preload radius: all the way to the right Chimney smoke density: 0 gamma: 1.3 anisotropic filtering: 8x terrain object shadows: off (this one I have to test again to see if I fall under 40fps) cockpit global illumination: off rain droplets: on (allthough I am not playing in the rain because frames would go down all the way) Vsync: off PD: 1 (strangely I can't go higher in dcs [in other titles no problem at all] without a massive performance loss - and my performance is way better and I mean waaaaaay better even with MSAA at 4x) Hope this helps making your decision easier. Cheers

Hey there! As long as I know it should be actually the same size. Since 2.5.6 stable is out now and just today/yesterday came a new patch for beta. But I could be wrong and maybe a veteran could help out and enlighten us. But I am pretty sure that the size is the same. Cheers

Hey there! Good to hear that it is working again. For performance purposes you could lower the "Clutter/Gras" setting all the way to the left. That should or could help with those microstutters. Cheers (I am waiting for more ram to arrive today. Hopefully this helps me out a little bit since my 16gb are always maxed out when playing DCS:joystick:)

Hey there! Could be a vram issue. I see you only got 4 GB. That could be the bad boy here. What are your settings in DCS? (graphics) EDIT: Just had a look at your pictures and it seems that your GPU has no vram left at all. That could be the problem as I don't see anything else, maybe these CPU spikes could be a problem too. But I would guess it is a vram issue!