squirrelmeister

Yeah, your mod gave me a boost in FPS in beta but I still see more FPS in the stable version without any shader mod compared to the beat with the mod. Cheers :joystick:

But and I just thought of that: My FPS in beta go under 40 FPS for around 75-90% of the time with the same settings as compared to stable where I just don't see FPS under 40. So for me at least I will stay on stable for the time being. Although I miss the Channel Map and I would love to see this map in stable and how it performes. Cheers :joystick:

Yeah, I know that it not really makes a difference when using ASW. But as I said stable feels also better than beta in general and for me I think it is better to have more places where it runs at full 80 FPS which is the case in stable compared to beta. Cheers :joystick:

Yeah, that was my mistake! And here are my personal conclusions (yet again :lol:) from testing today in the stable version (non-Steam and in VR using Rift S): Way better performance overall. 15-40 FPS more than compared to beta+shader mod! And I tested kegetys version for 2.5.6.49314 (latest compatible version for up to date DCS stable version) which gave me not really that much of a boost - actually I couldn't "really" see a difference in FPS (there is some but maybe max 5 FPS more). In that case I decided to go without the shaders mod (looks better too as we all know). And fortunately I could theoretically push visible range up to high because the FPS won't go under 40 even with MSAA x4. And what I saw too what always wondered me in beta: My FPS changed if I changed the MSAA, I never see that in beta. And to put one more thing on this: in beta it wasn't possible for me to go higher than a PD of 1.0 even with MSAA off completely which I always felt was strange, even when I lowered the PD to like 0.5 I couldn't get a single FPS more out of it, that's why I thought this all comes down to the CPU which also was strange since I don't think that my 7700k @ 4.9 MHz and my 1080ti could be that bad- but in stable I have to say DCS feels like a completely different game performance wise. I see differences in FPS when I am changing settings which, like I said before, strangely wasn't the case in beta. So the big conclusion (how many do I have now? haha :lol:): Something is wrong with the beta version at least in my case. And stable is the way to go when there are performance problems with the beta version. I would love to see others testing this and maybe you see the difference in FPS too. The attached screenshots are showing my ingame settings, the nvidia controll settings and an inflight screenshot from the instant action free flight mission in PG with the F/A-18. (same thing with the performance in Caucasus compared to beta!) And with that I am now going to have a nice cold Heineken! Cheers :joystick:

Hello there! So now I can say that, yes, stable version gives me deffinetely more performance. And I have to say I am getting like 15 up to 40! mor FPS. So with that said, I am gonna stay on stable. But I have a problem with the shader mod: it won't work, not the kegetys version and neither your one speed-of-heat. The following compiling error comes up no matter what version I tried. And yeah, I always do a repair after it is not working. Anybody can help? (I mean I am happy with the performance in stable - but even more FPS? WHY THE HECK NOT!) Cheers :joystick:

Ground Radar too? So no green screen for me :megalol: The p-47 is only on the beta branch that I do know. Two things I can live without if the performance is better. But everything under 10 FPS more and I am back in beta ^^ Cheers and thanks man! :joystick: edit: oh yeah, still downloading

edit: will test the stable version and will report back! Nevermind. I am downloading the stable version right now and using the non-steam version. With this I can have both versions and can see for myself what's eventually missing and what not. Cheers :joystick:

I know this is a little bit off-topic: But can you tell me what I would miss in the stable version from the beta one? Any significant modules that wouldn't function anymore (besides The Channel map which if I recall correctly is only in open beta right now)? Would love to be able to play with the F/A-18, Tomcat, and some WW2 warbirds (p-47 is beta too, right?). Cheers :joystick:

What frames are you getting in vr on the channel map? Especially the instant action free flights? Cheers :joystick:

Hey there! Did a lot of testing yesterday and my conclusion is that DCS is definetely more CPU bound than GPU bound. No matter the setting I use, one of the most important one is "Visible Range"! Everything else seem to have no to very less effect when it comes to FPS. How I got to this conclusion? Just a simple change in PD down to 0.5 gave me just like 10-15 frames more which seems in my eyes to be not normal since every other game will work absolutely flawless if you set the PD to half with almost all settings pushed to the max and I can be certain to reach constant 80 FPS with a PD of 0.5 (looks definetely shitty and not worth playing but for testing I thought this would be a good choice). Cheers :joystick:

Yes! See last couple of post. Cheers :joystick:

Just to let you guys know: I did a new post in the "Game Performance" section. Let's hope that someone from ED is reading it. Here is the link: https://forums.eagle.ru/showthread.php?t=278468 Cheers :joystick:

Tested again and with the clear water and IC-pass version everything works as intended! Cheers

Shadows get casted multiple times Just wanted to get a lot of attention to this seemingly and obvious bug: Shadows getting casted all over the place. For reference please see here: https://forums.eagle.ru/showthread.php?t=277805 This one could be potentially our FPS bug we all have and that the FPS in general is just bad! Tested with latest beta 2.5.6.50979 Cheers:joystick:

Does it work for anybody on the latest Beta 2.5.6.50979? I got a error again with failing to compile some shaders. Cheers Edit: deleting shaders folder and verifying files right now. Will test again after that verifying is completed.

No, not using any key commands. But the question stands: Is DCS changing the system setting of your VR device.

What are your settings? Do you have Cockpit Global Illumination "On"? If so then try to disable it and test again and see if it is better or even no drop in frames at all. Cheers:joystick:

For me it is the completely opposite of that on the SC. When I am looking down in the cockpit and there is nothing else in my view than the cockpit, my frames rise a lot, at least 10 FPS (sitting on like 40 +/- 5 FPS when looking at the island - so around 50-60 FPS looking down in the cockpit).

On point. Was exactly what I thought reading his last comment. But I would guess that happens to everyone...I mean when are you using kts in a normal life situation (and you don't have a boat in that case)? Cheers:joystick:

So here is the thing I am always confused about when starting DCS in VR: I start Oculus Tray Tool and set ASW to "disabled" for example. I start up DCS and I am in the menu pressing ctrl+pause to see the frames I am getting. And a lot of times I am wondering in flight why I am more or less constant at 40 FPS? Okay alt+tab out of DCS and see what the setting I did before is set to. It is set to disabled (ASW), so I quickly change it to another setting (doesn't matter which in this case) and change it back immedietely to "disabled". Alt+tab back into the game (don't forget to click in the window) and my frames are up over 40 FPS. I had the feeling before that something isn't right with DCS when it comes to VR. Another thing is that a change in PD with the tray tool doesn't work in DCS unless you do close it and start it again. Which seems off imo since I am quite sure that this is not the case in any other game in VR I played besides DCS. If this is something I got completely wrong then excuse me. My simple questions to the DEVs of DCS is: Is it possible that DCS is changing my system settings for VR? I am asking because I really do have the feeling that this is in any way true (the use of words seem off but I don't know how to say it in english - sorry). Anyone out there with the same feeling or maybe another sight onto it I did not see yet? Cheers:joystick:

Oh man! This would explain why my FPS is shitty even with my cockpit only mod and shadows for other planes only on the surface of the earth. I always wondered why the FPS gain is as low as it is with every shadow setting except all off completely. We have to get the attention of Wags. Wags come to rescue us!

Here is another option maybe: I don't know how the mod thingy jsgme works but deinstall the mod first with it when you have installed it with this tool. After that delete the whole "*:*DCSWorld\Bazar\shaders" - folder; delete the DCS-Folder in: *:\DCSWorld\Mods\terrains\*mapname*\misc\metacache (keep the dcs.lua!); delete everything in *:\DCSWorld\Mods\terrains\*mapname*\misc\shadercache; Repair your DCS installation which should bring back the shaders folder. Do not start DCS. Copy the shader (whatever version you prefer but make sure it is the newest one!) folder of the "Shader Mod" over to the bazar folder in DCSWorld and overwrite when asked. Start DCS and wait for it to load into the menu. After that open the mission editor, choose any map and place a plane you can fly. Start/test mission and wait again for it to load. After you have been loaded into the mission you can experience some stutters and some drops due to more shaders being loaded as you're flying through the map. Repeat for every map and it should be good to go. Keep in mind that you actually don't have to do the things with the mission editor, you can just hop in any mission and do it that way. The most important part is that it can take a very long time loading the shaders depending on your rig and CPU. Even if you think it crashed, do not close it and wait for it to finish its thing. Maybe this helps you because without this mod VR wouldn't be as much enjoyable as it is with this mod installed! Big thanks to kegetys and speed-of-heat for making DCS playable in VR! :thumbup::smartass: Cheers

It is very interessting how different the frames are for everyone here. Let me explain: I too have a 1080Ti but I am running with MSAA 4x and get constant 40 FPS (due to ASW kicking in) and I know that I am getting 80+ in air. I use the shader mod from Speed-Of-Heat and the shadow modification to just see the cockpit shadows. But I am thinking about getting all shadows back since most of the time I am running at 40FPS anyway and with shadows on high I am still not going under 40FPS - Supercruiser is another story but that depends a lot on other modules being visible (and that is actually generally the case allthough on the SC it seems to be more of a problem than anywhere else). I am running no extra PD (set to 1.0 in the settings) since the performance impact is way more noticeable for me in comparison to when running with MSAA 4x and the FPS show that too. I for myself came to the conclusion that there isn't any combination of hardware out there to this day that would be able to handle DCS in all its glory at 80+FPS in VR. And because of that the goal should be to achieve at least constant frames over 40 so that at least with ASW or similar technique it is playable and imo very much enjoyable. That is my case and for what I am going for - but there is just one big problem: the ghosting effect is of course very much noticable when high speeds are involved (in contrast to other planes, objects, etc.) but that is the downside of the techniques involved to achieve a good gaming experience with the hardware at hands. Another conclusion out of my personal experience and testing the last couple of weeks is that I strongly believe that DCS is way more CPU bound than GPU bound (I hope it is clear what I mean - english isn't my native language). But even on the GPU side there are differences. Especially when you compare the older 1080s/1070s to the newer gen of GPU like 2070s/2080s. I have the feeling that the older ones perform way better than the newer gen of GPUs - no testing here, just what I found reading through this forum and having an eye on peoples rigs. I think this has something to do with DirectX11 being the thing used by DCS and that the older gen is performing better with DirectX11 than the newer generation, but feel free to correct me on that statement - always good to know more and new stuff. And another one is: too much third party apps seem to influence your gaming experience in general and not only in DCS. This could be a simple hardware monitoring software which is causing frame drops and stutter because of the monitoring, it could be your OS (and if you don't have for example Win 10 Professional than IMO don't even bother playing games because of the restrictions the OS is giving you), it could be anything, literally. Just my two cents on this whole topic. And to say it a little shorter: I am just astound by the differences in performances for so many people. But also think that a lot doesn't ultimately mean that DCS is the bad boy in this situations (two examples: HWINFO64 caused massive stutters for me and was the cause for all frame drops I had in DCS; SteamVR standard resolution setting is actually nearly a 1.3-1.5 PD on the Rift S which lead to bad performance from the beginning as you can imagine - I am not using SteamVR anymore because of that). :joystick: Cheers:pilotfly:

Hey there! Don't know if you know that but keep an eye on the resolution settings within steamvr. I don't use steamvr anymore because of the faulty and wrong settings in resolution especially for Rift S and CV1. The resolution is set way to high on 100%. And I always wondered why I am getting that bad of a performance. Well with a PD of 1.5 (would translate into the 100% resolution settings of steamvr for my Rift S) no wonder I am watching a snail race :lol: Cheers

I would love to know your settings!