Jump to content

nikoel

Members
  • Posts

    448
  • Joined

  • Last visited

5 Followers

Recent Profile Visitors

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

  1. Absolutely, I completely agree with you. It's incredibly frustrating trying to engage something like a Mirage2000 on the DogFighters Server. The pipper often misaligns so much that pulling the trigger when it’s positioned right over the target feels futile since the firing solution is almost always off. I’ve stopped relying on locking altogether and have switched to manual deflection shooting because it’s simpler. When it comes to one circle fights, the F-16 is even more of a challenge as you've noted. The delay in the pipper response makes the firing solution so unpredictable that it’s hard to know where your shots will end up, let alone if they’re on target. The most reliable method I’ve found for taking down an opponent is engaging in a 2 circle fight at low altitude, focusing on funneling and pulling straight through with a good pre and after fire (without waiting for the pipper to confirm)
  2. Its a bug on all modern ED Aircraft. It started just over a year ago. You will find many reports and many fixes, but the bug is still there. Its the same with the hornet. Unfortunately it has gotten worse, lately when 2/3 times it locks more or less correctly the firing solution jumps once you get closer to the bandit. The firing solution has 2 maybe 3 jerk steps within compute as you get closer. The solution is to pray and spray, start about an aircraft length ahead of the bandit and let them pass through your firing line. Unfortunately snapshots are unreliable and often are a waste of time, unless you are a god and can compute without a lock
  3. Virtual Desktop (make sure you have a good WiFi modem and a wired connection to the said modem) You won't regret it, and there are none of those messages and everything works as the gods have intended
  4. DisplayPort is overrated. The future is wireless. Hell, the present is wireless too as far as I am concerned With Virtual Desktop we can have our cake and eat it. Zack develops a headset. Sells it at a gigantic loss hoping to recoup it through his MetaVerse bullcrap. We buy it. Purchase Virtual Desktop from the store give him the forks and Bob's ya uncle My favourite thing to do when I am dogfighting my friend is to go into rolling scissors. He has a crystal. It only takes a few revolutions and he loses every fight no matter the advantage. His wife sent me a video of him trying not to lose visual with that massive pimax headcrab on his face. It is a sight to behold and I'm trully surprised his head is still attached to his neck. That cable upsets balance and gets in the way. It's just not good - WiFi 6E modems are super fast and have very low latencies with throughput similar of USB. It's not perfect and I get a few artefacts here and there if I look for them. So I don't look for them. The only part where meta truly grinds my gears, is that they only released eye tracking via their social API. It's literally only there for social chat and this is the reason for gaze latencies. There is an other layer that is super fast; our headsets have it but we can not have it for PCVR. We could have flawless super fast DFR, but no - Aaaaaagh!
  5. Hey Wags Was great seeing you answer the questions appreciate the transparency. Especially how we as a community get to interact with developers and the team as a whole. It's not something that many other software companies do and I really appreciate it I know it's a difficult time with the current developments with a third party provider, but I very much hope it's a minor speed-bump that will be quickly moved on from where both parties are satisfied with the result Looking forward to the next video
  6. TheSlugNip™ Looks like you've put in a lot of effort slug. Love your work
  7. The reason you're getting these recommendations is because with DFR the hardware requirements to drive the headset are greatly reduced. Eye tracking is *that* good. A QuestPro with DFR can be ~40% (can't recall the exact number, dont shoot) easier to drive for the graphics card in comparison to Q2. It does come at a cost of the CPU, so it's not free - The build quality of QP is enterprise level. Stop looking for brand new and go for the second hand market. Heck, there is one floating about that I saw a week ago with a dead pixel that is dirt cheap. Still ions better than a Q2 There are no faceplate materials thus no hygiene issues. You can also just simply purchase a new comfort kit if that is such a huge issue Either way, everyone is shooting in the dark here since we do not know what your specs are
  8. Look at second hand market from reputable brands you can safely purchase used *COUGHnotpimaxCOUGH*. This how I stretched my dollar. Hell, I got a second hand 4090 for less than a new 4080 Since you're looking at cheap headsets, I am going to go out on a limb and say your hardware is low-mid end for VR FYI the hardware scale goes something like: Very Good: NVIDIA GB200 NVL72 Good: Intel 13/14th 700k / 7800X3D with a 4090 High Mid End: 5800X3D with a 3090 [Very] Mid: AMD5#### or intel eqv, 3080 - 6900XT if you like the dark-side Low End: AMD3####, intel 9th 10th 11th, 3070 Poe-Tay-To: On scale from one to even, you just won't. Won't Even All assume 32gb of Ram, NVME SSD As Qcumber said, DFR is a must. Quest Pro is the obvious choice for now, but there will be more headsets entering the market with DFR. This is especially the case if you do not have a powerful graphics card. It's much easier to push QP with a mid end system than Q3. The image quality will be miles ahead because you will be able to use the overhead for higher graphics settings. If you have a good graphics card, but a lower spec processor, Q3 is the way to go. DFR pushes processor harder. So chose wisely Second Hand QuestPro is hovering around the same price or lower as the 3; depending on where you are and how thrifty you get If those options are too exy, then the Pico4 is the only low end headset I would go for. You will be giving the CCP the colour of your boxers and all your personal info, but depending on your online habits they may already have these
  9. Disabling or going flat? Disabling seems like a massive concession to me, but what do I know. Especially since there is now flat shadow blur
  10. Does V63 also crash with Virtual Desktop? Please correct me if I am wrong, Mbucchia wrote the quadviews implementation with OpenXR in mind. Does the transition from OpenXR runtime to Oculus prevent DFR from working? Thankfully I yet to be "upgraded" and turned off updates before V63 could be installed. If you like me have been left out, go into settings, updates and turn them off for now
  11. Holy thread resurrection batman! Anyway, when I was rocking a GTX 1060Ti I was glad that someone told me with no uncertain terms that I should not spend any money on VR until I got a better PC I'm glad to have received this advice at the time Unfortunately there are gates. But those gates are the hard realities of DCS VR resource requirements - rather than the community it self. Telling a 2060 user that they should go full steam ahead is akin telling a cripple that he can run a marathon. I am sure we will find a guy on crutches there somewhere, but the vast majority will be setting themselves up for failure I agree one no longer needs the best hardware out there to run VR. A 4070 will do the job nicely for instance. But a 2060...?! This aint it chief
  12. I believe your spicy hot take would have gotten a more receptive response had you used the term 'Frame Timing'. This is one of the primary reasons VR overlays—be it fpsVR, OpenXR Toolkit, etc.—prioritize showing you frame-time graphs, with an FPS figure secondary. Frame delivery matters. Of course, this has its limits. If you're rendering at 100-250fps on a headset set to a refresh rate of 72Hz, it's highly unlikely you'll be impacted. But I digress The FPS value has correlation with the smoothness of the experience through frametimes. For example, if your frame delivery consistently hits 75fps at 13.3ms on a 90Hz refresh rate, the experience won't be pleasant; you'll encounter screen tearing. This happened to me when I upgraded from a 3900X to a 5800X3D. My FPS jumped from 45 to approximately 65 (forgive me, I can't recall the exact number), and the experience was horrendous. I thought, "What the heck did I upgrade for?" Because WMR only supported motion reprojection, I used Manual Reprojection, locking the game at 45fps in AMD Adrenaline. Because of the way AMD handles locking frame rates, this resulted in a consistent frame delivery of 22.2ms. This ensured the render of two identical frames for every two refresh cycles, resolving the issue at the cost of blurring fast-moving objects. This is particularly relevant for fast-moving objects, as you've pointed out The best experience for a G2 at 90Hz would be a GPU/CPU frame graph that does not exceed 11.1ms—this means that the frames are consistently delivered at or within the refresh cycle. Some people might be wondering right now, isn't this just a fancy way of saying 90FPS? Yes, but no! This is all because of frame time delivery! An experience at 90FPS at a constant 11ms frame timing is night and day difference compared to 89 frames which are all delivered for half a second, and 1 frame for the other 500ms. But both average out to 90fps An interesting fact: the reason we use 120Hz and 144Hz screens is that many movies are filmed at 24FPS, which helps avoid screen tearing.
  13. Virtual Desktop is being developed for the VisionPro so it's only a matter of time until DCS is running on this headset
×
×
  • Create New...