Jump to content

sleighzy

Members
 View Profile  See their activity

  • Posts

    914

  • Joined

  • Last visited

 Content Type 

Everything posted by sleighzy

  1. sleighzy
    Try adding your entire DCS installation folder as an exclusion in your anti-virus software and then restart your PC. Next run a slow repair of the game and try again.
  2. sleighzy
    The Virtual Desktop desktop has a note regarding AV1 and high bitrates causing decoding/networking/encoding causing issues. null
  3. sleighzy
    Page file should just be on one disk, not multiple. This shouldn't make a difference as it's a GPU issue.
  4. sleighzy
    This is still failing with GPU errors. This is repeated throughout the log (different instances for texture files). 2024-12-11 22:03:03.650 ERROR DX11BACKEND (12976): Failed to create shader resource view for /textures/f16c_cpt_scales.dds. Reason: The GPU device instance has been suspended. Use GetDeviceRemovedReason to determine the appropriate action. 2024-12-11 22:03:03.651 ERROR DX11BACKEND (12976): failed to create structed buffer. Reason: DXGI_ERROR_DEVICE_REMOVED 2024-12-11 22:03:03.651 ERROR DX11BACKEND (12976): CreateShaderResourceView FAILED. Reason: E_INVALIDARG I can't help diagnose this much other than say, DDU drivers and reinstall, check power issues, check GPU. Somebody else may know further reasons. DLAA is also selected from the Anti-Aliasing drop down in the DCS settings.
  5. sleighzy
    Please attach your "C:\Users\username\Saved Games\DCS\Logs\dcs.log" file, it may just be a text document named "dcs" if your Windows is hiding file extensions. Also run the Windows DxDiag tool, save the report, and attach it here as well. Have you also tried removing all your custom mods, running a slow repair of the game (with the remove files option selected), and deleting your "C:\Users\username\Saved Games\DCS\fxo" and "metashaders2" folders and restarting the game?
  6. sleighzy
    Based on this log you have a GPU issue. "failed to create vertex buffer. Reason: DXGI_ERROR_DEVICE_REMOVED" I've dropped you log file into the DCS log analyzer which has the following to say: There is a GPU-related error Remove any overclocking from your GPU. Uninstall your GPU driver with DDU and install a clean one. There is some additional information here on that as well: https://www.digitalcombatsimulator.com/en/support/faq/startup/#3312253 In addition to this: You only have 32Gb of RAM, and a tiny system managed page file. Create a custom page file on your fastest SSD with Initial and Max values of 32768. Make sure you only have one page file on your PC, remove any other system managed ones. Click Set, Apply, and restart your PC. In your DCS controls (where you do your bindings) at the bottom right there is a "Disable Hotplug" button which you can click. Make sure that hot plugging is disabled, this will prevent issues where DCS is constantly scanning for new devices. If you add a new device you can click the "Scan devices" button. Tuning advice: Turn off SSLR. Turn off SSAO. Set Shadows to Medium. Disable civil traffic. Set Water to Medium or Low. Consider using DLAA.
  7. sleighzy
    The one on Steam is years old, and does not support streaming PCVR games. If you’re looking for VD then you need to buy it from the Oculus store in your headset. The VD Streamer app for Windows that this connects to can be downloaded for free from their web site.
  8. sleighzy
    I honestly can't speak to this campaign and any specific issues within it, e.g. heavy amounts of scripting. I do however note your version of DCS is about 7 patches behind. Recommend upgrading as there have been performance improvements since then. Remove your Saved Games\DCS\fxo and metashaders2 folders after upgrading. You could also look at upgrading your GPU driver. I dropped your log into the DCS log analyzer which had some tuning advice: Turn off SSLR. Turn off SSAO. Disable civil traffic. You could drop your preload radius in DCS to 100000 so you're not loading as much of the terrain and textures unnecessarily. Check to make sure you have: Disabled game mode Disabled Hardware GPU scheduling Disabled core isolation Disabled core parking In addition to this you also have Process Lasso running which can cause issues. Have you tried running without this?
  9. sleighzy
    Possibly unrelated, however you're running DCS from the bin-mt directory, which means it won't be updating. You're running a few versions behind (2.9.7.59263). Run the updater and see what happens. Latest version also doesn't need to be run from the bin-mt directory as it is entirely multi-threaded now.
  10. sleighzy
    Multiple reports. Server down for maintenance. From ED News: Master Server Infrastructure Maintenance We will have infrastructure maintenance on Tuesday, December 10th, 2024 from 04:00 to 05:00 UTC. All users will not be able to connect to the DCS Master server and all account sessions will be reset. We appreciate your patience and understanding during this short downtime. Thank you Eagle Dynamics
  11. sleighzy
    Which Pimax Crystal do you have? One of the eye-tracked ones? Making those changes using the Quad Views Companion app?
  12. sleighzy
    If you're going to go with a wireless solution then have a look at Virtual Desktop. Really easy to setup with good results. Recommendation is to have your router (preferably dedicated) plugged into your PC via ethernet and within your play space. There are also USB ethernet adaptors that some folk use.
  13. sleighzy
    Should paste it into bin and bin-mt as DCS now runs entirely multithreaded so shortcuts pointing to bin directory will still run MT so the dll will need to exist there as well for folk using that executable.
  14. sleighzy
    Complicated on first setup, yes. I see it has changed a lot since I used it with my old card, I just used to use the vanilla script there. The improvement is that DCS releases new and modified textures and base files. If you use the Taz optimised ones then they will be out of date with what is used by the core game, so may potentially have unexpected issues, e.g. using older files which have since been replaced. Was just a heads-up in case you see problems and that you should repair the game to get the correct files again.
  15. sleighzy
    Also on Windows 11: Disable game mode Disable Hardware GPU scheduling Disable core isolation Disable core parking
  16. sleighzy
    The horizontal and vertical focal area in the Companion app do not control the fixed horizontal and fixed vertical section values that you will be using in your Quest 3 (the app only supports eye-tracked headsets for those values). By default they are 0.5 and 0.45 unless you modified manually in the settings file.
  17. sleighzy
    Some quick thoughts on your settings: Your headset is at 72 so change your DCS Max FPS to 75 Could drop your preload radius to 100000 (or even lower) so you're not loading a bunch of stuff you don't need Change "Res. of Cockpit Displays" to 1024 to make your MFDs more readable. Performance wise it's a better option, up to you, but I'd flip it so that textures are high and terrain textures are medium. Although in saying that the visual difference in the textures between medium and high in the Apache is next to nothing. EDIT: meh, you're flying low and detail is nice so leave those for now and revisit later if you want to try. Forest visibility is a perf hit as well, this one you can alter while flying so can quickly get feedback if decreasing helps anything Any reason for the 0.9 render resolution setting in the Meta link app? Are you modifying this somewhere else, e.g. DCS PD? You're using both Quad-Views-Foveated and OpenXR Toolkit. Is Quad Views enabled in the DCS VR settings? What settings are you using in Quad Views and the Toolkit? Debug mode enabled in both (it's on by default in Quad-Views-Foveated)? Resolution being increased in those, e.g. Quad-Views-Foveated is 1.1 by default? I don't use the Meta Link app (I use Virtual Desktop) so somebody else will need to weigh in on your Oculus Debug Tool settings. The Encode Bitrate might be a bit high, have you tried with lower values, or even default?
  18. sleighzy
    Neither of these logs contain a DCS crash, which may indicate that Windows killed the process. Can you run the Windows DxDiag tool, save the output report, and drop that here as well please.
  19. sleighzy
    As these can get out of date, e.g. there have been changes to textures in the game that won't be reflected here (don't know the consequences) there is also this script you can run to optimise your current latest textures.
  20. sleighzy
    I've dropped your DCS log file into the DCS log analyser which had the following feedback. Note, these items are performance related so are aren't strictly the cause of your loading time problem but worth resolving given the impacts that they have (and may help with that). Turn off SSLR. Turn off SSAO. Disable civil traffic. Consider using TAA instead of MSAA. In addition to this I see you are also using the OH-6A mod, along with the gunner export script. This has known performance impacts on multiplayer servers with a large number of units. The advice on the GitHub site calls out this performance issue as well and has a recommendation to remove that script. Remove gunner_export_hook.lua from Saved Games\DCS\Scripts\Hooks to avoid it (Doorgunner won't be functional anymore) The log analyzer also states that your Windows version is out of date. There may be performance improvements in later versions. If you haven't already then add an exclusion to your entire DCS installation directory in your anti-virus software.
  21. sleighzy
    Awesome-sauce!! Hopefully all continues well. Happy flying.
  22. sleighzy
    Please attach your "C:\Users\username\Saved Games\DCS\Logs\dcs.log" file (might just be a text document named "dcs" if your Windows is hiding file extensions). Make sure you've loaded all the way into the game and replicated the issue and not just the launcher.
  23. sleighzy
    Can you also increase your custom page file to Initial and Max values to 32768, click Set, Apply, and restart your PC. Decrease your DCS Preload radius setting from 150000 to 60000 or less.
  24. sleighzy
    The DCS log does not contain any crashes, so is probably Windows killing this, hence my request for the DxDiag report which shows the last 10 crashes in your system and the processes involved. The DxDiag report shows numerous Blue Screen crashes (codes 7e, 3b, be) which appear to quite serious. It also contains a hardware failure (code 141), but may just be related to GPU drivers. Make sure you've updated all your Windows drivers to the latest versions. Can you run the a command prompt (cmd.exe) as an administrator and then run each of the below commands individually and then restart your PC. dism.exe /online /cleanup-image /scanhealth dism.exe /online /cleanup-image /restorehealth dism.exe /online /cleanup-image /startcomponentcleanup sfc /scannow chkdsk /R /F /X The LiveKernelEvent 141 error is usually associated with hardware problems, especially related to the graphics card or power. For this one you can try reinstalling your graphics driver to see if it helps. You may need to use DDU to completely remove the old driver and install the latest if a basic driver reinstall doesn't work. There may be hardware issues somewhere, but the above may help with this. How much free space do you have on your SSDs as well, especially any that are hosting your Windows or page file?
  25. sleighzy
    Open the Controls settings, like how you bind controls for planes, there should be a "Disable hot plug" button down the bottom right. It will stop DCS from scanning for new USB devices every few seconds which can cause stutters etc. If you plug in a new device you can just hit the Rescan devices button beside it.
×
×
  • Create New...