Jump to content

Silvera

Members
  • Posts

    24
  • Joined

  • Last visited

1 Follower

Recent Profile Visitors

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

  1. I had exactly the same issue. That was only fixed when i got a new headset. I guess Quest has a flaw in design of the usb port which gets defected by time. First thing to check though if your USB root hubs are in power saving mode via device manager.
  2. oculus dash enable-disable.rar To disable it simply use the one for it. After you exit DCS use the other one to enable.
  3. I have a script disabling the oculus dash which increases performance. You may want to check that one. I don't experience the same though but oculus dash is just eating resources in the background.
  4. Can't this be implemented natively by DCS?
  5. I started having the same issue right after 2.9. Connecting EU server, having an average of 80-100ms in game. (It was same before 2.9) After 3-4 mins i get kicked out of the server due to high ping which i believe because of a ping spike (max 350 i assume). Never happened before 2.9. My location is Middle East. I have tried NA servers with the same result. The most i could think of was in game voice chat might have caused this issue.
  6. I get kicked from the server after 5 mins which never happened before 2.9
  7. Unfortunately, neither DLSS nor DLAA are usable for me compared to TAA or MSAA due to blurriness. I have Quest 2 at 90hz with maxed out in Oculus app, it so easy to spot the difference when DLSS is off. It's meant to be used in 2D not in VR in my opinion, at least for now. I am so happy for the results though with 2.9. Even TAA and MSAA gives me very smooth experience!
  8. Thanks! I was not aware such an option. Working great now.
  9. As title mentions in VR, HMCS is only rendered for the right eye and very disturbing. Was this reported before? I am sorry that i couldn't find any related topic.
  10. Beautiful explanation thanks a lot! I will try 1200 as default. I also noticed using 1200 was accurate. I was using 500 because of that bombs falling short issue. When set to 500ft my bombs were not drifted away from target and was getting better results.
  11. Thanks for the answer Fuggzy i am definitely trying that! Can anyone also enlighten me about how to use BA appropriately? Depending on what i should set it? Sometimes 500ft works perfect and bombs hit the target with explosions, sometimes there's no explotion at all and bombs go dumb. Is this somehow related to Radar Alt? How can i know if it is set correctly? I know it affects spread area but why in some missions it works and for other it does not?
  12. Here's my track file. Tried some different settings but mostly resulted in a miss. What do you think? There are so many variables that i cannot be sure of. https://www.mediafire.com/file/aw9qkqa5xk5se1h/cbu97_miss.trk/file
  13. Thanks for your suggestion Fuggzy, i was actually wondering if this might have an effect on why i miss. I am going to try this and report back. If i am dropping them with CCRP then it should be set to "0" as i will be flying level if i got it correct, right?
  14. Thanks for reply RuskyV, and yes i always set it to ELEC and i make sure PNEU disappears. I also tried to release the bombs at 20000ft - 25000ft - 30000ft and the results are all the same.
×
×
  • Create New...