Jump to content

dutchili

Members
  • Posts

    259
  • Joined

  • Last visited

1 Follower

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. See this thread: (start DCS with command-line option --force_open_vr to force the Oculus runtime
  2. Going to return it today. I formatted the drive, reinstalled windows, and the exact same issues occurred after the install.
  3. Thanks all for helping out here. I decided to go resetting the pc. That didn't go without issues. Resetting using the local copy didn't seem to work at all. I got page fault blue screen and the reset was rolled back every time. Then selected the online version which succeeded. But, when booting, the admin account was blocked. Fixed that in safe mode and ran McAfee and the Malisious Software Remove tool. None reported any issues. Still, while downloading DCS again and synchin my onedrive etc, i already see some stability issues coming back. Whenever i use Google Chrome and visit web.whatsapp.com, i get an access violation in the chrome tab. Same things happens often in youtube and the discord windows app. I have no clue why this happens. Even with all USB devices disconnected this happens (i suspected the USB audio driver). All hardware connections in the box seem fine and no intel/motherboard driver updates are available. Driving me nuts. As for DCS performance -> still many gigs to go for downloading (.....pro tip for those in the same boat -> change your power plan before going to sleep :) )
  4. The /verifyonly log file showed that the issues where of type 'access denied'. I ran DSIM as you said. Took a while to get passed 62.3% but then completed successfully. Reran /verifyonly and the error in the log indicate stuff related to drive staging updates. re-tried sfc /scannow. Did not complete again. Example log entry: 2024-03-01 12:29:48, Info CBS DriverUpdateStageUpdates failed [HRESULT = 0x8007001e - ERROR_READ_FAULT] 2024-03-01 12:29:48, Error CBS Doqe: Failed staging driver updates [HRESULT = 0x8007001e - ERROR_READ_FAULT] 2024-03-01 12:29:48, Info CBS Perf: Doqe: Staging ended. 2024-03-01 12:29:48, Error CBS Failed staging drivers, rebooting and trying again [HRESULT = 0x8007001e - ERROR_READ_FAULT] 2024-03-01 12:29:48, Info CBS Shtd: progress thread terminating. [HRESULT = 0x00000000 - S_OK]
  5. Thanks @Nedum ------- C:\Windows\System32>sfc /scannow Beginning system scan. This process will take some time. Beginning verification phase of system scan. Verification 48% complete. Windows Resource Protection could not perform the requested operation. ------- When i run /verifyonly it says if found issue. But...now what?
  6. Any suggestions for what to look for in my system?
  7. I played around with these settings and 60 fps as in-game setting, combined with a pre-load of 60000 improved the situation. There is still the occasional spike in simulation time according to the FPS counter, but less significant than before. When setting an in-game FPS setting of 30 i get bad overal graphics performance and the FPS counter shows 'FPS limit'. At 60 FPS set in-game and 90 FPS in the headset (45 per eye), the 'simulation' is unable to keep up at all times. I hope the team can find what is causing that to further improve and create more headroom.
  8. Thanks for having a quick look. These settings have no effect. I tried a small, medium (60000) and large setting for preload. For FPS cap: if i set my Oculus Quest from 90 FPS to 120 FPS is see the exact same thing. Changing in game FPS sliders has no effect.
  9. Here you go @BIGNEWY ground stutters.trk dcs.log DxDiag.txt options.lua
  10. Request: can the scripting as created by mission makers, modders etc run in a different thread not to influence the simulation? Long loops, bugs and scripting errors presented in a message box completely hold-up the simulation.
  11. I experience terrain stutters when looking sideways, approx. from a 45 degree angle compared to 'straight ahead'. The stutters disappear after a second or two when their are not many objects to show in my field of view. (but the issue is reproduceable even in de Nevada desert) It is very reproduceable and not something new in the latest release. I wonder: why is the 'system' working differently from a specific viewing angle? Anyway, it might be a clue to further performance improvements. @BIGNEWY
  12. I checked the tacview. Distance between the two helicopters was 1000 ft
  13. Difficult to see in this VR screenshot, but: - with LOD set to 0.3, the center of the Apache disappears at a center distance. - the apache in the front is fully visible. - the one in the rear only shows the rotor and two (gear?) elements.null I was expecting to see the entire Apache at distance, though will less detail.
  14. Pressing DMS left will change the displayed sensor on the left MFD. The newly shown sensor is not made SOI. I can see the logic in that if you just wanna have a quick peek using another sensor without losing 'the lock', but i don't find it intuitive. I change the sensor deliberately to use it. I do not have declassified information that this behavior is wrong. I also don't have documentation that this is right. My wish is that the newly selected sensor is made SOI automatically. (no track file and dcs log will be provided)
×
×
  • Create New...