sleighzy

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.

Same as above. No crash shown in the log. Still contains those other items. No DxDiag so can't confirm the Windows side. Are you able to replicate this on other servers, in case an issue with something on this server (not sure why'd it'd appear to crash as Windows "killing" it), or single player at all?

I've run your DCS log file through the DCS log analyzer which has identified a couple of issues you should attend to. It also indicated you do have mods in there. Note, one of the folk who runs some DCS support has also informed me that the MB-339 has been broken for almost 3 years. Memory Timing Issues Remove any overclocking (XMP) from your RAM. Some GPU cards come with a factory overclock, you can use MSI Afterburner to verify if this is the case. Bluescreen Your system crashes with Bluescreens. Remove any overclocking. Run SFC and DISM to check your Windows. Custom mod error Error '=' expected near '-' Line 6 Script C:\Users\Clemens Klömpken\Saved Games\DCS.openbeta\Mods/tech/V... (note that this is truncated in the logs so does not have the full name, but you definitely still have some mods in there Your DCS has crashed The crash occurred inside KERNELBASE.dll. Remove your custom mods. Try a slow repair of the game. Delete Saved Games\DCS.openbeta\fxo and metashaders2 and try again. Next, delete %LOCALAPPDATA%\TEMP\DCS.openbeta and try again. Next, try renaming Saved Games\DCS.openbeta to DCS.old and try again.

I double-checked the release now and there is a folder in there named VoiceAttack Plugin you can rename that folder to WhisperAttackServerCommand to match the README instructions before putting it in the VoiceAttack Apps folder. We can rename that in a subsequent release to match the docs. You can jump into the VR4DCS Discord server as well. The #vaicom-voiceattack channel in there is where we're hanging out so can get some more timely troubleshooting feedback. https://discord.com/channels/610534461456777257/809527129422430218

This log is when using the SteamVR OpenXR runtime. I've listed the issue below. Would be interested in seeing a similar log when running the Meta OpenXR runtime to see what the root cause is in there as well. VirtualDesktop does actually support hand tracking as well. I've run your log through the DCS log analyzer which has identified this as a GPU error: There is a GPU-related error Remove any overclocking from your GPU. (some GPUs come with a factory overclock if you are not doing this yourself, check with MSI Afterburner) Uninstall your GPU driver with DDU and install a clean one. This can also be seen in your log with the spammed DXGI_ERROR_DEVICE_REMOVED errors. See the article below on this as well. Errors or Crashes on startup or gameplay of DCS World Looking at your log I see you also have a dxgi.dll file in the DCS\bin directory. I know of only two reasons why you would have put that there, it does not come with the game, and that has also been known to cause crashes. Remove that as well. Additional performance tuning items, note that SSAO and SSLR are performance hits with little benefit. Turn off SSAO. Turn off Depth of Field. Disable civil traffic. Turn off SSLR. EDIT: Realise this is for a completely different problem. @PatMcKrotch , if problems persist after this then raise a new post vs. piggy-backing off this one.

That’s fine, just leave that Window open and you’ll see the transcriptions of your recorded voice logged there.

I see you have the SU-30 mod which has been known to cause issues, recommend removing that and running a slow repair of the game (Verify Files for Steam). I've run the logs through the DCS log analyzer which indicates that this was due to a memory timing issue. Remove any overclocking, e.g. XMP profiles, from your RAM. null You should also add a custom page file on your fastest SSD, removing any existing ones, e.g. system managed. Set the Initial and Max values to 32768, click Set, Apply, and restart your PC. Your preload radius is also maxed out at 150000. This will be loading a lot of redundant stuff into your RAM. Drop this down to 60000. Some additional performance tuning items. Up to you if you choose to change them. SSAO and SSLR in particular can be a performance hit with little benefit. Turn down Anisotropic Filtering. Set Shadows to Medium. Disable civil traffic. Turn off SSAO. Decrease Visib Range to Ultra or lower. Decrease Terrain Textures. Set Clouds to High. Turn off SSLR. Set Water to Low.

Your DCS logs don't appear to contain crashes, which is normally indicative that Windows itself is killing the process. Looking at the DxDiag reports however they contain numerous BlueScreen events with an error code of c0000005 and 3b. Based on a quick internet search it would appear that this is potentially related to RAM issues. Can you remove any overclocking you have on your RAM. Can you also run a memory test, this link contains some info on how to do so using the standard windows tools How to Test Your Computer's RAM for Problems There are also a few errors in the logs, appear to be possibly unrelated, but run a slow repair of the game and delete your C:\Users\username\Saved Games\DCS\fxo and metashaders2 folders. You don't appear to have any mods other than Tacview and SRS but try without those as well. Some additional feedback, some from the DCS log analyzer. Your preload radius is really high at the max of 150000. Drop that back to 60000 as you're loading a bunch of stuff into RAM which may be redundant. Consider using DLAA. Turn off SSLR. Turn off SSAO. Disable civil traffic. Disable Game Mode Disable Hardware accelerated GPU scheduling Disable Core Isolation

Raise a new post and attach your DCS log to that after replicating this again. Folk can have a look into reasons why and help troubleshoot.

Believe you, or may have been somebody else asking the same question, in the Eagle Dynamic Discord server. This was the response:

Are you still using the OpenXR Toolkit? If so then disable it. It doesn't work with PimaxPlay Quad Views as the OpenXR Toolkit expects 2 views, but will be getting 4. EDIT: I see you've said you've uninstalled the OpenXR Toolkit, worth double checking though as this was definitely a cause of black screens based on your description. You can also install https://github.com/fredemmott/OpenXR-API-Layers-GUI to see if it's still there, or are any other API layers that could be causing problems. If the game is crashing then create a new post along with your DCS log file as that is unrelated to this post.

You can use Nvidia Profile Inspector (the Orbmu2k one) and then in the Other section set Enable DLSS-SR Override to 1 and Override DLSS-SR presets to 0x000000A for J or 0xFFFFFFF for latest (preset K). This means you don't need to swap dlls as it will use the one from the driver. If you want to use OVGMe then in the folder you currently keep your mods for this create a DLSSTweaks folder, and then a bin and bin-mt folder under that. Put the dlls in that folder. When you enable the mod it'll put them in the right folder, basically it overwrites stuff based on the same folder structure as the core games folders. DLSS Swapper is also really easy for this and you can download and switch dlss versions without manually copying stuff. If you followed that video you would have created a new registry key that turned that text (the hud overlay) on. Just remove the registry key again.

Unfortunately not. Trial and error process of putting them back in to see which one is problematic. Given this doesn't occur with Standalone then I'm assuming not the case. What's the DCS FILMING template that requires Steam? I've used Xbox controllers in the past using Tuuvas's profiles (without Steam). I know Steam was required for PS controllers as their triggers don't work properly for rudders unless you use Steam, unlike Xbox controllers. I also noticed that neither of the Steam logs show an actual game crash, which would insinuate that Windows itself may be killing this process. What is your actual experience when it crashes, what do you see? Can you run the Windows DxDiag tool, save the report from that, and also attach here. Do you get a full dcs.log-<datetime stamp>.zip file created for any of these crashes? Drop here as well if it does. For the DCS log analyzer you can take your log files and drop them into the #dcs-log-analyzer channel in the Eagle Dynamics Discord server. The bot there will give immediate output so you can get feedback.

Super interesting. How does this differ from say disabling hotplug devices in the DCS controls settings?