Jump to content

av8orDave

Members
  • Posts

    607
  • Joined

  • Last visited

Everything posted by av8orDave

  1. That's interesting. I haven't tried SteamVR as the runtime, maybe I'll at least see what the reprojection looks like using it. Using reprojection with OpenXR, rotor blades look like they're made of jelly on my system. It's pretty awful.
  2. I use the official link cable with the Quest 3. I can't sit and play DCS long enough to discover the battery life running it linked to the computer. If I play for an hour, it's still shows at about 95%.
  3. This is probably largely a question of personal preference, but then again I’m not real sure. When I turn on Motion Reprojection (Reverb G2) or ASW (Quest 3) I get some hardcore, nasty “ghosting” (for example, if I roll the aircraft quickly while looking at the wingtips, I see about three wingtips for an instant). Do people who insist on using motion reprojection or ASW not see this (maybe it’s my system?), not mind this (see it as a fair trade off for less stuttering), or something else? Just curious if im missing something regarding the topic.
  4. I suppose this might already be a known issue, but the air to ground gunsight doesn't seem to function. It really is only good as a general reference at this point.
  5. I also tested yesterday. On a Ryzen 9 5950X, 3080, 64GB DDR4, I didn't notice a bit of difference between the old and new versions of DLSS. I really haven't had problems with ghosting though, so maybe it's only impacting systems that had ghosting issues.
  6. I do. The remarkable thing is that if you turn it off in ODT or OTT, when you run the game and watch the framerates, it clearly still turns on. In my experience the only way to really turn it off is by hitting Ctrl-1 every time you log in to the game. Does the ODT method work for you? Maybe I'm missing something?
  7. This bug annoys the daylights out of me. Hope it gets fixed soon. As is, the F-15E lacks its main fire and forget weapon for hardened targets.
  8. The above works. The first thing I do every time I boot up DCS is hit Ctrl-1 because ASW is the devil.
  9. There's some weirdness with the F-15E on what shows up on the armament page, but that is across the board, not just Retribution. Only other thought is that when you set up the campaign, make sure the start dates are consistent with the weapons you're trying to use. That probably isn't the problem though if the agm154 is showing up.
  10. I fly the F-15E in Retribution and Liberation all the time. What is the problem you're having? As a starting point, make sure you're using the one called "F-15E (Suite 4+)" or something to that effect. There is also an AI variant that probably doesn't work.
  11. Never flown a Mooney, but I’d like to! Good looking planes, and fast, but I’m getting off topic. Anyway, I’ll maintain that even the most stable aircraft needs constant input. If you let go of your Mooney’s controls, it’ll just fly along on the same heading and level with no input for an extended period of time? Just to clarify, I don’t think any small plane NEEDS roll trim, but that’s because the pilot is making constant control inputs to hold heading and keep the wings level. Granted, if you’re trimmed well, they’re small inputs you make with your fingertips, but inputs nonetheless. I think some DCS pilots think you just dial in the trim and go to sleep. All that to say that the A-10 flight model feels pretty legit to me.
  12. I’m also a real pilot. I generally agree with you, however one of the types I’ve personally owned required constant trim and control input in the roll axis due to tanks feeding unevenly during cruise flight. Also, any change in course, regardless of weight imbalances, likely require changes to the control surfaces in the roll axis due to things like wind direction and crab angle, not to mention disturbances from turbulence. In most planes I’ve flown, if you take your hands off the controls, it’s just a matter of time until you’re in a bank or turn. It might take a minute or two, but without the pilot intervening, it’ll happen. DCS simulates this in all of the airframes quite well. I’m trying to think of a flight model in DCS that you can just fly along straight and level, and there isn’t one (unless you’re fine with some big altitude and heading excursions). Also, most small planes don’t have roll trim because it would be an added complexity, more expense, and the pilot is expected to do the flying. Manually adjusted trim tabs on the ailerons are a more common option, but obviously aren’t adjustable in flight. A good example of a small plane with actual aileron trim is the Cirrus SR22. Again, any non-fly-by-wire aircraft will require the pilot to use control inputs, whether trim or actual stick/yoke input to keep the plane straight and level. Most planes won’t just fly along on their own unless an autopilot or stability augmentation system is engaged.
  13. I know this isn’t the answer being sought, but a couple things: 1) I don’t seem to have trouble trimming the A-10 in DCS; I haven’t flown one in real life, but the trim behavior feels believable to me. 2) Real, non fly-by-wire aircraft are impossible to trim perfectly; due to turbulence, wind, constantly changing fuel states, etc, real planes require constant input from the pilot to fly straight and level. The inputs will be very subtle if trimmed well, but if you were to let go of the yoke or stick on most days without an autopilot engaged, the plane will be banking, climbing, or diving in short order.
  14. Agreed, please fix this.
  15. That made me laugh out loud. Nice post! :)
  16. Oh for sure. I think I agree, and keep in mind, I don't find the F-16's systems to be "fiddly" at all, and don't have any problem employing it. My only point is that if it is "realism" you're after, the majority of the missions of the past few decades have been on-call CAS, not pre-planned strikes. Coincidentally, DCS can simulate this in a kind of "ok" fashion. The built-in JTAC gives a simple 9-line once you're on station, you plug it in as a steerpoint, slew the POD onto the target, designate, and drop.
  17. Have the aforementioned optimizations ever been implemented? The performance on the Syria map seems to be at a relative low point since launch. It makes any sort of complex mission in VR pretty unpleasant.
  18. Fair enough. My point is just that the idea that most missions IRL are pre-planned targets, something like interdiction, deep strike, or OCA, just isn't the case. Granted, I agree the majority of CAS missions would have a JTAC providing the pilot with coordinates. Early in this thread, my note was that the F-16's systems are actually super-easy to use in these scenarios. Punch the coordinates in, slave the TPOD to the coordinates, find the target, lase, and drop. Piece of cake, really. The only thing I'd maybe add that isn't so realistic is that even with coordinates, most real CAS scenarios involve the JTAC talking the pilot onto the target, as it is usually small, potentially obscured, and not easy to identify, even with coordinates. DCS doesn't simulate this well (and I'm not even sure how it would simulate this). Long story short, most real missions for the past 20 years haven't been pre-planned strikes. They've been pilots loitering, waiting on someone to pass them a target, whether through coordinates, a visual talk-on, or in most cases a combination of both.
  19. Well, regarding the "flying around and looking for targets is mostly a sim thing", that's really not the case. For the past 20 years, most of the activity that the US Air Force, Navy, Marines, and Army Aviation have been engaged in can be almost exactly described as "flying around and looking for targets." It's actually easier to name the few circumstances where pre-planned targets were a thing than it is to name those where they weren't. The early stages of OIF were largely pre-planned targets, but after the first week or so, it switched to mostly on-call CAS. OEF was almost exclusively on-call CAS, and Syria has been much of the same, except for the few instances where there have been retaliatory pre-planned strikes against fixed assets. Indeed, most of the activity the A-10, F-16, F-15E, F/A-18, F-14, AV-8B, and AH-64D that we have modeled in DCS have really spent most of their time over the past few decades just flying around looking for targets. Most accounts from pilots involved in these operations go something to the effect of "we took off, flew to the Ops area, checked in, refueled, refueled again, got called to respond to a target a JTAC had identified, dropped a JDAM on it, refueled again, and went home after 6 hours."
  20. I have the used the HP G2 for the past few years. My system: Ryzen 9 5950X, RTX 3080, 64 GB DDR4, SSD. I usually play single player, usually DCS Retribution or Liberation. I generally get about 75 - 90 fps depending on how complex the mission is. I run textures at medium, terrain textures at high, DLSS at quality, shadows at high, terrain object shadows default, clouds low, no civilian traffic, forest visibility at 100%, scenery 50%, forest and scenery detail .5, LOD at .5, and AA at 4X. WMR at 125%, no motion reprojection. Quest 3 I run all of the above, but through virtual desktop on "Godlike" and DCS PD set to 1.3. I get a pretty consistent 72 fps. No ASW. I also use Quad View FFR. The visuals and smoothness are significantly better than with the G2, especially at the edges of the field of view.
  21. I'm not the biggest Hornet fan, but one thing it definitely has that makes it interesting is the sheer variety of weapons it can employ. LGBs, JDAMs, HARM, CBUs, JSOWs, SLAM, SLAM-ER. Harpoon, Maverick, rockets (including the big ZUNIs), gun, AIM-9, AIM-120, on and on. It does all of that AND lands on the boat. You've got to admit that it is a very versatile aircraft. Additionally, it has almost unmatched performance at high angles of attack, making it the premier "knife fight in a phone booth" fighter.
  22. A couple more pointers: 1) I second the suggestion to give yourself a bit more space in the downwind while you're learning the Case I. If you're too tight to the ship, the turn from downwind into the groove will require a high angle of bank and will be difficult to execute consistently. 2) Anticipate changes and stay ahead of the plane. When about to turn from downwind into the groove, add a bit of power to compensate for the reduction in lift as you bank the plane. Once you're about to level out on centerline, start reducing power to compensate for the increase in lift as you reduce your bank angle. 3) Get in a lot of reps. Consider going around over and over again to get a feel for the right distance from the boat on downwind and the right bank angle to turn to be lined up with the centerline in the groove. I can't stress enough that many tutorials show the pilot banking 90 degrees in the initial break and pulling the daylights out of the stick and arriving less than a mile from the boat on downwind. This will then require a really high angle of bank in the last 180 turn, making things really difficult. Be patient in the initial break; maybe go to about a 60 degree bank, don't pull any harder than needed to maintain level flight in the break, and go from there.
  23. When flying a case I pattern with the Supercarrier module, the comms suddenly started getting "clipped" once I was in the groove. On approach, everything was good (initially contacting the carrier, the 10 mile check-in, etc) but once in the groove, I could hear the mic get cued, and I could see the subtitles in the corner of the screen, but there was no audio (all of the LSO calls were basically silent). Any thoughts?
  24. Ok, I have a bunch of old but very good liveries for the F/A-18C (VMFA-232, VFA-34, VFA-37) some of which I'm very fond of. I haven't touched the F/A-18C in ages, and I come back to it, and the BUNO/plane numbers are all over the place and huge. Any way to fix this?
  25. In the WMR settings screen, change the resolution to 150%. I run with DLSS Quality.
×
×
  • Create New...