sleighzy

You must still have lines in your export.lua file and the script for this in the Scripts\Hooks directory as Tacview is still present based on what is in your log file. As to the extent of what it is doing I'm not sure, but you should probably clean that up as well to make sure it's not exporting stuff etc. 2025-02-28 22:33:31.387 INFO TACVIEW.EXPORT.LUA (Main): Starting [C:\Users\Deckard\Saved Games\DCS\Scripts/TacviewGameExport.lua] 2025-02-28 22:33:31.387 INFO TACVIEW.EXPORT.LUA (Main): Loading C++ flight data recorder from [C:\Users\Deckard\Saved Games\DCS\Mods\tech\Tacview\bin\] 2025-02-28 22:33:31.396 INFO TACVIEW.EXPORT.LUA (Main): Tacview 1.9.4.200 C++ flight data recorder successfully loaded. Glad to hear the nod towards MSI Afterburner helped a little there as well

@jnr4817 I see you also have the web editor moving map in your logs. This is also another export. There is a new feature released a couple of days ago whereby in the browser view you can click a button to have it refresh units every few secs/mins/never, vs. constantly. This can also help reduce performance issues and stutters etc. Same applies to tacview which you're running. You could uninstall that as that will also be hitting performance. Note, not saying that this will help the CPU pegging, just general observations from your log for other performance issues.

Possibly part of your problem, has been for at least one other person who was also crashing with putting the dlls in DCS. You don’t need to copy the dlls into DCS when you use Nvidia Profile Inspector, it will use the dll that ships with the driver and will ignore the one in the DCS folder. Put the original dll files back and try again. You may need to run a repair of the game to get them back if you don’t have them anymore. If it crashes again then attach your log file and we can see why.

If you’re referring to DCS then NVPI shouldn’t cause that crash, it’s just for providing config. Like I said earlier, no way to tell without a DCS log after a crash. Raise that as a separate post as is a different topic. I’d recommend just use DDU to remove the driver and Nvidia app and reinstall the driver and start again. And just to confirm, you aren’t copying any dll files into DCS aye? Cos that can cause crashes.

Why? We mentioned that Nvidia App causes issues....

DLSSTweaks needs it to be called dxgi.dll due to a DCS patch ages ago, it’s a known issue for awhile now. Just do what @Qcumber said and just use Nvidia Profile Inspector, there is no need for copying any dlls into DCS.

Correct. I generally just advise a nice UI so people aren’t hacking the registry (that’s sometimes where the “fun” begins).

Install the latest Nvidia driver (don't install the Nvidia app) Install the latest Nvidia Profile Inspector (https://github.com/Orbmu2k/nvidiaProfileInspector) Select the Digital Combat Simulator: Black Shark profile in the dropdown and then in the Common section enable DLSS - Enable DLL Override and set the DLSS - Forced Preset Letter to Always use latest (the latest is K, so try that and J which are the most common at the moment to see which one you prefer) To tell if it's working (although you should see a notable difference anyway): Download and unpack DLSSTweaks (https://www.nexusmods.com/site/mods/550) No need to copy any files into DCS, just run the DLSSTweaksConfig.exe file At the bottom of it set the GlobalHudOverride to Enable (All DLLs) and then click Save Start DCS and jump in a plane. Some people say they only see it in 2D but there should be a hud overlay at the bottom left of the screen. Verify the DLSS version, starts with 310., and that the preset is K or J (whatever you chose to use). If you install a newer Nvidia driver later confirm in NVPI that it kept your settings, you may need to reapply them again.

I've run your log through the DCS log analyser, notes below. You mentioned you disabled hotplug scanning however the DCS log shows that this is still enabled. This can lead to stutters so turn that off. I'd also recommend uninstalling TacView completely, i.e. the hooks and exports, as this will also be taxing on your system. MSI Afterburner is also known to cause issues, are you using this for something specially, e.g. overclocking? Uninstall it. (I'd have to locate the info but if being used for overclocks then there is a way to run it for that without introducing the other problems...) Some additional performance tuning tips it called out. Tuning Tips Set Shadows to Medium. Set Clouds to High. Set Water to Low. Consider using DLAA. Decrease Terrain Textures. Turn down Anisotropic Filtering.

2x32 is generally recommended. Can be faster, and also prevents memory timing issues that crash DCS due to memory overclocking, XMP/EXPO profiles.

We are looking to release a 1.0.0 version in the near future. There is a WhisperAttack v1.0.0-alpha.3.zip (or later as we release more alpha versions) file located here: https://drive.google.com/drive/folders/1z-a-dgxeQS6Aj_jNq2mhuZNBfFwbaoNP?usp=sharing for folk to start using this now before final release. You can download and unpack that to any location, e.g. C:\Program Files\WhisperAttack, and run the WhisperAttack.exe file (can create a shortcut to that). Notable features in this release: A new window is now displayed that shows startup information, the text that was transcribed from your voice, and the text sent to VoiceAttack (or DCS only if the sentence starts with "Note"). This window can be closed and WhisperAttack will keep running. The window can be opened again from the menu in the system tray icon. WhisperAttack runs in the background, with an icon in the system tray to open the WhisperAttack window or exit. Multiple word replacements can be put on a single line in the word_mappings.txt file, separated by semi-colons. For example, gulf;gold=Golf Python and ffmpeg do not need to be installed Note: This requires CUDA 12. WhisperAttack ships with this runtime and libraries. If you however see an error stating that the cublas64_12.dll library couldn’t be found you will need to install the CUDA 12 Toolkit. Only the CUDA > Runtime > Libraries need to be selected from the installer if presented with a list of components in the installer: CUDA Toolkit 12.8 Downloads | NVIDIA Developer Please let us know if you see this and we'll have a look into it. The README.md (nikoelt/WhisperAttack at build-whisper-server-executable) contains more information (I need to convert this to a proper PDF instruction document for the final release so apologies in advance) Please try this out, let us know if you encounter any issues or suggested features, and look forward to the upcoming final v1.0.0 release. A VAICOM PRO folder is also on the Google drive and contains a VoiceAttack profile for Vaicom users. Vaicom Pro 3.0.0 was released recently and their exported key words are now in the same format we use so you can export those from your Vaicom database and update this VoiceAttack profile with those. Dark mode in the pipeline for a later release for those that enjoy that.

They’ve said they’ll look at it after Vulkan.

Restart your PC in case the process is already running. Add an exclusion in your anti-virus software, e.g. Windows Defender, for the entire DCS installation folder, and then restart your PC.

Without your DCS log file after a crash there's no way to tell the cause.

People having numerous problems with the new Nvidia app in general. Based on feedback I'd avoid it at this stage. You need it for anything specifically?

Router is the way to go for official support, or if Meta change anything that prevents the steps in the below guide from working. It may be enough just to use a usb-c to ethernet adapter for VirtualDesktop and Quest 3 (it does for some folk), however if you need the extra steps to get it working (note that these may only be needed for a Quest Pro ) then you can try them here:

Can try putting tape over the sensor as well. A few people do that to stop it sleeping for that very reason (although in your case it hasn’t actually gone to sleep).

If you haven't already then also add an exclusion in your anti-virus software, e.g. Windows Defender, to exclude the entire DCS installation folder. This can speed things up as won't be scanning everything downloaded and unpacked.

You mean the Nvidia nvngx_dlss.dll file (and others)? Nowhere. With the NVPI config change to enable the override and set the preset it will automatically use the DLSS version that ships with the driver. The one in DCS is ignored. So no dlls need to be put anywhere.

If you followed the steps to rename "DCS.openbeta" to "DCS.openbeta_old" then the "DCS.openbeta_old/Config/Input" folder contains all your bindings. Just copy that folder back to DCS.openbeta to get them back again.

This is expected and can be ignored. It just lists other API layers you have installed so you’re aware of them in case of problems. Nothing to worry about, we all get this. You maybe shouldn’t have done it the way you did though as there are registry keys associated with these two. In future, and if you experience problems, use the https://github.com/fredemmott/OpenXR-API-Layers-GUI tool to disable those layers. Hopefully you still have those in case you need to put them back in those directories again.

If using NVPI like you mention you don’t need to copy any dlls in. Does it still work fine if you don’t copy/replace those dlls in DCS?

Using a second GPU for this is not something we've looked at. Our default model is small.en however you can update your settings.cfg and change this to use smaller models which will use less VRAM, e.g. tiny.en whisper_model=tiny.en

You can't. Use DLSSTweaks. Select Enable (All DLLs) from the ForceOverrideHud drop down.

You can use VAICOM PRO a plug-in for VoiceAttack for this.