Jump to content

darkstarRAF

Members
  • Posts

    125
  • Joined

  • Last visited

About darkstarRAF

  • Birthday 08/06/1981

Personal Information

  • Flight Simulators
    DCS, Prepar3d, BMS.
  • Location
    Russia, St. Petersburg
  • Occupation
    system administrator

Recent Profile Visitors

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

  1. Now that may be unhelpful report, but I'm getting 90 FPS in VR with MT consistently(but CPU bound message appears anyway). My specs are: i7-12700k, 32GB DDR4, RTX4090, Windows 11, DCA OpenBeta MT latest, Oculus Quest 2 (native) with highest resolution 90Hz settings. What probably differs from other guys is that I have HT and E-cores disabled in BIOS. That's the old trick for W10 which I didn't change for W11 installation. Also in the nVidia panel settings I have vsync: Fast. Game mode off, HAGS off. What differs between ST and MT is multiplayer - I'm getting huge lags while server list updates in MT version and it updates much longer than ST.
  2. Эээ уважаемый, а нахрена ставить Encoding Resolution Width = 2912? Вы таким образом просто херачите качество картинки в полтора раза и на фпс это влияет абы как, т.к. тут работает конкретно чип кодировщика на видяхе, а не GPU. У вас 2070, на ней кодировщик вполне себе на уровне, да и в целом когда у меня еще до НГ была 2070 - я летал без проблем с Encoding resolution = 3664 (что в целом сейчас вообще дефолт, если на 0 выставить - оно и будет), bitrate = 350 (увы, после 26-ой версии больше пока лучше не выставлять, на 23-ей у меня вообще 500 стояло). Опять таки и качество текстур вы тоже зря вниз загнали, на самом деле главный "Жрун фпс" в данном случае это MSAA и у вас он вполне себе на перевариваемом для 2070 уровне (хотя конечно у вас ноут, там все может быть хуже чем десктоп, это надо принять во внимание). Еще комент на тему настроек самого DCS - Это выставленное у вас общее разрешение, оно на самом деле для VR вообще не работает, вы так только себе систему к херам убиваете вплане повтора на десктопе, уберите нафиг. Разрешение для рендера VR в случае Oculus Quest 2 выставляется в окулусовском софте в настройках графики шлема, там где герцовка и ползунок графики.
  3. Hi Dodge! V.25 currently pretty much bugged, I give you that, having had problems with it myself (though I don't have disconnect problem). As I mentioned in previous post - set encoding bitrate to >= 350, it helps with sound distortions / flickers and other stuff. For link disconnections - that's really random from what I've read over in OculusQuest subreddit, some people have this problem, some not. Also setting PD in DCS become nearly pointless, as it gives little difference in picture quality (though it still gives that, but at cost of FPS, so I'd play with that to see what's more comfortable). But that got me curious and I will compare pictures to see the difference between yours and mine settings of PD (which is default in mine), that way we could decide more/less ideal settings for us too. Hopefully with the next update FB/Oculus will fix that link so it would work normally again.
  4. Klaus, hey! Ok, let's go through steps with you. First: what cable do you use and does Oculus link USB test shows at least 1.3 GBPs throughtput? Second: no need to set PD in sim or OTT, leave it as default. Also check that you have Oculus software version v.23 minumum on PC and on Quest 2 device. I cannot translate what you have in nvidia settings, but you should set vertical sync to "fast" there, as shown in picture below. Also your Quest 2 settings in Oculus PC software should look like this: I think that 3060 is on par with 2070, so this should be enough. In DCS you should set textures to high, MSAA/SSAA off, probably disable shadows too (they're huge FPS eaters). I found that textures settings don't have huge impacts on FPS but you could play with that too. Also disable motion blur, set reflections to low or disable it too (I don't remember if you can do that). Set PD 1.0 in sim as default, you don't need that. In OTT only set default ASW mode to OFF, Adaptive GPU Scaling OFF, link settings: set encode resolution to 3664, not 3648. Should be enough for your setup.
  5. 1. WTF guys, why do you use SteamVR at all when you have Oculus? Do not do that, SteamVR in this case will just lower your performance, as it will act as "middleware" between Oculus and DCS, eating your memory and VRAM. DCS supports native Oculus SDK, so use that. 2. Dodge posted his settings and that's quite wrong way to do with DCS with his hardware. Now I have to post mine, just tp rectify that. Also settings are applicable for GPU like 2070 or higher. Well it worked fine for me when I had RTX 2070, with 3080 it even better. Those who has weaker GPU's I'm sorry I don't know what should be set for you. Anyway: 2.1: Oculus software -> Oculus Quest 2 graphics preferences: set it to 90Hz / 1.7 2.2: Oculus Debug tool: Encoding bitrate at least 350 (with new V.25 update it would become recommended as v.25 has problems with it set to 400+), Encoding resolution width: at least 3664, if you have RTX30++ GPU - set it to 4080. Distortion curvature - set it to low to have max fidelity in center of view. It would slightly distort edges, but center picture would be greatest. ASW - better disable it, as it works in mysterious ways and sometimes causes lags. Same with adaptive performance scale for GPU - turn it off. 2.3: DO NOT USE STEAMVR AT ALL 2.4: DCS settings: well, I have all textures and water set to high, max visibility. If you have 2070 - MSAA/SSAA should be set to off. 3070+ = MSAA/SSAA set to 2X 2.5: As mentioned earlier - in nVidia control panel set DCS profile with vsync = Fast. 2.6: I REPEAT FOR THIRD TIME: DO NOT USE STEAMVR
  6. That's clearly "Vsync" problem, You have to open nVidia control panel, graphics settings, find DCS settings and set vsync = Fast there, should eliminate latency while looking to the side.
  7. Насчет графики на самом деле все не так уж и плохо пока что. С тоннами багов соглашусь безоговорочно, однако в VR фпс позволяет летать вполне себе комфортно при наличии более-менее современного оборудования (к примеру вполне себе комфортно летал на RTX 2070 + Quest 2, а после обновления на 3080 так вообще все параметры в максимале стоят и ниже 40 фпс не опускается, за исключением некоторых моментах, о которых далее). Однако именно баги портят все напрочь. В особенности задрал баг (ну или не баг, возможно течет видеопамять), когда в VR режиме внезапно падает FPS до 5-10 и помогает только альт-таб, да и то не всегда, в половине случаев вообще только рестарт сима полностью делать приходится. 2 Чиж, про Су-30СМ и т.п., да дело даже не в том, что имба/не имба. Мультироля и нормальной реализации кабины за более-менее современные самолеты, стоящие на вооружении в РФ нет. Есть или "старички" типа МиГ-21 от сторонних разработчиков, или вертолет, который вообще единственный в ветке "красных" от ED выполнен на супер уровне. В итоге летаем на "фиктивных красных", ага. Эххх.
  8. Well I just flew in multiplayer with my Quest 2 / Link and this was just amazing! I had Rift S before, but now this is another level of visual quality and clarity. 1. I have i7-8700, RTX-2070, 32 GB Ram, 2xM2 SSD. Link cable not original, just USB-3.0 to USB-C 5-meters cable. 2. My settings in DCS: texture high, water high, terrain low, MSAA off, SS off, Anyzotropic filtering max, PD default. 3. Settings over link: 90Hz, 1.7 graphic level (5408 x 2736 rendering value). Also had Encoding resolution width set to 3664 and Encoding bitrate set to 500 Mbps in Oculus Debug Tool (you can set this either in debug tool or get Oculus Tray tool Beta 0.86.8.0 which has bitrate setting for link too.) Was pretty smooth flight in multiplayer with many objects and players (4ya Syria map PVE server). The only downside was that sometimes I had small freeze for about half a second, once per 10-15 minutes though so I guess it happens.But anyway this is just amazing.
  9. UPD: Actually light correction: you can set Distortion Curvature to High instead and you'll get more PD at the center. I recomment to play with this setting to see what suits you the best though.
  10. Hey dude, help is on the way here :) Just kidding. So, what you gotta do right now is this: 1. On you PC in Oculus Home App go to "Settings - > Beta" and Enable Beta channel 2. Wait till v.23 beta software installation finished, after that goto Oculus software folder (C:\Program Files\Oculus\Support\oculus-diagnostics) and run Oculus Debug tool. 3. Set this values in tool: 3.1: Pixels per display override: 1.6 3.2: Oculus link Distorting Curvature: Low 3.3: Oculus link Encode bitrate: 500 Should look like this: Also goto https://www.gamersbynight.com/dcs-settings-vr/ and make your DCS settings according to this page. After that run DCS and see the picture ))) P.S. Sadly you'll need to set settings in Oculus Debug Tool every time when you start Oculus Home. There's Oculus Tray tool that can simplify process, but they didn't update it for V.23 yet. V.23 software provides settings for Encode Bitrate for link cable, so you can have better picture. Without it you won't get good picture yet.
  11. Placed order #4565 just now (well Happy birthday to me :) ). Hope that it will arrive at the fall of september, when I'll be back from vacation.
  12. А, ну т.е. не я один такой и значит "временные трудности" и "ждем фикса", ок, спасибо за информацию.
  13. Ребяты, другой вопрос. Никто после крайнейго (июньского) обновления в опенбете ничего странного не заметил? Такое ощущение, что что-то с графикой натворили или это у меня что-то сбросилось? Летаю в Oculus Rift S, после апдейта все МФД практически засвечены, авианосец на море неожиданно фиг рассмотришь дальше чем 10 миль, на панели перед лицом символы фиг рассмотришь, особенно когда частоты пытаешься ввести. При этом если на мфд что-то еще можно рассмотреть, когда солнце не за спиной, то на панели фиг что рассмотришь независимо от положения солнца. UPD: SS похоже действительно с освещением связано, но понять не могу, это в симе или у меня что-то сломалось... настройки все на месте, SS выставлен в Oculus Trey tool в 2.0 (2070 тянет норм).
  14. Товарищи, подскажите плз., это я дурак или миссия "Курьер" багнулась? Подвесной бак включен (Внутр.), но как сажусь у уазика - сразу кончается топливо. И еще, вдогонку, миссия "Ущелье смерти" багнулась, вертолет появляется в МиГ-27 и оба сразу взрываются.
×
×
  • Create New...