lefuneste01

Thanks for the future users of your wonderful hack! If only I would have seen it before, it would have save me a lot of time...My future AH64 profile will be based on your script !

I did it for myself, as Cackles, but it should be easier for newcomers who may want to extend it...They may go back to standard because of this. And it won't change the behaviour of your great script. Could you at least put a sentence on first post to explain that Mouse and Keyboard are disabled by default and what to do in case of ?

I just redo what you did to be able to mix mouse emulation and keystroke with this 120 button hack. I should had a look sooner in this thread, i would have save time. @sedenion : why did you restrain device creation to joystick only ? Generate keystroke or setup mouse emulation is a common need, and by default it will not work without any error message with your hack. We were 2 people to spend time on it, so could you update your package as described by @Cackles for other users ?

It's not reshade based, another library is used : 3dmigoto.

You can also try my mod to have sharpen on cockpit only and not on landscape, plus other cool features for VR : https://forums.eagle.ru/topic/207154-3dmigoto-vr-mod-for-dcs-label-masking-color-enhancement-sharpen-fxaa-copypaste-of-radio-msg

Can you put this file in the directory where DCS.exe is and try again ? As I can not reproduce, I'm not sure it will help... d3dx.ini

This means that fame a created a .bin file in addition to the files distributed in the mod. These .bin are cached complied shaders, so you should delete them, they will be created again if needed. You do not have to backup your settings, they are kept in d3d11_user.ini, that is not distributed in the mod, so it will remain.

As I know, other version of Kegetys mod removed some modified shaders, so some optimizations. If you use kegetys mod, use the "DCS VR Shaders mod patch for 2.7.7.14727" on top of it. Do not use the "update Kegetys VR Shaders mod for 3Dmigoto v1.1" because it will introduce some 3dmigoto variables in the Kegetys shaders. The purpose here is to check impact of Kegetys mod. If you use "update Kegetys VR Shaders mod for 3Dmigoto v1.1" or "DCS VR Shaders mod patch for 2.7.7.14727" on anything else than original Kegetys mod it may have unwanted side effects. My mod introduce ~5 fps loss (depending on options) so do not use it to define the current impact of Kegetys mod on fps otherwise you won't be able to understand which mod is doing what. I am surprised that the 3dmigoto mod alone id creating the night issue you shown. Are you using options shown in troubleshooting guide and no other mods ? That is full repair, just 3dmigoto mod install (without any patch things related to shader mod).

Be sure that you'll always have 45 fps in DCS if you want to use 90 Hz, this is may be difficult for some missions if you keep decent settings.

The full version, this is the one that give the most fps win. See the first post of this thread to get the patch to make it working with the last beta. Do not use the patch for my mod if you want to benchmark it. And I think it's best to use a real mission than a track to do testing, otherwise you may miss the real mission game context and find fps win you'll never seen when playing.

I was surpised by fps, so I did some measurements with fpsVR in Quick Mission / A10CII / takeoff, without and with my mod, without and with Kegetys mod. I supressed my DCS setting and set them to the value I used, to check if something may impact fps on this side also. With the last beta, it seems that the Kegetys mod is actually slightly decreasing fps ! At least with this scenario when you need every single fps... As I was not able to find any new "readable" shader in last beta (even though they removed white balance) I think they moved additional shader into encrypted files. So maybe Kegetys optimization are not taken into account. From my point of view, it's no more worth to install it and risk install issue. Too bad.

It's impossible to get 90 Hz every time due to poor CPU usage parallelization. And you will also find some difficulties to maintain 45 Hz in every time, to allow reprojection with 90 Hz. So 60 Hz is a good target. A better GPU may increase the time for which you will be able to have these 60 Hz, if CPU is not the bottleneck.

There is a troubleshooting guide in the first post can you try it ? At first try to make the mod working without kegetys mod, then add the kegetys mod. Is this issue only in the hangar ? I can not reproduce it...Which scenario to have this problem ?

Version 11.4 available in first post : compatibility with OB 2.7.8.16140

Hello, the last OB break the mod because of the line "Automatic white balance disabled due to incorrect colors. " in change log. I'm on it.

Here :

Hello, at first : Do a full repair, install the 3dmigoto mod only. Test it and check all is working. Then install again full kegetys mod, the patch for last beta and the shader mod for 3dmigoto compatibility. I did not test speed-of-heat version of shader mod. Maybe some files are missing in his version to make it work with my mod. The easiest thing to check is to setup cockpit color mod to zero => cockpit should be black. If nothing or all image change, there is something wrong.

I do not know if the patch is working with the IC version...Try at first to do it with the original full version of shader mod...

I just wanted to show you can not discuss in generally about DCS performance. For some mission or track replay, you may be able to use most of your PC resources and have good fps, while in another DCS mission context you won't be able to use half of your rig resources...So at first define a context that everyone can play (not a track, because you may miss some game logic eating CPU) and then compare with different user configurations to see if there is something odd. Otherwise it is like comparing apples and oranges...

I have 80 fps on my config when playing a F18 track and just after 45 fps in quick mission / A10CII / takeoff. So I do not see why this "something" will slow down my rig only with this mission and not for another one...Did you try the same mission ?

You're not alone :

There is something more fondamental in fps issue, my rig is not used at its full power for some missions:

normal path for a shader is [DCS install]\bazar\shaders\... All previous error messages were giving shader involved with relative names for example /shaders/deffered/Compose.fx But in your case it's a shader that seems to be in M:\shaders...no "bazar" directory, no install of DCS directory in the file path...strange, no ?

Hello, Why did you have error messages referencing shaders in M:\shaders where others have relative path ?

I mean you may use Fhloger's sharpening instead of mine or Reshade, as it used also CAS algorithm.