Jump to content

splash

Members
 View Profile  See their activity

  • Posts

    1180

  • Joined

  • Last visited

 Content Type 

Posts posted by splash

    Introducing Meta Quest 3

    in Virtual Reality

    Posted

    On 1/28/2024 at 2:48 PM, DJ3vil said:

    yea im trying it thanks .. with 72x1.0 and 1.8 DCS DLSS Quality i can get almost 72fps native. 
    And the picture looks almost perfect.

    Maby i should change Bitrate in ODT, i ditch OTT for now, it seems mess up smthg for me

    edit its only 36fps but GPU only takes 70% usage, i asume hes not getting to 72fps so he cuts in half with asw

     

    I'm leaving "bitrate" at default values for some time, because at 960 (maximum) causes sound stuttering from time to time in my machine (5900X + RTX 4900 + Samsung 980 Pro). Default value is 200. My current setting is very similar to yours, except I configure the PPD in Oculus Tray Tool (1.8 or 2.0) in order to apply it to DCS, IL-2, FS2020, etc.

    Introducing Meta Quest 3

    in Virtual Reality

    Posted

    I did more tests. With PPD=1.3 in ODT, MFDs are legible but not perfect and so the labels in consoles, specifically the right console in F-16 that has lower texts. With PPD=1.8 they are very clear/sharp. These test were performed with Oculus App in default (72hz/1.0x), OpenXR Toolkit at default and changing just the PPD in Oculus Debug Tool (encoder bit rate=0 -> 200 mbits/s, encoder width=0 -> 4128 in my case).

    Introducing Meta Quest 3

    in Virtual Reality

    Posted · Edited by splash

    1 hour ago, ACS_Dev said:

    At what PD would you say it becomes legible?

    Please do!

    I would say 72hz/1.0 in Oculus App, 1.3 in ODT/OTT, 1.0 in VR tab in DCS. I got better results this way. My card is a 4090 and use 2.0 in OTT, very clear texts and labels.

    I’m currently experimenting with OpenXR Tools, there you can set resolution, turbo mode, etc.

    • Like 1

    Introducing Meta Quest 3

    in Virtual Reality

    Posted · Edited by splash

    53 minutes ago, ACS_Dev said:

    Can anyone confirm or deny that the quest 3's resolution is sufficient to read F-16 displays without zooming in or leaning forward?

    It dependes on the settings. By default (oculus app at 72 Hz and 1.0x) definitely not. But if you increase the PPD setting in Oculus Debug Tool/Oculus Tray Tool, or set the PPD in the VR tab in DCS, you can read all the texts in the MFDs, consoles, etc. very good. They're very sharp and clear.

    Maybe the main problem for me is the mouse movement with your head, it is difficult to be precise when pressing a button. I'd rather not to use the head and just the mouse.

    • Like 1

    DCS: MiG-29A Fulcrum

    in DCS: MiG-29A Fulcrum

    Posted · Edited by splash

    My wish is a Izdeliye 9.12, referred internally in the Air Force as Izdeliye 5 (NATO Name: Fulcrum-A), as oppossed to the export version A (izdeliye 9.12A, izdeliye 5A) or export B (Izdeliye 9.12B, izdeliye 5B), whose names were Fulcrum-A too.

    Export version A was a slightly downgraded version for Warsaw Pact countries, featuring a RLPK-29E radar targeting system. Anyway it has a similar performance that Soviet Fulcrums.

    • Like 1

    Introducing Meta Quest 3

    in Virtual Reality

    Posted · Edited by splash

    Hi, I'm thinking in buying a Meta Quest 3, does someone who owns this model and the official cable link can tell me if it charges the device while playing? How many hours you can fly with the cable plugged in? Above it has been commented but I hesitate if buying the official cable USB-C to USB-C (I have 1 port) or look for an unofficial USB-C to USB-A (I have a 16-port USB 3.0 HUB with external power).

     

    Thanks.

×
×
  • Create New...