Jump to content

DeltaMike

Members
  • Posts

    851
  • Joined

  • Last visited

1 Follower

Recent Profile Visitors

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

  1. Open adrenaline, performance, custom settings. Set your minimum clock speed to within 100-200 of max clock speed. Increase your DCS graphics settings until your GPU frame time is about 20. Note, I'd be careful about pushing clouds, water, or shadows -- that'll put a strain on your CPU. I'd start with medium water, standard clouds and try this with shadows off. Don't worry too much about textures, you have plenty of VRAM. I'm currently running low terrain textures, high cockpit textures, and AF x16 Turn off MSAA and try to get resolution up to 150% or so. It doesn't have to be exactly 150%, it could be 145 or 182, whatever it takes to get your GPU time to 20ms. Point being, when you dip below 90fps you're dropping frames. Only three ways to solve that, really -- Keep it above 90fps, which is hard to do in this game Lock frame rates to 45, either using Chill or Motion Reprojection Get FPS below 60. You'll have microstutter due to early frames, so it won't be perfectly smooth, but that's better than dropping frames. Some prefer option 3, me included. Others prefer option 2. Your Odyssey should look pretty awesome with a resolution of 150%, I'd try that first Let us know what your CPU times look like. Are you overclocking?
  2. G2 is a WMR headset and needs a work-around to run SVR games. We now have a choice of two work-arounds: WMR4SVR, or OXR. We jump through those hoops to get a high resolution headset (equal to Pimax 8K) for cheap, basically. Pimax is a SVR headset and according to the internet, doesn't support OXR. Good news is, it doesn't need a workaround. I'm constantly amazed at how well Pimax works with GPU's that would be considered woefully underpowered in the G2 world. Unsurprising to me that the 3090ti does well here. Not clear to me what the OXR Toolkit is doing for this guy. If anything. Doesn't appear to be clear to the developer either.
  3. Microstutter -- if that's what you are experiencing -- is caused by frame rate / refresh rate mismatch. Easy way to test this is to turn motion reprojection on. Is Oculus -- ahem "meta" -- still calling that "ASW"? If so, turn it on and see if that solves your problem If it does, you have options: Keep motion reprojection on (I know not everybody likes to do that, because of the artifact) Turn your settings down so you can consistently hold 80fps Turn your settings up so your framerates are consistently between 40 and 60fps. If you're running at 40fps, each frame will be displayed twice. You'll suffer from slow framerates -- watch the horizon and do a barrel roll, and you'll see what I mean -- but there will be no microstutter. At 80fps, each frame is displayed once; likewise, no microstutter (but with the benefit of a higher framerate). As you increase framerates from 40, most frames will be displayed twice, and occasionally you'll get an early frame. As you decrease framerates from 80, most frames will be displayed once, with an occasional dropped frame. I think the dropped frames are way more annoying than early frames, hence the recommendation to run in the lower end of that 40-80fps range. Back when I had a Rift S, I shot for a GPU time of 20ms, and that seemed to work OK for me. I had the opposite problem: I was trying to flog a Vega56 fast enough to keep up. If your 3080 can't consistently hold 80fps, you may need to slow that beast down a little bit. Note, the easiest way to to that is to crank up supersampling. There are other ways of doing it. Pixel density can help but it's tricky to manage, as performance varies (inversely) with the square of PD, so take it easy. You could crank up clouds and shadows, but note that'll affect your CPU times as much as your GPU times. You could try turning on MSAA, and probably have plenty of horsepower to do that. But, I feel supersampling is the easiest to get just right, and it makes the Rift S look fantastic ETA: one way or another, we need some numbers. CPU and GPU render times are way more helpful than the FPS counter
  4. Appears they changed the name on us. "Open XR Tools for Windows Mixed Reality" is the old "developer's toolkit."
  5. That's what I'm thinking. Way I see it, the problem is, we don't have "a" framerate, we have a distribution of framerates, and the challenge is to manage the tails. If we want to avoid dropped frames, we need to keep that distribution between 45 and 60. If we split the difference again, we come up with a target framerate of 52.5, or a frame time of 19ms. Which works for me, always has. Slow enough to avoid dropped frames, fast enough to smooth out the horizon a little bit when I'm doing a barrel roll. It's not perfect; nothing is in this game
  6. It'll actually work a little better if you keep it below 60fps, I get the best results at 50. Try turning up your resolution until your frame times are about 20 consistently on the map you're usually flying. OTOH if you're consistently above 60fps, you could try running your headset at 60hz It's not possible to make it perfectly smooth, talk to me when we can consistently run DCS at 90fps. Maybe with the next gen GPU's
  7. A tactical victory that fails to advance, or even works against strategic goals.
  8. Believe it or not there's been a ton of work on opencomposite since we last talked, this guide is kept up to date. The only caveat is, as of a week or two ago some people were having problems switching between OXR and SVR games using the "global install" procedure. I'd consider doing a manual install into the DCS install/bin directory and leave SVR alone so the kids can play whatever they want. Otherwise you're gonna be getting a lot of technical support calls along the lines of "DAD! You're ruining my life! FIX THE COMPUTER!!!!" To do that, you'd follow the "Per Game Installation" instructions here, download the 64-bit dll and just slap it into your DCS install /bin folder. In that same folder, find D3DCompiler_47.dll and rename it to something like D3DCompiler_47.dll.old and you should be gtg. Be advised, your rig might wind up running too well. If your frame rates are peaking above 60 you'll start getting dropped frames. If that happens, don't freak out, we'll fix it for ya
  9. You should be well below 22ms on cauc single player to give yourself enough headroom to play Syria or MP. You're close though, shouldn't take much. GPU upgrade will help you push textures and resolution, and may make msaa possible but it won't do squat for mp
  10. Not exactly stable, got the black screen of death and had to roll it back. I'm still impressed though, the boys are definitely on the right track
  11. apples and oranges. there's a big step up in memory bandwidth between 6700xt and 6800xt. Neither one is directly comparable to 3070, which probably slots in between That said, 6700xt may be ok for Q2. I'd hit gamers-by-night up for advice, he recommends the 6700xt as a good choice, see if he has any experience/numbers. Agree, that price is pretty durn attractive
  12. Simple upgrade, no issues. OXR with no mods, I have some post processing effects in the toolkit (gotta have my shades, of course). All done in F18. Test run, Syria. GPU times PRE: 15.9 in the country, 16.6 over a town POST: 15.2 in the country, 15.0 over a town Those are good for 58-62fps. Seems like I'm usually in the 50's on that map but that was before cleaning house during the last update. Figuring maybe the real difference was over the city, I figured I'd dust off the NTTR map. Holy cow. Over the desert: 10.6 (91fps) Suburbs: 12.4 Buzzing the strip: 15.0 (58-62fps) On the ramp at Nellis: 14.6 (where I was CPU bound, framerate 46) I'm normally right at 46fps buzzing the city, I was consistently 58fps plus and over 60 most of the time. Solid 90-91fps flying over the desert. Consistently >80 in the pattern at Nellis, including rolling down the runway. I'm impressed.
  13. Memory bandwidth is quite a bit better on the 3070, and there's a lot more experience to draw from when you're setting it up. That said it depends on your headset, even 3070 is marginal for G2 for example.
  14. yeah 2080ti is a beast with the Rift S, there's not much more to squeeze out of that headset I would think any situation that would benefit from the 3D would call for at least 32Gb of decent (3200MHz+) RAM
  15. I have my theories... this happens intermittently to some of us, fix seems to be to run opencomposite.exe again, re-select OXR, try again. If that doesn't work try starting DCS without any arguments... easiest way to do that is to dig down into your install /bin folder, find DCS.exe and start from there. Should work if VR is enabled within DCS
×
×
  • Create New...