zaelu

Fain! You are so oldstyle with that X45 :) btw, Are you ok mate with this corona rahan?

Ok, I can confirm that I also have that too transparent water "bug" without fixing the Water.fx but just deleting the moded file. I need to "fix" it. Also I tested now with 1024 on every frame and I would say.... ads a liiiiilte bit of readability in cockpit.... I would say very little but visible. I checked by looking at the radio altimeter in F14 (straight to it from normal zoom, that means NOT zoomed in). Also I disabled SS in OTT and just went to 1.5 PD in game and performance looks better at same multiplier. Are they on parity the ingame and OTT, meaning 1.5x in OTT is the same with 1.5 PD in game? (I am not using steamVR) Attached are the water without fix. I think I just played in areas with just small rivers that look OK see second screenshot where the river starts from lake/wide part it looks OK. And third picture is the weird effect I tried to avoid by deleting the water.fx.

No, they are blue. I would say normal looking. But I think is a shader issue. You need to delete old compiled shaders so they are not used anymore. I had MSAA 2x but at some point I've noticed little performance loss by an improvement in jagginess from aliasing so I switched to 4x. Also I always had 1.0 Pixel Density in game but I think I will start testing the differences between it and OTT. I want to see if OTT does a poor job at SS because there is still quite significant shimmering even if I test 2.0 SS in OTT (with the expected performance loss but just for testing). How to you set textures to 1024? You mean the cockpit displays? Aren't those controlling just the HUD MFDs?

Yes, on my system the difference is minimum as the FPS is low so for example 25% might be just 5fps bu in a higher end system it could go to 25FPS and that is big. The grass looks horrible in some settings. like shimmering dots... like old MSFS terrain textures used to look 20 years ago. But the filtering settings do make the grass look better. It's a combo of MSAA/AF/SuperSampling in OTT and the shadow settings in game. In my observation shadows look good even on low, almos same quality with mid and high and with a bit better FPS but flickers tend to appear and those flickers on grass combined with the rest of things needed to be applied makes it look awful imho. My Methodology is not perfect but I always load same mission and spawn/fly in same places and observe the FPS and "general" feeling". Sometimes at 20-25 FPS all feel fluid and sometimes is a jerky mess. So I choose between the two. I always restart the game and delete FXO/Metashaders2 contents... a real fun time on a HDD :D

After a gazillion of testing I ended up with this config for my rig. Note that I have DCS World on a HDD drive which really ads to "the fun". I don't have any AA added through the nvidia drivers as I found to be either a placebo or simply mirage. Nothing happens with any setting. 2x 4x 8x FXAA on/off MSAA... enhance or override... nothing! Waste of time! All I have forced in the drivers are high performance power setting and the optimizations on. No Vsync etc. Simple shadows in Kegetys mod adds to little to the FPS while ruining the lighting in some aspects. Some flickers... and general appearance a bit dull. Same if you put Shadows bellow high... you get a bit more FPS but artefacts and flickering appear immediately. So High shaddows is a worth sacrifice. The MSAA mask size is 0.4 as I really dislike that you can spot the aliasing on the sides so I keep it in a medium range. Also I removed the Water shader from mod for glitches reasons. #define ENABLE_HMD_MASK 1 #define ENABLE_SIMPLE_SHADOWS 0 #define ENABLE_SIMPLE_GRASS 0 #define ENABLE_SIMPLE_CANOPY 1 #define ENABLE_SIMPLE_HG 1 #define ENABLE_NO_BLOOM 0 // improvements #define ENABLE_DITHERING 0 #define ENABLE_DIFFUSE_SS 4 #define NVG_GAIN_ADJUSTS_POSITION 0 // other settings #define MASKSIZE 0.620 #define MSAA_MASKSIZE 0.4 #define NVG_SIZE 4.0 #define NVG_VERTICAL_OFFSET 0.07 #define NVG_NOISE_STR 0.075 #define NVG_HOTPIXEL_THRESHOLD 0.99982 Attached are my ingame settings and opinion about them. Emphasis on "opinion"... you know... everyone has one... Also I run ASW OFF religiously. and 1.5 SS in OTT. With these settings I have between 20 and 35 FPS, usually above 25 which I can tolerate.

No, it's like you negate a quote. It doesn't matter if it's an affirmation or negation. :D ============= I tested with water shader removed from pack and the artefacts are gone 99.9%. Sometimes when you start viewing a flotilla they produce a strange patern of waves at first ... could be DCS here and from 10 000m alt you can see a strange reflection of the clouds in the water.

:D It's a simple YES to a NO... So with 1 you activate the no...

Me too. Trying now with optimisations on water reverted to default.

While waiting for the Axis support to be able to replace my Joy2Key I wanted to ask for another feature maybe? How about emulating joystick presses with keyboard buttons or combos? I know... is backwards. Some uses might be... the one I mostly want, ability to map hardwired controllers functions to a keyboard press... like... Oculus controllers buttons? :D I would like to have a combo on my keyboard which I can reach/find faster than the darn oculus controllers to simply turn on passthrough to see what my 3 year old is doing around me. So that would mean a extension to this feature... support for Oculus or any other VR controllers? Another cool feature would be to have the ability to map either the keyboard combos or a controller buttons to another controller buttons or even an expanded direct input set? If this is even possible. For example . Ability to map a keyboard button/combo or a button press or long press on my Bu0836X controller to apply short press on the 33 button on the Warthog stick. Yep... it doesn't have 33 buttons but extra virtual buttons might come in handy. Example, Discord has ability to map joystick buttons for Mute, Unmute, toggle VOD etc.... but once a joystick button is mapped to that function ALL the other buttons with same number on the rest of the controllers do same function. So if I have MUTE mapped on my modded throttle to a toggle switch No 7... Mute function toggles when I puss up TMS on Warthog... Not really a joy...

Restarting a mission and/or deleting the fxo/metashaders folder contents from DCS(.openbeta) folder from Windows User folder also can solve it. But usually restarting the missions restores the cockpits. maybe is Kneeboard Builder... I have it and is useful.

Mig21 is I think the only cockpit that looks smaller than it should in VR. You can notice this if you just jump from one plane to the other... planes similar in size cockpitwise. It feels like you are Gulliver in a Midget sized Mig21 No screenshot in 2D would exemplify the bug but I almost certain is not something with my setup as all the other planes look OK. The throttle looks tiny and awkwardly away. All switches feel like I need to flip them with the very tip of the fingers. The world around is consistent but the cockpit is midget size. Any way to set up some lua files in the module to modify maybe the perceived PID so this cockpit would not feel this bad? For testing I recommend jumping from L39 to Mig21 for example.

One odd thing with this shader fix and the one found here: The first time I load a mission DCS starts and run. But when I just restart the same mission invariably it crashes the game. Constantly.

Yeah but having two shortcuts to switch at the start is easier. I used to simply start in VR, untick the VR on in VR options... restart... go about my business in ME.

Thanks. faster way to load ME, yay.

what is the parameter for that shortcut?

I also experience lewer performance in VR with the latest patch. With the kegetys tweak not updated and unusable I can feel the full blow of low performance in DCS. I am a guy that is happy at 25-30 constant FPS but now I am in the 15-20 and is an eye strain. And please ED don't aim for "low" settings your optimisations, having to chose between bad looking game and low FPS I choose to play something else. And on the longer term aiming for "low graphics with high FPS" will get you nowhere.

OK, but doing just a replace didn't basically discarded maybe some improvements were put in the file with latest patch?

Yeah. Yours works. I managed to find what to do. I added reference to rough_met texture (correct ones after 100 tries :) ) and they start working. LE For others that might have same problem and want a solution... you have to add this: {"MiG-15_MAIN", 13 ,"MiG-15_DIF_RoughMet",true}; {"MiG-15_MAIN_N", 13 ,"MiG-15_DIF_RoughMet",true}; {"MiG-15_MAIN_N_R", 13 ,"MiG-15_DIF_RoughMet",true}; {"MiG-15_MAIN_N_N", 13 ,"MiG-15_DIF_RoughMet",true}; {"MiG-15_MAIN_N_N_R", 13 ,"MiG-15_DIF_RoughMet",true}; {"MiG-15_MAIN_N_N_N", 13 ,"MiG-15_DIF_RoughMet",true}; {"MiG-15_MAIN_N_N_N_R", 13 ,"MiG-15_DIF_RoughMet",true}; {"MiG-15_MAIN_N_f3", 13 ,"MiG-15_DIF_RoughMet",true}; {"MiG-15_MAIN_N_f3_R", 13 ,"MiG-15_DIF_RoughMet",true}; {"MiG-15_MAIN_N_N_f3", 13 ,"MiG-15_DIF_RoughMet",true}; {"MiG-15_MAIN_N_N_f3_R", 13 ,"MiG-15_DIF_RoughMet",true}; {"MiG-15_MAIN_N_N_N_f3", 13 ,"MiG-15_DIF_RoughMet",true}; {"MiG-15_MAIN_N_N_N_f3_R", 13 ,"MiG-15_DIF_RoughMet",true}; At the end of the lines of textures from description.lua of skin you are trying to fix. just before the name and countries and inside the {} from the list of textures. ACTUALLY after some more testing I couldn't manage to make it work with the above code that sends the game to load the texture already inside an archive that comes with the module so I managed to make it work only after taking out that file from that archive and place it inside the folder of the skin I correct and add the code you can see bellow!! The address of the file is this: \DCS World\CoreMods\aircraft\MiG-15bis\Textures\MiG-15bis.zip Inside you find: MiG-15_DIF_RoughMet.dds If you want to use this one or one of your own roughmet texture then place it in the livery folder you are working on (and replace the MiG-15_bis_DIF_RoughMet with what is called yours) and add at the end false instead of true because the texture is not a default one already loaded. example with a texture placed inside the skin folder you are editing/correcting: {"MiG-15_MAIN", 13 ,"MiG-15_DIF_RoughMet",false}; {"MiG-15_MAIN_N", 13 ,"MiG-15_DIF_RoughMet",false}; {"MiG-15_MAIN_N_R", 13 ,"MiG-15_DIF_RoughMet",false}; {"MiG-15_MAIN_N_N", 13 ,"MiG-15_DIF_RoughMet",false}; {"MiG-15_MAIN_N_N_R", 13 ,"MiG-15_DIF_RoughMet",false}; {"MiG-15_MAIN_N_N_N", 13 ,"MiG-15_DIF_RoughMet",false}; {"MiG-15_MAIN_N_N_N_R", 13 ,"MiG-15_DIF_RoughMet",false}; {"MiG-15_MAIN_N_f3", 13 ,"MiG-15_DIF_RoughMet",false}; {"MiG-15_MAIN_N_f3_R", 13 ,"MiG-15_DIF_RoughMet",false}; {"MiG-15_MAIN_N_N_f3", 13 ,"MiG-15_DIF_RoughMet",false}; {"MiG-15_MAIN_N_N_f3_R", 13 ,"MiG-15_DIF_RoughMet",false}; {"MiG-15_MAIN_N_N_N_f3", 13 ,"MiG-15_DIF_RoughMet",false}; {"MiG-15_MAIN_N_N_N_f3_R", 13 ,"MiG-15_DIF_RoughMet",false};

is the mod compatible with latest open beta? imho the compose.fx file is very different and should be adapted not just replaced with the moded one. Am I wrong?

There is an community roughmet patch that still doesn't fix the problem and also some skins that are made few days ago that look OK on screenshots from author but present the bug once installed in the game. It looks to be a Spec file problem not roughmet. It's either the "MiG-15_SPEC" file which I can't find it anywhere inside the game for some reason or "empty" which is less likely since is usually a generic one pixel texture but is set as decal and has the parameter "true" so is taken from game folder not actual new livery.

So did anyone updated the Compose.fx file?

Maybe they went over the limit or they change the files? Wait a bit.

At least one file is changed: \DCS World\Bazar\shaders\deferred\Compose.fx

here is were you find it now https://cam.em-key.de/

I thought is to set the drop not to be all at once but in ripples.