lefuneste01

Haze control is working OK for me with No MSAA or MSAA2x with the last patch...

I checked with the previous one it was OK, I'll do it again. But they are planning a new patch...

Thanks for your answer. I'll will for sure purchase the red flag, at least to help people like you continuing doing campaign as you are doing. I do not know when I'll finish the mig killer, but I'm sure I won't be disapointed by moving to the red flag later. I just did not see the bingo cell in the kneeboard...my bad again. 2 lessons in a same mission ! Take care of fuel jauge and read extensivelly kneeboards...

Just to test, I asked chatGPT a fuel planning for your flight plan (dist. + altitude) : Phase Distance / Time Altitude Speed (TAS) Fuel Used (lbs) Notes Startup & Taxi ~5 min Ground — ~150 Idle + taxi Takeoff & Climb ~5 min To FL200 Climb profile ~550 May include short AB burst Enroute to AO ~80 nm / ~11 min 20–14k ft 430–415 KTAS ~1,300 Cruise at 85% RPM Combat Allowance Variable AO Altitude Flexible ~6,000 available Includes AB, loiter, maneuvering RTB (Return Leg) ~90 nm / ~13 min 14k–4.6k ft 415 → 390 KTAS ~1,700 Descent included Approach & Land ~5–7 min 4k → 0 ft Pattern speed ~500 Includes approach and taxi Reserve on Landing N/A Ground — 2,000 (required) Safety buffer — min fuel at shutdown I'll see when I'll fly the mission...What do you think about it ?

Hello, I started this campaign and are quite happy with it, even if I did only the fam. flight for the moment. I specially like efforts made to align the simulation and real life processes, plus all the interaction and voices. It seems to me I'll be able to learn a lot in the way to flight the F4E thanks to your work. But there is a "blind spot" in briefing and flight plan. We have the headings, alt,.. but not the speed and so time on waypoint or time to travel. I'm used to have campaing/mission having globally enough fuel to do what you have to do, so I did not care too much, but I ended my first fam. flight out of fuel in middle of nowhere...I was not aware of the fuel consumption of the F4E in afterburner, not displayed in fuel flow counters and I did not care too much on monitoring fuel quantity before reaching alert levels...Good lesson to learn the F4E, you may say I did again the mission by using low speeds/fuel flow for travelling and limiting the number of manoeuvers to 1 of each, to avoid to be again out of fuel. But now I'm wondering what will be the situation for next mission, as there are different manoeuvers to do, and so at least mil. power or more during them...It should be good to have elements in flight plan (speed ?) to ensure people will come on manoeuver area with the expected fuel level, as to provide a "bingo" fuel ensuring capacity to come back to airbase: if you did not achieve all the objectives and reach in bingo, you'll know you will have to restart mission... I search in campaign doc. some elements on assumed cruise parameter but did not find them... More globally, fuel management is a crutial topic for mission planning, I'm sure you did it to ensure feasability of your campaign, so it should be great to have some fuel elements somewhere in the briefing or kneeboards, to help noobs like me...It may help also by ginving example to plan later mission, even outside your campaign. Maybe something like this (coming from F4manual) ?

What are your fps ? If you are not at the frequency of the VR display you will have stutters, especially when looking sideway. Did you try reprojection/smart smoothing ? Did you try with low settings ? there is no HW that will provide 90 Hz with insane settings. Some people are stacking supersmapling, MSAA, DCS settings to increase VR resolution and so saturate their hardware. The rule : try with the lowest settings, if no stutter increase settings to try to improve rendering but keep things smooth. 72 Hz is a good compromise to increase settings and keep native frequency. Too bad you did not like it. Exporting MFD was impacting fps when I used it in the past. You should setup a DCS config for VR only. And use Quad view if you can.

Could you just activate "debug message in log" in "debug options", restart game, go to AH64 cockpit (without "technique in VR"), save reshade.log file somewhere, do the same with "technique in VR" activated and post both reshade.log here ?

Could you explain more in detail what was creating your issue and how you get out of it ? Are you able to use VREM technique ?

This feature is a must have for these campaigns. It would be a game changer, by allowing more complex missions. It should enable people not having too much time playing these campaign without the current frustration, and so purchase more of them. Personally, this will be the only context I could use it... When would it be available ?

2025/03/18 for DCS version DCS DCS 2.9.13.6818.2 => version 8.1 option to disable effect for 2D and keep them for VR only restored. Small optimization for techniques.

In the folder where DCS.exe is : could you : rename reshade DCS VREM.addon64 into reshade DCS VREM.addon64.bak, unzip shaderhunter.zip in the folder (it should create ShaderHunter.addon64), launch the game, go to cockpit, press F1 and share the reshade.log here ? (it will be huge). ShaderHunter.zip As you are Pimax user, could you report here if everything is working as expected , especially for haze control ? PawlaczGMD is also Pimax user and he has some strange issue with shaders. I'd like to be sure this is not something related to Pimax (even if he has issue in 2D too).

Not really. You should just install it for the version you are using. But it may be tricks to know which folder is used if you did not setup dcs shortcuts...

You should not have installed reshade with addon support as explained in the first post. check at first all things in 2D.

Reshade technique are not changing game shaders. Just in case of, could you try to do a full repair of the game ? What are your graphics driver settings (nvidia) ?

Haze in 2D is working on my machine with your .ini file. The "haze" shader is identified at the beginning of game session but not in the cockpit view...It should ! So something is making it different, I can not define what. Did you have some mods installed ?

Could you try with this version (unzip the file in the directory where DCS.exe is, it should replace addon.exe. If this is not working, lauch game, in welcome screen activate reshade menu, go to addon/debug option tick "debug message in log...", restart game, launch 3D session, kill the game when it would block, send the reshade.log here. reshade DCS VREM.zip

So if Dehaze is not working in 2D, it should not be linked to Pimax, but to something with your configuration, maybe...Dehaze is based on "global illumination" shader that I modified, for non AA and MSAA2x. This is the most "fragile" item, as some settings are changing the shader and I do not want to handle all configuration. Do you have any DCS mod installed ? What you can do anyway is to activate the debug feature, save mod option, restart game and once in cockpit press the "capture frame" in debug section, then quit game. It will generate a huge reshade.log file (in the same directory than dcs.exe) that you should share with me. So I'll be able to verify what are the shaders identified or not. Could you also post the file DCS_VREM.ini that is in the same place than reshade.log ?

Everything is working on my DCS install with your settings, especially the haze control. Could you try in 2D : just try haze control, as it is not working in VR for you. Most of features are working both in 2D or VR (same for color control, but "techniques in VR" of course are not working in 2D). Ensure you did not install Reshade wtih any OpenXR or VR support option.

Did you install the last version of reshade with add on support ?

Using Pimax should not change any game shader. You may have to restart game if you change AA, otherwise texture size are not updated. Can you put your option.lua here ?

You are not using the good settings. Please check the screen copy of setting in the first post. It should not. Please fix the problem above first, maybe I need to do some check in case of invalid configuration... Which effect did you select for VR ?

It should work with any VR helmet, as the mod act in DCS directX rendering and not in the VR layer after. If you have issue, check it is well installed and ensure you are using compliant graphic settings.

hello, I have the same issue with the remaining Mi26...Indestructible...I switch to next objective, after a while there were message saying it has been destroyed...

2025/02/22 for DCS version DCS 2.9.13.6818 => version 8.0 support of 2.9.13.6818 remove reshade unoficial library as the 6.4.0 with support for thecnique injection has been released bug fixes (technique injection for MSAA2x,..) change default key mapping to avoid overlap with modules remove option to disable effect for 2D and keep them for VR only as it is making game crashing It is best to re install the latest reshade version.

There was a bug with the key I added to toggle on/off technique (it was ALT+V instead ALT+F5). It is fixed now in the version available.