Jump to content

Midair

Members
  • Posts

    77
  • Joined

  • Last visited

Everything posted by Midair

  1. It's the worst thing of the new update for me, I play in VR, it's very unrealistic and it looks horrible. The Dot render line on the autoexe file change nothing to fix this thing.
  2. It's working now, I delete all my Reshade VR files and now I can launch DCS in MT. I didn't know Reshade was a problem for Virtual Desktop.
  3. I'm now able to launch DCS on VR only in single thread (I have to close VD streamer and restart it manually to make it works), but I'm still unable to launch the MT version in VR. dcs.log autoexec.cfg
  4. I can't launch the MT version of DCS with Virtual Desktop on my Quest 2, do you how I can do it?
  5. Update: Now it's impossible for me to fly in VR with DCS even with the single Thread.exe, I didn't change anything but DCS always launch on 2D.
  6. Hi, I just start using Virtual Desktop with my Quest 2 (my Headset is not seen by my computer with my cable link). I can launch DCS in VR on the single thread shortcut but when I try with the Bin-MT it open DCS in 2D. I had the line --force_enable_VR --force_OpenXR on the shortcut target. Any help will be much appreciate.
  7. Midair

    steerpoint 1A

    You can edit the SP 1A after creating SP 2A and select it for destination.
  8. Hi, I have a display bug with my Quest 2 only with cloudy weather. The bug has appeared for a few updates. At the start of the flight everything is normal but after a few minutes a lighter band forms in the lower part of the image and it becomes increasingly clear with graphic artifacts. I have the impression that the problem comes from the management of the shadows of the clouds. In my settings I have the shadows off, and cockpit shadows on low. My system is I9 9900k, RTX 2080, 64gb ram, SSD M2, Quest 2 via link cable. I already try a DCS repair and I have the latest NVidia driver installed. In almost clear weather I don't have the bug. Do you know how I can solve my problem?
  9. I disable the HT on the BIOS and it's better. I9 9900k, RTX2080, 64go Ram.
  10. Do you know if we will have the figther to fighter datalink in EA?
  11. That's why I refuse to buy the KA-50 BS3 and for the J8 II PP it's not a prototype, it's a project of prototype and it never flew.
  12. What's wrong with that? DCS is a flight simulator. If you want to reproduce high fidelity product why do you select a fictionnal aircraft NEVER produced? DCS is not War Thunder.
  13. How can they pretend to have accurate documentations about an aircraft that doesn't exist???
  14. The "Lacroix" installation was mount on the French Jaguar aswell. I think it's a french technician who create this for the Jaguar at the beginning.
  15. https://www.airliners.net/photo/France-Air-Force/Dassault-Mirage-F1CT/2314755/L?qsp=eJxtjbEOwjAMRP/FcwYqIEA2ujCWgR%2BwHAORShvZHqiq/jshlZjYTu%2Bd7magcTB%2B223KDAGUUegJDjIKvhTCDJiEBO/WoiZaa7vN/uR%2B4sIDy38FoTl6f3Cgo1g7lYOIxmcizsYRVt5JZPkqVqrPj7LTlMByrRm2vvCYNPdYN9gw9bAsH/A%2BPqo%3D
  16. The F1 M will be like a F1 CT without the laser range finder. Modern HUD, modern INS+GPS, CCIP, CCRP better radar performance but not the best and Air-Sea mode. But like I said before they will not have the ATLIS Pod (if Aerges want to model it like the real one).
  17. In France only the Jaguar and the Super Etendard used the ATLIS Pod and the AS 30 L. The Exocet was used by the Super Etendard and now the Rafale. The Iraki Mirage F1's were the only Mirage F1's ever wirred to carry the ATLIS Pod, the AS 30 L and the Exocet (on the EQ5/6 only).
  18. A great server but really demanding on my system especially on the Caucasus scenario. My specs are: I9 9900K@4.5ghz, 32Go DDR4, RTX2080, SSD M2 and Quest 2. When I'm flying on the frontline I have terrible stuttering and my framerate dropped. It's really difficult to fight with this condition. Is it possible to reduce the amount of units on the frontline?
  19. I manage to have a more stable experience. I set the Headset to 90HZ and put a maximum limit of 30 fps on the NVidia panel. I disabled the ASW via DebugTool and put the bitrate at 300. I'm now able to fly for hours on Blue Flag server without stuttering but on Enigma server it's less effective and I have a lot of stuttering near the frontline especially on the Caucasus scenario (I think it's a server or mission problem, to big for VR players).
  20. I just switch from a faulty Reverb G2 to a Quest 2 + link cable and I have the exact same problem. Maybe it's an Oculus bug, I don't know if the problem was there before (I also have a Rift S and never experience somthing like that so for me it's a Quest 2 problem).
  21. I have the exact same problem with my Quest 2 and link cable. I have set it to run at 90HZ and locked it to 30HZ on the OTT. I use the recommend resolution and no super sampling on OTT, I also have enable the sharpening on the OTT and the birate is set to 300. The image is crystal clear and the FPS are locked at a constant 30 fps but sometimes I have horrible stutters and the alt-tab solution help to be smooth again (not every time). The worse for me is when I fly on the Enigma server fast and low after 20 or 30 minutes the stuttering start. I test it on the Blue Flag Modern server and it remain smooth for 2 hours on my F16, it began to stutter when I land at Beslan but the Alt-Tab solved it. I really don't know where this problem come from and how to solve it.
×
×
  • Create New...