Jump to content

Fisu_MAD

Members
  • Posts

    296
  • Joined

  • Last visited

Everything posted by Fisu_MAD

  1. I have uninstalled QFVR and I do not have OpenXRToolkit running. Doing tests and comparisons with the latest update. I am not using OXRTK at any time, I directly modify the resolution on the Quest Pro. Before the Update, QFVR worked well, but with 2.9 I have observed many stutters, which after uninstalling, have disappeared. Still, if it worked correctly it would be a good point to give performance a boost with 2.9.
  2. I don't know what GPU you have or CPU, but the best results have been with Airlink (100mbs), and connecting the device to 18w charger to play infinitely. My specifications: nvidia rtx 3080 ti CPU: intel i9 13900k RAM: 64 6200Mhz In the OTT app I have created a profile for DCS. Default SS = 0 Default ASW = auto Adaptive GPU scaling = on Fov: 0.7 & 0.77 CPU Priority: High Detection: WMI Screen Mirror: 0 .... OVR Server priority: realtime ... Note: (...) default values. In the profile window, change the desktop resolution to something like 1980 x 1080 or less (this for me changes a lot of FPS improvement) The AirLink part: Distortion Curvature: low Enc. resolution: 3600 ( changed with ODT - oculus debug tool) Encode bitrate:0 Encode dynamic bitrate: Default Dynamic Bitrate max: 0 Sharp: enable I load the OTT application manually, nothing about activating it on Windows loading. This in Windows 11 did not activate the trigger to change the resolution. In the Oculus app on your desktop. Multiplier to 1.3 (5408x2736) DCS. PD 1.0 OpenXR. NIS : 100% size : 20% sharp Fixed Foveated Rendering: OFF Turbo: Off Also i have installed: https://github.com/mbucchia/OpenXR-Eye-Trackers/wiki https://github.com/mbucchia/Quad-Views-Foveated/releases (important if you previously install OpenXR see the steps for a clean config) Reading this thread, using different SS (0.9~1.1 in the oculus app, 1.0~1.6 in OTT, 1.0~1.3 in DCS, the only thing it causes is a greater workload on the processor and GPU, because the increases and reductions have to be made) causes the performance hit. Better to let the desktop Oculus App and the device do their job. This is what has worked for me, now with the 12 RAM of the GPU I can handle things at high speed. In missions with a large number of units I have had to lower the terrain to low. Let me know if the test helped you.
  3. Maybe something was configured incorrectly yesterday when I was trying to start DCS in server maintenance. The full window and resolution options are as they should be. Now when I start the session in MT with Oculus, it always does it in a window. Fine if it has nothing to do with QFR
  4. The installation forces the screen to window?, or is it me, my installation. Before the installation of the program, I could see the VR mirror in full screen (3840x2160), now it is only available in a window of about 1920x1080px or less when I start DCS. Followed all the steps in the guide (https://github.com/mbucchia/Quad-Views-Foveated/wiki)
  5. Doesn't load, steamVR + MT = CTD
  6. Why not give some support to OPENXR, it was promised long ago that ED would work on improving the VR experience, but every time there is a graphical update, VR users are penalized without. Now in STEAMVR the experience is terrible.
  7. VRK gets a lot of system VR resources to work. Its outdated long time ago. Abandoneware.
  8. mmmmm, thum option press dont work as spected. When you choose the thumb option some times the pointer appear, and only works this way. Then playing with the options some times thumbs press works @BIGNEWY
  9. New update, in spanish of course (https://en.wikipedia.org/wiki/List_of_languages_by_number_of_native_speakers) If you dont understand, sorry, maybe its time to learn a bit XD. Feliz Navidad!
  10. If you have any other setting that matches within the specific profile of the module, the UI execution is prepended, which causes that the assignment does not work, and more if you combine it with a modifier.
  11. Right now it is not very usable. In the F16 you can eject the dome, in the 18 you can lower the landing gear. There is no precision in pressing and I flick whatever switch is around. The rotaries are impossible to operate without pressing any element. Come on, this need a lot of love. Right now it has a lot of potential, but it is 0 usable. VA por ti Dis XD
  12. I already have mine. I could not resist. The truth is.... I am impressed and not disappointed to be one of the first iterations in the implementation. The integration of course has to improve enormously, but as BIGNEWY has said, it is in the early stages. I have been able to start the F18C (with some other problem), but the handling of the MFDs and their buttons deserves it. Love it! Here first video demo XD:
  13. Yes, if you put anothe plane , example F18, you will get a F18 in spare parts
  14. But no map in kneeboard like have in PG or Caucasus.
  15. Yes, coords lossed in undesignate press. No make sense have. Now we have only one store coord, when the TPOD is on, you can fire, then move, fire, move,.... but TOO storage is useless, bug?? y think yes. Before we can store coords.
  16. Yes, this bug is here from the start, i hope can be fixed as son as possible, very anoying to use the global kneeboard to add the charts. If you load nevada, you have also the syria ones.
  17. Thank you so much, awesome app!! looks cool! THX.
×
×
  • Create New...