nikoel

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

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

Hey Team In the instant action mission Caucuses - Medium - Foothills Summer At the end of the mission, the last assignment is to contact JTAC Playboy. Long story short, no response. I believe this might be the infamous ARC210 issue I've dialed the frequency and double checked that the channel was set to AM but no response from JTAC. I also tried COM2 and COM3 just in case I had my bindings wrong. No response - I am not ruling out operator error, but I did all idiot checks with no success Track File Attached playboy aint playin.trk

Best. Day. Ever. I am so excited for Fulcrum. I remember seeing one as a little boy and it has been my favorite plane ever since. Your video brought that little boy out in me You have made my day, there was no better aircraft to develop. (Not even the 'my humps... my humps, my humps, my humps' 9.13) Don't listen to the partypoopers. They will look at a Spitfire and say with a straight face it's crap because it doesn't have AMRAMs On the down low, historically I just wish the design bureau gave us Air to Air Refueling Capabilities before the K variant Now there were 9-12 with retrofitted wing drop tanks that flew over Iraq... could reduce that 'Range Anxiety'

Holly Thread Reviving Batman Anyyyyywaaaaay. I believe there are two others threads on this same bug. Do we know where we stand on this Heatblur? We have two camps here. She is constantly undershooting under all phases of flight and it shouldn't do that, and she is constantly undershooting under all phases of flight because the devs are gods and they put the real bugs into the virtual bugs of the aircraft Putting my 5 cents into this. I am somewhere between the two. I do believe that it's not realistic to be able to go COD 360 no scope with razor point accuracy, but it doesn't make sense that under all flight parameters the calculation is reliably off by the same margin each time. With other words, a good pilot still can still COD 360 no scope as long as they aim the pipper the precise few diddles in front of the tomcatculated firing solution when they press the trigger. Thus negating the argument completely and just making the whole debacle annoying I am not an expert on DCS aircraft design, I just find it a little weird that something so vital to the module and the game is left to the side with no resolution either way, whilst the modelling of say a circuit breaker is taking a higher priority My 2c

I haven't no, I did think about it but it would be of limited benefit for me. I run a small extension cable, and have a socket on my desk. Plug the original Quest Pro AC Plug into it. Drape the cable over top of my WinWing setup which is already at neck height and I am good to go. Difficult to explain, and I don't have a photo of it at the moment but, just imagine the cable inside the little groove, between the left MFD and the UFC. When I unplug, the cable falls perfectly between them and is easy to find. Hope that makes sense. It's more of a pragmatic solution with tradeoffs that works for me, rather than win-win-win Quest Pro AC Adapter but anything will do, it doesn't matter as there is no data being put through it. Just google USB-C Magnetic Cable and take your pick. There are a few out there that light up and have RGB effects if that floats your boat

Hybrid. I use a cable with magnetic attachment when I am chillin' - then when it hits the fan pull the cable. (Then fondle for it later if I feel like it/still alive to do so) It's not perfect, but a solid compromise

I understand. FYI, I sat down with the campaign again and got up to mission 8 I did the ground checks yesterday and quit. Today I chose to skip them and go straight into the flight Took off as per normal up to Waypoint 2. Got Instructions to fly FYYTR Direct by Nellis Departure. So I skipped WP3, WP4 and went to FYYTR direct. This entire leg was done in silence at 14,000ft. When I reached FYYTR Biff finally spoke and said to turn to waypoint 6. Which I promptly did and overflew it. I then went to Waypoint 7, overflew that too by 0.5nm and entered into a right hand orbit. After three orbits I quit the mission as nothing was happening

Yes! Somehow I haven't tweaked settings and forgot I did this weeks ago. This tool is the bomb https://www.digitalcombatsimulator.com/en/files/3332882/ for that exact thing

Virtual Desktop - all the way I do specialise in dog fighting and not having a cable is revolutionary. I can now use cold war era fighters and quickly flick between the Airspeed indicator and the bandit. Where before I had to be careful as the cable could whip and upset the balance of the headset. I find it also uses less VRAM, but with my graphics cards IDGAF either way. Quadviews track faster and settings are all there, on one screen. No more going between the debug tool, the other third party taskbar tool etc... Different resolution is an interesting thing to talk about, about as you can increase it to whatever it is that you want it to be via the PD settings or OXRTK. With QuadViews and a 4090 it's actually my CPU that can struggle in complex missions with lots of things going on The best thing about Virtual Desktop is that now I just pick up the headset, double click DCS, in VR using built in hand tracking and I am set. No more of this Link BS on every update and trying to figure out why feature X is no longer working Once the settings are tweaked, the quality of the render for me is on par and in some way better than link

It could be as easy as settings. You can try with Turbo on/off. Also be careful with having turbo on in multiple places that really screws everything up. (i.e. in the toolkit and the quadviews)

You must be one of the few people who know what they are doing and are not running Virtual Desktop Give In. I have found that wireless VD over a crappy WiFi5 modem and a Ethernet Connection is better than wired link in basically every way. I can imagine a WiFi 6 connection is the next step up

Hey Guys a bit more feedback on Mission Six, Air to Air Refueling + ILS Approach I am not going to lie, she is a bit of a dog's breakfast at the moment and needs attention. A grand shame as I can clearly see that there was a lot of work that has been put into the campaign and there are a few oversights that are a really letting the entire experience down. Some of them very simple, but make a big difference Altitudes are all over the place. Some kneeboard pages state to be overhead Mormon at 18,000ft. Others state 19,000ft. During the emergency exercise Biff tells you you put in a deck of 16,000ft and then promptly tells you to make sure you doubly check that you do the simulated HYD failure at 15,000ft; below the deck. In the story however the hard deck is at 15,000ft. There are many of these instances littered across the campaign TACAN for Aerial Refueling did not work, had to use F10 Map worked everywhere else though. Probably DCS Error, not a biggie The following error happens in a lot of missions. Pre-recorded campaign ATC Says descend and maintain 5000ft. But does not provide further descent instructions afterwards, either via 'Cleared Visual Approach', or continue descent etc... thankfully when I saw the glide-slope hit the floor I promptly ignored instructions and continued the approach. ATC Finally clears you to land, but too late for a pilot who is observing instructions. This error is not a one off and appears in other missions You can really make things *a lot* easier for VR users by having the knee-board pages sequenced correctly. There are 20 pages between the frequencies and the ILS approach that is burred between all the other irrelevant approaches. This one really grinded my gears and made this whole thing really tedious Biff stops communicating when we are flying back leaving me to do the entire ILS exercise by myself without his help. Since I still get the press space messages every now and then, I believe this is an other ARC210 issue that keeps coming and going. The other missions suffer from the same issues Anyway, I am putting the entire campaign down as it's not enjoyable with the current bugs and errors in place I hope you will decide to fix it soon

I had exactly the same behaviour. I restarted the mission completely, and got the same outcome the second time through. After waypoint 2 there is no Biff, but I do get the "other" menu after a while with options to repeat etc...

For them to no longer show up you need to put them back on the cradle. aka Charging

Put cradle on desk. Plug cradle into power supply. Put Controller inside [on top?] cradle. Profit.

Nailed it on the eye-tracking assessment with the Quest Pro; it's indeed a game-changer. Although the relevance might be diminished for DCS, the QP controllers compared to the Q3's are much better The Quest 3 does feature lenses that have a similar feel, but with some compromises. It offers a higher pixel density, but falls short in terms of color gamut. The passthrough is also significantly better than the pro. The closed-in design of Q3 versus the cat-ear curtains of the Pro, boil down to personal preference. I do like the Pro for its ventilation and the ability to peek through to the real-world switches and my kneeboard. If I had to choose today, I'd likely go for a second-hand Quest Pro over a brand-new Quest 3, even if their prices are comparable. The eye-tracking polling rate might not be instantaneous, but coupled with DLAA shimmer reduction, any imperfection becomes almost indiscernible over time – similar to how I got used to the notch on a MacBook Pro. Ultimately, both are great options. The prospect of using Virtual Desktop to forgo the need for a cable connection enhances their appeal. It's definitely the point of diminishing return, you have to spend a lot more to get a bit better headset

I'll try to record a mirror and attach the video with the track I know you can only take my word for it, but the reticle for me was exactly over the bandit, especially at the end when I held the trigger for a couple of seconds

Heya We are back to rounds falling short of target once again. It's this thread, except the fix has stopped fixing, or the bug has started to bug harder The track features a few phantom locks (target lock in mid air) Shooting down the target using dragon breath technique (aka spray and pray) Flying up behind the target and shooting with both cues over the target and all 200 rounds missing Track is attached Shootin them blanks.trk

100% agreed. I have been lucky that this has not happened to me, but the forced software update thing is very apple-like But unlike apple, Meta seems to be okay Beta testing their release candidates on public releases. Trouble is that it not possible to go back to a version that worked. Nvidia often screws driver updates but at least they allow you to screen back to an earlier build Pimax just releases unfinished products with horrible build quality and QC and blames the consumer for using it wrong You get screwed either way; chose your dildo

There are people are using FSR 1.0 with VR. Some people supersample from 100% resolution using the the up-scaler for a better [to them] image DCS suffers from shimmering even with MSAA; DLSS may achieve better image quality because it uses different technology to reduce this shimmer. Activating it to increase the resolution from 100% to say 140% with similar performance and reduced shimmer would be a win to many You may be right, however without having seen what the implementation that ED has gone for, you have no idea what the image quality will actually be like

Implementation is key You can have amazing results with DLSS and you can have half baked dog's breakfast MSFS suffers from having DLSS reconstruct the entire image and the text elements especially suffer The technology is not static, and is getting better with every iteration

Hey Silhou Just wanted to quickly check in with you about this

Cant you use a descent USB Powerbank to see if it works in theory? I know it will only work as long as the powerbank has charge but it's a good way to prove the concept Also how much charge do you really need. After 3hrs in VR I am ready to go do something else anyway

Hey Matthieu Is the redundant geometry submission happening on the same thread[s]? When i am CPU limited, I notice that my CPU is not at 100%. In theory telling me that I am being bottlenecked by the utilisation of the main thread However, Varjo counterparts run higher resolutions at 90hz/90fps. We are running lower resolutions (still 1.3-1.5x supersampled) but unable to achieve 72fps under some conditions I have a high end system, 5800X3D with a 4090 and 64GB Ram, better than many of the Varjo Bourgeoisie It doesn't make sense unless there is something else at play. Do you think that there may be bottlenecks introduced by oculus somewhere?