tomeye

Try this command from PowerShell to check the applied policy, what is the output? Get-ExecutionPolicy

There is a reshade preset on the first post, does this work?

Do you receive the error for a specific texture or every time? An idea that comes to my mind is that it could be an issue that it cannot read the texture size or name of a specific file.

Sharing a thought, the script creates a temp folder in the location you execute. It unzips and processes the files there. It might be on a different drive from where you have DCS installed. Also when you receive the out of memory error, did you check the free space on your drives?

Thanks! I am also using nirsoft tools like soundvolumeview.exe to set volume for bass shakers.

@speed-of-heat do you mind sharing the complete script? I have a similar solution where I start DCS updater, Voice attack when I power my g2 through event log monitoring. But I am keen into starting VA only with DCS launch and kill afterwards.

On a similar thread

You should only use the mod folder and install in DCS folder (not saved games). Using a mod manager you will backup and overwrite files to make it easy to reinstall after updating.

Both mods offer the same result, reduced texture size which affects the VRAM usage. The PowerShell script is a manual/adhoc method that anybody can apply without waiting for others to reduce textures and upload.

yes it's get cleared at the end of the conversion Remove-Item (Join-Path $tempPath -ChildPath "*") -Recurse Remove-Item (Join-Path $tempPath -ChildPath "*") -Recurse

Default policy is RemoteSigned which could explain your error

do you mind sharing the customization?

Comparing size of textures zip indicates the problem. After running the script we have: Mods\aircraft\AH-64D\Cockpit\Textures\AH-64D-CPT-TEXTURES.zip 490Mbytes Mods\aircraft\CH-47F\Cockpit\Textures\Cockpit_CH-47F_Textures.zip 1.6Gbytes Chinook is 3x times larger!

I am using 3080ti (12GB VRAM) and I have similar experience with Chinook textures even using this script. Changed configuration to medium textures and Chinook is playable but Huey looks blurry.

The powershell script reduces textures size for those already provided by Taz and includes other modules too. I think you only need the Powershell script.

VR user (g2) and I can see no NVRAM benefit too, with 3080Ti I still have to use medium textures for heavy/new modules (ch47, ah64, etc.). OpenXR toolkit provides very useful statistics in CPU/GPU/NVRAM usage and you can see NVRAM 100%+ causes shuttering. The F10 issue seemingly is affecting more people now.

ED in the next update said they will bring enhancements related to VRAM usage which in most cases it's responsible for shuttering. Let's see how much it will help.

Override the graphic settings and apply medium textures for the heavy modules.

Do you think we could automate this per module?

I wonder how these presets work and modify textures size on the fly and eventually affect VRAM usage? This must be working on a different way than the script because they apply immediately.

Apologies if my question is not strictly related to thread but does anyone knows how ED uses high/medium textures in graphic options? I am asking this because when I set to medium all new aircrafts (ah-64, ch-47) utilize less VRAM. My idea is to set medium for those while keep high for old modules (uh-1h, mi-8) which do not consume VRAM.

Servers are fully restored, I can see my old stats.

Thanks for that! I had an idea, have you considered an option on the GUI to allow addition or duplication of existing to a custom named aicraft/heli? This could help with mods or interim time between updates.

tbh I have been using the above mode for very long time which means I would not have noticed the difference in loading times. Even with additional load times, the VRAM stays below 100% which makes every module flyable with VR and my setup.