sleighzy

You can only have one runtime set to be the default OpenXR runtime. It sounds like you have Mbucchia's PimaxXR installed as well as the PimaxPlay one. This is fine, however, go into Mbucchias' PimaxXR app and check to see if you have the SteamVR option selected in there. This may be why it is attempting to use that runtime (which doesn't exist as you aren't using SteamVR). Change that to instead be PimaxXR and restart your PC. That same error is in your dcs.log file so it's definitely trying to use a non-existent runtime: 2025-02-15 16:17:02.603 ERROR VISUALIZER (Main): OpenXR failure XrResult failure [XR_ERROR_RUNTIME_UNAVAILABLE] Origin: xrEnumerateInstanceExtensionProperties(nullptr, 0, &instanceExtensionCount, nullptr) Source: Projects\Visualizer\Source\OpenXR\openxr_program.cpp:225 null

First DCS Forum post on this I've seen. Looks like he's put this warning on all his other repos as well. https://github.com/mbucchia/Quad-Views-Foveated/blob/main/README.md https://github.com/mbucchia/OpenXR-Toolkit/blob/main/README.md

The one on your left hand controller that makes the VD menu slide out when you're not in VR.

DLSS Swapper not needed, the Nvidia Profile Inspector settings will force it to use the one in the driver and not the one in DCS. You can either choose _GLOBAL profile, or if just for DCS then the profile is named “Digital Combat Simulator: Black Shark”.

DCS.exe doesn't show for me either, like you said it's the Black Shark one. You can just use _GLOBAL and will apply to everything. Check if you're on the latest 2.4.0.11 release. I believe in previous releases these options were DLSS-SR Override and DLSS-SR Preset (0x000FFFF is latest and 0x000000A is J if it gives you hex values). It may still appear like that.

J and K are both available in the dropdown so you can select J if you like. Latest just defaults to K currently.

For folk wanting to use the executable version of Whisper Attack you may encounter an error stating that the cublas64_12.dll library couldn’t be found. This should be using CUDA 11 (and comes with it) but appears it’s looking for CUDA 12. If you do hit this then install the CUDA 12 Toolkit https://developer.nvidia.com/cuda-downloads

Yes.

Yeah, Python 3.11 is what we have documented on the README due to that issue (its for PyTorch).

Do you have more recent logs than the ones originally posted? The below is based on those logs. Errors Memory Timing Issues Remove any overclocking (XMP) from your RAM. Config File Corruption Delete Saved Games\DCS\MissionEditor and try again. Your System ran out of Memory Your Preload Radius in DCS is currently set at 133500 which extremely high for your RAM, and you're loading a lot of redundant stuff into RAM. Reduce this to 60000 Your page file is too small. Set the custom page file (one only) with an Initial and Max values of 32768, click Set, Apply, and restart your PC In Windows: Disable Game Mode Disable Hardware accelerated GPU scheduling (this may also fix the issue with the laggy browsing) Tuning Advice: Note that SSAO and SSLR are a performance hit with no real benefit. Turn off SSLR. Enable Full Screen mode. Turn off SSAO. Set Water to Medium or Low. Consider using TAA instead of MSAA. Turn down Anisotropic Filtering. You also mentioned lagging with the mouse. There had been a preexisting issue, some people have mentioned it still effects them, with this. Using your mouse software drop your polling rate below 1000 (this is polling rate and not DPI). Choose something like 500 and see how you get on.

These are the two options to change in the latest Nvidia Profile Inspector: null

If you still want it I believe there is a fixed version of that mod now.

Randomly saw this forum comment get posted a few hours ago re: hyper threading on the same CPU as you. Might be worth a shot (shrug)

Yes please, primarily because I don't know what Python completely cleans up when uninstalled. You may still need it if needing to use and troubleshoot with the Python version as well. You can uninstall it again once we sort out the issues and the executable version is working perfectly for you. Feel free to jump into our Discord server as well for a bit of back'n'forwards if you like. We can post an update as to the resolution here. https://discord.com/channels/610534461456777257/809527129422430218

Can you run the below commands, run each of them separately, agree to any messages which ask you if you wish to remove packages. It's fine if it doesn't locate a package, this is expected, but let me know which ones it doesn't find. The last command will then install a different version of torch (it's possible in one of the earlier versions of WhisperAttack that it installed an incorrect version. Then try both the executable and the Python version to see if this makes a difference. pip uninstall torch pip uninstall whisper pip uninstall openai-whisper pip install torch --index-url https://download.pytorch.org/whl/cu118

Hmmm, sounds vaguely familiar, let me double-check. Can you attach your full log please. Is this the first time using it, i.e. you hadn't tried the previous version (which I've removed from that Google drive but still have on hand). And to confirm, you haven't run any of the previous Python versions of this previously, i.e. the non-executable ones? Or is this the Python one?

This is how the options appear for me now, a little more user friendly: null

I've uploaded a new version of the v0.4.1-beta executable. You will need the full contents when unzipping it. It can be found in the same location, https://drive.google.com/drive/folders/1z-a-dgxeQS6Aj_jNq2mhuZNBfFwbaoNP?usp=sharing This still has the system tray icon, but also has a console window (closing this will also stop WhisperAttack) so you can the model being loaded and any fatal errors. All other logging, e.g. transcribed text, will still go to the log file and not the console window.

Raise a new forum post, these issues are unrelated to the current topic. The latest crash is the same as the last one, i.e. GPU issue. This is also seen with the LiveKernelEvent errors with code 141 in your DxDiag report. Based on your comment above it doesn't sound like you've followed the steps to address it yet. The latest log also shows that hotplugging has been enabled in the DCS controls settings (wasn't present in the earlier one). Disable that as well as it can cause stutters as it polls for new devices.

There's an executable version of this available here. https://drive.google.com/drive/folders/1z-a-dgxeQS6Aj_jNq2mhuZNBfFwbaoNP?usp=sharing This does not require you to install Python or ffmpeg. Download and unzip the file. Put the contents in the folder of your choice, e.g. C:\Program Files\WhisperAttack, just make sure they're all together. You can create a shortcut to the WhisperAttack.exe file. When you run this it will run in the background and put an icon in your system tray. You can right-click on that to exit it. Closing VoiceAttack will also exit it automatically. Logs will get written to C:\Users\username\AppData\Local\WhisperAttack\WhisperAttack.log , you may need to open and close the log file if your text editor does not auto-refresh it. First load may take a little bit as it downloads the Whisper model. Let us know how you get on with it and if you encounter any issues. This executable application will be our way going forward in the near future. null

You haven't described what the actual problem is. If it's an audio input issue; Is your PC picking up any audio input from your mic? There's settings in VD for the audio device to use, might want to check that everything is aligned with the VD settings + PC audio input device + SRS input audio.

Sounds like a similar experience I may have (if I'm reading this right). If you double click the Oculus menu button to bounce you back to the desktop, click the button to slide out the VD menu, and then double click to jump back into VR again does this workaround around it? IIRC the cause was due to the encoder/bitrate being used, I'd need to find the direct reference to this on the VD Discord.

Yup, that’s the one. The ways of doing this evolved rapidly over the days as the tools got heaps better in a very short space of time, so yeah you’re right about the changes between pages 1 through 7.

Eagle Dynamics have said they're not planning on anything in that area until after Vulcan support. Not sure what all the hacks are that you've been doing, it's just updating two fields in Nvidia Profile Inspector.

Log is spammed with DXGI_ERROR_DEVICE_REMOVED errors. Generally a GPU issue of some description. Dropped your log into the DCS log analyzer which verified the same. There is a GPU-related error Remove any overclocking from your GPU. Some GPUs may come with a factory overclock, you can confirm whether or not this is the case with MSI Afterburner Uninstall your GPU driver with DDU and install a clean one. See also this DCS FAQ article on it: https://www.digitalcombatsimulator.com/en/support/faq/startup/#3312253 You also have a dxgi.dll file in the DCS bin folder. I'm aware of only two reason why this would be placed there, this does not ship with the game. Remove that as well as it has been known to cause crashes. It may be fine if you resolve the other GPU issue, however I would recommend trying that. Some additional tuning advice. The SSAO and SSLR are a performance hit with little benefit. Turn off SSAO. Turn off Depth of Field. Disable civil traffic. Turn off SSLR. I see you also have the VirtualDesktop API layer, any reason you're not using that vs. SteamLink? Will be more performant and less VRAM overhead than that introduced by SteamVR.