Jump to content

Blue73

Members
  • Posts

    473
  • Joined

  • Last visited

3 Followers

Personal Information

  • Flight Simulators
    Was BMS, now DCS.
  • Location
    Perth, Australia
  • Interests
    3D Printing, Electronics, CAD, Model Making, Coding
  • Occupation
    Comms Engineer

Recent Profile Visitors

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

  1. Hi Skywalker, you need to disable the sliced encoder setting in ODT. Then you can chose what gfx setting you like. Very minor impact on latency, in the ms.
  2. I'm on a 4090 and it's still very much there. When I played on the HP G2, though no where near as sharp, had far less severe ASW artifacts.
  3. If you get the lighter band again you'll need to disable Sliced Encoding in the Oculus Debug Tool. (PTC)
  4. For me their ASW introduces major ocean and sky flickering artifacts that makes ASW unusable. No such issues with my G2. It's a shame as the image looks allot better than the G2, greater FOV and sweet spot.
  5. I remember just having the windows image viewer running I'd get constant regular 1-2 second pauses as the cpu kept spiking.
  6. Yes OpenBeta. I'll switch to OTT for PD see if that makes a difference. Ultimately I'll need to reduce my settings until 72fps constant can be achieved.
  7. Great choice, it is a very good headset. If you're not on a 4090 I recommend planning for that. The headset really shines when the PD is increased and running MSAA 4x. I also could run the encoder at 960 without issues unlike my 3090, had to limit to 500. I swear the extra BW gave the colour spectrum more room. Recommend flipping the back pad around to allow the headset to tilt forward, feels very comfortable and improves the FOV especially extending below you.
  8. Thanks for checking Yes ASW hasn't activated when you're constantly at 72 fps so you wont see the distortions. I have an 4090 but an 8700K @ 5GHz. My settings are the same in game as yours except for heat blur is low and terrain shadows are default. In-game PD is 1.3 but in OTT it's 1.0. 960 Mbps enc speed. 3600 px Width. ASW Mode Auto. I think the answer is to stay away from ASW. I was reading it's an ASW 1.0 problem, ASW 2.0 will fix it but not supported in DCS. WMR reprojection didn't have this issue, so hadn't noticed it on my G2. cheers John
  9. Hi Slughead, I fly Mission -> F/A-18 -> Supercarrier -> Launch ( Caucus ). Fly away from the carrier, get above 2000 ft, look down at the ocean on your left hand side, look back at the carrier when above 3000 ft. For me it's jumping all over the place. If yours is good and your FPS is below 72/80/90 then there's hope. Thanks! Track File: ana.trk
  10. I tried 90Hz, it has the same issue. I took the best picture I could with my phone. That blue line is the border of the distortion, lower section is the issue, it flicks randomly all across the ocean and sometimes the upper sky section. If the Carrier is caught up in it, it too flicks between multiple positions. With ASW off it's all good so I don't think it's a BW issue or the distortion created from the ASW warping requires more than 960Mbps of bandwidth to render. FS2020 has the same issue in the sky, but not as bad as DCS.
  11. I'll try this thanks. My enc bitrate is at 960 already but haven't tried upping the refresh rate, I thought it might make it worse as ASW is kicking in sooner.
  12. Do you see the distortions with ASW enabled with the water and sky?
×
×
  • Create New...