Jump to content

Qcumber

Members
 View Profile  See their activity

  • Posts

    2222

  • Joined

  • Last visited

 Content Type 

Everything posted by Qcumber

  1. Qcumber
    My QP eye tracking has suddenly stopped working. When I try to calibrate or switch it on I just get a loading screen and the app crashes. I've tried a factory reset. Currently running v74. Developer mode enabled etc. Has anyone had an issue like this?
  2. Qcumber
    I am getting some instability since the last update and freezing. With both VD and meta link.
  3. Qcumber
    Yes. I have noticed this as well. There seems to be a loss of contrast against some backgrounds. Also, severe smearing of aircraft against the ground.
  4. Qcumber
    Yes. I am seeing that too.
  5. Qcumber
    The Mariannas Lagoon Island Patrol has been my test bed for DLSS. Previous to this release there was always horrible ghosting and smearing in the sky.That is now gone. After testing a bit further I can see smearing when there is a busy background: zero flying low over Marianas trees. However, elsewhere no ghosting.
  6. Qcumber
    Thanks. This works great. A slightly easier option. In my initial testing this looks very good. Hardly any ghosting.
  7. Qcumber
    How do you activate J? I can only see ABCDEFG in DLSSTweaks. Confirmed I am using 310.1.0.0.
  8. Qcumber
    I would second that. I got my QP used (immaculate, like new) for £300. It's still a very good headset.
  9. Qcumber
    I would disagree. I've used both VD and link cable and the quality is comparable.
  10. Qcumber
    Yes. Where is WW2 stuff?
  11. Qcumber
    2 week later each year. Adds up to 2051.
  12. Qcumber
    By my reckoning the 2051 and beyond video will be in December.
  13. Qcumber
    I've tried hand tracking on the QP but never found it very useful in DCS. Very hit and miss regarding cockpit clicks and dial turning. How do you get it working well?
  14. Qcumber
    Are you referring to using a headset with a display port cable? Unfortunately this is where the cost is as they are now only on high end headsets. The Q3 is a good option but relies on a usb tether and compression/decompression of the signal. Meta link cable allows up to 960mbps so is a pretty good solution and you can use a powered cable, such as the one mentioned by Tensorial_Architect. I use a QP which is still a good option as it has eye tracking. It has been discontinued but software support remains and will for a while as it's the same software as the Q3. You can get one for a good price.
  15. Qcumber
    You can easily change all the settings in the config file or using Quad Views Companion. There is a limit with peripheral resolution as DCS does not always cope well with textures and shadows at lower resolutions.
  16. Qcumber
    With QVFR you can control the centre and periphery. The default settings are 0.5x0.5 at 1.1 times base resolution and 0.5 for the periphery. This means that 75% of the headset image is at 0.5 resolution. The only difference between fixed and dynamic is that eye tracking allows you to move the centre. As a result you can get away with a smaller centre size. I have mine set to 0.3x0.3 so 91% of my screen is at resolution 0.5. It gives me a massive performance boost.
  17. Qcumber
    I am not getting a single core maxed out either. Until this point I had thought it was an Intel thing but Moxica has an AMD CPU.
  18. Qcumber
    Sorry. "Presumption is the mother of all F*** ups". Do you see any performance gain with your CPU/GPU combination?
  19. Qcumber
    I presume you have not been using eye tracking with your QP? With QVFR enabled your CPU will be the bottleneck.
  20. Qcumber
    I have mouse recentre mapped via JoyToKey and an offset left/right so I can use headpoint. I also have a finger mouse attached to my joystick for easy mouse click and scroll. Haptufer Mini 2.4G Wireless Finger Ring Mouse Ergonomic Handheld Optical Travel Mice(Black) https://amzn.eu/d/7o5gl5i
  21. Qcumber
    Another comment on latency, and I realise this is different from that discussed in the video. I am adding it here for anyone reviewing the thread. For anyone using VD I have found that if the decode latency goes above about 12 ms I notice stutter and lag, even if the overall latency is below 40 ms. This latency is dependent on Bitrate. The maximum Bitrate I can get with WiFi is 200 Mbps. If I use an ethernet cable I can manage 400Mbps.
  22. Qcumber
    I would not worry too much about the "CPU bound" message in DCS. From what I understand this just means that you have GPU overhead and that CPU "might" be the limiting factor. There was a lot of discussion on this a while back but I can't find the thread. I used to get microstutters but now the only time I get any stutters is when the FPS drops below the refresh rate. I am not sure exactly what I did except that I went back to absolute basics, set Nvidia to default, no mods and minimal settings with OXRTK etc. Everything has been smooth for me now for awhile. It might be an AMD vs Intel thing but I doubt it.
  23. Qcumber
    Yes. CPU. A 4090 is going to remain great for a long while yet. The 5800x3d is a good CPU but is outmatched by the 4090. Go for the 9800x3d, especially if you use QVFR or plan to.
  24. Qcumber
    I had not seen that. Good call. Does it work now and does it negate the need for DLSSTweaks? Edit: just looked at the NVIDIA brief and it looks very promising.
  25. Qcumber
    @Hippo Is it worth renaming this topic to "NVIDIA 5000 series and DLSS4 for VR" or similar for a wider discussion?
×
×
  • Create New...