Jump to content

nikoel

Members
  • Posts

    441
  • Joined

  • Last visited

Everything posted by nikoel

  1. 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
  2. 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
  3. 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
  4. 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
  5. 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
  6. 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.
  7. Virtual Desktop is being developed for the VisionPro so it's only a matter of time until DCS is running on this headset
  8. Thanks. That makes sense Yeah, you’re right. I was expecting the SAMs to engage at will and wanted to practice getting shot at Then try to use terrain masking whilst simultaneously engaging an enemy force. I did initially follow the waypoints as laid out on the TADs but when they did not engage decided to investigate further All the best
  9. DLAA all the way, no comparison My number one annoyance with DCS was the shimmering. Especially around towns and cities. I don't mind a few jaggies here and there, but DCS was on an other level. DLAA makes this a thing of the past. Whilst you can't quite get the sharpness of MSAA, its truly a massive improvement. Like yourself I use DFR with Quest Pro and it looks great There is ghosting, but on the newest DLSS release its reduced by a lot and it's a non issue. Especially for those of us who can remember the times where we couldn't get the FPS above the refreshrate of the headset. VR has moved in strides and I can not wait to see what Vulkan will bring
  10. I will chime in. George is a gumby, no questions. He be learnin' tho. My gut feeling is that at least partially the root of the problem is that the Vortex Ring State is over-exaggerated/modeled. It's in the same bucket as the current implementation of Tail Rotor Roll and the vaseline-coated tyres I will preface this by saying I've never flown an Apache in real life, but I have flown many other helicopters. When we teach the Vortex Ring State, it can be at times difficult to even get properly into. We often pick calmer days to give us the best chance of success (successful failure?) and even once inside, the aircraft can often get out of the situation automatically because of a random wind gust as you descend through flight levels. This, of course, usually happens just as you hand the controls over to the student. The hazardous condition is less of a on-off switch, more of a clutch, or a gradual lever. The Apache becomes akin to an Ornithopter from Dune with its wings folded. Minimal onset, minimal shuddering, just an express elevator to the ground level, you're a passenger now, Yeeee-Haaaaw In addition to the above, there needs to be a certain amount of randomness introduced, the odds of getting in (and out) adjusted, especially in missions with wind. Additions: We can't feel our stomachs being left behind, so I believe it's important to introduce sound. The more junk there is, the more the helicopter sounds like a rattlesnake. Apache got juuuunk, should sound like one of those Indian belly dancers covered in cymbals. In my experience I see a lot more random pitching and yawing too Maybe real Apache Pilots can chime into this and prove what I have experienced so far in other aircraft does not apply to this bird
  11. I believe the issue might be that you haven't selected the "Pass face-tracking to PC" option in the Virtual Desktop VR menu settings. (I am paraphrasing the name, not in front of my PC right now) Mine unticked when I updated to the latest VD Build
  12. Hey Team Hope someone can have a look at the issue I had during one of the default missions that comes with the AH64. The SAMs never engage or try to lock me or my wingman during the Nevada mission 'SAM Evasion". Even in direct line of sight. I flew directly at one at the end with no response. Maybe an activation trigger somehow broke? P.S. I got the audio through the comms that the SAM Site has become active Track File Attached All the best, ah64D Sam Ev .trk
  13. Hey Folks Short and sweet. The firing range missions for the AH64D as well as the hot startup and cold startup etc… should have the FCR enabled I’ve caught myself doing the missions in prep of practicing the new radar, only to discover it was not installed so had to make my own
  14. Yaaaah! They are Excellent! They need a weaker spring though. The one that comes with the pedals is perfect for warbirds There is a slight cam action through neutral Apart from that very good. Quality looks to be getting better with each new product Winwing releases, but they always leave one or two problems as if on purpose Like the squishy yet stiff MIP buttons
  15. Yes, the issue was with the MGRS coordinate 38T in one of the missions. My main challenge was the lack of direct references to 38T within the mission itself—I scrutinized the message transcripts and the kneeboard but found no mention. The need to switch from 37T to another coordinate isn't the issue; the problem lies in the absence of any hint to try 38T unless the player recalls its use from a previous mission. Even you seemed uncertain whether it was 38T or 38Y, illustrating my point: it's possible to fail the mission due to this ambiguity, which could even trip up the creator of the campaign. Regarding Mission 21, whenever I commanded my wingman to target ground units—be it a general command or a more specific target—he opted for the most over-the-top weapon, leading to the unintended destruction of the critical building. This happened on two occasions: the first, a direct order to attack ground targets, resulted in immediate demolition. On a subsequent attempt, even a more precise directive failed to prevent collateral damage from nearby strikes due to splash damage I understand the intent to mirror real-life aviation's often monotonous reality, especially the stretches of silence during cruise on autopilot. However, my pursuit of DCS campaigns aims to escape this real life tedium I get during the day, not replicate it. While striving for realism is commendable, I believe incorporating the types of conversations I mentioned could enrich the experience. Offering players something akin to an "audiobook" during these quieter moments could maintain engagement without sacrificing the campaign's authenticity even though you're right, naval instructors are a side of cardboard with a mains of wetbix dry
  16. I'm in Brissie and only checked in at 13:00. This darn duck weather made my flight late and I missed out, ah well I bet mine will be still the first to arrive. [Fast] International shipping has been faster than domestic lately
  17. Missed out on the Aus stock. So, I bought from the world-wide store $149.00 Freedom Eagles for just the delivery Oh... My butt-cheeks
  18. I have just finished the campaign. First of all, TLDR: Buy it. It has been created with a lot of love and attention to detail. Baltic Dragon can hold its head up high as one of the best campaign designers in DCS. I am considering buying the Mirage mostly because of the numerous missions/campaigns created by BD. It's a masterpiece. This campaign will be a lot better once the DCS Save Game feature is added to the OpenBeta. There are bugs, but they are not game-breaking. Due to the complexity of the missions and DCS's habit of releasing updates that break things, issues are expected. These are usually trigger issues where there are numerous transmissions at once or timing mismatches. There are DCS bugs that BD cannot do anything about, which forced me to restart a few times. That's just part of the game we play, and I accept it for what it is. A bit off topic, but in my opinion, The Iron Flag campaign is a much higher priority. It needs a rework post-ARC210 update much more, as this is where the customer is paying for audio that is supposed to be instructional and it's missing a lot of the time. The campaign stumbles in the first two or three missions - sorry, I can't recall exactly, as they are a chore. It tries to gently introduce the player to the situation at play, which wouldn't be so bad, except this introduction is several hours long. For people who want to sit down and have fun, those missions just aren't it. My advice to players, unless you enjoy MSFS2020 with occasional voiceovers, is to read the briefs and then skip them. Once the missions finally start, they are exciting, well-scripted, and offer a good challenge. I only skipped two missions, which in my eyes are either bugged or poorly implemented. One of them is due to a mission design issue (MGRS coordinate related) and the other due to mission triggers. All missions (post-introduction) are great and diverse. They are not just repetitive tasks. However, Mission 20 is a masterpiece. It stands in a tier of its own. I replayed it three times as it was so much fun. I wished it was more challenging, but I am sure there are people who would wish for the opposite. P.S. No one in the history of mankind would fire a flare in full IMC conditions during the day and expect anyone to see it - for anyone reading, use the RWR as your "flare". You'll understand when you play it. Mission 21. BD, mate. Why would you give the player a wingman who will make you fail the mission? The house is manufactured by Evergrande, not up to code, and is likely made out of straw. I know you try to warn the player that the wingman has a temperament, but you really are setting the player up for failure as the first missile fired by him which hits somewhere this side of the galaxy will destroy the house. I recommend you modify the mission to give your wingman some kind of failure where he has to jettison all his weapons, or can't fire them. When I read the kneeboard, I expected my wingman to somehow defect to the enemy and give me a dogfight, not make me restart an hour into the mission. Anyway, these criticisms might sound harsh. And they really are. With beautifully designed and complex missions, there are more chances of something going wrong because of some DCS bug. I do not want to understate how good this campaign is. Bravo, BD P.S. No pilot in the history of piloting talks about scenery this much. If you ever make another campaign, I would recommend eliminating this filler dialogue and making pilots talk about a recent failure and how they overcame it, or an alternative way they used XYZ weapon, or some other interesting feature of the plane, or why TSL is not used anymore, or how they used the Avenger to open their beer bottle. How they emberassed themselves by broadcasting on the new ARC radio on the FM frequency and getting roasted by their squadron. You have obviously studied the manual a lot and know so much, why not put it to good use? Thanks again for all the hard work
  19. Heya This thread is a few months old but is literally what you're asking. The G2 Owners (I was one of) upgrading to QuestPro If you have 20min watch this video as well: Finally many of us have moved on to Virtual Desktop. This gives me the same image quality as cable but with WiFi (Good router is needed for this), so no cable and is revolutionary for dogfighting and just overall headset balance Honourable mention goes to Bigscreen Beyond and [less honourable] goes to Pimax Crystal. Varjo XR4 is what you're truly after but don't do it to yourself; a divorce will surely follow Quest 3 is also a good consideration. Does a few things better than the Pro, but for DCS only I still think Pro wins out mainly because of the efforts of one man who gave us QuadViews (Eye tracking dynamic res). The design and build quality is superior and so are colours. Everything else, including the resolution Quest 3 is better If you go for the Pro, just pay the little bit extra for the aftermarket comfort kit. It's good.
  20. Here is something I would consider as better - hand tracked passthrough, Works for Quest 3 and Pico I believe https://eurekaworks.booth.pm/items/5174163
  21. Totally understand Can you add to the list that Mission 16 has a potentially mission breaking oversight Anchor Waypoint 3 is MGRS 37T ###### ###### When you're talking to pre-recorded JTAC The radio calls omit first set of coordinates and give you 6 digits. When you are talking to DCS Default JTAC, he too omits the first set of coordinates. So using the lessons from Iron Flag I created the new waypoint. The 37T gets carried over. However this sends you in the completely wrong direction. It took me a minute to figure this out and through past experiences and memory try 38T. This worked. However before I could even get to AO the mission failed so I had to restart from scatch, this is almost an hour into the mission, which is frustrating. I checked message log to see if I missed '38T' in any of the broadcasts but I did not find this to be the case
  22. Thanks mate I know it's been tough with the ARC changes. It goes without saying but I am not ruling out user error The track is my second play though. On the first it broke. I believe this is because learned the hard way that I can not have 30.00FM and 40.4FM tuned at the same time (we can do this with the ARC210 + the old FM Box). So in my original playthough the mission broke completely by having both two digit FM frequencies up on the two seperate comms. I got a lot of transmissions all at once and then nothing Not sure if it matters, but I always use pre-programmed presets entered manually at the start via the left MFD. But I am sure you saw this at the start of mission (P.S. A suggestion - if you want to eliminate the AM/FM bug reports I would recommend having the presets pre-filled for all the missions)
  23. Hello BD, I'm currently on Mission 15, and I've encountered a few issues. When entering the AO and engaging in combat, there are instances where 3, possibly 4, transmissions overlap each other. Also, the mission instructs to call in the helicopter crew once the AO is deemed clear. I do this when I believe all enemies are eliminated. However, subsequent communications with Overlord then instruct to call for rescue, which I have already done by that point. There's a minor yet confusing aspect as well. During the coordination for the first two targets, AA and Manpad, it's mentioned that we should engage these targets and then contact Springfield. But the game requires contacting Springfield first. Additionally, after clearing the AO and reconfirming by directing my wingman to attack ground targets (to which I receive a negative response), and performing several low passes, the helicopter still gets shot down by a ground vehicle. I suspect this vehicle may have spawned in between these actions, or it somehow doesn't engage with me. In response, the helicopter starts taking fire, and I attempt a risky maneuver to locate the shooter, hoping it will target me instead. I suspect the attacker might be a BTR, which gives him the ungodly sniper powers that DCS creators have bestowed these types of vehicles It seems there are some irregularities with triggers and timing in this mission. I've attached the trackfile for reference Mission 15 CF.trk
  24. You know, we can simply have the pilot model black out at >9G, and everyone will be unhappy enough to be happy. Alternatively, if you really want to go banananananas, create a slight 'fatigue blur/chromatic aberration' effect afterwards for a few seconds. If you really want to piss everyone off, then the 'Mario Maker Drunk effect' should be perfect. The aircraft is still intact, but the unholy, the weak, the desperate, and the devilish forces of the paddle will be kept at bay
×
×
  • Create New...