Jump to content

av8orDave

Members
  • Posts

    625
  • Joined

  • Last visited

Everything posted by av8orDave

  1. I really want VD to provide better visuals and performance than the link cable and Meta software, but for me it currently doesn’t. I am on a dedicated 6e router, 4090, Ryzen 9 7950X, 64G DDR5. Ive tried every codec, and everything from maxing bitrate, to half the max, to auto adjust. Even at Godlike, and with a slight PD increase in the DCS options (1.3), it is a bit “blurrier” than the link cable is right now. Additionally, the link cable currently provides a silky-smooth experience at a PD in oculus debug tool of 2.0, while VD has a slight “micro-stutter” or “judder” much of the time. I’m using the latest Nvidia drivers, which I think the VD team discourages, but it is what it is. I’m not running obsolete drivers for one game and one piece of VR software. It is a bummer because VD once outperformed link by a long shot, but that isn’t where things stand right now, at least in my experience.
  2. Yeah I had the same thought. I went into the mission editor, and set the waypoint elevation to 0 agl. Tried again, and it still seems to point down at the ground shortly in front of the helicopter. Im hoping to have some time to play around with it this afternoon. Maybe I can suss out what I’m doing wrong, otherwise I’ll try to maybe post a video.
  3. For the life of me, I cannot figure out how to get the MMS to point at a waypoint. Is anyone willing to explain the procedure step-by-step? Here is roughly what I am doing: LMC on MMS pulled up on MFD MMS mode switch to PPT laser armed press PPT button on MFD enter waypoint number and hit “enter” press mms manual button twice to get to PPT mode After doing this, the MMS seems to be point forward and slight down into the ground, and not remotely at the waypoint. What am I missing?
  4. I'm sure I'm a bit slow on this one, but can someone explain what this bit means?: "Please note, in order to follow our DCS updates, you must have the latest information about our network changes, we kindly recommend updating your DNS cache (run "ipconfig /flushdns" in Windows)." Something maybe is lost in translation. I honestly have no clue what this is referring to or saying.
  5. I think shadows comes down largely to the details of the system. A few years back, I had a 3080, and I had to be very conscious of the shadows setting, as anything over medium would really kill performance and was a major limiter. I have a 4090 now, and graphics settings really aren't the obstacle... if I get poor framerates, it is almost entirely because large numbers of AI units are killing the CPU (Ryzen 9 7950X). Said another way, if I'm flying solo missions with a 4090, I can go hog-wild on graphics settings with little consequence. If I'm flying a complex mission, all bets are off.
  6. You’re going to get varied input from different people, but my simple answer is: no. You don’t need all the third party software. I use the regular Meta App combined with Oculus Debug Tool (already in your Quest software) to make any necessary changes. VR in DCS doesn’t need to be a science project. Frankly, many of the “benefits” people seem to tout from 3rd party software I believe to either be a placebo effect or unique to their specific system / setup. Find some settings that work for you and go enjoy. At this point OTT is obsolete and OpenXR Tools might be as well.
  7. I seem to be having the same problem. Dropping textures to medium didn't do a thing. System is Ryzen 9 7950X, 4090, 64GB DDR5. Quest 3.
  8. Just picked up the Chinook for the first time in a bit. Before flying the Chinook, I was flying both the F-16 and the AH-64 with a rock-solid 72fps. With the Chinook in Nevada, my FPS was suddenly a 36 - 42 fps stuttery mess. System is a Ryzen 9 7950X, 4090, 64GB DDR5, on an SSD, Win 11 Pro. I'm not running any mods, totally clean install.
  9. Maybe they do videos like my son does book reports for school. <knows about book report due date for months>.... <day before book report is due>... "Hey, I haven't started that book yet."
  10. Dang, now I'm sitting here trying to figure out which group I fall into. Maybe both.
  11. Remarkable, right? How does a video get delayed?
  12. This is the correct list. Of these items, I predict: I hope to see the sniper pod on our f-16.. We will see this. the API Vulkan in action: Won't see it. the DTC: Won't see it. the Dynamic Campaign in action: Won't see it. the save option to mission progress: Won't see it. the F-15E the solved problem with RZ: Definitely won't see it.
  13. A full-fidelity F-15C would be a really nice surprise. Has there been a more important, successful, and historic aircraft in modern service?
  14. I feel for the DCS users that add a 50X0-series card to their system, only to have a DCS mission with a handful of AI units bring their CPU to its knees.
  15. I hear ya’, and yes, it’s a great module. It would still be nice to know if it will be maintained going forward or if features that used to work (like ATHS) will be allowed to gradually “erode.”
  16. I've tried with pretty much all of the encoders, at least H264+, HEVC10 Bit, AV1. I've tried running at bitrates as low as 100 with all. My in-game overlay shows a solid 72 fps, latency around 40, and a solid network connection with low network latency (I'm on a dedicated 6G router, 2400bps). Yes, I'm on the V72 firmware. I don't use OpenXR Toolkit (it is antiquated and no longer necessary, no?). I get great performance with the link cable, but get a wild micro-stutter with Virtual Desktop. System is a Ryzen 9 7950X, 4090, 64G DDR4.
  17. It is super-flyable and very enjoyable. I really like the module. Having said that, there are definitely some features that are regressing (i've been annoyed that the ATHS no longer functions since the RAZBAM dispute). Also, figuring out how to use some of the features has been an adventure as the implementation of many things (TPOD functionality for example) has changed over time.
  18. I know this is an old post, but did either of you figure out a solution to this? Tried Virtual Desktop today for the first time in a while and the judder was pretty bad... I don't get that with the link cable. It's a rock solid 72 fps (Quest 3), but if I roll the jet or move my head quickly there is like a weird micro-stutter.
  19. Just finished Mission 3 (Danger Close) and loved it. Great mission from start to finish. Awesome work! This campaign holds a special spot for me... I was born in Northern Ohio, and although I've lived around the country at this point, I live back in Ohio now. I'm a private pilot, and when I was completing my PPL, my "long" cross country was to Toledo Express. Seeing the Vipers on the ramp as I taxied by was really otherworldly. Every year on Memorial Day in May, the Vipers of the 180th Fighter Wing scream around Northern Ohio at treetop level, treating everyone who happens to be outside at the right time to a brief but really exciting flyby in honor of our country's fallen soldiers. I look forward to it annually. Many thanks, Reflected, for this awesome campaign featuring Ohio's own Stingers!
  20. This was helpful, thank you.
  21. No, there is no "auto-anti-ice system." The pilot-controlled system will prevent windshield and pitot ice in light to moderate conditions. If you want to prevent icing on the rotors and engines, don't fly in visible moisture in sub-freezing temperatures. As a side-note, I can't say for certain for the Chinook, but the AH-64 for example has historically been VFR only. Obviously this is stretched if mission-critical, but these machines aren't intended to fly around in icing conditions. One thing about DCS is for all the effort made in the name of simulating "realism", aviation weather is not much of a consideration in DCS compared to how it is analyzed and planned for in the real world.
  22. ^ This, 100%. The problem with sharing performance in VR for DCS is that the baseline is nearly never the same. I too can get a solid 90 fps if I'm flying the Flaming Cliffs F-15C at altitude in the Caucasus with no other units on the map. Meanwhile, with the same settings, I could drop down to barely being able to maintain 50 - 60 fps if I'm sitting on the ground in the AH-64 in the Marianas with a 18 other AI units around. It all just depends. The bottom line, I have learned in my experience, is that DCS is very bottle-necked / constrained by the CPU. I have a 4090, and performance is nearly never limited by the capability of the graphics card. I have a Rzyen 9 7950X, and if I push the envelope with AI unit count, the framerate begins to struggle in a major way.
  23. What is your pixel density? I have mine set to 1.5. Also, try turning textures to medium, terrain textures to low, and visibility to medium. After that, cross your fingers, sprinkle some holy water directly on your CPU, build a shrine to the glorious MiG-29, pray for smooth VR framerates while kneeling in front of it, and if necessary sacrifice a small goat to Robin Olds. If this doesn't do the trick, you'll have to make a pilgrimage to the National Museum of the US Air Force at Wright-Patterson AFB in Ohio to say the framerate prayer in front of the P-47, P-51, F-86, F-4E, F-5, A-10, F-16, F-15, and F-15E (in that order). If done properly and all steps are followed, you may get 72 fps with decent settings so long as no more than 8 AI units are active on a map of your choice. If this doesn't work, you'll need to reach out to Sandia National Laboratories to see about using one of their supercomputers for your gaming sessions. Good luck and godspeed.
  24. My impression was that ED was going to maintain the modules in at least the state they were in prior to the dispute. If that isn't the case and the modules will gradually "erode" regarding their functionality, that would be very disappointing.
  25. Any update here? This bug is months old.
×
×
  • Create New...