speed-of-heat

Also just having two drives doesn't mitigate against the failure of one of them unless you are mirroring them...

ah the joys of a well spent youth ... they are similar to the thrustmasters in the version i have, as i fly in VR 99% of the time, so no video displays, but you can buy the video displays if you wish, but for VR it makes no sense. A couple of differences firstly they are slightly bigger than the TM's and secondly they have more buttons/axis, what is not obvious is that the seperators between the buttons are also buttons, so that's another 16 buttons, which i use a surprising amount, on the Apache, F-5E, the Tomcat, and the even the Viper , though that is mostly the lower MFD for startup functions they are just really useful button boxes!

null

the only thing i can think of that it will be less efficient in some scenarios, so when page file is being used at the same time as game disk i/o or operating system functions etc... that said with that sort of M2 drive, would you notice the difference ... i assume not. from a cost perspective though you might be better going with multiple separate drives (though just glancing at the prices that seems to be very brand dependent) other than that the only other thing i can think of is any game in which rebar is actually used... but thats a theoretical in the context of DCS

Honestly, go with the most buttons you can afford, you will use them....

Thank you @SkateZilla!

Doh! Thank you!

Is there meant to be a difference in game effects between Position 1 and 2 (other than the physical switch position) ... ?

yeah you missed out some directories to clear: # ============================================== # NAME # Cache Cleaner # # AUTHOR # VS / vslash.com # ---------------------------------------------- # CHANGELOG # 2025/01: Init # 2025/02: command prompt to close win # ============================================== #gci env:* | sort-object name #Set-ExecutionPolicy Unrestricted #Get-ChildItem -Path $DP_CACHE -Include *.* -Recurse | foreach { echo "$_" } $DP_CACHE = "$env:LOCALAPPDATA\CrashDumps" $D3_CACHE = "$env:LOCALAPPDATA\D3DSCache" $NV_DXCACHE = "$env:LOCALAPPDATA\NVIDIA\DXCache" $NV_GLCACHE = "$env:LOCALAPPDATA\NVIDIA\GLCache" $NV_LOW_DXCACHE = "$env:HOMEPATH\AppData\LocalLow\NVIDIA\DXCache" $NV_LOW_PDCACHE = "$env:HOMEPATH\AppData\LocalLow\NVIDIA\PerDriverVersion\DXCache" $DCS_FXO = "$env:HOMEPATH\Saved Games\DCS.openbeta\fxo" $DCS_METASHADER = "$env:HOMEPATH\Saved Games\DCS.openbeta\metashaders2" echo "*** D3D/GL Shaders Cache Cleaner ***" echo "------------------------------------" echo "==> Starting" echo "" echo " > INFO : errors like items being used by another process will be silently ignored" echo "" $d = $DP_CACHE if (Test-Path -Path $d) { $count = (gci $d | measure -Line).Lines echo " > Cleaning $d for $count items:" Remove-Item $d\* -Recurse -Force -ErrorAction SilentlyContinue } $d = $D3_CACHE if (Test-Path -Path $d ) { $count = (gci $d | measure -Line).Lines echo " > Cleaning $d for $count items:" Remove-Item $d\* -Recurse -Force -ErrorAction SilentlyContinue } $d = $NV_DXCACHE if (Test-Path -Path $d) { $count = (gci $d | measure -Line).Lines echo " > Cleaning $d for $count items:" Remove-Item $d\* -Recurse -Force -ErrorAction SilentlyContinue } $d = $NV_LOW_DXCACHE if (Test-Path -Path $d) { $count = (gci $d | measure -Line).Lines echo " > Cleaning $d for $count items:" Remove-Item $d\* -Recurse -Force -ErrorAction SilentlyContinue } $d = $NV_LOW_PDCACHE if (Test-Path -Path $d) { $count = (gci $d | measure -Line).Lines echo " > Cleaning $d for $count items:" Remove-Item $d\* -Recurse -Force -ErrorAction SilentlyContinue } $d = $NV_GLCACHE if (Test-Path -Path $d) { $count = (gci $d | measure -Line).Lines echo " > Cleaning $d for $count items:" Remove-Item $d\* -Recurse -Force -ErrorAction SilentlyContinue } $d = $DCS_FXO if (Test-Path -Path $d) { $count = (gci $d | measure -Line).Lines echo " > Cleaning $d for $count items:" Remove-Item $d\* -Recurse -Force } $d = $DCS_METASHADER if (Test-Path -Path $d) { $count = (gci $d | measure -Line).Lines echo " > Cleaning $d for $count items:" Remove-Item $d\* -Recurse -Force } echo "" echo "==> Done" echo "------------------------------------" Read-Host -Prompt "Press Enter to exit" specifically Low PDCache and Low DX Cache and FXO the above script works for DCS openbeta as the install path (just remove .openbeta)

you also need to add the low's in as well you add the environment variables but not the action

I would suggest ,adding in FXO as well to the clean script; nice script by the way. And I would note it relies upon DCS being the target directory, if you still have DCS.openbeta as your install the DCS path needs to be edited by the user

in an absolute sense, yes ghosting to some degree is inherent in the technology... it's just the way it works, improved over what was present in earlier versions, yes, but it will still be there at some level... now for me with Preset K on a 4090 solves most of my issues with ghosting but it is still "there"... i'm no longer looking at a big smear behind the trailing edge of a wing... but every now and again yep its definitely there (the worst offender for me is fences on the ground) .

not natively with DCS's F-16 but you can with the SUFA mod https://discord.com/channels/853709103728820295/1246424444268839015

The latest Nvidia drivers are not always the best, and normally I only update my drivers if there is a significant personal benefit to the games i play as a rule of thumb i watch this thread or its later iterations under performance. That said, I'm not sure the issues you are describing are as a result of the latest full stack driver, rather the DLSS dll within the driver that you can manually add to DCS if you choose to do so, and then make the correct changes via profile inspector or similar to enable the latest profile (K). DLSS does have artefacting and does impact clarity , at least in my experience, however the impact of the 310.2.1 dll is considerably less than that of previous drivers. This also improves clarity/performance of DLAA in a similar way. It does not improve the visual artefacts from not using DLSS or DLAA but significantly reduces them and improves performance for the *SAME* quality level so if you were using preset D before and you continue to use preset D you would see an improvement in performance, if you went from D to K you would see an improvement in quality... maybe a slight drop in perf. The Jelly effect is normally, in my experience, associated with some form of CPU bottle neck when using ASW or similar tech.

honestrly no idea, but try clearing out fxo and metashaders2 from the saved games directory for DCS? Also if you have any mods try it without the mods more for a diagnostic baseline

so i think i asked this question regarding the F-14 when i first got it, and it's sort of meant to feel like that... but if you want to change it then you can edit snapviews.lua's VR setting for the specific aircraft: you may need to fiddle with it to get it right for you , but look for the Default VR view, which is normally number 14)

Map it to joystick button, it. Should un map it from num5 Or hit clear

The G2 supports a limited low resolution greyscale pass through. It’s triggered by saying “flashlight “ and there is an equivalent keyboard command it projects a hole in that shows the outside world , when i used it you couldn’t really see the key labels… but it might be suitable for your use case

Tracks are notoriously fragile across versions...

you are a dev amongst dev's thank you for this!

9800x3d is basically the king of gaming performance right now...

roger that, i'm escorting the strike out... but i go into left hand orbit as BUG calls it out so it could be that

as i understand it you manually move the lenses, they slide in and out...

nope, its happened 3 times now as we start to prosecute the pop-up's i start to get the grid from Bug, and then almost as i have it entered i am saying RTB... as we are BINGO