Jump to content

Loki 1-1

Members
  • Content Count

    10
  • Joined

  • Last visited

About Loki 1-1

  • Rank
    Junior Member

Recent Profile Visitors

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

  1. Perhaps the fact that the 3090 has 24 gb ram memory vs 10 for the 3080 has an affect on the results. I have the 3080 aswell and will do some VR benchmarks this week. Will post back when done.
  2. Thank you for the update, I will have to try this. If the "chrashes" keep happening please update us so we know.
  3. Thanks, I will try launching my apps in different orders and see if that affects the issue.
  4. There is also the issue of the framerate dropping / screen tearing after some time in a mission in VR. I just experienced this again and it happened in the Syria map the same way twice. Events unfolding: Take of in Syria, fly up to flir bombing altidude (14.000-30.000 feet) stay there practising for about 30 min. On my way down to land the screen starts tearing and the head turning becomes janky. Stayed this way until I landed and logged out of the server. Same thing happened twice now. It could be connected with staying at high altitude for some time then as you get closer to the
  5. I will second this. The amount of units (AI) in the multiplayer server seems like it affects the possibility of this crash happening. With greater numbers meaning greater chance of it happening.
  6. I have a thrid party cable of good quality. I have tried reducing the resolution = lowering the bandwidth, and it does nothing. I do not think the cable is the problem. Thank you, to reproduce it this time I used the Swedish multiplayer server RedMed (you can find it if you search RedMed) and tried to go in to the F10 map. I have attached the Log. The bug happened at the start of the 10:40 mark, around 20 seconds after the kick out I was able to reconnect the headset to the computer and then I just had the black screen. I glanced at my flatscreen monitor, logged out o
  7. I have been fighting with this bug / issue for weeks now. It has gotten so bad that I am holding off buying the Viper that I would like to buy. I also made a bug post about it you can find it below. In the post I detail how I can reproduce it 100%. Very prominent in multiplayer servers with a lot of Units. Almost never in singel player. I have read this whole thread and it seems like @BIGNEWYhave not been able to reporduce it. I ask you to please read my post. Run quite abit of supersampling (in oculus link I use the max supersampling allowed to get the crispest picture), Use a Reverb G2 Or Qu
  8. I am having this issue alot right now with the Q2 and link. This really needs to be adressed. It is frustrating that we don't know if it is DCS or Oculus software that is the issue.
  9. Computer, 10700k, 3080, 32 gb ddr4 ram VR: Quest 2 via link, Standalone launched with DCS Updater Utility So this is about the F10 VR "crash". I write "crash" because it is not really a game crash per say. What happens is that you get kicked out of VR and the game continues to work in the background. For me on the Quest 2 it kicks me out to the home screen and then I can connect back to the PC but I cannot get back to the VR view in the game. The game is running in the background and I can glance at my flatscreen and control the game but my headset is black. Things I have
×
×
  • Create New...