Jump to content

=Garuda=

Members
  • Posts

    8
  • Joined

  • Last visited

Recent Profile Visitors

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

  1. All, I have tried Ctrl +Num1 and found it is much smoother disabling ASW for my system rather than ASW auto or Force ASW in half FPS. I am setting 72FPS as default of Meta quest 3, so OTT gave 36FPS for force ASW mode. Force ASW is OK but not smooth enough for gun fighting between P51 and FW190A8 in Channel map in instant action. I could increase PD to 1.1 without dropping much FPS disabling ASW with foveated rendering with Quality x Balanced. For my note, I just write down the Hotkeys for ASW. Ctrl+Num1 Disable ASW Ctrl+Num2 Half FPS with ASW disabled Ctrl+Num3 Half FPS with Force ASW Ctrl+Num4 Auto ASW Anyway, thank you for all who gave me advices !! Core I7-13700F 64GB RAM(DDR5-4800) RTX4070 SSD 2TB VR : Quest 3 Genuine Meta Link Cable
  2. Will try it and see what happens when I get back home next week since now I’m out of town, but thank you for the advice.
  3. 5ephir0th, yes, I wanted to try ASW disabled and also force enabled as you pointed and that’s where I had difficulty with. My Oculus Debug Tool settings and Oculus Tray Tool settings on ASW do not affect on DCS somehow despite of using as admin. I need to try with Ctrl+Num 1 hot key on Quest link application.
  4. Thank you for the advice. Sure, I tried it by FPS limiter in DCS and also Nvidia control panel at 40 and 50FPS as well. ASW still want switch back to 40FPS or 50FPS frequently causing stuttering. Setting 36 also creates stuttering. I see smooth higher FPS result with DLSS On but it is too ugly / ghosty for close gunfight with WW2 aircraft. IL2 Stalingrad VR doesn’t require DLSS and keep solid 72FPS with much higher settings. I know it is totally different sim, but I personally thought my new PC is not as bad even not as the best and will be reasonable level to market as VR user as good customer population (and IL2 works at least!) On the other hand, I also tried and got smoother result to put more load on PC with MSAA and Pixel Density 1.4 trying with initial flight for furball in Channel map. It locks 36FPS with constant ASW working, however, if you fly in P51 bluenosed bastards in Normandy, flying over Dover, ASW start switching back off and on intermittently and makes stuttering. Then when you gunfighting around bombers with 109s, you don’t have enough power to generate playable FPS because of heavy load. So I decided myself to try and find my sweet spot with DLSS off and ASW off with PD1.0 or hopefully just a bit more PD like 1.1. Core I7-13700F 64GB RAM(DDR5-4800) RTX4070 SSD 2TB VR : Quest 3 Genuine Meta Link Cable
  5. Qcumber, Thanks for your advice. I installed Oculus Tray Tool as you mentioned and tried several options including 45Hz forced, but my DCS doesn’t reflect those settings somehow.
  6. Thank you daviddrbarnette. Will try it and see if it work for my system. I suppose this might be a good option for ED to feature in DCS as MSFS has it.
  7. Hi, Recently i got new computer and started VR with Quest 3 PCVR. I am suffering with FPS fluctuation switching 72 and 36FPS every seconds resulting stuttering. It seems ASW keeps cycling work and stop. I started Oculus debug tool as admin and disable it or tried Forced 45 disabling ASW but it did not work somehow. I also tried disable ASW with Oculus Tray Tool, however FPS in DCS just keep switching 72/36 instead of gradually going down from 72 to 60, 50, 40... Is there anyway to disable ASW in DCS or any plan to have that fuction like MSFS? Thanks, Core I7-13700F 64GB RAM(DDR5-4800) RTX4070 SSD 2TB VR : Quest 3 Genuine Meta Link Cable
  8. Hi, I have just faced this difficulty and cannot proceed the mission even airborne and form up with the squadron because… When my flight leader HV-P (if I’m correct) come to runway, rev up the engine, release brake and then suddenly makes left turn to the left to 9 o’clock to the runway. he just crash into the other p47 behind me and keep going out the air base. Then the other one ahead of me also make the same thing and burn the poor p47 behind me. he says “two eject” or something. Then finally, my turn, I just take off normally but since the one behind me is burning and staying there, those behind him also start crash to him from behind one by one. I skipped mission 9 and tried mission 10. When I start engine, then 3 P47 suddenly come up from 12 o’clock with full throttle and crash through the tent on my left, the p47 in the tent, and hit my left wing. Something going crazy on my AI….is there anyone who got same problem?
×
×
  • Create New...