Jump to content


  • Posts

  • Joined

  • Last visited

  • Days Won


About ShuRugal

  • Birthday October 25

Personal Information

  • Flight Simulators
    DCS World
    MSFS 2020
  • Location

Recent Profile Visitors

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

  1. The way my VR HMD sits on my face, the center of the IHADSS ends up about 15 degrees above my natural line of sight, which makes the thing pretty headache inducing to use. i've found myself mostly flying with it off except when i need to prosecute targets to reduce my eyestrain from always looking up to see it. Can we get a setting to offset the IHADSS rendering height? bonus points if it can be bound to key commands so i can adjust in the cockpit.
  2. Laser-guided rockets are unlikely for the Ka-50. As previous posters have noted, the only proposed system for that never entered service, and this is a study simulator, which means we are limited to real-world loadouts. It's probably helpful to keep in mind that, in the real world, aerial rockets are not considered precision-attack weapons. They come in pods and fire in salvos for a reason. You shouldn't look at a 20-rocket pod and think "i'll kill 20 tanks with this". full pod of S8s is good for 1-2 tanks, maybe 3 if you're a real surgeon or the tank isn't shooting back so you can get inside 500m to shoot. If you want rockets to supplement your vikhrs, you need to know what you will be shooting at. Infantry? take S-8 OFP (HE Frag), fire "medium" salvos from 2-3 km. Trucks or armor? S-8 KOM (HEAT), fire medium salvos from 0.5-1 km. General purpose? s-13, fire singles from 1-5 km. Generally, the s-13 is the best rocket to take. nice big blast radius for trucks and infantry, and you get 5 shots vs 4 "medium" salvos of the S-8. good for clearing manpads out of treelines where you can't see them to use the gun and dont want to waste vikhrs.
  3. Was linked to a thread from the beginning of this year about this issue which is now locked. Playing in multiplayer with the F/A-18, every time i die and respawn, i spawn on the catapult with wheel chocks in place unless i change slots, in which case i spawn cold on the elevator. the F-14B does NOT suffer from this problem. In my experience, the bug is 100% reproduceable: 1: be on multiplayer 2: start a cold F/A-18 on the supercarrier, launch 3: die 4: without changing slots, respawn. upon respawn, you will be engine hot on the catapult with wheel chocks in place, and crew chief saying "unable" to all commands apart from "rearm"
  4. @XPACT @Flappie Just for shits and giggles, I ran the game with Procmon capturing activity, just to see if anything interesting happened. Lemme know if you want the procmon dump, it's about 4 GB, and aside from just over a million NAME NOT FOUND events, is pretty dry. Top level counts for event results: For shits and giggles, I also threw a paging file on my 1TB platter drive at 32GB (which is pretty fucking pointless, because that drive would take 10 minutes to swap 32 GB into RAM... faster to read it off the SSDs it actually lives on) just to see how memory allocation behaved. Even with all this swap space to play with, DCS never requested a commit greater than 17 GB, and that my total commit never exceeded 28GB. Wasn't able to reproduce crash conditions (with the Hornet, it's pretty sporadic, only about 1 crash to desktop every 10-15 hours of gameplay on average) I'm not asking for help bandaging the bad behavior in the application, I am reporting the bad behavior and providing as much data on it as I can so that ED can identify the internal engine cause of it and correct it (or not, memory allocation problems have never seemed high on their radar in the past).
  5. Commit charge is a meaningless number by itself. how much RAM is actually in-use? That's the important figure. if I have 32GB of RAM, and only 16 is in use, and DCS is throwing fits about RAM while it still has 16 billion bytes available, that's a DCS problem.
  6. which makes this a problem with DCS. If DCS is coded to be intolerant of no swap file, that's bad code.
  7. I have recently gone from 16 to 32 GB of RAM. you can see from my procmon capture that while DCS had requested commit for 98% of my total ram, it was only using 16GB at the time of the crash. There are also virtual no hard faults ocurring, the game is not even requesting swap access, this cannot be a swap issue. I have the swap file completely disabled on all my hard drives except for the drive I have windows OS loaded on, and the swap size there is the minimum to allow windows to save crash data in the event of a BSoD. If DCS is having memory issues when i have 16GB of RAM unused, that's a problem with DCS, not my system.
  8. two more crashes this evening. Both flying the F/A-18C in multiplayer. One a bit after a firing a string of HARMS, possibly at the same time a group of T-90s spawned in. Second crash occurred during handover to tower on the way back to the carrier. Logs.zip DxDiag.txt
  9. I have the page file disabled deliberately, I should have more than adequate actual RAM and don't care to have windows thrashing my drives. If you are seeing memory errors, I will look into acquiring more RAM.
  10. I've been having a problem on Multiplayer with being unable to launch after I die or return to the carrier. First launch is always good, second launch always refuses to pop, crew just stands their holding their thumbs up. Shooter puts his arm out, but does not complete the signal to shoot (does not touch the deck and lift). If I go into AB, the aircraft breaks the launch bar after a couple seconds and tumbles off the deck. attached track shows this happening three times. First launch is cool, then i die, and when i spawn back in, all subsequent launch attempts result in this condition. Caucasus_Dynamic_Conflict_v1.3.0_BW-20210423-180357.trk
  11. Adding my name to the crash list. For me, the crashes in DCS are so hard that they impact other Windows applications. Steam VR has modules begin to fail, any open browser windows I have in the background will freeze, and Discord goes blank and must be task-killed to get running again. For me, the crashes happen most often when connected to any multiplayer server, though crashes in SP missions happen as well. DxDiag.txt crash.zip
  12. Yeah, it's pretty frustrating. the Steam VR mirror doesn't include an audio feed, and Discord doesn't let me select what my stream audio source is. I have to choose between having good picture or audio. I've played around with a few products which let me mix the game output and my microphone input into a virtual microphone, and set that as my mic in Discord, but that has its own set of problems.
  13. I have no idea, as I'm not using WMR, i'm running in Steam VR with a Valve Index. The sound going to my headset is also not the problem. The problem is that when I tell Discord to stream the Steam VR mirror (which reprojects the VR image from my headset to 16:9), it does not include audio from the game. Steam VR has an audio mirror function, but it can only direct sound to physical devices. Discord lacks the ability to select specific audio sources for streaming, if the app you are streaming the video from doesn't have audio, then you don't get audio in the stream.
  14. Ah, the old "perfect is the enemy of good enough" issue.
  15. I realize that this is pretty low priority for the DCS team, but it really aught to also be pretty low-hanging fruit to fix as well: I am running into a serious problem with the way the desktop mirror in DCS works. When streaming DCS in Discord, viewer complain about the 9:16 aspect ratio. If I use alt-enter to force fullscreen, it doesn't actually crop the top/bottom off the mirror, and I end up with a an ugly stretched view that some people are reporting actually makes them nauseas to watch. While i can set SteamVR to mirror the VR view and stream that, no audio is forwarded to discord this way. Can we please get an option to have the VR Desktop mirror cropped and centered to a 16:9 aspect ratio so that it is practical to stream this thing in Discord?
  • Create New...